CLI & Tooling

Zink uses the standard Solana CLI and Agave validator binaries. There is no Zink-specific fork to install for normal operation: configure the upstream tools to point at Zink endpoints, then verify the target cluster before deploying, transferring, or operating nodes.

Installing the Solana CLI

The recommended approach is the official install script, which pulls the Agave-maintained release:

sh -c "$(curl -sSfL https://release.anza.xyz/stable/install)"

This installs the solana CLI, solana-keygen, solana-test-validator, and related utilities into ~/.local/share/solana/install/active_release/bin/.

Add the install directory to your PATH if the installer does not do it automatically:

export PATH="$HOME/.local/share/solana/install/active_release/bin:$PATH"

Verify:

solana --version

Upstream-compatible

The solana CLI from Anza's official release channel works with Zink out of the box. Do not install Zink-specific forks unless explicitly directed by the Zink team.

Pinning a specific version

If the Zink cluster is running a specific Agave version, match your local CLI to it:

solana-install init <VERSION>

Check the current cluster version at any time:

solana cluster-version

Zink recommendation

Before deploying programs or performing validator operations on Zink mainnet, match your local CLI version to the output of solana cluster-version. Version mismatches can cause subtle issues with transaction serialization or feature gate availability.

Installing the Agave validator

For node operators, the agave-validator binary is needed in addition to the CLI. The install script above includes it. You can also build from source:

# Clone the Agave repository
git clone https://github.com/anza-xyz/agave.git
cd agave
git checkout <TAG_MATCHING_CLUSTER_VERSION>

# Build the validator (requires Rust toolchain)
cargo build --release --bin agave-validator

Zink-specific

Zink may occasionally require a patched build of the validator for network-specific features. When that happens, follow the build or distribution instructions published by the Zink operators rather than assuming upstream stable is sufficient.

Configuring the CLI for Zink

Set the cluster URL

solana config set --url https://testnet-rpc.z.ink

For unpublished or operator-only environments, substitute the onboarding URL provided by the Zink team.

Set your default keypair

solana config set --keypair /path/to/your/keypair.json

View current configuration

solana config get

You should see the configured RPC URL reflected in solana config get, for example RPC URL: https://testnet-rpc.z.ink when targeting the current public Zink Testnet endpoint.

Key CLI commands for Zink operators

Command	Purpose
solana config get	Show current CLI configuration
solana config set --url <URL>	Switch to a different cluster
solana cluster-version	Query the cluster's running software version
solana block-height	Fetch the current block height
solana balance	Check native token balance of the configured keypair
solana transfer <DEST> <AMOUNT>	Send native tokens
solana-keygen new	Generate a new keypair
solana-keygen pubkey <FILE>	Display the public key from a keypair file
solana gossip	List gossip-visible nodes in the cluster
solana validators	Show the current validator set and performance stats
solana catchup <PUBKEY>	Monitor a node's catchup progress relative to the cluster
solana vote-account <PUBKEY>	Inspect a vote account's state and credits
solana stakes <VOTE_PUBKEY>	Show stake delegated to a vote account

Starframe

Starframe projects use the same Solana CLI configuration as any other SVM program. Scaffold, build, and deploy with standard tools:

cargo install star_frame_cli
sf new my_program
cd my_program
cargo build-sbf
solana program deploy target/deploy/my_program.so --url https://testnet-rpc.z.ink

The framework does not require a Zink-specific fork. Point the Solana CLI and your client SDKs at the intended Zink RPC endpoint.

Other tools

Any tool or library that speaks the Solana JSON-RPC protocol works with Zink. This includes:

• @solana/web3.js and @solana/kit — pass the Zink RPC URL to the Connection constructor.
• solana-py — same pattern; different URL.
• Metaplex SDKs — configure with a Zink Connection.
• Geyser plugins — load into agave-validator using --geyser-plugin-config.
• Block explorers — if the explorer supports custom RPC URLs, point it at Zink. Publish explorer links centrally once they are confirmed for the target cluster.

Next steps

• Wallets & Keypairs — key generation and wallet configuration
• Clusters & Environments — which URL to use
• Run a Validator — using these tools to operate a validator