Vision
The Cowboy CLI (cowboy) is the primary tool for developers building on the Cowboy blockchain. It handles project scaffolding, wallet management, actor development, token operations, data feeds, and deployment — all from a single binary.
Design principles:
- Zero-config start —
cowboy init devcreates project config and a devnet wallet in one command. - Convention over configuration — Keys live in
.cowboy/, actors live inactors/, and the CLI finds them automatically. - Explicit over magic — Every command shows what it does. No hidden state, no surprise network calls.
- Network-aware — Commands target
localordev. The network choice affects defaults (RPC URL, faucet, chain ID).
Command Overview
All commands that need a private key or RPC URL use auto-discovery.
Project Structure
Aftercowboy init dev, the project has CLI configuration. Actor files are created separately with cowboy actor new <name>:
Key conventions
.cowboy/keys/<network>— Per-environment secp256k1 private key (PEM). Never overwritten by re-runningcowboy init..cowboy/config.json—{ "active": "<network>", "environments": { ... } }. Each environment storesrpc_url,key_file, optionalwatchtower_registryand optionalidentity.actors/— Each subdirectory is one actor. Created on demand bycowboy actor new <name>; not part ofcowboy init.
Networks
Zero-Config Workflow
After runningcowboy init dev and scaffolding an actor, commands use the discovered key and RPC URL:
--private-key and --rpc-url flags still work and take priority.
See individual spec files for detailed behavior:

