📅 Original date posted:2014-03-14
📝 Original message:I think
* if we change to mBTC because your state currencys price for bitcoin
make this a valid option we will change again in future
* users do not like changes
* we should keep a good standard
A good standard should be
* built on standards (e.g. SI)
* backed by best practice: never force the user to take an option he
cannot change
* do not make changes without users permission
* take care of users at fault when entering 5.967 ot should be pointed
out before sending that e.g.
the sw understood 5967.000 000 00 BTC
instead of 5.967 000 00 BTC
because the user failed to use the correct delimiter.
For now a good standard is
* simply bitcoin as BTC with eight decimal places
or could be
* uBTC as SI prefix, probably using XBT as a symbol for compatibility
with other software
* satoshis (w. SI prefixes if numbers are to big) for regions where
decimal places in prices are uncommon
So I'd prefer:
Make the choice transparent to users and set a standard that the user
alway should be empowered to use all available decimal places.
And there should be a set of official test-cases for wallet software and
the desired behavior.
vv01f [ARCHIVE] /
npub16w…ws45h
2023-06-07 15:15:40
in reply to nevent1q…p7g3
Author Public Key
npub16wxlvxa5c25gcawkfcf7v6w8ray5scwm8t8y0qkxpfr3h5c5j0aqhws45hPublished at
2023-06-07 15:15:40Event JSON
{
"id": "6b661a664f147e991cc3c74d209e924a69d5027cf1edd6c40082e6f3777cfc09",
"pubkey": "d38df61bb4c2a88c75d64e13e669c71f494861db3ace4782c60a471bd31493fa",
"created_at": 1686150940,
"kind": 1,
"tags": [
[
"e",
"a5889b6003c7241c893062a271bfd01eb179b582d390c0baf2198e69cbfe2d2d",
"",
"root"
],
[
"e",
"af7b3abeaafa1894e38b8f4c7eaf90d6631921bfcfb79d2474d85cbced877228",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2014-03-14\n📝 Original message:I think\n* if we change to mBTC because your state currencys price for bitcoin\nmake this a valid option we will change again in future\n* users do not like changes\n* we should keep a good standard\n\nA good standard should be\n* built on standards (e.g. SI)\n* backed by best practice: never force the user to take an option he\ncannot change\n* do not make changes without users permission\n* take care of users at fault when entering 5.967 ot should be pointed\nout before sending that e.g.\nthe sw understood 5967.000 000 00 BTC\ninstead of 5.967 000 00 BTC\nbecause the user failed to use the correct delimiter.\n\nFor now a good standard is\n* simply bitcoin as BTC with eight decimal places\nor could be\n* uBTC as SI prefix, probably using XBT as a symbol for compatibility\nwith other software\n* satoshis (w. SI prefixes if numbers are to big) for regions where\ndecimal places in prices are uncommon\n\nSo I'd prefer:\nMake the choice transparent to users and set a standard that the user\nalway should be empowered to use all available decimal places.\nAnd there should be a set of official test-cases for wallet software and\nthe desired behavior.",
"sig": "ae52d6c08d107ee55e5306f97aed89709204c208a3fd3b62dbca89a6464e788054760ec16ee801b8da5ac8218e9f52353626f34c86f5e76d843df0bd15e9d9bf"
}