Matt Corallo
Matt Corallo
While it can't be perfect, it's totally possible to do as well as is reasonable - assuming a smart server, it can rotate any time it sees the address it...
That is correct for this name, but you can't universally exclude `NSEC3`/`NSEC` records, they may be needed in cases where you hit a wildcard. There's a pretty good set of...
There's also logic to build a proof you can crib from at https://git.bitcoin.ninja/?p=dnssec-prover;a=blob;f=src/query.rs;h=cd7fe6a01a4be19858310f9b55a3d435daa9cfb4;hb=HEAD
Nice! I could test a Linux/x64 build.
Ah, I guess its a bit hard for me to test without funds in a sparrow wallet 😅 . I hacked up a quick and dirty tester at https://satsto.me/prooftest.html which...
Nice! I think those are the ones that are most likely to be broken (they test many of the edge-cases - cross-TLD linking, wilcards, and NSEC inclusion), as long as...
> I often felt while working on this that "BIP 353 HRNs" need a better name. The obvious is "bitcoin address" but that's already widely used for normal onchain addresses....
> I couldn't find a place to discuss it there, but I propose Bitcoin Readable Address (BRA). I believe you can open an issue on https://github.com/BitcoinDesign/Guide/ AFAIR the conclusion of...
In general I prefer that we let the `MessageRouter` decide the kind of blinded paths it wants the `ChannelManager` to use. This is for a few reasons, (a) it is...
Maybe we should discuss whether we're happy with delving, it doesn't really seem like people are really using it for lightning discussion.