How Transfer Domain
Routing Works
Every permitted asset transfer between jurisdictions is backed by an on-chain route record. Once registered, it cannot be silently altered — only explicitly revoked with an append-only audit trail. Routes are directional; reverse permission requires a separate registration.
Diagram — how a transfer route is registered
A route is uniquely identified by three inputs: source domain, destination domain, and asset class. Their combined key is written on-chain alongside a permission evidence hash and the block it becomes effective.
Diagram — graceful revocation
Routes cannot be deleted — they go through a two-step revocation. The initiator sets a future effective block (the grace period), during which transfers remain permitted. Once that block passes, the route is finalized as revoked. The full history stays fully readable on-chain.
Live smart contract · Ethereum Sepolia
Stores permitted transfer routes keyed by source domain, destination domain, and asset class. Supports graceful revocation with an auditable on-chain trail of every initiation and finalization.
Contract Address · Sepolia
0xB3c1D4e8F2a9C5b7E0d6A1f4B8c2D5e9F3a7C0b4A registered route cannot be silently changed. Any modification requires an explicit on-chain transaction.
Every route registration, revocation initiation, and finalization is recorded on-chain.
Any party can look up a route and confirm whether a transfer between two domains is currently permitted.