Tradfi Chains

Standards and proposals

Standards and proposals 15 tracked · register 2026-11-15

How to read this

Which rules each chain runs, what its own registry says about them today, and how much of that we have measured on a contract we hold. A proposal is the earliest public signal of a capability change — earlier than a testnet — and it is never the capability itself.

A status is the registry's own word, mapped into four values. The registry's word is printed next to ours whenever they differ, so the mapping is never invisible.

"Proposed — not live" means a rule is moving. It is not a claim that any chain does something new: a capability is ours to state only from bytecode, and that reading lives on the contract pages.

Conformance is split into measured (we read the interface) and asserted (the spec or issuer says so). The two are never added together.

CIP is Canton's proposal process on this page and Cardano's cardano-foundation/CIPs elsewhere. The name ARC on this site means Circle's chain — when you see ARC-1 mentioned (Algorand's, or Aergo's), that is a name-collision clarification, not a standard we track here; no row on this page is an ARC-1 row. Every row names the registry it was read from.

In force, by the registry
0
the registry’s own word is on the row
Recorded by us
12
status curated from documentation; the registry’s word is not a column yet
Proposed
3
moving rules — not a capability, not a change on a chain
Measured conformance
13
contract interfaces we read ourselves

Every standard we track

StandardKindStatusWhat it is, and who changes itConformance on our registerRegistry read
CIP-0112
Canton Network Token Standard V2 - Improvements for Privacy, Performance and Traditional Accounting
canton
tokenProposed — not live
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

d6's named pair. Approves v2 token-standard packages on top of CIP-0056 — 'traditional accounting' is the DTS audience's exact question. Approved ≠ shipped: no capability claim until bytecode says so.

Changes are governed by Canton Foundation (CIP process, Global Synchronizer).
the spec itself as of 2026-11-15
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement
CIP-56
CIP-56 (Canton token standard)
canton
tokenRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

The token standard DTS settles against is what institutional buyers ask about; this is the V1 it rests on, and our existing row cited DTCC's page instead of the spec.

Changes are governed by Canton Foundation (CIP process, Global Synchronizer).
the spec itself no web link · scheme unparseable: as of 2026-11-11
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement
EIP-7702
Set Code for EOAs
ethereum
capabilityRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Changes who can hold and move tokenised assets from an institutional wallet; Final, so it is capability-shaped, and custody answers on the chain page have to reflect it.

Changes are governed by Ethereum EIP process (ethereum/EIPs, Standards Track).
the spec itself as of 2026-11-15
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement
EIP-7708
EIP-7708 system emitter (Arc native USDC stream)
ethereum
capabilityRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Already a curated row and the reason our Arc USDC reading is safe (dual-emitter trap: never sum across emitters). It is the clearest case of a spec our surface depends on that is NOT final.

Changes are governed by Ethereum EIP process (ethereum/EIPs, Standards Track).
the spec itself no web link · scheme unparseable: as of 2026-11-12
0 measured 1 asserted
USDC (arc) asserted
ERC-1967
Proxy Storage Slots
ethereum
capabilityRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Upgradeability is the first question institutional diligence asks about an issuer contract; the proxy slots are readable from bytecode, so this standard has a measured side.

Changes are governed by Ethereum ERC process (ethereum/ERCs).
the spec itself as of 2026-11-15
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement
ERC-20
ERC-20
ethereum
tokenRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Existing row kept. The EVM baseline every other EVM-chain row is compared against; also the interface Arc's 6dp mirror is measured on (the dual-emitter warning lives here).

Changes are governed by Ethereum ERC process.
the spec itself no web link · scheme unparseable: as of 2026-11-10
0 measured 4 asserted
USDC (arc) asserted
EURC (arc) asserted
USYC (arc) asserted
cirBTC (arc) asserted
ERC-2612
Permit Extension for EIP-20 Signed Approvals
ethereum
capabilityRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

permit() is a caps-shaped capability (signed approval) that our caps vocabulary can measure per contract; pairing the standard with measured conformance is the measured-vs-asserted demo.

Changes are governed by Ethereum ERC process (ethereum/ERCs).
the spec itself as of 2026-11-15
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement
ERC-3009
Transfer With Authorization
ethereum
capabilityProposed — not live
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Off-chain-authorized transfer — the mechanics behind institutional settlement flows and gasless moves; still Draft, so it is an open item, not a capability.

Changes are governed by Ethereum ERC process (ethereum/ERCs).
the spec itself as of 2026-11-15
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement
ERC-3643
T-REX - Token for Regulated EXchanges
ethereum
tokenRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Flagship #3 of the phase-B cut: the compliance-transfer standard buyers cite, and the ISO work item. Final per the registry, fetched today.

Changes are governed by Ethereum ERC process (ethereum/ERCs) + T-REX Association.
the spec itself as of 2026-11-15
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement
ERC-4626
Tokenized Vaults
ethereum
capabilityRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Vault shares are a fund-shaped token; any tokenised-fund story on an EVM chain meets this interface.

Changes are governed by Ethereum ERC process (ethereum/ERCs).
the spec itself as of 2026-11-15
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement
SEP-41
SEP-41 (Stellar smart-contract-asset standard)
stellar
tokenProposed — not live
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Five contracts on our register already conform to it; its going-final is a dated watch, and it is the proof case that proposals are our earliest internal corroboration.

Changes are governed by Stellar Development Foundation (SEP process, stellar/stellar-protocol).
the spec itself no web link · scheme unparseable: as of 2026-11-11
0 measured 5 asserted
SPL
SPL (Solana Program Library token)
solana
tokenRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Existing row kept — two contracts carry it and it is the 'plain token' baseline against TOKEN-2022.

Changes are governed by Solana Foundation / solana-program.
the spec itself no web link · scheme unparseable: as of 2026-11-11
0 measured 2 asserted
USDC (solana) asserted
OUSG (solana) asserted
TIP-20
TIP-20 (Tempo token standard)
tempo
tokenRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Thirteen contracts carry it and it is the reason Tempo's payment rails look uniform, but the only public evidence is one mention in the developer docs. Row stays, labelled asserted; the crawl for it is a no-op with a stated reason.

Changes are governed by unpublished — Tempo docs only.
the spec itself no web link · scheme unparseable: as of 2026-11-10
0 measured 13 asserted
USDY (tempo) asserted
YLDS (tempo) asserted
wYLDS (tempo) asserted
PRIME (tempo) asserted
TOKEN-2022
Token-2022 (Solana extended token standard)
solana
tokenRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Thirteen contracts on our register carry it; it is Solana's compliance-extension shape (transfer fee, permanent delegate, confidential). No status lifecycle exists to crawl — the honest state is 'implemented in code, no proposal process', and d2 must not invent one.

Changes are governed by Solana Foundation / solana-program (repo governance docs, not a proposal registry).
the spec itself no web link · scheme unparseable: as of 2026-11-11
13 measured 0 asserted
WORMHOLE-NTT
Wormhole Network Token Transmission
solana
infraRecorded as in force — our reading
no explanation written for this one yet. A list without prose is what every other registry out there already is, so this row is not finished.
Why we track it

Existing row kept, flagged for d3: kind=infra and it belongs to no chain's standards registry — rendering it next to SEP-41 without that distinction is the kind of false equivalence /standards must avoid.

Changes are governed by Wormhole protocol repo.
the spec itself no web link · scheme unparseable: as of 2026-11-11
conformance not joined for this row yet — that is an absent join, not a zero and not a measurement

Statuses come from each registry's own repository, read on the date shown. When one changes, a dated row appears on the change log — that is the point of keeping them at all.

How this list was chosen the filter, not the firehose

A curated whitelist, not a dump: every tracked standard carries a one-line reason for being here, and the ones that did not earn one stayed out. Canton's CIP registry holds 120 numbered proposals, 79 of them admissions of specific Super Validators — none of those are on this page, because a proposal about who validates is not a standard about tokens. Ethereum's EIPs repository carries 972 files; we track the handful that touch asset mechanics, and say which ones we looked for and could not find.