public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel McNally <therealsangaman@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP Proposal: Utilization of bits denomination
Date: Wed, 13 Dec 2017 18:00:02 -0500	[thread overview]
Message-ID: <CADPKye3r+ZRGFqdF2ihyuJomzQNemUU+4+TprouPhZu_OGu89Q@mail.gmail.com> (raw)
In-Reply-To: <CADPKye0Kt87cHbuOqphMOPY3TPmO1awH46k17rEoVZ4kAejkxw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2440 bytes --]

I think standardization of this term is a great idea. I second all of
Jimmy's points. I think the analogy of dollars & cents to bits and satoshis
is easy to grasp, particularly given that satoshis and cents are the
smallest tangible units of their respective currencies. It's a concept
that's common across cultures and countries as it also applies to pounds
and pence, pesos and centavos, etc...

To David's points, I agree that it's not ideal that bit is a homonym for
other words, but I don't think it's a terrible flaw as context will usually
make the meaning clear. I'm actually not in love with the term "bit," but
rather the idea of a non-SI term for a millionth of a bitcoin. But bit has
already caught on to some extent and I can't think of anything better.


> - 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]


I find the SI prefixes to be very user unfriendly. I have plenty of smart
friends and family who constantly confuse mega, giga, micro, nano, and so
on. Rather than try to train users, I think we should choose terms that
will be easy for them to grasp right away. Even for people fluent in SI
terms, I think some of the problems regarding unit bias still exist. 500
microbitcoins sounds diminutive and uttering it is a reminder that it's a
very small fraction of a larger unit. 500 bits sounds like you have 500 of
something, neat!

I consider "bits" to be a term that's quite future proofed. While I won't
dismiss the possibility of $10M or $100M bitcoins in the not-too-distant
future, there would still be plenty of time for a bit to be a useful
day-to-day unit. Even at the $10M point, small ticket items like coffee
could still be priced at 0.30 bits for example, not bad I'd say.

Should bitcoin ever soar past the $100M mark, it might be time for a new
term akin to bits and maybe a hard fork to allow for more decimal places on
chain. A nanobitcoin could not be transacted with today anyhow. These would
all be good problems to have.

Thanks for reading and thanks to Jimmy for taking the initiative with this
BIP.

Daniel

[-- Attachment #2: Type: text/html, Size: 3291 bytes --]

       reply	other threads:[~2017-12-13 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2017-12-24  4:26 Tamas Blummer
  -- strict thread matches above, loose matches on Subject: below --
2017-12-13 19:46 Jimmy Song
2017-12-13 21:36 ` David A. Harding
2017-12-14  8:02   ` Marcel Jamin
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

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=CADPKye3r+ZRGFqdF2ihyuJomzQNemUU+4+TprouPhZu_OGu89Q@mail.gmail.com \
    --to=therealsangaman@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /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