API Reference

Tokens

Create and run your own tokens. RoxCustody deploys the contract from a vault wallet, keeps the keys in custody and signs every later operation. Templates. Create Token from Template deploys an audited contract template: • erc20-v1 (standard ERC20): a fungible token. You choose its capabilities at creation (canMint, canBurn, canPause). • erc721-v1 (standard ERC721): an NFT collection. Each NFT is minted later with its own metadata. • erc3643-v1 (standard ERC3643): a permissioned security token (T-REX). Only addresses verified in your ERC-3643 identity registry can hold it, and agents can freeze, force-transfer and recover balances. It starts paused. • title-fraction-v1 (standard ERC3643): an ERC-3643 token backed by a TradeTrust title. The title is handed to the token, then split into fractions; holding every fraction lets you redeem the title. Create Token (v1) is the original flow for plain ERC-20 and Solana tokens. Deployment is asynchronous: the token comes back with status PENDING and moves to DEPLOYED once the contract is on-chain (or REVERTED, INSUFFICIENT_GAS, ERROR or NONCE_TOO_LOW). Follow it with the token_created_with_asset webhook or Get Token by ID. Once deployed, the token is also an asset (assetId): wallets of that asset hold it. Roles. The owner (OWNER role) is the wallet set at creation. ERC-3643 tokens also have agents (AGENT role), added and removed by the owner; the owner starts as the first agent. Get Token Roles lists who holds which role, and each operation says which role signs it. Fees. The deployment fee is paid by the vault's gas station wallets, by payerPublicAddress when given, or from your corporate balance when the vault is gasless.
Tokens
v1 (Solana)

Was this page helpful?