public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Thomas Voegtlin <thomasv1@gmx•de>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] "bits": Unit of account
Date: Mon, 21 Apr 2014 10:52:56 +0200	[thread overview]
Message-ID: <5354DC68.5040602@gmx.de> (raw)
In-Reply-To: <CANOOu=-JB4nZpEPRq+X_JBHJsGGvOsTVKROkciRu4SCp_EL4Vg@mail.gmail.com>

Let me make a sacrilegious proposal: keep using the name "bitcoin", and
shift the decimal point.

There would be a short adaption period, where people will need to talk
about "new bitcoins" and "old bitcoins" in order to disambiguate them.
However, Bitcoin users are techies, so I don't think that the ambiguity
will be a big issue. I don't think lots of people will mistakenly send
1000 times more than the amount they intended.

The name "bitcoin" has a huge advantage over any other proposal, because
it is already established. No marketing is needed.

This kind of renaming has already taken place many times in history,
because the currency was debased. Bitcoin would be the first time it
happens in the other direction.




  reply	other threads:[~2014-04-21  8:53 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 [this message]
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
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=5354DC68.5040602@gmx.de \
    --to=thomasv1@gmx$(echo .)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