Skip to content
FSCO Docs

Asset

Overview

Section titled “Overview”

The Asset module provides everything you need to mint, transfer, approve, and manage tokens onchain — whether they’re fungible (ERC20), non-fungible (ERC721), or multi-token (ERC1155, coming soon). It abstracts contract interaction and enforces consistency across wallets, deployments, and chains.

Key Features

Section titled “Key Features”
  • ERC20 Support: Mint, transfer, approve, burn, and fetch balances for fungible tokens
  • ERC721 Support: Mint, transfer, approve, burn, and fetch NFT metadata and ownership
  • ERC1155 Support (Coming Soon): Multi-token standard for batch mints and game-like assets
  • Collection Management: Define ERC721 metadata schemas via structured collections
  • Cross-Chain Ready: Supports assets across any EVM-compatible deployment
  • Direct Metadata Access: Pull metadata by asset ID or token ID
  • Batch Balance Lookups: Fetch balances across many wallets or deployments in one call

How It Works

Section titled “How It Works”

ERC20 Tokens

Section titled “ERC20 Tokens”

ERC20 tokens are managed via deployment IDs. FSCO handles minting, burning, and transfers through signed requests using your wallet ID.

ERC721 Tokens (NFTs)

Section titled “ERC721 Tokens (NFTs)”

Each NFT is part of a collection, which defines the metadata schema. Minting requires linking to the collection and providing metadata that matches.

Coming Soon

Section titled “Coming Soon”
  • ERC1155 Support: Batch minting and transfer for multi-token scenarios

Common Use Cases

Section titled “Common Use Cases”
  • Stablecoin & Utility Token Issuance: Manage ERC20s with full custody integration
  • NFT Marketplace: Mint and transfer ERC721s with collection-level control
  • Game & Loyalty Assets: Future-proof with ERC1155 support (coming soon)
  • Enterprise Tokenization: Use structured metadata and on-chain traceability
  • Multi-chain Deployed Assets: Same token contract logic across multiple chains

Best Practices

Section titled “Best Practices”
  • Always store contractDeploymentId per asset type
  • Use collections for NFT metadata standardization
  • Retrieve balances and metadata through API instead of RPC
  • For ERC20 approvals, clear allowances when no longer needed
  • Use descriptive collection names to improve traceability

Limitations

Section titled “Limitations”
  • ERC1155 is not yet supported (launching soon)
  • Requires pre-deployed contracts (via Contract module)
  • Metadata must match the schema defined by the collection (for ERC721)