pull down to refresh
Yup. To add to what @DarthCoin said, here's the basic rule around how changes are merged into the common Lightning spec:
Spelling, typo and formatting changes are accepted once two contributors ack and there are no nacks. All other changes get approved and minuted at the spec meeting. Protocol changes require two independent implementations which successfully inter-operate; be patient as spec changes are hard to fix later, so agreement can take some time.[1]
The splicing spec was merged now that discussions are over and there's interrop between Eclair and LDK[2] (and I think also Core Lightning[3]) it has been merged with 2+ ACKs into the main spec.
Yes, specification work takes time between drafting and reaching interoperability. Merged this morning.
Thanks for your comment! I wrote the part on Satring last week so it might have aged a bit since then 😅 I saw the domain verification/restore feature with the .well-known, pretty cool.
Do you have any early usage (by agents) stats? Or is it still too early?
Thank you! Yes these topics often have their own posts on SN (eh, sometimes it's how I first hear about them), so it'd probably make sense to link to these discussions for the SN version of the issue. Thanks for doing the work here!
Unofficial Bounties of 1,000 sats for person who has the link to one of the original writeups dictating a configuration implementing wireguard VPN + reverse-proxy (they didn't call it that, but that's what it is. Sounds cool, because it is cool). #revengeofthenerds
I don't know if that's what you have in mind, but I've used this guide from Warren Togami in the past. Seems unmaintained though.
Pretty neat UI, reminds me of UberEats, which arguably nails food ordering experience.
Yup, Victor explains that users connect their Aqua wallet via the SamRock protocol.