Documentation
Tokenization
The eight-step issuance flow and the gates between the steps.
The flow
- Select an asset — a token is always issued against an asset record, never standalone.
- Verify — run the validation engine and record the asset state at the moment of issuance.
- Structure — supply, mint and burn policy, transfer restrictions, roles and redemption.
- Compliance — review the recorded compliance position. Deployment is blocked unless it is approved.
- Review — the complete deployment summary, including what cannot be changed later.
- Deploy — simulate, confirm, then sign in your own wallet.
- Verify the contract — guided Blockscout source verification.
- Complete — contract address, explorer links and verification status.
Deployment gates
Deployment targets Robinhood Chain Testnet (chain ID 46630) by default. Robinhood Chain requires a separate, explicit acknowledgement in the interface, and confirmMainnet: true over the API.
- The compliance review must be approved internally, or the request fails with compliance_review_required.
- The asset must not already have a deployment on the target network.
- The transaction is simulated first. A deployment that would revert never reaches your wallet.
- The deployer balance must cover the estimated gas, or the simulation says so before you sign.
AssetForge never holds a private key and never broadcasts on your behalf. The deploy endpoint returns an unsigned transaction for you to sign in your own wallet or with your own deployer key.