Supported Blockchains and Currencies

Introduction to Blockchains and Currencies

If you are unfamiliar with blockchain concepts, a blockchain can be described as a distributed ledger that records a sequence of actions. It is maintained and synchronized across multiple computers connected through the Internet. Visualize it as a decentralized database where participants in the network record their transactions according to predefined rules to prevent fraudulent or dishonest actions. Notable examples of blockchains include Bitcoin and Ethereum.

Typically, a blockchain supports one or more cryptocurrencies, often known as tokens. These tokens can represent value and are sometimes interchangeably referred to as currencies. In most cases, a blockchain hosts a native currency and may include additional tokens or currencies on the same chain. For instance, the Ethereum blockchain supports its native currency, Ethereum (ETH), alongside various tokens such as USDC and EURC. To streamline compatibility and interaction between different tokens, many adhere to a technical standard known as ERC-20.

It is worth noting that occasionally, a single currency can be available on multiple blockchains, expanding its reach and versatility.

Supported Blockchains and Currencies

Programmable Wallets support the Avalanche, Ethereum, and Polygon blockchains.

Supporting additional EVM blockchains

If you have a requirement where you need a consistent wallet address across multiple EVM chains, ensuring a direct mapping between the addresses on different chains, our wallet creation APIs can support this functionality. This means that when you create a wallet address on one EVM chain, you can replicate and map the same address to another EVM chain seamlessly. This 1-to-1 mapping ensures that the wallet address remains consistent and easily identifiable across the different chains you are utilizing.

• For user-controlled wallets, you can achieve this by sending an API request using the POST /user/wallets. Make sure to include the same X-User-Token in the header for authentication. In the request body, specify the new blockchain(s) you want to associate with the wallet(s) by including them in the blockchains field. The existing EVM wallet address will be used by default to create the wallet(s) on the newly specified blockchain(s), ensuring consistency across chains.
• For developer-controlled wallets, you can achieve this by sending an API request using the POST /developer/wallets endpoint. Include the same walletSetId that was used for previously created wallets on another EVM chain. To ensure consistency, provide the same count value as the number of wallets currently associated with the walletSetId. If you need to obtain the count for a specific walletSetId, you can send an API request to GET /wallets?walletSetId=<ID> and include the walletSetId as a query parameter.