From: Michael Cassano <mcassano@gmail•com>
To: Bitcoin Error Log <bitcoinerrorlog@gmail•com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [BIP Proposal] Redefinition of the Bitcoin Unit to the Base Denomination
Date: Fri, 13 Dec 2024 10:16:23 -0700 [thread overview]
Message-ID: <CAAg3Je02CszYvwF1kL3DofpnxXZvBZx7GAJaM2y1z6ePiG5Y2A@mail.gmail.com> (raw)
In-Reply-To: <CAE2fw6tjVQQT4mpvec2kQg45eLS7VemzQgUfW7Pghdk_Si3PpA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3620 bytes --]
Dear John,
Thank you for the write up.
To further explore this idea, did you consider the idea of dropping
"bitcoin" and keeping "sats" as it is already?
Benefits:
1) We don't re-purpose the existing label of "bitcoin" to represent
something else
2) "sats" is already well defined throughout the system, this minimizes
changes
3) "bitcoin" can live on to represent the network "Bitcoin: a decentralized
peer to peer network"
4) We preserve the honor to Satoshi Nakamoto, the prescient honored founder
of Bitcoin
5) Easy to roll out, we just stop using "bitcoin" over time because we all
agreed it represents an awkward decimalization.
Best regards,
Mike
On Fri, Dec 13, 2024 at 7:50 AM Bitcoin Error Log <bitcoinerrorlog@gmail•com>
wrote:
> Dear Bitcoin Community,
>
> I’d like to introduce a new BIP that aims to redefine the "bitcoin" unit
> to match Bitcoin’s fundamental integer-based accounting. Under this
> proposal, what has traditionally been called "1 BTC" (100,000,000 base
> units) would instead be represented directly as 100 million bitcoins, while
> the smallest indivisible unit becomes the unit of reference—simply "one
> bitcoin." This change removes the complexity and confusion of representing
> values with eight decimal places.
>
> *Key points:*
>
> - Redefines the "bitcoin" to the smallest indivisible unit tracked by
> the protocol.
> - Eliminates the need for decimal points, aligning displayed values,
> and community understanding, with the integral nature of Bitcoin’s
> accounting.
> - Simplifies mental arithmetic and reduces user confusion associated
> with decimal-based representations.
> - Future-proofs the display format by preventing the need for new
> fractional denominations as Bitcoin adoption and valuation evolve.
> - Has other various perks like mitigating unit bias, preventing
> miseducation about Bitcoin's divisibility.
>
> This proposal also addresses alternative suggestions such as BIP 176
> ("bits"), explaining why introducing another sub-unit still forces users to
> think in decimals and multiple denominations. By adopting an integer-only
> display, we can provide a clearer, more intuitive, and ultimately more
> durable representation of Bitcoin’s value.
>
>
> *Full draft BIP Text:*
> https://github.com/BitcoinAndLightningLayerSpecs/balls/blob/main/BIP%2021Q.md
>
> Please share your comments here on the mailing list. I look forward to
> refining this proposal based on community input.
>
> Thank you for your consideration,
>
> John Carvalho
> bitcoinerrorlog@gmail•com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Bitcoin Development Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to bitcoindev+unsubscribe@googlegroups•com.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/CAE2fw6tjVQQT4mpvec2kQg45eLS7VemzQgUfW7Pghdk_Si3PpA%40mail.gmail.com
> <https://groups.google.com/d/msgid/bitcoindev/CAE2fw6tjVQQT4mpvec2kQg45eLS7VemzQgUfW7Pghdk_Si3PpA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAAg3Je02CszYvwF1kL3DofpnxXZvBZx7GAJaM2y1z6ePiG5Y2A%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4779 bytes --]
prev parent reply other threads:[~2024-12-15 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 19:52 Bitcoin Error Log
2024-12-13 15:09 ` George Burke
2024-12-13 17:16 ` Michael Cassano [this message]
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=CAAg3Je02CszYvwF1kL3DofpnxXZvBZx7GAJaM2y1z6ePiG5Y2A@mail.gmail.com \
--to=mcassano@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=bitcoinerrorlog@gmail$(echo .)com \
/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