Avatar
daywalker
b733b84bc61902fe4b31d34748c3132ecc6b9f3be95f771613e575a8c6659aae
Replying to Avatar jb55

Just need a way to include a some data (a zap request nostr note) when fetching a bolt12 invoice. Not sure if thats possible nostr:npub179e9tp4yqtqx4myp35283fz64gxuzmr6n3yxnktux5pnd5t03eps0elz4s

With lnurl we include this in the deschash (cln stores the original). So we can retrieve it when the invoice is paid and then we can send the zap.

You can use the payer_note field during invoice fetching to put some data in the invoice

Who still uses ONLY nip04 de/encryption in their NWC code? Can we drop nip04 already?

I want that hook filter!

true, too many projects try to make a perfect release and don't release for more than a year which makes alot of people think the project is dead.

Day 1270 of waiting for taproot multisig self custody with atleast 3 different hardware manufacturers.

Can someone make a progress overview like https://en.bitcoin.it/wiki/Bech32_adoption

I'm using my own relay now, but i tested the alby relay and atleast it didn't complain about content length or a few transactions done. I did not test multiple different NWC's with different pubkeys on the same relay tho. Definitely the best public relay yet!

What relays are you using for NWC? I get rate limited fast on public ones...

assert False so i can see the logs to double check the tests aren't wrong

Yes, both `fundchannel` and `multifundchannel` have a `utxos` argument.