Hi Bastien,
thanks for verifying my proposal, and I do share your concerns regarding
privacy leaks (how many hops are encoded in the onion) and success ratio
if a payment is based on a fixed (partial) path.
> I believe this makes it quite usable in Bolt 11 invoices, without blowing up
> the size
Hi Christian,
This is great, thanks for sharing!
What's really nice with your proposal is that there is effectively no onion
payload for `RV` in the partial onion, which frees up more space than mine.
I believe this makes it quite usable in Bolt 11 invoices, without blowing up
the size of the QR
Hi Bastien,
seems you were a bit quicker than I was with my writeup of my
proposal. I came up with a scheme that allows us to drop a large part of
the partial onion, so that it can indeed fit into an outer onion, and
the rendez-vous node RV can re-construct the original packet from the
included
Good morning list,
After exploring decoys [1], which is a cheap way of doing route blinding,
I'm turning back to exploring rendezvous.
The previous mails on the mailing list mentioned that there was a
technicality
to make the HMACs check out, but didn't provide a lot of details.
The issue is that
