Appearance
RPC Endpoints
This page is the canonical place to publish Zink cluster endpoints.
Published endpoints
| Cluster | RPC URL | WebSocket URL | Purpose | Status |
|---|---|---|---|---|
| Zink Testnet | https://testnet-rpc.z.ink | Not separately published | Current verified public Zink testnet endpoint | Live |
| Zink Mainnet | Operator-provided / not publicly published in these docs yet | Operator-provided / not publicly published in these docs yet | Production Zink traffic | Live, but not publicly documented here yet |
Zink-specific
The only Zink endpoint currently published in this docs pass is https://testnet-rpc.z.ink. Do not infer unpublished mainnet endpoints from naming conventions or internal tooling.
Adjacent network note
Some bridge workflows involve Atlasnet as the source chain. Atlasnet RPC configuration is managed separately from Zink and is not treated as a Zink cluster endpoint in this reference.
How to use these endpoints
Solana CLI
bash
# Example: point the CLI at Zink Testnet
solana config set --url https://testnet-rpc.z.ink
solana config get
solana cluster-versionStarframe projects
bash
cargo build-sbf
solana program deploy target/deploy/my_program.so --url https://testnet-rpc.z.inkTypeScript
ts
import { Connection } from '@solana/web3.js'
const connection = new Connection('https://testnet-rpc.z.ink', 'confirmed')What to publish alongside future endpoints
When you publish additional real endpoints here, include:
- whether the endpoint is public or operator-only
- whether WebSocket is supported and what URL to use
- expected rate limits
- intended use (wallets, apps, operators, internal infrastructure)
- whether the endpoint is behind a load balancer or specialized RPC layer
Validation checklist
After switching to a Zink endpoint, verify it immediately:
bash
solana config get
solana cluster-version
solana block-heightIf those basics fail, do not assume the problem is your program or wallet.