📅 Original date posted:2017-05-06
📝 Original message:
Olaoluwa Osuntokun <laolu32 at gmail.com> writes:
> However, it utilizes an
> encoding whose rationale make sense for the Bitcoin address use-case, but in
> my opinion, doesn't carry over those compelling traits to the LN payreq
> use-case.
I agree, but it's nice for QR codes too, and denser than hex. And now
we're using your key recovery idea, having a checksum is not
*completely* pointless.
I've implemented and pushed fallback addresses in the example
encoder/decoder, and tweaked the format slightly: the first 5-bit value
is the witness version, or 17 for p2pkh, 18 for p2sh. It's now
complete.
In some places the encoding is a little awkward (trying to get on 5 bit
boundaries), ideas welcome.
<Feedback please!
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 12:47:11
in reply to nevent1q…c6ld
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 12:47:11Event JSON
{
"id": "809ec7f65da6f4eaf2291f56cb74f885609fd627ea6dddcdf52e9b82480623eb",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686314831,
"kind": 1,
"tags": [
[
"e",
"56742c88f6265e0090cd0ac17729d1bb4693d9767822b89dc939db0c32d43bbb",
"",
"root"
],
[
"e",
"5d033e825e317a95a8bff9267d33881f9dcebe8fba9eb82400fdfaeae24c71a0",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "📅 Original date posted:2017-05-06\n📝 Original message:\nOlaoluwa Osuntokun \u003claolu32 at gmail.com\u003e writes:\n\u003e However, it utilizes an\n\u003e encoding whose rationale make sense for the Bitcoin address use-case, but in\n\u003e my opinion, doesn't carry over those compelling traits to the LN payreq\n\u003e use-case.\n\nI agree, but it's nice for QR codes too, and denser than hex. And now\nwe're using your key recovery idea, having a checksum is not\n*completely* pointless.\n\nI've implemented and pushed fallback addresses in the example\nencoder/decoder, and tweaked the format slightly: the first 5-bit value\nis the witness version, or 17 for p2pkh, 18 for p2sh. It's now\ncomplete.\n\nIn some places the encoding is a little awkward (trying to get on 5 bit\nboundaries), ideas welcome.\n\n\u003cFeedback please!\nRusty.",
"sig": "222a4b76558e16b3b253b2328448ec2a740f745205d25b983065ddf8167a8e2a544f336f60d3c72804708f593d15da082d850efcc0bf1807ab47f63b0ea842b1"
}