Token Configuration
Guide for configuring tokens in BuilderKit flows.
Token Configuration
BuilderKit flows require proper token configuration to function correctly. This guide explains the required fields for different token configurations.
Basic Token Structure
All tokens in BuilderKit share a common base structure with these required fields:
ICTT Token Fields
ICTT tokens extend the base structure with additional fields for cross-chain functionality:
Field Requirements
Base Token Fields
address
: Must be a valid contract address or "native"name
: Should be human-readablesymbol
: Should match the token's trading symboldecimals
: Must match the token's contract configurationchain_id
: Must be a valid chain ID
ICTT-Specific Fields
supports_ictt
: Required for ICTT functionalitytransferer
: Required if token supports ICTTis_transferer
: Optional, indicates if token is a transferermirrors
: Required for ICTT, must contain at least one mirror configuration
Mirror Configuration Fields
address
: Required, contract address on mirror chaintransferer
: Required, transferer contract on mirror chainchain_id
: Required, must be different from token's chain_iddecimals
: Required, must match token contracthome
: Optional, indicates original/home chain
Edit on GitHub
Last updated on