Appearance
Program IDs
This page is the canonical place to publish deployed Zink program addresses.
Why this page matters
Program IDs are operationally important because they affect:
- frontend configuration
- client SDK constants
- Starframe program declaration and generated keypair
- multisig / governance actions
- deployment verification
Incorrect program IDs are one of the easiest ways to sign perfectly valid transactions that do the wrong thing.
Verified bridge program IDs
The bridge repository currently exposes three bridge-program constants:
| Environment | Program ID | Status | Source |
|---|---|---|---|
| Production constant | BR1DGEaF3Z3ZN9UouYiRLKbK2WWgFmHwUwcZKJfmJSSP | Defined in source | programs/bridge/src/lib.rs |
| Dev / testnet constant | BSMryvZi4HYn6ASXrY3xcDwo1sG6pXigaakQMgPMv6gT | Current verified live atlasnet ↔ zink-testnet bridge program | programs/bridge/src/lib.rs + live bootstrap runbook |
| Localnet constant | 5Bw3DZTvadDWGJMg7urmZJQwhYoU87fRKcLQ2umT983n | Local development only | programs/bridge/src/lib.rs |
Bridge-specific
The current Zink bridge UI bindings and generated Codama bindings default to BSMryvZi4HYn6ASXrY3xcDwo1sG6pXigaakQMgPMv6gT, which is the same program ID recorded in the verified atlasnet ↔ zink-testnet bootstrap runbook.
Current live bridge deployment facts
| Item | Value |
|---|---|
| Live bridge program | BSMryvZi4HYn6ASXrY3xcDwo1sG6pXigaakQMgPMv6gT |
| Upgrade authority / authority 1 | AUTHvT1tzXUniLNNPLsQb2wf1fasfXvxi3yDKVfLKbot |
| Authority 2 | CFB1dxBvtRhQHLemJjgoJe5Yc7h4wtaJsndAdtKyUkdC |
Atlasnet bridge PDA (other_chain_id = 1002) | 5JfsZDmv2FqAqokhxjHcYtv49QWq7EgQGGXjofYPRSJz |
Zink bridge PDA (other_chain_id = 1001) | 8Pxfu2h2F5yo4ozRA4RResCmPUHWc3WjYqdH3YMYmFDy |
Published program table
| Program | Mainnet | Testnet / Dev | Notes |
|---|---|---|---|
| Zink Bridge | BR1DGEaF3Z3ZN9UouYiRLKbK2WWgFmHwUwcZKJfmJSSP | BSMryvZi4HYn6ASXrY3xcDwo1sG6pXigaakQMgPMv6gT | Production and dev/test constants from bridge source; live atlasnet ↔ zink-testnet flow is verified on the dev/test constant |
Additional Zink-native program IDs should be added here only after they are confirmed from source code or live deployment records.
Zink recommendation
Treat this page as source-of-truth config. Avoid scattering program IDs across docs pages, chats, and dashboards where they drift out of sync.
Verification workflow
Before using a published program ID, verify that the intended cluster recognizes it:
bash
solana program show <PROGRAM_ID>If the program is deployed through generated bindings, cross-check the program declaration, keypair, and IDL expectations as well.