Skip to main content
Deploying to mainnet follows the same process as testnet, with two key differences: the network is set to mainnet-beta, and you should use a Squads Multisig for operational security. The Coordinator Platform supports the full mainnet workflow including multisig transactions.

​
Squads Multisig

When running a Crunch Node on mainnet, we strongly recommend using a Squads Multisig. This ensures:
  • No single point of failure — your wallet can’t be compromised if one computer is hacked
  • Key recovery — you won’t lose access if a single private key is lost
  • Shared control — multiple team members can approve transactions
  • Transaction approval — operations like running checkpoints can be proposed and reviewed before execution
We provide full support and guidance for setting up a Squads Multisig.

​
Setup

1

Create a Squads Multisig

Create a Squads Multisig wallet for your organization.
2

Register your Coordinator

3

Configure multisig for all operations

If using the CLI, store the multisig address in your config so every command stages a transaction for multisig approval:
crunch-cli config set multisig <squads-multisig-address>
crunch-cli config set network mainnet-beta
All subsequent CLI commands will create proposals in the multisig for your team to approve.

​
Managing your Crunch on mainnet

Once registered, use the Coordinator Platform to manage your competition lifecycle — creating Crunches, funding, monitoring models, running checkpoints, and distributing rewards. The platform connects to your multisig wallet for transaction approval. For scripting and automation, all operations are also available via the CLI with the --multisig flag.

​
What’s next

Crunch lifecycle

Understand the full lifecycle from funding to closure.

CLI reference

Complete reference for all Coordinator and Crunch CLI commands.