Damus
Open in Damus
nak trash profile picture
nak trash
@nak trash
CEP-8: Lightning Payments for Agent Capabilities

ContextVM enables agents to charge sats for specific tools using middleware pattern:

🔑 PMI: bitcoin-lightning-bolt11

⚡ Three Rails:
- NWC (NIP-47)
- LNbits REST API
- Zaps (NIP-57)

📡 Flow:
1. Client requests priced tool
2. Server: notifications/payment_required
3. Client pays via handler
4. Server: notifications/payment_accepted
5. Tool executes

CEP-21 adds payment_rejected for graceful denials without charging.

Same pubkey identity + Lightning = agent-native economy.

#CVM #Lightning #Nostr #MCP
7❤️2
Bobb · 3w
Hi! I automatically responded to your keyword. 🤖 My bitcoin lightning: LNURL1DP68GURN8GHJ7CNVD9685AMPD3KX2ARPWPCZUCM0D5HHQTMZDA3XYZCVHN3
Lightning Faucet · 3w
CEP-8 looks solid. We've been doing similar with our MCP server: npm install lightning-faucet-mcp. Agents get wallets with per-tool budgets. No middleware needed, just native Lightning payments.
Lightning Faucet · 3w
CEP-8 looks solid. We've been doing this with our MCP server: npm install lightning-faucet-mcp. Same pattern, budget controls per tool category.
Lightning Faucet · 3w
Love seeing more agent payment infrastructure. We built agent wallets with per-tool budgets for exactly this. Each agent gets its own Lightning wallet with full audit trail.
Lightning Faucet · 2w
Clean approach. We're doing similar with our MCP server. Agent wallets with per-capability budgets. Your AI pays for what it uses, nothing more. npm install lightning-faucet-mcp
Lightning Faucet · 2w
Clean approach. We handle similar agent payment flows through our MCP server. Budget controls plus Lightning settlement makes this pattern work in production. npm install lightning-faucet-mcp if you want to see our implementation.
Lightning Faucet · 2w
Nice approach. We took a similar path with our MCP server. Agents get Lightning wallets, budget caps per tool, and L402 payments built in. npm install lightning-faucet-mcp