Bridge Servers
If you already run a Lightning node but don't want to build your own LNURL server, bridge servers let you connect your node and domain to a Lightning Address.
What is a bridge server?
A bridge server is an HTTP service that serves the LNURL-pay payload needed to let user@domain.com resolve to a live Lightning payment flow.
In practice it sits between:
- your Lightning node or wallet backend
- the HTTP / LNURL discovery layer
- the sender's wallet performing resolution
When someone pays your Lightning Address, the bridge server typically:
- Receives the LNURL request
- Asks your node or backend for an invoice
- Returns the invoice to the sender
- Lets your node receive the payment directly
This is useful when you want your own domain and node-backed payments without building a full LNURL server from scratch.
Hosted bridge option: bridgeaddr
bridgeaddr is a lightweight hosted bridge solution that can connect your domain to a Lightning node in a non-custodial way.
Historically it has supported backends such as:
- Sparko
- LND
- LNPay
- LNbits
The bridge serves the required JSON and then talks to your Lightning backend to fetch invoices on demand. That means you can often get set up with just:
- a domain
- the right DNS records
- working access to your Lightning backend
Self-hostable bridge: Satdress
Satdress is a federated Lightning Address server that you can host yourself.
It gives you a plug-and-play way to connect nodes to addresses and can be used both for your own setup and for multi-user deployments.
# Clone and configuregit clone https://github.com/nbd-wtf/satdresscd satdresscp .env.example .env# Edit .env with your node detailsSupports:
- LND
- c-lightning
- Eclair
- LNbits
- LNPay
Satdress also provides a simple web UI for connecting nodes to addresses.
Other bridge-style approaches
Umbrel / Citadel
If you're running Umbrel or Citadel, you can use:
- Alby Hub — Connect to get an
@getalby.comaddress - LNbits — Self-host LNURL endpoints
- BTCPay Server — Full payment processing with Lightning Address
Lightning Box
Lightning Box provides Lightning Address support for Blixt wallet users and other LND-backed setups.
Setup guide
- Choose a bridge — Pick one that supports your node type
- Configure the connection — Usually REST, gRPC, macaroon, or API credentials
- Set up DNS — Point your domain's
.well-knownflow to the bridge - Test end to end — Resolve your address and send yourself a small payment
Important notes
- Not fully trustless — the bridge can see invoice flow and metadata even if it doesn't custody funds
- Uptime matters — if the bridge is down, your address may stop resolving
- HTTPS still matters — payment metadata remains security-sensitive
- Custom domains are usually possible — but DNS setup varies by bridge
Self-hosted vs. hosted
| Aspect | Self-hosted bridge | Hosted service | |--------|--------------------|----------------| | Trust | You control everything | Trust the provider | | Uptime | Your responsibility | Provider handles it | | Setup | More technical | Usually faster | | Custom domain | Often supported | Usually supported | | Cost | Hosting + ops | May include service fees |
For many users, a hosted wallet with built-in Lightning Address support is simpler. Bridge servers are best for:
- node operators who want sovereignty
- developers building custom setups
- users with stronger privacy or infrastructure requirements