📅 Original date posted:2017-05-09
📝 Original message:
Christian Decker <decker.christian at gmail.com> writes:
> 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 :-)
Well, Pieter can pronounce them too apparently:
http://pieterwuillefacts.com/?43
>> 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).
I considered using the m/u/n modifier as the decimal point, eg:
0.0001c = 0n62
0.01c = 62n5
1c = 6u25
$1 = 625u
$1000 = 625m
Unfortunately, it's horrible to write the code to encode/decode (I just
spend an hour on it and I'm not happy with the result).
>> 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.
Huh? I just did exactly the same thing! So I'll take BOLT 11.
Cheers,
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 12:47:12
in reply to nevent1q…2c0n
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 12:47:12Event JSON
{
"id": "e3a45fd962b23ffcce2b039672de7ae0fad6810101eae8baeefbd7b67454003c",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686314832,
"kind": 1,
"tags": [
[
"e",
"56742c88f6265e0090cd0ac17729d1bb4693d9767822b89dc939db0c32d43bbb",
"",
"root"
],
[
"e",
"b3ebcee0525cfba38c185c2d2f648b333ab7655850c37e7ee10014a4c4d23841",
"",
"reply"
],
[
"p",
"72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057"
]
],
"content": "📅 Original date posted:2017-05-09\n📝 Original message:\nChristian Decker \u003cdecker.christian at gmail.com\u003e writes:\n\u003e On Tue, May 09, 2017 at 11:07:28AM +0930, Rusty Russell wrote:\n\u003e\u003e Hey, invoices are totally human readable, for some humans :)\n\u003e\u003e \n\u003e I know Pieter can decode bech32 on the fly :-)\n\nWell, Pieter can pronounce them too apparently:\n\n http://pieterwuillefacts.com/?43\n\n\u003e\u003e But a good point. So let's use BTC with m (milli), u (micro), n (nano)\n\u003e\u003e and p (pico). In theory we could allow . in that part, but I think it's\n\u003e\u003e too distracting.\n\u003e\u003e \n\u003e\u003e At $1600/BTC:\n\u003e\u003e \n\u003e\u003e 0.01c = 62500p\n\u003e\u003e 1c = 6250n\n\u003e\u003e $1 = 625u\n\u003e\u003e $1000 = 625m\n\u003e\n\u003e Perfect, even though your price is already outdated, and it currently\n\u003e is $1700/BTC. I mention the conversion confusion because I often run\n\u003e into that problem myself (and keep typing 0s until the client\n\u003e complains).\n\nI considered using the m/u/n modifier as the decimal point, eg:\n\n 0.0001c = 0n62\n 0.01c = 62n5\n 1c = 6u25\n $1 = 625u \n $1000 = 625m\n\nUnfortunately, it's horrible to write the code to encode/decode (I just\nspend an hour on it and I'm not happy with the result).\n\n\u003e\u003e OK, if people like this change, I think we can move start turning this\n\u003e\u003e into BOLT 10?\n\u003e\n\u003e Oops, I think I did what Luke hates, and sort of self assigned a\n\u003e proposal number... I can of course assign the DNS bootstrap BOLT\n\u003e another number.\n\nHuh? I just did exactly the same thing! So I'll take BOLT 11.\n\nCheers,\nRusty.",
"sig": "66abf01e03a7a5ffea0ce0f7214b6c6b380c17a0199c55899a3f0cbc5509bea301cb919004ddfdc93398b4bdbbd2935eee1ad66bd75a22223758110c9f63d2b6"
}