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 to get a Lightning Address.
What is a Bridge Server?
A bridge server acts as an intermediary between:
- Your Lightning node (which handles payments)
- The LNURL protocol (which handles the address resolution)
When someone pays your Lightning Address, the bridge server:
- Receives the LNURL request
- Asks your node for an invoice
- Returns the invoice to the sender
- Your node receives the payment directly
Available Bridge Solutions
Umbrel / Citadel
If you're running Umbrel or Citadel, you can use:
- Alby Hub — Connect to get an
@getalby.comaddress - LNbits — Self-host your own LNURL endpoints
- BTCPay Server — Full payment processing with Lightning Address
Satdress
Satdress is a lightweight bridge server:
# Clone and configure
git clone https://github.com/nbd-wtf/satdress
cd satdress
cp .env.example .env
# Edit .env with your node details
Supports:
- LND
- c-lightning
- Eclair
- LNbits
- LNPay
Lightning Box
Lightning Box provides Lightning Address for Blixt wallet users and other LND nodes.
Setup Guide
- Choose a bridge — Pick one that supports your node type
- Configure connection — Usually REST API or gRPC credentials
- Set up DNS — Point your domain's
.well-knownto the bridge - Test — Send yourself a small payment
Important Notes
- Not fully trustless — The bridge sees your invoices (though not funds)
- Uptime dependent — If the bridge is down, you can't receive
- Custom domains — Most bridges support your own domain
Self-Hosting 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 instant | | Custom domain | Often supported | Usually supported | | Cost | Just hosting | May have fees |
For most users, a hosted wallet with Lightning Address is simpler. Bridge servers are best for:
- Node operators who want sovereignty
- Developers building custom setups
- Users with specific privacy requirements