From: Jimmy Song <jaejoon@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP Proposal: Utilization of bits denomination
Date: Wed, 13 Dec 2017 13:46:09 -0600 [thread overview]
Message-ID: <CAJR7vkqcBo+o9BL8sK1TBqqNUNSMWdut_aL_YMXse8rDC2ju9A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3499 bytes --]
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
Entire BIP included below (mediawiki format) for convenience.
Best,
Jimmy
----------
<pre>
BIP: ????
Title: Utilization of bits denomination
Author: Jimmy Song <jaejoon@gmail•com>
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-????
Status: Draft
Type: Informational
Created: 2017-12-12
License: BSD-2-Clause
License-Code: BSD-2
</pre>
== Abstract ==
Bits is presented here as the standard term for 100 (one hundred) satoshis
or 1/1,000,000 (one one-millionth) of a bitcoin.
== Motivation ==
The bitcoin price has grown over the years and once the price is past
$10,000 USD or so, bitcoin amounts under $10 USD start having enough
decimal places that it's difficult to tell whether the user is off by a
factor of 10 or not. Switching the denomination to "bits" makes
comprehension easier. For example, when BTC is $15,000 USD, $10.50 is a
somewhat confusing 0.00067 BTC, versus 670 bits, which is a lot clearer.
Additonally, reverse comparisons are easier as 67 bits being $1 is easier
to comprehend for most people than 0.000067 BTC being $1. Similar
comparisons can be made to other currencies: 1 yen being 0.8 bits, 1 won
being 0.07 bits and so on.
Potential benefits of utilizing "bits" include:
# Reduce user error on small bitcoin amounts.
# Reduce unit bias for users that want a "whole" bitcoin.
# Allow easier comparisons of prices for most users.
# Allow easier bi-directional comparisons to fiat currencies.
# Allows all UTXO amounts to need at most 2 decimal places, which can be
easier to handle.
== Specification ==
Definition: 1 bit = 1/1,000,000 bitcoin.
Plural of "bit" is "bits". The terms "bit" and "bits" are not proper nouns
and thus should not be capitalized unless used at the start of a sentence,
etc.
All Bitcoin-denominated items are encouraged to also show the denomination
in bits, either as the default or as an option.
== Rationale ==
As bitcoin grows in price versus fiat currencies, it's important to give
users the ability to quickly and accurately calculate prices for
transactions, savings and other economic activities. "Bits" have been used
as a denomination within the Bitcoin ecosystem for some time. The idea of
this BIP is to formalize this name. Additionally, "bits" is likely the only
other denomination that will be needed for Bitcoin as 0.01 bit = 1 satoshi,
meaning that two decimal places will be sufficient to describe any current
utxo.
Existing terms used in bitcoin such as satoshi, milli-bitcoin (mBTC) and
bitcoin (BTC) do not conflict as they operate at different orders of
magnitude.
The term micro-bitcoin (µBTC) can continue to exist in tandem with the term
"bits".
== Backwards Compatibility ==
Software such as the Bitcoin Core GUI currently use the µBTC denomination
and can continue to do so. There is no obligation to switch to "bits".
== Copyright ==
This BIP is licensed under the BSD 2-clause license.
== Credit ==
It's hard to ascertain exactly who invented the term "bits", but the term
has been around for a while and the author of this BIP does not take any
credit for inventing the term.
[-- Attachment #2: Type: text/html, Size: 4517 bytes --]
next reply other threads:[~2017-12-13 19:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 19:46 Jimmy Song [this message]
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
[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=CAJR7vkqcBo+o9BL8sK1TBqqNUNSMWdut_aL_YMXse8rDC2ju9A@mail.gmail.com \
--to=jaejoon@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