reply on: Stacker Saloon \ stacker news

pull down to refresh

6 sats \ 23 replies \ @nemo 24 Sep 2023 \ parent \ on: Stacker Saloon

deleted by author

9 sats \ 21 replies \ @Natalia 24 Sep 2023

deleted after seen

11 sats \ 17 replies \ @DarthCoin 24 Sep 2023

You can also send a 1 sat message attached to his LN address or nodeID (if you know it) as keysend. That could be another secret way to communicate this stuff...

Just a tip.

6 sats \ 0 replies \ @nemo 24 Sep 2023

deleted by author

0 sats \ 15 replies \ @Natalia 24 Sep 2023

deleted by author

7 sats \ 14 replies \ @DarthCoin 24 Sep 2023

I wasn't talking about SN address. I know that is not supporting yet LUD12. Hear that @k00b ?

when SN lndhub account
when support for LUD12 and 18 ?

0 sats \ 8 replies \ @WeAreAllSatoshi 24 Sep 2023

LUD18 doesn't seem to be quite as widely adopted from a wallet perspective¹. It shouldn't be too hard to implement from a receiver side, but if not many wallets support sending it, it's probably lower on the priority list to support, if I had to guess.

https://github.com/lnurl/luds/tree/luds ↩

87 sats \ 7 replies \ @DarthCoin 24 Sep 2023

Be the example... don't wait for other to be for you. Few implemented because they do not know the power of it.

100 sats \ 5 replies \ @WeAreAllSatoshi 24 Sep 2023

Good point, re-reading the spec I see some of the potential usefulness of it aside from associated arbitrary identity data on the invoice. Good looking out, Darth!