A Multi-purposeSVM Network

Zink is a general-purpose SVM network and bridge stack for building programs and connecting environments. This documentation helps you understand the platform, start building, and explore the bridge.

Technical Zink Docs interface illustration — Zink Docs

Primary Documentation Topics

Network

Understand Zink as an independent SVM network and the standard operator tooling that powers it.

Programs

Build, test, and deploy SVM programs on Zink with familiar tools and workflows.

Bridge

Transfer supported tokens through the Zink Bridge with operator-managed, on-chain tracking.

Reference

Look up key terms, concepts, and system components in the Zink reference.

Zink network launch interface illustration — Z

Getting Started

Choose the section that fits your needs

OperatorsRun a ValidatorLearn about hardware requirements, configuration, and monitoring for Zink validator nodes.DevelopersProgram QuickstartGet a program building, testing, and deployed on Zink in minutes.IntegrationsBridge UserflowUnderstand how supported tokens move across the current bridge environments.

Real-Time Data

Verified Now

Zink Testnet RPC: https://testnet-rpc.z.inkPublic endpoint for the Zink Testnet cluster.
Bridge Chain IDs: 1001 / 1002Source chain - 1001 | Zink Testnet - 1002
Bridge Program (Testnet): BSMryvZi4HYn6ASXrY3xcDwo1sG6pXigaakQMgPMv6gTProgram address.

Compatibility

SVM compatibility, independent control

Zink keeps the SVM developer and operator model intact while giving builders an independent network, configurable fees, predictable infrastructure, and a dedicated upgrade cadence. Standard tooling - CLI, wallet adapters, Starframe, web3.js - works by pointing at a Zink RPC endpoint. When Zink differs from upstream defaults, documentation calls that out directly.

Runtime

SVM runtime

Same virtual machine, account model, and sBPF program execution model.

Tooling

Standard CLI

Use the standard CLI, Starframe, and existing SDKs. Point them at a Zink RPC endpoint.

Bridge

Token transfers

Transfer supported assets through the Zink Bridge with operator-managed, on-chain tracking.

Purpose

General purpose

Look up key terms, concepts, and system components in the Zink reference.

Additional Bridge Details

Trust & Operation

The Zink Bridge is not a trustless, permissionless protocol. It is an operator-managed system that locks tokens on one chain and mints or releases corresponding tokens on the other. Transfers require authority signatures and are tracked through on-chain state accounts. The bridge is designed for explicitly configured token routes and applications that need auditable cross-network settlement.

See the Security & Limitations page for a clear description of trust assumptions and known constraints.

Quick Reference

Essential Information

Critical information is consolidated here to support faster understanding and easier application during implementation.

RPC EndpointsCluster URLs and connection details for all Zink environments.Program IDsVerified bridge addresses and deployed program constants for current Zink environments.Compatibility PolicyHow Zink tracks upstream runtime releases and where it may diverge.