I just released lnbits-clink (v0.1.0), a Nostr-native Lightning extension for LNbits. It builds on the CLINKme.dev standards, offers (nOffer1...) and wallet debits (nDebit1...), so everything runs over Nostr relays with signed, E2E-encrypted events. No LNURL, no NWC. It simply plugs LNbits to a Lightning(.pub) node. A list of all CLINK-aware apps is available at clinkme.dev/apps.html.
What it does:
- Offers — publish a
noffer1...; anyone can request and pay a fresh BOLT11 invoice over Nostr. Fixed or spontaneous price. Includes a public checkout page and API. - Pay offers — pay any remote CLINK offer from an LNbits wallet with fresh ephemeral keys per payment.
- Subscriptions auto-renew — define a plan (amount + day/week/month frequency), attach a payer’s
ndebit1..., and a permanent poller bills each period over kind 21002 debit requests. Self-cancels after repeated failures. - Wallet debits — a node service that listens on relays and draws payments from wallets, with per-period budgets, frequency matching,
allowed_pubkeysrules, and k1 replay protection. - Funding source — use CLINK (e.g. Lightning.Pub) as the funding source for the instance, or run the node service standalone.
The hook that matters for most people: subscriptions that auto-renew over Lightning without a custodian. That’s the piece no LNURL/NWC flow gives you today.
Announcement: LNbits-CLINK extension: LN Paymens, Subscriptions Auto-Renew & Funding Source \ stacker news
Demo: https://clink-lnbits.fly.dev
Repo: https://github.com/WoompaLoompa/lnbits-clink
License: GPL-3.0
Happy to answer questions here, and if a maintainer wants a closer look, I’d love feedback on the registry PR too.