# Supported Chains

Tortuga tokens are ERC-3643 permissioned security tokens deployed on EVM-compatible chains, with the ICP Master Ledger as the canonical settlement record and the ICP KYC Registry as the compliance source of truth. Chain Fusion synchronizes compliance state from ICP to each live chain natively, without bridges or wrapped tokens.

# Internet Computer (Infrastructure Layer)

The Internet Computer is the canonical source of truth for all Tortuga assets and compliance state.

Property	Value
Role	Master Ledger + KYC Registry + Chain Fusion Orchestrator
Token Standard	ICRC-1 / ICRC-2
Finality	~1–2 seconds
Transaction Cost	~$0.0001

Functions:

Master Ledger: canonical record of all tokenized bonds, holder balances, and transaction history
KYC Registry: single authoritative record of verified investor identities and wallet whitelist status
Chain Fusion: threshold-signed transaction submission to EVM chains
Yield Distributor: holder snapshot and distribution coordination

# Live Chains

ERC-3643 permissioned security tokens on EVM-compatible networks. Compliance is enforced at the smart contract level on every transfer via the on-chain Identity Registry.

flowchart LR
    ICP[Internet Computer] --> CF[Chain Fusion]
    CF --> PLUME[Plume]
    CF --> BASE[Base]
    CF --> CANTON[Canton]

# Production Networks

Chain	Type	Token Standard	Rationale
Plume	RWA-native EVM L2	ERC-3643	Purpose-built for real-world asset tokenization; deliberate positioning within the RWA ecosystem
Base	Coinbase EVM L2	ERC-3643	Broad crypto-native capital pool access via Coinbase's distribution and liquidity infrastructure
Canton	Institutional permissioned chain	ERC-3643	Used by major financial institutions (Goldman Sachs, BNP Paribas); institutional distribution channel

# EVM Integration

Tokens minted via threshold ECDSA signatures from ICP (Chain Fusion)
ERC-3643 compliance enforced at contract level: canTransfer() checks Identity Registry and Compliance Module on every transfer
Only wallets registered in the ERC-3643 Identity Registry can hold or transact tokens
Identity Registry state synchronized from ICP KYC Registry via Chain Fusion

# Roadmap Chains

The following chains appear in the codebase as roadmap targets. They are not live.

Chain	Status	Notes
Ethereum mainnet	Roadmap	—
Arbitrum	Roadmap	—
Polygon	Roadmap	—
Solana	Roadmap	Would use SPL Token via threshold EdDSA signatures
Osmosis	Roadmap	Cosmos ecosystem, IBC-compatible
Cosmos Hub	Roadmap	IBC routing

# Cross-Chain Transfers

Transfers between live chains are coordinated through the ICP Master Ledger:

sequenceDiagram
    participant User
    participant ChainA as Source Chain (e.g. Plume)
    participant ICP as ICP Master Ledger
    participant CF as Chain Fusion
    participant ChainB as Target Chain (e.g. Base)

    User->>ChainA: Burn tokens
    ChainA->>CF: Burn event detected
    CF->>ICP: Report burn, update balances
    ICP->>CF: Request mint on target chain
    CF->>ChainB: Mint via threshold signature
    ChainB-->>CF: Confirmed
    CF->>ICP: Confirm mint
    Note over User: Tokens now on Base

Burn tokens on source chain
Chain Fusion detects burn event and reports to Master Ledger
Master Ledger updates balances and requests mint on target chain
Chain Fusion signs and submits mint transaction via threshold cryptography
No wrapped tokens or bridges required

For technical details, see architecture/cross-chain-ops.md.