Coin Brief ENDE

ERC-8325, 8326 and 8327 reach Final: registries for asset claims, documents and transfer routes

Three related Ethereum standards moved from Last Call to Final on 10 November, in commits by co-author David Hay to the ERCs repository. ERC-8325, ERC-8326 and ERC-8327 share the same four authors, among them Chris Turner and David Hay, and all were created in July 2026. The last-call deadline recorded in ERC-8327 was 19 October.

ERC-8325, the Asset Anchor Registry, deals with tokens that claim to represent something off-chain. Today a token can say so in its metadata, but another contract has no common way to check which anchor record it claims, whether a registry records the same link, whether the link is exclusive within that registry, or whether it covers the whole contract or one token ID. The standard defines registry and token-side interfaces so both sides of a binding can be checked, keeps an immutable binding history, and adds lifecycle states such as expiry, re-attestation and deactivation. An optional recovery interface can invalidate a disputed binding without deleting its record.

ERC-8326, the Canonical Document Bundle Anchor, fixes how a set of off-chain documents becomes one bytes32 commitment. Each document becomes a fixed-width entry with its content hash, role, media-type hash, filename hash and a normalisation-profile identifier; entries are ordered and hashed under a schema-version prefix. The on-chain part anchors that hash under a subject and role and keeps an append-only history of what superseded what. The authors separate normalisation, turning a file format into canonical bytes, from the manifest, so two systems only get the same hash if they used the same normalisation.

ERC-8327, the Directional Transfer Domain Registry, answers a narrower question: for a source domain, a destination domain and an asset class, is that transfer route currently allowed? Domains can stand for jurisdictions, venues, enterprise networks or DAO treasuries, and permission from A to B says nothing about B to A. An optional extension adds delayed revocation.

All three are careful about their limits. ERC-8325 does not assert that the underlying claim is legally valid, ERC-8326 does not prove a document's authenticity or legal effect, and ERC-8327 neither assigns domains nor enforces transfers.

ERC-8325, 8326 and 8327 reach Final: registries for asset claims, documents and transfer routes
ERC-8325, 8326 and 8327 reach Final: registries for asset claims, documents and transfer routes — Coin Brief

Why it matters

Tokenised assets keep running into the same gap between a token and the paperwork behind it. These standards do not close it, and say so, but they give contracts a shared way to look up who recorded what, when, and whether it is still current.

Written by Victoria Shinder.