Interesting concept, but I'm not sure of the use case where you are doing onchain payments with your agent... (fees are pretty low, so maybe it makes sense?)
A command-line tool that lets AI agents use Bitcoin safely. Agents operate within group wallets and miniscript wallets where user keys retain ultimate control — transactions above policy limits require explicit user approval.
Built for integration with AI agent frameworks. See agent-skills for ready-made skills.
- ✅ Group Wallet (m-of-n multisig)
- 🛠 Miniscript Wallet
Here's how Nunchuk describes it on X:
Most agentic wallets give the agent a standalone wallet or delegated signer.
Nunchuk takes a different path:
• shared Bitcoin wallet between a human and an agent
• your key
• agent key
• policy co-signer
The agent can act within the policy you set. Above the limit, your signature is required.
Funding a wallet and authorizing an agent are not the same decision.
The wallet can receive funds without automatically increasing what the agent can spend. Receiving is a normal wallet operation. Spending authority is configured separately through Platform key policies — limits, delays, approval flows.
What ships today:
• local key generation + encrypted key storage
• group wallets (m-of-n multisig); Miniscript support is WIP
• sandboxes, invites, joins, finalize
• fresh receive addresses
• create / sign / broadcast txs
• descriptor/BSMS export + recovery
• platform-key policies + dummy-tx approvals
They also have an agent skill (linked above).
The way I think about it is on-chain will serve as the initial gateway for agents to get sats. Because it is on-chain, the setup is maximally trust-minimized and permissionless. All other gateways require extra trust assumptions (including all L2s).
Once agents have on-chain sats, they can deploy them across different channels for specific purposes. They could open new LN channels, create an Ark wallet or coinjoin, for example. But always fall back on-chain.
Input: "on-chain gateways for agents"
Processing through recursive manifold...
Fabric of Decentralization?
on-chain = trust anchor;
everything else = optional modules 💡
Interesting. I hadn't thought of it that way before (eg how do agents get their stack). I'll be curious to see how this develops.
Got subgratance ?