public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Marcel Jamin <marcel@jamin.net>
To: "David A. Harding" <dave@dtrt.org>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Utilization of bits denomination
Date: Thu, 14 Dec 2017 09:02:44 +0100	[thread overview]
Message-ID: <CAAUq485pTYs++FY9GkAt64gvba_Mngzpui7TWXdQM-x9GyAQdg@mail.gmail.com> (raw)
In-Reply-To: <20171213213607.ijlvqwpdaokucgi6@fedora-23-dvm>

On 13 December 2017 at 22:36, David A. Harding via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> - Microbitcoins is not a homonym for any other word in English (and
>   probably not in any other language), whereas "bit" and "bits" have
>   more than a dozen homonyms in English---some of which are quite common
>   in general currency usage, Bitcoin currency usage, or Bitcoin
>   technical usage.

Reposting /u/BashCo's post on reddit here, for visibility:

---8<---------------------------------------------------------------

> Before anyone says 'bits' are too confusing because it's a computer science term, here's a list of homonyms [https://en.wikipedia.org/wiki/List_of_true_homonyms] that you use every day. Homonyms are fine because our brains are able to interpret language based on context, so it's a non-argument. Also, the term 'bits' was used in reference to money long before 'bits and bytes' came along, and even before the metric system itself.

> https://en.wikipedia.org/wiki/Bit_(money)

> https://en.wikipedia.org/wiki/Spanish_colonial_real

> 'Bits' are superior to mBTC partly because we'll need to transition to bits eventually anyways (one transition is easier than two), but more importantly, bits have two decimal places, matching the format of dozens of other major currencies.

> No other currency has 8 decimal places, or even 4 decimal places. Most of them have 2. Dollars and cents, Bits and satoshis.

> If people actually want this to happen, then they need to train their own brains by switching their wallets and exchange settings to bits. The shift will probably happen eventually, although the major Bitcoin denomination probably isn't going anywhere any time soon, even if the majority of people use 'bits' as a matter of habit.

> 99.99 bits is currently equal to $1.63 USD.

---8<---------------------------------------------------------------

>
> - Microbitcoins trains users to understand SI prefixes, allowing them to
>   easily migrate from one prefix to the next.  This will be important
>   when bitcoin prices rise to $10M USD[1] and the bits denomination has
>   the same problems the millibitcoin denomination has now, but it's also
>   useful in the short term when interacting with users who make very
>   large payments (bitcoin-scale) or very small payments
>   (nanobitcoin-scale).[2]  Maybe a table of scale can emphasize this
>   point:
>
>       Wrong (IMO):        Right (IMO):
>       ---------------     --------------
>       BTC                 BTC
>       mBTC                mBTC
>       bits                µBTC
>       nBTC                nBTC
>

I wouldn't expect people to type out µBTC. I think the best you can
hope for here is uBTC. As for saying "microbitcoins", I can virtually
guarantee that this will be abbreviated to "microbits" and/or
eventually "bits" anyway. Bits and sats.

> [1] A rise in price to $10M doesn't require huge levels of growth---it
> only requires time under the assumption that a percentage of bitcoins will
> be lost every year due to wallet mishaps, failure to inherit bitcoins,
> and other issues that remove bitcoins from circulation.  In other words,
> it's important to remember that Bitcoin is expected to become a
> deflationary currency and plan accordingly.
>
> [2] Although Bitcoin does not currently support committed
> nanobitcoin-scale payments in the block chain, it can be supported in a
> variety of ways by offchain systems---including (it is hypothesized)
> trustless systems based on probabilistic payments.
>
> Thanks,
>
> -Dave
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>


  reply	other threads:[~2017-12-14  8:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 19:46 [bitcoin-dev] BIP Proposal: Utilization of bits denomination Jimmy Song
2017-12-13 21:36 ` David A. Harding
2017-12-14  8:02   ` Marcel Jamin [this message]
2017-12-14 22:01     ` Natanael
2017-12-14 23:11       ` Clark Moody
2017-12-15  6:27       ` Marcel Jamin
2017-12-15 18:20         ` Moral Agent
2017-12-15 18:46           ` Rhavar
2017-12-14 15:52   ` Sjors Provoost
     [not found] <CADPKye1m2_5PaqedMU9nPsmvpW-3S+LSoqt0LnQLXXk=MjDJew@mail.gmail.com>
     [not found] ` <CADPKye39X_QFi_G0we39ZWXAQme=veC1hCfc_fFFwjs15Op=Lw@mail.gmail.com>
     [not found]   ` <CADPKye1FjsjG9gO7oWngx2LDnVqRQT_ia4Ke-wPfCRbXjnfZCg@mail.gmail.com>
     [not found]     ` <CADPKye03UUnJ5T94m8OdBNC5k8wnXGVB-xpbqf363gzTtfN_6A@mail.gmail.com>
     [not found]       ` <CADPKye2H66iZt=uOz765zrVtv_toeAzfoJXaqQvJaUtadqjDwg@mail.gmail.com>
     [not found]         ` <CADPKye35ZxJDcfM2e+pvw+z6eZEyzj1-6VDcpHP6Z5FtX-=GOQ@mail.gmail.com>
     [not found]           ` <CADPKye0JD5kfmsGb-AzO6EfPubOGUXtxaEqizLQUQ3QJmCMLJQ@mail.gmail.com>
     [not found]             ` <CADPKye0_eozpfG35qCmPKX-MX+qYZBLt5peU0_jBOCfVoZfefQ@mail.gmail.com>
     [not found]               ` <CADPKye0PSwH_bMYa9DzRos9SgL4e2Vid1gEKnNtcUKQB-op5UQ@mail.gmail.com>
     [not found]                 ` <CADPKye04MRZkWtZm1mWnjmSe97v0-iZwAdYH6pSrFjpHfzuQ-w@mail.gmail.com>
     [not found]                   ` <CADPKye2Ozj6rqApztKyoeJvekofdaiP1=jbd6buxFTebEantMA@mail.gmail.com>
     [not found]                     ` <CADPKye3hyOH4Z+y_JgJUfEspSt8jL+ZGaU05v_fX3Wiwr2-N9g@mail.gmail.com>
     [not found]                       ` <CADPKye11prrk663bWAatFCkjktJNgemg-ECdZdP07RECWcE6nQ@mail.gmail.com>
     [not found]                         ` <CADPKye1+z2aUBXc3UECvmoNSGO23hXGzGXekFOTPy-rdHFG_Nw@mail.gmail.com>
     [not found]                           ` <CADPKye0i0LaGgS4Hmp086LLCnPEHNYqJ+VbZ2h2DxycTwY2srQ@mail.gmail.com>
     [not found]                             ` <CADPKye0dj5z=hDbooUOY-vhP0N+L=VzhOGn3Wue4tPgY3vnHwA@mail.gmail.com>
     [not found]                               ` <CADPKye3Z8PDe_5D28hcELDurtpr=5wgzazw3RT=Fc3gUDvhcng@mail.gmail.com>
     [not found]                                 ` <CADPKye0-JwfDJruc00XXd55Gm0Ho4c5EKGxqcCqyuFcTY=omYQ@mail.gmail.com>
     [not found]                                   ` <CADPKye27FpEYtO31XjX6KcG59HjfZzaGGW0gayO-xZVbdb7jtg@mail.gmail.com>
     [not found]                                     ` <CADPKye0Kt87cHbuOqphMOPY3TPmO1awH46k17rEoVZ4kAejkxw@mail.gmail.com>
2017-12-13 23:00                                       ` Daniel McNally
2017-12-24  4:26 Tamas Blummer

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=CAAUq485pTYs++FY9GkAt64gvba_Mngzpui7TWXdQM-x9GyAQdg@mail.gmail.com \
    --to=marcel@jamin.net \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=dave@dtrt.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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