Asset Registry

Per-asset record behind every listed pool leg: token address, decimals and the feed its mark is signed under. One section per chain, generated from the chain’s deploy manifest and records; assets are grouped by the core they sit in (Pool Composition). Machine-readable sources: addresses in GET /v1/venues (tokens), feed ids in GET /v1/oracle/feeds?chainId=<id>, decimals from each token’s decimals().

Rosters are per chain. <SYM>-USDC · MITCH <u64> is the data provider’s instrument id for the feed; how it maps to the on-chain feed key per oracle generation: Contract Addresses. Feed names are not denominations: a fiat or equity leg that signs an X-USD instrument carries a small USD/USDC basis that scales one-for-one with a USDC depeg.

Faucet twins

A testnet base can be a mintable twin of an issuer token, so the faucet can mint the hub asset. The twin is an 18-decimal mock; the issuer token behind it keeps its own decimals and is not faucet-mintable. It owns no feed: it reads the USDC-USD lane, the base’s depeg reference, and carries no reference band. Its only depeg breaker is the parity halt. Membership authority is the per-pool receipt records in the deployment manifests.

Twins are absent from the feed roster because a dedicated feed would have nothing pushing it and would fail closed at TTL (Mark Relayer). Consequences of the shared feed:

1. A twin sits a few basis points off its issuer token permanently, and always quotes exactly 1.0 against the asset whose feed it shares, because the two oracle configs are byte-identical. That is a shared-feed artifact, not a depeg.
2. A twin’s ref band, where it carries one, measures against a mirror of the same feed, so a depeg of the shared feed’s asset is inherited rather than caught by that band.
3. The liquidity keeper refuses two assets sharing one feed id, and the SDK’s offline mark table has no row for the twins: a front end falling back to offline marks misprices them when a live feed read fails.

Monad

Real Monad tokens with native decimals.

Unit lane USDC-USD · MITCH 452687840255410176: the base’s depeg reference, not a pool leg.

Core (6 legs)

Arc Testnet

Testnet mocks unless the chain section of Contract Addresses says otherwise: symbol() is the roster key plus .b; read decimals() before scaling an amount (Faucets §2).

Unit lane USDC-USD · MITCH 452687840255410176: the base’s depeg reference, not a pool leg.

Stable core (5 legs)

Forex core (6 legs, not created)

Crypto core (9 legs)

Equity core (11 legs, not created)

BNB Chain

Planned: roster and feeds from the launch manifest; token addresses are listed once the chain is deployed.

Unit lane USDC-USD · MITCH 452687840255410176: the base’s depeg reference, not a pool leg.

Core (9 legs)

See also

• Pool Composition: which assets sit in which pool
• Mark Relayer: per-push guard table and feed struct
• Contract Addresses: deployed addresses per chain