How the Asset Anchor
Registry Works
Every real-world asset gets a durable on-chain anchor backed by source-document fingerprints. The interface makes assertions easier to verify and audit; it does not itself create legal title or prove off-chain claims true. Tokens can then be bound to the anchor, linking on-chain instruments to the asset record.
Diagram — how an asset anchor is registered
A registrar submits an asset identifier, a metadata URI, and an evidence hash. These are hashed together to produce a deterministic anchor ID and recorded on-chain. The evidence hash lets any party verify the registrar's off-chain documentation.
Diagram — token binding
After an anchor is created, a token (ERC-20, ERC-721, or ERC-1155) is bound to it via bindToken(). The binding links a contract address and token ID to the anchor, making the on-chain instrument traceable to the real-world asset it represents.
Live smart contract · Ethereum Sepolia
Stores asset anchors indexed by a deterministic ID derived from the asset identifier, registrar, and evidence hash. Supports token bindings, anchor deactivation, and URI updates — all with an append-only on-chain audit trail.
Contract Address · Sepolia
0xA1b4C8d2E5f3A9c7B0e6D4f8A2c5E1b9D7f3A0c8Once an anchor is registered, its core identity fields cannot be silently changed. Updates require explicit on-chain transactions.
Every registration, binding, and deactivation is recorded on-chain with the acting address and block number.
Any party can re-hash registrar documents and confirm they match the evidence hash stored in the on-chain anchor record.