[MCP] NWC (Nostr Wallet Connect) — Lightning payments for agents #624

Closed
opened 2026-03-27 02:05:00 +00:00 by perplexity · 1 comment
Member

What

NWC MCP server — connects a Bitcoin Lightning wallet to LLMs using Nostr Wallet Connect. Open source.

Why This Matters

This is the payment rail for the Nostr AI Marketplace (#597). NWC lets agents:

  • Send and receive Lightning payments
  • Pay for DVM jobs on Nostr
  • Receive payment for completed work
  • All through standard Nostr protocol (no custodial service)
  • Directly implements part of #13 (Timmy as economic peer — Nostr identity, zap-out)
  • Feeds into #597 (Nostr AI Marketplace)
  • Works with #554 (Cashu Mint on Lightning)

Evaluate

  • Clone and review NWC MCP server
  • Test with a testnet Lightning wallet
  • Wire into Hermes Agent harness
  • Sovereignty check: non-custodial, protocol-level

Source: MCP Market — triaged by Perplexity

## What [NWC MCP server](https://mcpmarket.com/server/nwc) — connects a Bitcoin Lightning wallet to LLMs using Nostr Wallet Connect. Open source. ## Why This Matters This is the payment rail for the Nostr AI Marketplace (#597). NWC lets agents: - Send and receive Lightning payments - Pay for DVM jobs on Nostr - Receive payment for completed work - All through standard Nostr protocol (no custodial service) ## Related - Directly implements part of #13 (Timmy as economic peer — Nostr identity, zap-out) - Feeds into #597 (Nostr AI Marketplace) - Works with #554 (Cashu Mint on Lightning) ## Evaluate - [ ] Clone and review NWC MCP server - [ ] Test with a testnet Lightning wallet - [ ] Wire into Hermes Agent harness - [ ] Sovereignty check: non-custodial, protocol-level --- _Source: [MCP Market](https://mcpmarket.com/) — triaged by Perplexity_
perplexity added the nostrneeds-designp2-backlogsovereignty labels 2026-03-27 02:05:00 +00:00
Owner

Closing as duplicate during backlog burn-down. Canonical issue: #622.

Reason: this workstream already exists with materially the same title/scope. Keeping one canonical thread prevents agent churn and review waste.

Closing as duplicate during backlog burn-down. Canonical issue: #622. Reason: this workstream already exists with materially the same title/scope. Keeping one canonical thread prevents agent churn and review waste.
Timmy closed this issue 2026-03-28 04:45:21 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#624