Networks & Clusters

Deploying to other SVM chains

bake isn't locked to Cookie Chain — since it's built on standard Solana/Anchor tooling, it works against any SVM-compatible chain.

Switch clusters

bash

bake use cookie       # Cookie Chain (default)
bake use devnet       # Solana devnet
bake use mainnet      # Solana mainnet
bake use https://your-custom-rpc.example.com  # any custom RPC

Everything — bake deploy, bake rollback, bake logs, bake stats, bake prove — works identically regardless of which cluster is active. This has been tested end-to-end against Solana devnet with zero code changes required.

Per-command targeting

Point specific commands at a different program without switching your active cluster:

bash

bake prove --program <address>
bake rollback --program <address>

Check your current cluster

bash

bake whoami

Shows your active wallet(s) and the current cluster. You can also run bake doctor for a full diagnostic check.

Built-in presets

Command	Cluster	RPC
`bake use cookie`	Cookie Chain	`https://rpc.cookiescan.io`
`bake use mainnet`	Solana Mainnet	`https://api.mainnet-beta.solana.com`
`bake use devnet`	Solana Devnet	`https://api.devnet.solana.com`

Custom RPC URL

bash

bake use https://my-rpc.example.com

Any valid Solana RPC URL works.

Local validator

bash

bake use http://localhost:8899

Point at a local solana-test-validator instance.

Cookie Chain specifics

Cookie Chain is a fast, cheap, community-owned SVM blockchain:

Finality: Sub-second
Cost: Deploys cost pennies
RPC: https://rpc.cookiescan.io (default)

bake is designed around Cookie Chain's economics — rollbacks cost cents, permanent on-chain history is practical.

Configuration

Cluster settings are stored in ~/.bake/config.json:

json

{
  "activeCluster": "cookie",
  "walletPath": "~/.config/solana/id.json"
}

See Clusters & Config for details.