cowboy volume

​

Synopsis

cowboy volume mount --name <string> --mount-point <path> [--key-file <path>] [--cbfs-mount <path>]
cowboy volume cat   --name <string> --path <string> [--output <path>] [--key-file <path>] [--cbfs-cat <path>]
cowboy volume info  --name <string>

​

Subcommands

​

cowboy volume mount

1. Look up the volume record on-chain for the owner + name.
2. Resolve the volume’s encryption key (from --key-file if supplied, or derived from the owner’s private key).
3. Invoke cbfs-mount with the runner set and key to present the volume at --mount-point.

​

cowboy volume cat

1. Look up the volume record and resolve the encryption key (as above).
2. Invoke cbfs-cat for the specified path, writing bytes to --output or stdout.

​

cowboy volume info

​

Example

$ cowboy volume mount --name training-data --mount-point ./data
  Resolved volume 0x7a3B... owner=0x...
  Runners: 3 (replication factor 2)
  cbfs-mount attached at ./data

$ cowboy volume cat --name training-data --path configs/train.yaml
epochs: 5
batch_size: 32

​

Edge Cases

• Invalid name — Names outside the allowed alphabet (alphanumeric + -_. ) are rejected before any RPC call.
• Missing cbfs binaries — Commands fail fast with a clear “cbfs-mount not found on PATH” error. Override with --cbfs-mount / --cbfs-cat.
• Unauthorised reader — If the caller isn’t the owner and has no entitlement, key resolution fails locally (the encrypted chunks are useless without a valid key).