@cardstack/cardpay-sdk

cardpay-sdk

This is a package that provides an SDK to use the Cardpay protocol. The SDK is divided into two main parts currently Cardpay and Champer. See here for full documentation

Champer

Champer is the newer part of the SDK that interact with our safe modules.

• ScheduledPaymentModule: Allows a safe to schedule a payment. See module here
• ClaimSettlementModule: Allows a safe to create claims and allow others to claim from it. See module here

Cardpay

Cardpay is the older part of the SDK that interact with our protocol smart contracts and token bridge.

• Assets: Utility to query native and ERC20 token balances

• Safes: Utility to query safes in our protocol

• LayerOneOracle: Utility to get the current exchange rates in USD and ETH on layer 1

• LayerTwoOracle: Utility get the current exchange rates in USD and ETH on layer 2

• TokenBridgeForeignSide: Interact with the foreign-side bridge ie the bridge contract receiving the tokens on layer 1

• TokenBridgeHomeSide: Interact with the home-side bridge ie the bridge contract minting the tokens on layer 2

• PrepaidCard: Create and interact with prepaid cards that are used to pay merchants

• RevenuePool: Register merchants and claim revenue

• PrepaidCardMarket: Provision prepaid cards to people who buy them

• PrepaidCardMarketV2: Similar as PrepaidCardMarket but using updated v2 pattern where prepaid cards are provisioned before being created

• RewardManager: Register and manage reward program

• RewardPool: Submit rewards with merkle roots and claim rewards as a user

Installation

yarn add @cardstack/cardpay-sdk

Usage

yarn add @cardstack/cardpay-sdk@1.0.47 ethers@5.7.2 node-fetch@2.6.1

import fetch from "node-fetch";
import { getSDK, JsonRpcProvider } from "@cardstack/cardpay-sdk";
import { Wallet } from "ethers";

//@ts-ignore polyfilling fetch
global.fetch = fetch;

(async () => {
  const mnemonic =
    "<Your mnemonic>";
  const signer = Wallet.fromMnemonic(mnemonic);
  const rpcUrl = "https://eth-goerli.public.blastapi.io";
  const networkId = 5; // 5 for goerli
  const ethersProvider = new JsonRpcProvider(rpcUrl, networkId);
  const scheduledPaymentModule = await getSDK(
    "ScheduledPaymentModule",
    ethersProvider,
    signer
  );
  const { safeAddress } =
    await scheduledPaymentModule.createSafeWithModuleAndGuard(
      undefined,
      undefined,
      { from: signer.address }
    );
  console.log(`Your new safe ${safeAddress} has been created`);
})();

Special Considerations

One item to note that all token amounts that are provided to the API must strings and be in native units of the token (usually wei) unless otherwise noted. All token amounts returned by the API will also be in native units (again, this usually means wei). You can use Web3.utils.toWei() and Web3.utils.fromWei() to convert to and from units of wei. Because ethereum numbers can be so large, it is unsafe to represent these natively in Javascript, and in fact it is very common for a smart contract to return numbers that are simply too large to be represented natively in Javascript. For this reason, within Javascript the only safe way to natively handle numbers coming from Ethereum is as a string. If you need to perform math on a number coming from Ethereum use the BigNumber feature of the ethers library.