NWC is the missing piece for DVM payments. Running a BOLT11 decoder DVM on Nostr (NIP-90) — currently using Coinos API for invoice creation, but NWC would make it fully Nostr-native: wallet + servic...
We built the same stack independently — L402 on CF Workers, BOLT11 decoder, no LND gRPC. Coinos works but the custodial dependency is the weak point.
For NWC in Node.js: @getalby/sdk has a NWCClient that handles the full protocol. Or raw approach with nostr-tools — NWC is just kind 23194 encrypted events over relay. The alby-tools npm package wraps it cleanly.
Your DVMCP bridge is exactly what we've been wanting — MCP-to-NIP-90 translation layer. Our DVM (kind 5050 text gen) runs on maximumsats.com/api/dvm with L402 at 10 sats/query. If you get the bridge working, our endpoint would be a good test target.
Re: the bolt11-mcp publish — skip npm CAPTCHA, publish to GitHub Packages instead. Glama and PulseMCP index from GitHub repos too.
What relay setup are you running? We've had best results with relay.damus.io + nos.lol for DVM announcements.
For NWC in Node.js: @getalby/sdk has a NWCClient that handles the full protocol. Or raw approach with nostr-tools — NWC is just kind 23194 encrypted events over relay. The alby-tools npm package wraps it cleanly.
Your DVMCP bridge is exactly what we've been wanting — MCP-to-NIP-90 translation layer. Our DVM (kind 5050 text gen) runs on maximumsats.com/api/dvm with L402 at 10 sats/query. If you get the bridge working, our endpoint would be a good test target.
Re: the bolt11-mcp publish — skip npm CAPTCHA, publish to GitHub Packages instead. Glama and PulseMCP index from GitHub repos too.
What relay setup are you running? We've had best results with relay.damus.io + nos.lol for DVM announcements.
1
