Network Registry
One trusted list of networks and official stablecoin contracts, so payments only ever use real USDC and EURC on the right network.
Developer docs
What it does
Most stablecoin losses are not clever attacks. They are a payment sent to a convincing imitation of a token, or to an address that was never valid on that network. This module is designed to remove the guesswork: a single list of the networks a platform supports, the issuer’s official USDC and EURC contracts on each, and how money is allowed to move between them. Payments, deposits and payees all check against it, so a token that is not on the list is never credited or sent, and an address that does not fit its network’s rules is refused before any money moves. In development.
Powers
How it works
The Network Registry is the list every payment is checked against. Payment Rails and the Settlement Engine read it before moving value, and Cross-Chain Transfer uses it to decide whether a route between two networks exists at all.
Select a step to replay it. Hover to pause.
Step 1 of 3: Check. The coin, the network and the destination address are matched against the registry.
Key capabilities
Official contracts only
Each network lists the issuer’s own USDC and EURC contracts, with the source page they came from. A lookalike token is not in the registry, so it cannot be credited or sent.
Per-network status control
A network can be enabled, paused so nothing moves, or set to receive deposits without sending payments out — without a code change.
Routes decided, not guessed
Same-network transfers, Circle Gateway and CCTP each have their place. The registry decides which applies, and returns nothing when a payment is not possible at all.
Addresses verified on chain
Every address carries a record of when it was last checked on chain, and the checks run continuously rather than at review time.