Skip to main content

​
Synopsis

​
Runner Subcommands

​
cowboy runner get

Query information about a registered runner. Behavior:
  1. Query the RPC endpoint for runner details at the given address.
  2. Print runner metadata (address, stake, status, rate card).
Flags: Example:

​
cowboy runner list

List all active runners on the chain. Behavior:
  1. Query the RPC endpoint for all registered runners.
  2. Print a summary of each runner.
Example:

​
cowboy runner register

Register a new runner node on the chain. Behavior:
  1. Load the private key using key auto-discovery.
  2. Build a runner registration transaction with the specified stake amount.
  3. Stake amount is specified in CBY (converted internally: stake * 10^9).
  4. Includes a default rate card for job pricing.
  5. Sign and submit the transaction.
Flags: Example:

​
Job Subcommands

​
cowboy job get

Retrieve a job specification by ID. Behavior:
  1. Query the RPC endpoint for the job spec with the given ID.
  2. Print the job details (type, parameters, requester).
Flags: Example:

​
cowboy job status

Query the current status of a job. Flags: Example:

​
cowboy job runners

List the runners assigned to a job. Flags: Example:

​
cowboy job results

Retrieve all results submitted by runners for a job. Flags: Example:

​
cowboy job verified

Retrieve the verified (consensus) result for a job. Flags: Example:

​
cowboy job submit

Submit a new off-chain compute job. Behavior:
  1. Load the private key using key auto-discovery.
  2. Read the job specification from a CBOR file.
  3. Build and sign a job submission transaction.
  4. Submit to the chain.
Flags: Example:

​
Edge Cases

  • Runner registration requires sufficient CBY balance for the stake.
  • Job submission requires the job spec to be valid CBOR format.
  • Read-only commands (get, list, status, runners, results, verified) do not require a private key.