public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Bitcoin Error Log <bitcoinerrorlog@gmail•com>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] [BIP Proposal] Redefinition of the Bitcoin Unit to the Base Denomination
Date: Thu, 12 Dec 2024 19:52:40 +0000	[thread overview]
Message-ID: <CAE2fw6tjVQQT4mpvec2kQg45eLS7VemzQgUfW7Pghdk_Si3PpA@mail.gmail.com> (raw)

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

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.

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

             reply	other threads:[~2024-12-13 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 19:52 Bitcoin Error Log [this message]
2024-12-13 15:09 ` George Burke
2024-12-13 17:16 ` Michael Cassano

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=CAE2fw6tjVQQT4mpvec2kQg45eLS7VemzQgUfW7Pghdk_Si3PpA@mail.gmail.com \
    --to=bitcoinerrorlog@gmail$(echo .)com \
    --cc=bitcoindev@googlegroups.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