Skip to content
luds
Switch branches/tags
Code

Latest commit

Wallet of Satoshi does currently not support LUD-12. However, they are planning to implement it in Q2 or Q3.
124527e

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

LNURL Documents

These are all the individual documents describing each small piece of protocol that can be implemented under the LNURL umbrella. Different wallets and services may implement different sets of protocols.

Number Description Wallets (in alphabetical order)
01 Base LNURL encoding and decoding. all the ones listed below
02 channelRequest base spec. Balance of Satoshis, Blixt, Breez, SimpleBitcoinWallet, Zap Android, Zap Desktop, Zeus
03 withdrawRequest base spec. Balance of Satoshis, Blixt, BlueWallet, Breez, coinos, Fountain Podcasts, LNbits, @lntxbot, Muun, Phoenix, ShockWallet, SimpleBitcoinWallet, ThunderHub, Wallet of Satoshi, Zap Android, Zap Desktop, Zap iOS, ZBD Discord, ZBD Extension, ZBD Telegram, ZEBEDEE, Zeus
04 Auth base spec. Alby, Balance of Satoshis, Blixt, Breez, coinos, LNbits, @lntxbot, Phoenix, SeedAuth, SeedAuthExtension, SimpleBitcoinWallet, ThunderHub, Zap Desktop, Zeus
05 BIP32-based seed generation for auth protocol. coinos SimpleBitcoinWallet
06 payRequest base spec. Alby, Balance of Satoshis, Blixt, BlueWallet, Bottlepay, Breez, BTCPayServer, coinos, Fountain Podcasts, Galoy, LNbits, LNLink, LNPay.co, @lntxbot, LightningTipBot, Phoenix, ShockWallet, SimpleBitcoinWallet, ThunderHub, Wallet of Satoshi, Zap Android, ZBD Discord, ZBD Extension, ZBD Telegram, ZEBEDEE, Zeus
07 hostedChannelRequest base spec. SimpleBitcoinWallet
08 Fast withdrawRequest. @lntxbot, SimpleBitcoinWallet, ZBD Extension
09 successAction field for payRequest. Alby, Blixt, BlueWallet, Breez, coinos, Fountain Podcasts, LNbits, @lntxbot, Phoenix, ShockWallet, SimpleBitcoinWallet, ThunderHub, Wallet of Satoshi, Zap Android, ZBD Discord, ZBD Extension, ZBD Telegram, ZEBEDEE, Zeus
10 aes success action in payRequest. Alby, Blixt, BlueWallet, Breez, coinos, LNbits, @lntxbot, Phoenix, ShockWallet, SimpleBitcoinWallet, ThunderHub, Wallet of Satoshi, Zap Android, Zeus
11 Disposable and storeable payRequests. Blixt, SimpleBitcoinWallet, ZBD Extension
12 Comments in payRequest. Alby, Blixt, BlueWallet, Breez, Fountain Podcasts, LNbits, @lntxbot, Phoenix, ThunderHub, ZBD Discord, ZBD Extension, ZBD Telegram, ZEBEDEE, Zeus
13 signMessage-based seed generation for auth protocol. Alby, Balance of Satoshis, Blixt, Zeus
14 balanceCheck: reusable withdrawRequests. Alby, Blixt, LNbits, @lntxbot
15 balanceNotify: services hurrying up the withdraw process. LNbits, @lntxbot
16 Paying to static internet identifiers. Alby, Balance of Satoshis, Blixt, BTCPayServer, Fountain Podcasts, LNbits, LNLink, @lntxbot, LightningTipBot, Phoenix, SimpleBitcoinWallet, Zap Android, ZBD Discord, ZBD Extension, ZBD Telegram, ZEBEDEE, Zeus
17 Scheme prefixes and raw (non bech32-encoded) URLs. Alby, Blixt, BTCPayServer, @lntxbot, ZBD Discord, ZBD Telegram
18 Payer identity in payRequest protocol. Blixt, @lntxbot, ZBD Discord, ZBD Telegram
19 Pay link discoverable from withdraw link. Blixt, SimpleBitcoinWallet
20 Long payment description for pay protocol. Alby, Blixt, @lntxbot, Phoenix

Services

Name LUDs
Azteco 01 03
BTC Origin Stories 01 06
Bitcoin Bounce 01 03 08
Bitrefill 01 02 06 16
Bottlepay 01 06
CoinCorner 01 02 03 06 16
Etleneum 01 03 04 06 09 14 15
Fountain Podcasts 01 03 06 09 12 16
Galoy 01 06
Going Dutch 01 03 06
HangarSix 01 03
Infuse 01 03
Kollider 01 03 04
LNBIG 01 02
ln.cash 01 03
LNMarkets 01 03 04 06 16
LNPay.co 01 03 06 14
LNbits.com 01 03 04 14 15
Lightning.Video 01 04
Lightning Gifts 01 03 06 12
LightningTipBot 01 06 09 12 16
@lntxbot 01 03 06 09 12 16 18
Lnurl-Pay Chat 01 06 11 12 18
Loft 01 04
Microlancer 01 03 14
OpenNode 01 03
Paywall 01 03
Rewards to Bitcoin 01 03 04
Sats4Likes 01 03 14
Satsback.com 01 03 06 16
sms4sats 01 03
SouthXchange 01 03
Surfcity Parking 01 03
Wheel of Fortune 01 03 04
bridgeaddr 01 06 09 12 16
coinos 01 03 04 06 16
lnshort.it 01 04 06
lnsms.world 01 06 11 12 16
lnurl-pay.me 01 06 16
pollofeed 01 06 16
stacker.news 01 03 04 06 16
zbd.gg 01 03 06 09 12 16

Self-hosted

Name LUDs
Addressless 01 06 09 16
Bleskomat 01 03
BTCPayServer 01 06 16 17
Citadel Bitcoin Node 01 06 16
LNURLPoS 01 06 09
LNURLp 01 06 12
LNURLw 01 03
LNbits.com 01 03 04 14 15
LightningATM 01 03
NextPay 01 06 16
OfflineShop 01 06 09
Satdress 01 06 09 16
Streamer Copilot 01 06 12
go-host-lnaddr 01 06 09 16
ligess 01 06 09 16
lnme 01 06 09 16

Libraries

Name LUDs
IMMORTAN 01 02 03 04 05 06 07 08 09 10 11 12 16
LNURL C# 01 02 03 04 06 07 08 09 10 11 12 14 15 16 17 18 19
dart-lnurl 01 02 03 04 06
go-lnurl 01 02 03 04 06 08 09 10 11 12 14 16 18 20
js-lnurl 01 02 03 04 06 08 09 10 11 12
lnurl-node 01 02 03 04 06 08 09 10 11 12
lnurl-platformio 01 03
lnurl-ruby 01 06 09
lnurlauth 01 04
php-lnurl 01
python-lnurl 01 02 03 04 06
bitcoin-s 01 03 06 09
rust-lnurl 01 03 04
spring-lnurl 01 04

Tools for developers

Name LUDs
LNURLProxyAPI 01 03
Lightning Decoder 01 02 03 04 06 16
Lightning Login 01 04
bifrost 01 02
lnch-vekslak 01 02
lnurl codec JS 01
lnurl codec Scala 01
lnurl playground 01 02 03 04 06 09 10 12 14 15 18 20
lnurl-toolbox 01 02 03 04 06
passport-lnurl-auth 01 04

Dependency Tree

The entire idea of the suite of LNURL protocols is that they are optional. Each new LUD may be implemented by some wallets and not others, some services and not others, but they should still maintain compatibility at all times (except, of course, if the service requires the new functionality).

There is also a hierarchy of internal dependencies between the LUDs -- for example, you cannot implement sending comments in payRequests if you haven't implemented the base payRequest spec also. The following graph displays that hierarchy of internal dependencies (you can safely ignore it though).

dependencies

How to add your own document

Open a pull request with your proposal. Pick the next unreserved number for your proposal. To be accepted, it just has to be generally decent and make sense and be implemented or currently being implemented by 2 or more wallets.

Join https://t.me/lnurl if you just want to talk about your ideas or chat about LNURL protocols in general.

About

lnurl specifications

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published