public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sjors Provoost <sjors@sprovoost.nl>
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 16:52:24 +0100	[thread overview]
Message-ID: <B8087CB6-CBF7-43C6-8368-9E98523FB68B@sprovoost.nl> (raw)
In-Reply-To: <20171213213607.ijlvqwpdaokucgi6@fedora-23-dvm>

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

As much as I love SI standards, "trains users to understand SI prefixes, allowing them to
easily migrate from one prefix to the next" seems unrealistic. The metric system is about to
have its 220th birthday and people in the US still don't use it.

It makes sense to embrace terms that stick. "bits" as a formal-yet-informal alias for µBTC makes sense to me, unless someone can point to another term that's already commonly used.

I'm not too worried about the word bit having other meanings in common language. The word "bit coin" was introduced in the English language without a problem. A "bit" being 1 millionth of a "bit coin" doesn't seem too difficult. It will give a while new meaning to the expression "a bit expensive" :-)

Rather than nano-bitcoin, I would suggest milli bits.


It's rather unfortunate that 1 satoshi was defined as 10^-8 BTC instead of 10^-9. We could redefine satoshi to 10^-9 BTC. Then we can use kilo-satoshi instead of bits. Then the next step can be satoshi, followed by millisatoshi (you never know).

The smallest amount that can be handled by bitcoin software under this redefinition would be 10 satoshi rather than 1; mostly a matter of changing some source code comments.

The only place where I've seen the unit "satoshi" used is fee estimators. I think it's still early enough that people aren't terribly attached to the numbers shown on those sites (most people express fees in fiat terms, especially when complaining). We could switch from vbytes to weight units at the same time.

Sjors

> Op 13 dec. 2017, om 22:36 heeft David A. Harding via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> het volgende geschreven:
> 
> On Wed, Dec 13, 2017 at 01:46:09PM -0600, Jimmy Song via bitcoin-dev wrote:
>> Hey all,
>> 
>> I am proposing an informational BIP to standardize the term "bits". The
>> term has been around a while, but having some formal informational standard
>> helps give structure to how the term is used.
>> 
>> https://github.com/jimmysong/bips/blob/unit-bias/bip-unit-bias.mediawiki
> 
> Wallets and other software is already using this term, so I think it's a
> good idea to ensure its usage is normalized.
> 
> That said, I think the term is unnecessary and confusing given that
> microbitcoins provides all of the same advantages and at least two
> additional advantages:
> 
> - 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.
> 
> - 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
> 
> [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


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-12-14 15:52 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
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 [this message]
     [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=B8087CB6-CBF7-43C6-8368-9E98523FB68B@sprovoost.nl \
    --to=sjors@sprovoost.nl \
    --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