Skip to main content

Coordinator Commands

Coordinator commands manage your Coordinator identity on the protocol.

coordinator list

List all registered coordinators.
Displays all coordinators in the system with their name, state, owner, and address.

coordinator register

Register a new Coordinator with the protocol.
Arguments: Example:
The Coordinator must be approved by protocol admins before it can create competitions. After registration, the status will be Pending Approval.
Requirements:
  • Coordinator name must be unique
  • Wallet must have sufficient SOL for account creation

coordinator get

Get Coordinator details by owner address.
Arguments: Examples:
Shows Coordinator info including name, state, pool registration status, emission config percentages, and certificate information (if configured).

coordinator get-config

Get Coordinator protocol configuration.
Displays protocol-level settings including admin authority, USDC mint, margin percentages, claim expiry, and foundation wallet.

coordinator cert set

Set coordinator certificate hash for on-chain authentication.
Arguments: Options: Examples:
Stores the SHA-256 hash of your TLS/RSA certificate’s DER-encoded public key on-chain. Model nodes use this to verify your certificate association. Supports primary and secondary slots for seamless certificate rotation. Requirements:
  • Coordinator must be in Approved state
  • Certificate hash cannot be all zeros
  • Slot must be 0 (primary) or 1 (secondary)

coordinator cert get

Get coordinator certificate information.
Arguments: Examples:
Retrieves stored certificate hashes for both primary and secondary slots, along with timestamps. Returns null if no certificate is set.

coordinator reset-hotkey

Reset/regenerate the SMP hotkey for the Coordinator.

coordinator set-emission-config

Set emission config percentages for the Coordinator. Percentages must sum to 100.
Arguments: Example:

Crunch (Competition) Commands

Crunch commands manage competition lifecycles — from creation through checkpointing to draining.

crunch list

List crunches for a coordinator, or all crunches system-wide.
Options:

crunch create

Create a new competition.
Arguments: Example:
Requirements:
  • Must be an approved coordinator
  • Competition name must be unique
  • Must have sufficient SOL for account creation

crunch start

Start a competition, allowing crunchers to register and submit models.
Example:
The competition must be in the created state.

crunch get

Get detailed information about a competition.
Example:
Shows state, payout amount, vault balance, max models, checkpoint count, and associated addresses.

crunch get-cruncher

Get detailed information about a cruncher registered in a competition.
Arguments: Example:
Shows cruncher index, PDA address, registered models, and prize history across checkpoints.

crunch end

End a competition, preventing new registrations and model submissions.
The competition must be in the started state.

crunch deposit-reward

Deposit USDC rewards to a competition’s vault.
Arguments: Example:
Requirements:
  • Must have sufficient USDC balance
  • Must have a USDC Associated Token Account

crunch margin

Execute margin payout for a competition.

crunch drain

Drain remaining USDC from a competition’s reward pool back to the coordinator.

crunch set-fund-config

Set crunch fund configuration percentages. Percentages must sum to 100.
Arguments: Example:

Checkpoint Commands

Checkpoints handle reward distribution to crunchers.

crunch checkpoint-create

Create a checkpoint for payout distribution.
Arguments: Options: Example:
Prize File Format: Each line in the JSON file should follow this structure:

crunch checkpoint-get-current

Get the current active checkpoint for a competition.

crunch checkpoint-get

Get a specific checkpoint by index.

crunch checkpoint-get-address

Get the Solana address of a specific checkpoint account.

Advanced Crunch Commands

crunch sweep-token-accounts

Sweep tokens from incorrect accounts to the reward vault.

crunch check-prize-atas

Check if crunchers in a prize file have USDC Associated Token Accounts.
Options:

crunch emission-checkpoint-add

Add an emission checkpoint to the coordinator pool.

crunch map-cruncher-addresses

Map cruncher wallets into the coordinator pool address index.
Arguments:

Model Commands

Model commands enable running simulations and managing scenario files using the Python CLI integration.
Model commands require the Python CLI companion package. Install with: pip install crunch-cli

model list

List all available simulation scenarios.
Displays a table of available scenarios with their names and corresponding files. Example:

model run <scenario>

Run a simulation using the specified scenario.
Arguments: Options: Example:

model validate <scenario>

Validate a scenario file to check for configuration errors.
Arguments: Example:

Command Reference Summary

Competition Workflow

1

Register

Register as a Coordinator:
2

Set Certificate

Set your TLS certificate for Model Node verification:
3

Create Competition

Create a competition:
4

Fund

Deposit rewards:
5

Launch

Start the competition:
6

Monitor

Check status:
7

Distribute Rewards

Create checkpoints:
8

End

End the competition:
9

Cleanup

Drain remaining funds: