Claw Cash primary sources — 2026-05-03

Project status in this pass

• No canonical standalone Claw Cash whitepaper or litepaper surfaced.
• The clearest current source of truth is the official site, the repository README, the operator runbook, and the published SKILL.md package docs.
• The project is best understood as agent wallet and machine-payments infrastructure built around verifiable-Bitcoin treasury framing, not as a generic wallet CLI.

Primary-source snapshots

1) Official site / product framing

• URL: https://clw.cash/
• Key excerpt:
  • The site’s top-level framing is “Stablecoins in. Bitcoin out.” and “Money agents can trust, and verify.”
  • It argues that autonomous agents should hold Bitcoin because the supply, signatures, and chain history are cryptographically verifiable by code.
  • It positions the product around stablecoin ingress, Bitcoin treasury, Lightning, Arkade, payment links, and MPP-style cash pay flows.

2) Repository README / architecture and roadmap

• URL: https://raw.githubusercontent.com/tiero/claw-cash/main/README.md
• Key excerpt:
  • The README says Claw Cash gives agents one CLI for BTC, Lightning, Ark, and stablecoins, with private keys managed either by a hardware-isolated Evervault Enclave or a cheaper Cloudflare Worker mode using AES-256-GCM.
  • It lays out the product structure as API, enclave signer, SDK, skills, CLI, schemas, and infra.
  • It also documents Telegram-based auth, bot-session flows, and local dev / deploy paths.

3) Operator runbook / trust-boundary details

• URL: https://raw.githubusercontent.com/tiero/claw-cash/main/docs/runbook.md
• Key excerpt:
  • The runbook documents two signer backends: enclave mode and worker mode.
  • Enclave mode uses an Evervault Enclave and is described as operator-non-readable key isolation; worker mode is cheaper but operator-trusted because the operator controls the master sealing key.
  • The runbook also documents D1/KV state, Telegram webhook setup, key-backup formats, signer-mode migration caveats, and secrets-rotation considerations.

4) Published SKILL.md / machine-facing operational surface

• URL: https://unpkg.com/clw-cash/SKILL.md
• Key excerpt:
  • The SKILL.md presents cash as a Bitcoin and stablecoin agent wallet where the CLI never touches private keys directly.
  • It documents concrete commands for receiving and sending over Arkade, onchain Bitcoin, Lightning, and stablecoin swap flows.
  • It also says cash pay handles MPP 402 Payment Required challenges automatically using Lightning and a preimage as proof, and gives detailed reactive guidance about auth, polling, swap monitoring, and confirmation requirements.

5) Notable first-party inconsistencies

• URLs:
  • https://clw.cash/
  • https://raw.githubusercontent.com/tiero/claw-cash/main/README.md
  • https://raw.githubusercontent.com/tiero/claw-cash/main/docs/runbook.md
• Key excerpt:
  • The marketing site foregrounds AWS Nitro Enclave language.
  • The README and runbook instead describe an Evervault Enclave deployment and a Cloudflare-worker-only fallback signer mode.
  • The common product claim is still clear: Claw Cash is centered on isolated signing and operator-visible trust boundaries. But the exact enclave implementation should be read cautiously until the first-party docs converge.

Working conclusion

Claw Cash is best cataloged as an agentic-wallet and machine-payments control plane. The deciding evidence in this pass was the combination of Bitcoin-as-verifiable-treasury positioning, stablecoin ingress/egress, Lightning and Arkade payment rails, cash pay support for MPP 402 flows, bot-auth/session tooling, and explicit signer-mode trust boundaries. It is broader than a wallet CLI and more opinionated than a plain payments SDK: it is packaging walleting, identity, treasury conversion, and machine-payment execution into one stack for autonomous agents.