02 — Stablecoins

Map your stablecoin's identity layer

Every stablecoin on every chain has a different compliance surface. The identity standards, DID methods, and Travel Rule solutions available depend on both the token and the network. This tool maps the combinations.

Five layers from blockchain anchor to end-user application. The state transition at L3 marks where identity resolution succeeds or fails.

IDENTITY COMPLIANCE STACKL1 · ANCHORBlockchain AnchorHedera · Ethereum · Bitcoin (ION) · DNSL2 · RESOLUTIONResolution LayerDID Resolvers · .well-known · HCS Topics · Mirror NodeL3 · IDENTIFIERDID Methodsdid:web · did:hedera · did:key · did:ionL4 · CREDENTIALVerifiable CredentialsW3C VC · ACK-ID · Notabene TAP · Verifiable PresentationsL5 · APPLICATIONUser InterfaceWallets · AI Agents · dApps · Compliance Dashboards▲ IDENTITY RESOLVED ▲Hover a layer to see details · L3 state transition: identity resolution boundary

Select a stablecoin and chain to see which DID methods, compliance frameworks, identity standards, and Travel Rule solutions are available.

USDC on Ethereum

DID Methods

did:ethrdid:web

Identity Standards

W3C VCACK-ID

Compliance Frameworks

MiCAGENIUS Act

Travel Rule Solutions

NotabeneChainalysis

Circle-issued USDC on Ethereum mainnet with full compliance integration

This registry maps stablecoin × chain combinations to their identity standards and compliance solutions. Each entry reflects current deployment status as of April 2026. Travel Rule solutions are only relevant for cross-border transactions subject to FATF AML requirements.

Stablecoin compliance is not a single layer — it's a stack. The anchor layer determines which DID methods are available. The resolution layer determines latency and trust model. The credential layer determines what can be proven.

Hedera's stack is the most vertically integrated: did:hedera for identity, Stablecoin Studio for issuance, HCS for credential anchoring, and a governing council of 39 institutions for governance. Base and Ethereum offer more method diversity but require assembling the stack from independent providers.