Standards
The published standards that tokens, ledgers and deployments follow: token interfaces, messaging formats and identifiers. Usage is recorded from sources as researchers review each record, so counts grow over time.
Token standard
Base (Coinbase)B20Base's own fungible-token standard, an extension of ERC-20 built into the network rather than deployed as separate contracts. It adds a multiplier that reflects dividends and splits without changing balances, policy-based allowlists and blocklists, pausable functions and on-chain announcements of corporate actions. Coinbase's tokenised stocks are issued in it.Recorded on 1 recordCanton Foundation (Canton Improvement Proposals)CIP-56Standard Daml APIs for tokens on the Canton Network, so that wallets and applications can hold, transfer and display any compliant token without code specific to each asset. Approved in March 2025; Canton Coin implements it, and issuers such as Societe Generale-FORGE state that their Canton tokens follow it.Recorded on 2 recordsCapital Markets and Technology Association (CMTA)CMTATAn open smart-contract framework from the Swiss Capital Markets and Technology Association for tokenising equity and debt securities, including structured products, with the controls issuers need under securities law.No usage recorded yetEthereum community (EIP process)ERC-20The common interface for fungible tokens on Ethereum and compatible chains, covering balances, transfers and approvals that let a third party move tokens on the holder's behalf. Most stablecoins and tokenised funds on EVM chains implement it.Recorded on 64 recordsEthereum community (EIP process)ERC-3643A permissioned token standard built on ERC-20, so that security tokens move only between verified, eligible holders and follow compliance rules set by the issuer.No usage recorded yetEthereum community (EIP process)ERC-4626A common interface for vaults that issue shares in a pool of one underlying token, covering deposits, withdrawals and share values; used by some yield-bearing and fund-like tokens.Recorded on 3 recordsStellar community (Stellar Ecosystem Proposals)SEP-41A standard smart-contract interface for fungible tokens on Stellar's Soroban contract platform, covering balances, transfers, allowances and burns. It is a subset of the built-in Stellar Asset Contract, so classic Stellar assets and contract tokens can be used the same way. Still marked draft (version 0.5) by its authors.Recorded on 1 recordSolana Program Library (Solana ecosystem)Token-2022Solana's extensible token program, also called Token Extensions. It is a strict superset of the original Solana Token program, deployed at a separate address, and adds optional extensions to the token mint and accounts, such as transfer hooks and confidential balances. Issuers of permissioned fund tokens and stablecoins use these extensions to control who may hold and move their tokens.Recorded on 22 recordsStellar Development Foundation (protocol documentation)Stellar AssetThe protocol-level token on the Stellar network, identified by an asset code and the issuing account. Holders need a trustline to the issuer, and the issuer controls it through account flags. A built-in Stellar Asset Contract lets Soroban smart contracts use the same asset through the SEP-41 interface. Stellar's docs give Circle's USDC and EURC as examples.Recorded on 9 recordsXRP Ledger (protocol documentation at xrpl.org)XRPL trust line tokenThe original fungible token format of the XRP Ledger. Balances sit in trust lines, two-way ledger entries between a holder and the issuer, so nobody can be made to hold a token they have not opted into. Stablecoins and fund tokens on the XRP Ledger are commonly issued this way; the newer Multi-Purpose Token format is separate.Recorded on 5 records
Messaging
Identifier
ISO, with GLEIF overseeing the global LEI systemISO 17442 (LEI)A 20-character code that uniquely identifies a legal entity taking part in financial transactions, with public reference data. The register records LEIs on organisations.Recorded on 170 recordsISO, with the Digital Token Identifier Foundation as registration authorityISO 24165 (DTI)Gives each digital token a unique Digital Token Identifier (DTI). The second edition separates the ledger itself, which gets a Digital Ledger Identifier (DLI), from the tokens on it. The register records DTIs on assets and DLIs on networks.Recorded on 24 recordsISO, with national numbering agencies (ANNA) issuing codesISO 6166 (ISIN)The 12-character code that identifies a security, such as a bond or fund share, across markets. Tokenised bonds and fund shares often carry one; the register records ISINs on assets.Recorded on 71 records
Interoperability
Chainlink Labs (Chainlink)CCIPChainlink's protocol for sending messages and tokens between blockchains, run by Chainlink's oracle networks. Issuers enable a token for cross-chain use through its Cross-Chain Token (CCT) standard, which uses burn-and-mint or lock-and-release token pools with configurable rate limits, and can combine a transfer with instructions for the receiving contract (programmable token transfers). Version 2.0 adds configurable cross-chain verifiers and settlement speeds. It is a vendor protocol rather than a standards-body standard; stablecoin and tokenised-fund issuers use it to move the same token across chains without wrapped copies.Recorded on 5 recordsFINOS (originally developed by ISDA)CDMA standard, machine-readable and machine-executable model of financial products, the trades in them and the lifecycle events of those trades. It began as ISDA's model for derivatives and is now developed in the open at FINOS under the Community Specification process (version 7.0.0 at review). Classed as interoperability rather than messaging because it defines a shared data and event model that different systems and ledgers implement, not a message format sent between them. In 2019 Digital Asset released an open-source library implementing it in Daml.No usage recorded yet