From: Ricard <rbou.pro.us@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Strict circular economy within the Bitcoin network
Date: Sun, 28 Jun 2026 05:42:58 -0700 (PDT) [thread overview]
Message-ID: <c8ad8400-abcb-4923-a4ea-f9155faf12c9n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]
Dear list,
This BIP proposes a consensus rule update to implement a strict circular
economy within the Bitcoin network, keeping the 21 million maximum supply
limit permanently intact.
An expiration limit is introduced for Unspent Transaction Outputs (UTXOs).
UTXOs that exceed a maximum age threshold of `MAX_UTXO_AGE` (e.g.,
1,048,576 blocks) will be deemed invalid for spending and pruned from the
nodes' active Chainstate database. The nominal value of these expired
satoshis will not be injected into immediate block rewards. Instead, they
will be reintroduced into the pending emission reserve, dynamically
extending the duration of halving epochs to guarantee a perpetual block
subsidy without adding inflation.
https://github.com/bip-proposer/bitcoin-infinity/blob/main/infinity.md
I appreciate discussion on this proposal.
Best,
Ricard.
--
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/c8ad8400-abcb-4923-a4ea-f9155faf12c9n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1621 bytes --]
next reply other threads:[~2026-06-28 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 12:42 Ricard [this message]
2026-06-30 8:19 ` [bitcoindev] Re: [BIP Proposal] Strict circular economy within the Bitcoin network Nuh.dev
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=c8ad8400-abcb-4923-a4ea-f9155faf12c9n@googlegroups.com \
--to=rbou.pro.us@gmail.com \
--cc=bitcoindev@googlegroups.com \
/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