Tokens
Iyrs supports most poppular tokens for paying for uploads.
Mainnet tokens
On Nodes 1 and 2 can pay for uploads in any of these tokens:
| Token / Blockchain | Token | Parameter Value | Irys Support | WebIrys Support |
|---|---|---|---|---|
| Aptos | APT | aptos | yes | yes |
| Algorand | ALGO | algorand | yes | no |
| Arbitrum | ETH | arbitrum | yes | yes |
| Arweave | AR | arweave | yes | no |
| Avalanche C-Chain | AVAX | avalanche | yes | yes |
| Binance Coin | BNB | bnb | yes | yes |
| Boba | BOBA | boba | yes | yes |
| Boba-eth | ETH | boba-eth | yes | yes |
| Chainlink | LINK | chainlink | yes | yes |
| Ethereum | ETH | ethereum | yes | yes |
| Base Ethereum | ETH | base-eth | yes | yes |
| Linea Ethereum | ETH | linea-eth | yes | yes |
| Scroll Ethereum | ETH | scroll-eth | yes | yes |
| Fantom | FTM | fantom | yes | yes |
| IoTeX | IoTeX | iotex | yes | yes |
| Near | NEAR | near | yes | yes |
| Polygon | MATIC | matic | yes | yes |
| Solana | SOL | solana | yes | yes |
| USDC (on Ethereum) | USDC | usdc-eth | yes | yes |
| USDC (on Polygon) | USDC | usdc-polygon | yes | yes |
Specifying token
To use a different token, link your private key and supply the token name when creating a new Irys object. The accepted values for token are listed in the third column of the tables above.
Example:
const getIrys = async () => {
const network = "mainnet";
// Optional RPC URL
const providerUrl = "";
const token = "ethereum";
const irys = new Irys({
network, // "mainnet"
token, // Token used for payment
key: process.env.PRIVATE_KEY, // ETH or SOL private key
config: { providerUrl }, // Optional RPC URL
});
return irys;
};