path: root/e4/83f6bfa9a59eff8f3576d3047c0e300279c201

Return-Path: <asher@seent.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id B738BC000B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  4 Mar 2022 02:08:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id ADF1340162
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  4 Mar 2022 02:08:12 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5
 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=seent-com.20210112.gappssmtp.com
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id u6vnFQ9UvHaF
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  4 Mar 2022 02:08:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com
 [IPv6:2607:f8b0:4864:20::b2d])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 589D640131
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri,  4 Mar 2022 02:08:11 +0000 (UTC)
Received: by mail-yb1-xb2d.google.com with SMTP id w16so13946379ybi.12
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 03 Mar 2022 18:08:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=seent-com.20210112.gappssmtp.com; s=20210112;
 h=mime-version:from:date:message-id:subject:to;
 bh=oAvXsUzamwEdlB9OfC26fnsBhNLUgplLCfhYf4CZWpk=;
 b=UNm3YQf1FAMxTh8N9eT8koHOsDKzFZZ5Igk2zbdTMW0oNNJme29RBcobnYsoCXRSLK
 KdTKJQF4yT0KiB9UsHaUr7voLh/G7Qcy75hq6yVNxhDITtNZivkI+24nPOmOr65apihJ
 LPAy500zFRQGMGqBx5RydjHkqQ6MO/xSOdjI/w+qiry/7/esglJ1anrfWHG+fI/ppfOE
 KHnYvWh56H/e5PLI+ZGhEAGrJ1GRfvfYsulSlmxcBt0n/xG8xM0l6//4NqXYL4u21/4x
 JRBQJdfp273wg4Uj42A/+Y7zT0EreLuQ755clMqe/ulUTxAuWd4zqRp7l4w3x1+YFv8R
 vF4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=oAvXsUzamwEdlB9OfC26fnsBhNLUgplLCfhYf4CZWpk=;
 b=f0Qb9I2JeNO3bbtTMHKZ1rf7PWyV4hxbawXFEm3Eb9n764z40CDTB7aQrKFeLF66ex
 48ZuCKNIrGcEhiwVA/59yi0kHy5dT0h5+n7WuRA2nYHuILprFasOQ7naQpp9t6B2JH4e
 qo2Z6lBIYddLxY8O9Eh3u4mCNShgxer7NRgr2NHnayC39cZ9/KmC19DNqoRZY7QCWbqo
 GGM6/t/sWx0UoM8TiU2ZQppIWc9Xm8o04uJVylXgJ8Zj6j9nXfdZH/JCe4BQmKQqn7B2
 cSacT2IQvSl88CwcXHuyRkM3wEmnVoiksWSoXWL089GyhJIMMwQXHzx8Kqumby8m8NMa
 wRGw==
X-Gm-Message-State: AOAM533pQucJAgAjHAZbPyquR3JT3bnqS+eU0tXgLwna1d+3zCQWvImg
 VPryQGcPVpymQUASViX7ZN+AkHSJTZjBiZOfLBWU6Z8iEBhXAqys
X-Google-Smtp-Source: ABdhPJweDlpeKPMwORw9gzFwDFoLr82ZhA6y2UgcCz5kcG2mJZB0Op7S7YqEh7YrOW3bgzmnf1+L1jFvqGfaSBRx8JY=
X-Received: by 2002:a25:6608:0:b0:628:d9bd:6245 with SMTP id
 a8-20020a256608000000b00628d9bd6245mr3158686ybc.560.1646359690079; Thu, 03
 Mar 2022 18:08:10 -0800 (PST)
MIME-Version: 1.0
From: Asher Hopp <asher@seent.com>
Date: Thu, 3 Mar 2022 18:07:59 -0800
Message-ID: <CANK0iRNL82xvOqiJcR2k64bOMnOdmRBdQUzuJAQKO9QzHKvHAg@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="00000000000080036c05d95afcfe"
X-Mailman-Approved-At: Fri, 04 Mar 2022 15:19:22 +0000
Subject: [bitcoin-dev] BIP Draft Submission
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2022 02:08:12 -0000

--00000000000080036c05d95afcfe
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This is my first time submitting anything to this mailer list, so I am here
with humility and I would appreciate any feedback about any aspect of my
BIP draft submission below. If you want to reach out to me directly you can
email me at asher@seent.com.

Abstract
Rather than having a maximum supply of 21 million Bitcoin, there should be
a maximum supply of 21 trillion Bitcoin. This can be accomplished by moving
the decimal place 6 places to the right of where it is today, while
reserving two degrees of accuracy after the decimal point.

Copyright
This BIP is under the Creative Commons Zero (CC0) license.

Background
On February 6th, 2010 Satoshi Nakamoto responded to a bitcointalk forum
discussion about the divisibility and economics of bitcoin as a global
currency. Satoshi chimed in to the conversation when two ideas formed:
1. Bitcoin is so scarce that a perception may exist that there is not
enough to go around =E2=80=93 there is not even 1 Bitcoin available per per=
son on
Earth.
2. If Bitcoin=E2=80=99s value continues to deflate against inflating fiat
currencies, Bitcoin transactions may become smaller and smaller, requiring
the potentially tedious use of many leading 0=E2=80=99s after the decimal p=
oint.

Satoshi=E2=80=99s suggested response to these issues was a software update =
to
change where the decimal place and commas are displayed when software
interprets a Bitcoin wallet=E2=80=99s balance: =E2=80=9CIf it gets tiresome=
 working with
small numbers, we could change where the display shows the decimal point.
Same amount of money, just different convention for where the ","'s and
"."'s go.  e.g. moving the decimal place 3 places would mean if you had
1.00000 before, now it shows it as 1,000.00.=E2=80=9D (
https://bitcointalk.org/index.php?topic=3D44.msg267#msg267)

Since 2010, when Satoshi wrote that post Bitcoin has indeed become a
globally adopted currency, the dollar has inflated significantly, and
Bitcoin has deflated. There are many debates in the Bitcoin community
concerning the nomenclature of Bitcoin=E2=80=99s atomic unit (satoshis, sat=
s, bits,
bitcents, mbits, etc). The debate has somewhat spiraled out of control, and
there is no clearly emerging community consensus. Additionally this issue
impacts the technology world outside of Bitcoin because there are several
proposals for various Unicode characters which factions of the Bitcoin
community have started using to represent the atomic Bitcoin unit despite
no formalized consensus.  Therefore The conditions are right to move
forward with Satoshi's vision and move the decimal place.

Details
There are several benefits to moving the decimal 6 places to the right in
Bitcoin wallet balance notation:
1. Unit bias. It is a widely held belief that Bitcoin=E2=80=99s adoption ma=
y be
hindered because would-be participants have a negative perception of
Bitcoin=E2=80=99s unit size. One Bitcoin so expensive, and some people may =
be
turned off by the idea of only owning a fraction of a unit.
2. Community cohesion. The Bitcoin community is deeply divided by various
proposed atomic unit names, but if this BIP is adopted there is no need to
debate nomenclature for the Bitcoin atomic unit. Bitcoin software providers
can simply continue using the Bitcoin Unicode character (=E2=82=BF, U+20BF)=
, and
there are no additional unicode characters required.
3. Simplicity and standardization. Bitcoin has no borders and is used by
people in just about every corner of the world. Other than the name Bitcoin
and the Unicode character we have, there is no consensus around other
notations for Bitcoin as a currency. Rather than introducing new concepts
for people to learn, this BIP allows Bitcoin to grow under a single
standardized unit specification, with a single standard unit name, unit
size, and unit Unicode character.

There is only one drawback I can identify with this BIP, and it is purely
psychological. Moving the decimal place may produce bad optics in the
short-term, and Bitcoin=E2=80=99s detractors will likely seize the opportun=
ity to
spread misinformation that moving the decimal place changes the monetary
value of anyone=E2=80=99s Bitcoin. It is important to note that if this BIP=
 were to
gain consensus approval, the community would need to prepare talking points
and coordinate educational outreach efforts to explain to Bitcoin users and
wallet developers that this change does not change the proportion of the
total value of Bitcoin any particular wallet holds, and is simply a
notational change. There are no =E2=80=9Cwinners=E2=80=9D and no =E2=80=9Cl=
osers=E2=80=9D in this BIP =E2=80=93 all
Bitcoin participants would be impacted in an equal and proportionate manner
on pari passu terms, and there is no change to Bitcoin=E2=80=99s monetary p=
olicy.

Implementation
The software updates needed to implement this BIP are restricted to the
wallet's CLI/GUI configuration, and only involve changing the location of
the decimal point and commas when viewing balances or reviewing transaction
data. Each wallet provider including Bitcoin Core would simply need to
update the display of a wallet=E2=80=99s balance by moving the decimal plac=
e 6
places to the right.

Compatibility
Because this BIP is a consensus change around the display of Bitcoin wallet
balances and transaction amounts, everything will be backwards compatible
with previous versions of Bitcoin. There would be no interruption in
services for Bitcoin wallets which do not implement this BIP, however there
could conceivably be human error problems with miscommunication between
counterparties after this BIP is implemented. I believe this risk is
extremely minimal because an error of 6 decimal places is so significant
that it should be immediately noticed by any two parties conducting a
transaction.

Cheers,
Asher

--00000000000080036c05d95afcfe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This is my first time submitting anything to this mai=
ler list, so I am here with humility and I would appreciate any feedback ab=
out any aspect of my BIP draft submission below. If you want to reach out t=
o me directly you can email me at <a href=3D"mailto:asher@seent.com">asher@=
seent.com</a>.</div><div><br></div>Abstract<br>Rather than having a maximum=
 supply of 21 million Bitcoin, there should be a maximum supply of 21 trill=
ion Bitcoin. This can be accomplished by moving the decimal place 6 places =
to the right of where it is today, while reserving two degrees of accuracy =
after the decimal point.<br><br>Copyright<br>This BIP is under the Creative=
 Commons Zero (CC0) license.<br><br>Background<br>On February 6th, 2010 Sat=
oshi Nakamoto responded to a bitcointalk forum discussion about the divisib=
ility and economics of bitcoin as a global currency. Satoshi chimed in to t=
he conversation when two ideas formed:<br>1. Bitcoin is so scarce that a pe=
rception may exist that there is not enough to go around =E2=80=93 there is=
 not even 1 Bitcoin available per person on Earth.<br>2. If Bitcoin=E2=80=
=99s value continues to deflate against inflating fiat currencies, Bitcoin =
transactions may become smaller and smaller, requiring the potentially tedi=
ous use of many leading 0=E2=80=99s after the decimal point.<br><br>Satoshi=
=E2=80=99s suggested response to these issues was a software update to chan=
ge where the decimal place and commas are displayed when software interpret=
s a Bitcoin wallet=E2=80=99s balance: =E2=80=9CIf it gets tiresome working =
with small numbers, we could change where the display shows the decimal poi=
nt.=C2=A0 Same amount of money, just different convention for where the &qu=
ot;,&quot;&#39;s and &quot;.&quot;&#39;s go. =C2=A0e.g. moving the decimal =
place 3 places would mean if you had 1.00000 before, now it shows it as 1,0=
00.00.=E2=80=9D (<a href=3D"https://bitcointalk.org/index.php?topic=3D44.ms=
g267#msg267">https://bitcointalk.org/index.php?topic=3D44.msg267#msg267</a>=
)<br><br>Since 2010, when Satoshi wrote that post Bitcoin has indeed become=
 a globally adopted currency, the dollar has inflated significantly, and Bi=
tcoin has deflated. There are many debates in the Bitcoin community concern=
ing the nomenclature of Bitcoin=E2=80=99s atomic unit (satoshis, sats, bits=
, bitcents, mbits, etc). The debate has somewhat spiraled out of control, a=
nd there is no clearly emerging community consensus. Additionally this issu=
e impacts the technology world outside of Bitcoin because there are several=
 proposals for various Unicode characters which factions of the Bitcoin com=
munity have started using to represent the atomic Bitcoin unit despite no f=
ormalized consensus.=C2=A0 Therefore The conditions are right to move forwa=
rd with Satoshi&#39;s vision and move the decimal place.<div><br>Details<br=
>There are several benefits to moving the decimal 6 places to the right in =
Bitcoin wallet balance notation:<br>1. Unit bias. It is a widely held belie=
f that Bitcoin=E2=80=99s adoption may be hindered because would-be particip=
ants have a negative perception of Bitcoin=E2=80=99s unit size. One Bitcoin=
 so expensive, and some people may be turned off by the idea of only owning=
 a fraction of a unit.<br>2. Community cohesion. The Bitcoin community is d=
eeply divided by various proposed atomic unit names, but if this BIP is ado=
pted there is no need to debate nomenclature for the Bitcoin atomic unit. B=
itcoin software providers can simply continue using the Bitcoin Unicode cha=
racter (=E2=82=BF, U+20BF), and there are no additional unicode characters =
required.<br>3. Simplicity and standardization. Bitcoin has no borders and =
is used by people in just about every corner of the world. Other than the n=
ame Bitcoin and the Unicode character we have, there is no consensus around=
 other notations for Bitcoin as a currency. Rather than introducing new con=
cepts for people to learn, this BIP allows Bitcoin to grow under a single s=
tandardized unit specification, with a single standard unit name, unit size=
, and unit Unicode character.<br><br>There is only one drawback I can ident=
ify with this BIP, and it is purely psychological. Moving the decimal place=
 may produce bad optics in the short-term, and Bitcoin=E2=80=99s detractors=
 will likely seize the opportunity to spread misinformation that moving the=
 decimal place changes the monetary value of anyone=E2=80=99s Bitcoin. It i=
s important to note that if this BIP were to gain consensus approval, the c=
ommunity would need to prepare talking points and coordinate educational ou=
treach efforts to explain to Bitcoin users and wallet developers that this =
change does not change the proportion of the total value of Bitcoin any par=
ticular wallet holds, and is simply a notational change. There are no =E2=
=80=9Cwinners=E2=80=9D and no =E2=80=9Closers=E2=80=9D in this BIP =E2=80=
=93 all Bitcoin participants would be impacted in an equal and proportionat=
e manner on pari passu terms, and there is no change to Bitcoin=E2=80=99s m=
onetary policy. <br><br>Implementation<br>The software updates needed to im=
plement this BIP are restricted to the wallet&#39;s CLI/GUI configuration,=
=C2=A0and only involve changing the location of the decimal point and comma=
s when viewing balances or reviewing transaction data. Each wallet provider=
 including Bitcoin Core would simply need to update the display of a wallet=
=E2=80=99s balance by moving the decimal place 6 places to the right.<br><b=
r>Compatibility<br>Because this BIP is a consensus change around the displa=
y of Bitcoin wallet balances and transaction amounts, everything will be ba=
ckwards compatible with previous versions of Bitcoin. There would be no int=
erruption in services for Bitcoin wallets which do not implement this BIP, =
however there could conceivably be human error problems with miscommunicati=
on between counterparties after this BIP is implemented. I believe this ris=
k is extremely minimal because an error of 6 decimal places is so significa=
nt that it should be immediately noticed by any two parties conducting a tr=
ansaction.<div><div><br></div><div>Cheers,</div><div>Asher</div></div></div=
></div>

--00000000000080036c05d95afcfe--