From: Jannis Froese <s9jafroe@stud•uni-saarland.de>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] "bits": Unit of account
Date: Sun, 20 Apr 2014 19:47:05 +0200 [thread overview]
Message-ID: <53540819.3050908@stud.uni-saarland.de> (raw)
In-Reply-To: <87BC4D35-2E10-40A0-B2FE-4C49184C0565@swipeclock.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I agree that a unit based on 1e-6 BTC is easier to use in practice
than BTC. The name microbitcoin is ok-ish. Nearly all countries
officially use the SI-system, but that doesn't mean that the average
citizen knows all the SI prefixes. Mega, kilo and milli are
universally understood, micro not so much. This is a serious
accessibility concern.
But I dislike the term bit for the already stated reasons: It's
already used in various languages for various things. Simply using
Satoshis may be easier and is universally understood.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTVAgZAAoJEBrvn3PsoRcmWYgP/0JMXmJjzdBFBQscl3+yA987
4zD+W+7o/wPqRmtCU9voJ1PFj9zM6zagHAz455wjnF4IwdgYZjqtadyfxgP5Mg8p
WGoplGQPWJ5KorsQfbiJP8uTOfTzJK5p6Aw9DwscN4aBjCMaHskvyWGVpE8U7ibQ
Pk+a6lX1UUOnjm/G7v5UDKFSlUGAe0GCTnI8FDjxAfF8mzS9XzMSPCfbZfoc7eEx
F7yKkAQGZCDJKP4y6oenj4CGXn100KSZEmombNQ7PeOEwqcKsd1RgPtHWTZzb0Ya
hk2sSnEEt05uwyYsGRnb1EYUwiSS/6sgT9m7fU3bpFf3dWqGuMweSVuGgCTMPrRb
3ei18TJAI59lF/du5zbhQOujpNx/ocmf538hcpFkqaM3RTpeXifaSAefp37S5Zbq
xw013M5T55SmJZYQwdWTFA689kvmOT1N33ht2QtSszl6ZJDFOrwICdcIqMsS6a0a
cGcigi2Ru4M9J7w7wk448ky22Z8VjZrKTQFqhiKzoRk2t0N/SQbKSFKCm7ffsAB/
7EGB9cA3va5ZFBnDAae84Vj0RAMJDHYO7VZIg/mF5qNs8YWs6okQoeJ8FMfNAhW2
pDgZdJfl46lnzfQvgiV/jAMkFr/oSj0UZUPAWXbaGcAm3ZFNO4B0SgNB2VYUfLIe
VNW1pzTKiwL83RjNTGfV
=EPvS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-04-20 17:47 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 12:35 Mike Gehl
2014-04-20 13:15 ` Rob Golding
2014-04-20 14:28 ` Tamas Blummer
2014-04-20 14:52 ` Christophe Biocca
2014-04-21 8:52 ` Thomas Voegtlin
2014-04-21 9:34 ` Tamas Blummer
2014-04-22 14:55 ` Natanael
2014-04-20 14:53 ` Pieter Wuille
2014-04-20 15:05 ` Tamas Blummer
2014-04-20 15:50 ` Alan Reiner
2014-04-20 16:19 ` Chris Pacia
2014-04-20 16:27 ` Wladimir
2014-04-20 16:30 ` Chris Pacia
2014-04-22 13:51 ` Aaron Axvig
2014-04-23 9:44 ` Danny Hamilton
2014-04-23 9:56 ` Tamas Blummer
2014-04-23 11:48 ` Chris D'Costa
2014-04-20 16:23 ` Erik Garrison
2014-04-20 16:30 ` Alan Reiner
2014-04-20 16:56 ` Mike Caldwell
2014-04-20 17:47 ` Jannis Froese [this message]
2014-04-20 18:10 ` Pavol Rusnak
2014-04-20 17:42 ` Arne Brutschy
2014-04-20 18:11 ` Mike Caldwell
2014-04-20 18:22 ` Arne Brutschy
2014-04-20 18:34 ` Mike Caldwell
2014-04-20 18:43 ` Oliver Egginger
2014-04-20 19:19 ` Christophe Biocca
2014-04-20 19:32 ` Gmail
2014-04-20 20:28 ` Mike Caldwell
2014-04-21 0:16 ` Justin A
2014-04-21 1:18 ` Mike Caldwell
2014-04-21 1:33 ` Un Ix
2014-04-21 3:34 ` Mike Caldwell
2014-04-21 4:08 ` Christopher Paika
2014-04-21 5:41 ` Pieter Wuille
2014-04-21 5:51 ` Tamas Blummer
2014-04-21 6:21 ` Tamas Blummer
2014-04-21 12:14 ` Un Ix
2014-04-21 12:24 ` Tamas Blummer
2014-05-01 22:35 Aaron Voisine
2014-05-03 2:06 ` Gordon Mohr
2014-05-03 5:41 ` Aaron Voisine
2014-05-03 15:48 ` Christophe Biocca
2014-05-03 16:02 ` slush
2014-05-03 16:10 ` Tamas Blummer
2014-05-03 16:27 ` Mike Caldwell
2014-05-04 1:04 ` Chris Pacia
2014-05-04 5:18 ` Drak
2014-05-04 6:15 ` Aaron Voisine
2014-05-04 6:23 ` Un Ix
2014-05-04 6:27 ` Wladimir
2014-05-04 6:36 ` Tamas Blummer
2014-05-04 6:59 ` Wladimir
2014-05-04 14:42 ` Mike Caldwell
2014-05-05 22:33 ` Gordon Mohr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53540819.3050908@stud.uni-saarland.de \
--to=s9jafroe@stud$(echo .)uni-saarland.de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox