Supported Routes and Environments

This page lists the bridge routes and cluster environments that are confirmed from current bridge source, bridge UI configuration, and the verified live bootstrap runbook.

Verified environments

Network	Chain ID	Role in verified bridge flow	RPC
Atlasnet	1001	Source / destination counterpart to Zink Testnet	Managed separately from Zink docs
Zink Testnet	1002	Current verified Zink-side bridge environment	https://testnet-rpc.z.ink

Current verified bridge deployment

Item	Value
Bridge program	BSMryvZi4HYn6ASXrY3xcDwo1sG6pXigaakQMgPMv6gT
Threshold	51% (from the verified live bootstrap runbook)
Fee target	AUTHvT1tzXUniLNNPLsQb2wf1fasfXvxi3yDKVfLKbot
Authority 1	AUTHvT1tzXUniLNNPLsQb2wf1fasfXvxi3yDKVfLKbot
Authority 2	CFB1dxBvtRhQHLemJjgoJe5Yc7h4wtaJsndAdtKyUkdC

Bridge-specific

The bridge UI configuration currently labels the supported direction as Atlasnet ↔ Zink Testnet, using chain IDs 1001 and 1002 and the public Zink-side RPC https://testnet-rpc.z.ink.

Verified token-pair routes

The following pairs are currently visible in live bridge state.

Asset	Atlasnet mint	Zink Testnet mint	Mode on both chains	Status
ATLAS	6PhneWhbN4R3nFutrRUVnE3sNgRsFS6yPrjRC29mMWnv	E4HHFKoHAJNm1utnBvdmApWC4AnQJbhKNi8zQotZoMjq	Vault / Vault	Live pair observed on-chain
Bootstrap test mint	DF7FGMPtfGbx8GG78ZQG5oViQWQ1bDneFUHsRqnktpDF	DF7FGMPtfGbx8GG78ZQG5oViQWQ1bDneFUHsRqnktpDF	Vault / Vault	Verified in the first successful live bootstrap flow

Route observations from live bridge state

For the currently observed live pairs:

• both visible routes are not frozen
• both use OwnMintType::Vault
• both carry hourly import/export limits of 1000000000000 raw units in current on-chain state
• the live bridge state currently shows pending-entry counts, which are operational data and will change over time

Zink-specific

These route tables reflect what is currently visible from the live bridge configuration and bootstrap runbook, not a broad promise that every pair is public, production-ready, or supported forever. Treat on-chain presence and operator support as separate questions.

Verified live bootstrap mint

The first verified live end-to-end bootstrap runbook used this mint on both chains:

• DF7FGMPtfGbx8GG78ZQG5oViQWQ1bDneFUHsRqnktpDF

That route is useful as a protocol-verification reference; it is not a polished end-user production asset list.

Adding New Routes

Adding a token route is an operator action, not a permissionless process. The sequence is:

1. deploy or identify the mint and vault/mint-authority accounts on both chains
2. create an AuthProposal with an AddTokenPair item specifying both mints, bridge mode, rate limits, and optional freeze/limit authorities
3. have bridge authorities vote until threshold is reached
4. confirm the resulting TokenPair is visible in the Bridge account on both sides

Removing or modifying a pair follows the same proposal/vote path. Modifying a pair cannot change the mint addresses — only operational parameters like limits, freeze state, and authorities.

Bridge-specific

A token pair cannot be removed while it has pending_entries > 0. All in-flight transfers for that pair must complete or be cleaned up before removal.

Related pages

• Bridge Overview
• Architecture
• CLI Reference
• Program IDs