Christian Decker [ARCHIVE] on Nostr: 📅 Original date posted:2017-05-09 📝 Original message: On Tue, May 09, 2017 at ...
📅 Original date posted:2017-05-09
📝 Original message:
On Tue, May 09, 2017 at 11:07:28AM +0930, Rusty Russell wrote:
> Hey, invoices are totally human readable, for some humans :)
>
I know Pieter can decode bech32 on the fly :-)
> But a good point. So let's use BTC with m (milli), u (micro), n (nano)
> and p (pico). In theory we could allow . in that part, but I think it's
> too distracting.
>
> At $1600/BTC:
>
> 0.01c = 62500p
> 1c = 6250n
> $1 = 625u
> $1000 = 625m
Perfect, even though your price is already outdated, and it currently
is $1700/BTC. I mention the conversion confusion because I often run
into that problem myself (and keep typing 0s until the client
complains).
> > Other than that, I really like the proposal, it's clean and
> > extensible, and it supports testnet ;-) I also like using bech32 as a
> > serialization format, if people also support the DNS bootstrapping and
> > node lookup they can simply reuse that dependency, and it is a bit
> > shorter than hex. We might consider also supporting a different, human
> > readable, encoding though (without changing the signature
> > serialization). And finally we could directly derive a URI scheme from
> > the bech32 encoded string by replacing the '1' with a ':', but we can
> > spin that discussion off in another thread ^^
>
> OK, if people like this change, I think we can move start turning this
> into BOLT 10?
Oops, I think I did what Luke hates, and sort of self assigned a
proposal number... I can of course assign the DNS bootstrap BOLT
another number.
Cheers,
Christian
Published at
2023-06-09 12:47:12Event JSON
{
"id": "b3ebcee0525cfba38c185c2d2f648b333ab7655850c37e7ee10014a4c4d23841",
"pubkey": "72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057",
"created_at": 1686314832,
"kind": 1,
"tags": [
[
"e",
"56742c88f6265e0090cd0ac17729d1bb4693d9767822b89dc939db0c32d43bbb",
"",
"root"
],
[
"e",
"4a87422b417969c7c1f5898a2865b128a6d7a109d3c6774202f09deb7012ec5a",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "📅 Original date posted:2017-05-09\n📝 Original message:\nOn Tue, May 09, 2017 at 11:07:28AM +0930, Rusty Russell wrote:\n\u003e Hey, invoices are totally human readable, for some humans :)\n\u003e \nI know Pieter can decode bech32 on the fly :-)\n\n\u003e But a good point. So let's use BTC with m (milli), u (micro), n (nano)\n\u003e and p (pico). In theory we could allow . in that part, but I think it's\n\u003e too distracting.\n\u003e \n\u003e At $1600/BTC:\n\u003e \n\u003e 0.01c = 62500p\n\u003e 1c = 6250n\n\u003e $1 = 625u\n\u003e $1000 = 625m\n\nPerfect, even though your price is already outdated, and it currently\nis $1700/BTC. I mention the conversion confusion because I often run\ninto that problem myself (and keep typing 0s until the client\ncomplains).\n\n\u003e \u003e Other than that, I really like the proposal, it's clean and\n\u003e \u003e extensible, and it supports testnet ;-) I also like using bech32 as a\n\u003e \u003e serialization format, if people also support the DNS bootstrapping and\n\u003e \u003e node lookup they can simply reuse that dependency, and it is a bit\n\u003e \u003e shorter than hex. We might consider also supporting a different, human\n\u003e \u003e readable, encoding though (without changing the signature\n\u003e \u003e serialization). And finally we could directly derive a URI scheme from\n\u003e \u003e the bech32 encoded string by replacing the '1' with a ':', but we can\n\u003e \u003e spin that discussion off in another thread ^^\n\u003e \n\u003e OK, if people like this change, I think we can move start turning this\n\u003e into BOLT 10?\n\nOops, I think I did what Luke hates, and sort of self assigned a\nproposal number... I can of course assign the DNS bootstrap BOLT\nanother number.\n\nCheers,\nChristian",
"sig": "f64421ead09270ad4b3dbbfb63c145ca5fc048300ca21fcf326ce192fcfc0002b8a229981be2a2f9eacbf6f96d671c8924faadda70d403a2fcdb40f34726430a"
}