{"type":"rich","version":"1.0","author_name":"npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","author_url":"https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-13\n📝 Original message:On Thu, Mar 13, 2014 at 9:53 AM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\u003e BitPay should use mBTC as well. Unless you can point to any major wallets,\n\u003e exchanges or price watching sites that use uBTC by default?\n\u003e\n\u003e I think it is highly optimistic to assume we'll need another 1000x shift any\n\u003e time soon. By now Bitcoin isn't obscure anymore. Lots of people have heard\n\nSuch hand-wavy, data-free logic is precisely why community\ncoordination is preferred to random apps making random decisions in\nthis manner.\n\nmBTC is problematic because you do not need 1000x shift in value to\nproduce annoyances for major accounting packages that are hard-limited\nto two decimal places.  Further, spreadsheets hide information if\nformatting is configured naively -- that is, if formatting is\nconfigured for bitcoin the way it is configured for other currencies.\n\nFundamentally, more than two decimal places tends to violate the\nPrinciple Of Least Astonishment with many humans, and as a result,\npopular software systems have been written with that assumption.\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc.      https://bitpay.com/"}