Practical overview
When it fits
Use it when an existing NIP-47 client needs access to a Lightning wallet or node through Alby or LND, or when reviewing its documented integration flow. Its stated inactive maintenance status is relevant when assessing it for new development.
Who it is for
- Operators connecting Nostr clients to an Alby or LND Lightning backend.
- Developers integrating NIP-47 wallet requests into compatible applications.
Documented uses
- Connect a compatible Nostr client, such as Damus or Amethyst, to a Lightning wallet or node.
- Provide an NIP-47 bridge for supported wallet operations, including balance checks and invoice handling.
- Configure client authorization through a connection secret or a client-generated public key.
Requirements & limits
The repository identifies the project as open source under the Apache-2.0 license. Its README says the project is not actively maintained and development is focused on Alby Hub.
- Backend choice determines configuration needs: Alby uses OAuth credentials; LND uses gRPC, TLS certificate and macaroon settings.
- SQLite and PostgreSQL are supported for storage, with PostgreSQL recommended.
- NIP-47 method coverage is backend-specific; multi-invoice payment is listed as unsupported for both.
- The README identifies the project as not actively maintained.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure the service for an Alby or LND backend
Prepare the application configuration for a selected supported Lightning backend.
Before you start
- Go executable; the application has no runtime dependencies.
- SQLite or PostgreSQL storage; PostgreSQL is recommended.
- A randomly generated 32-byte hexadecimal Nostr private key.
- For Alby: OAuth client ID, client secret and redirect URL. For LND: gRPC address, TLS certificate file and macaroon file.
Steps
Copy
.env.exampleto.envand edit the configuration.Set
NOSTR_PRIVKEY,LN_BACKEND_TYPE,DATABASE_URIand the other required settings for the selected backend.For Alby, provide the OAuth credentials and redirect URL; for LND, provide the address, certificate and macaroon file locations.
Expected outcome
A configured environment file for the application and chosen backend.
Guide limitations
- These steps cover configuration only; they do not document a complete deployment or connection test.
- Supported NIP-47 methods and response details differ between Alby and LND.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- getAlby/nostr-wallet-connect · Official homepage title · retained in its source language

