From: "Nuh.dev" <ar.nazeh@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: [BIP Proposal] Strict circular economy within the Bitcoin network
Date: Tue, 30 Jun 2026 01:19:05 -0700 (PDT) [thread overview]
Message-ID: <f857d6e6-2be4-4b94-bc26-a46d8d6654f9n@googlegroups.com> (raw)
In-Reply-To: <c8ad8400-abcb-4923-a4ea-f9155faf12c9n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1840 bytes --]
Expiring UTXOs might be a step too far, especially when other projects
considered state rent, where you pay more fees when you try to spend an old
UTXO. Of course some UTXOs may never be spent, but that only means they are
effectively out of circulation, giving more value to the mining rewards,
whether these rewards are subsidy or fees. So miners win whether these old
UTXOs move or don't, and if they move, miners eventually get rewarded for
the marginal cost of storing these UTXOs for so long.
On Sunday, 28 June 2026 at 16:54:25 UTC+3 Ricard wrote:
> 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/f857d6e6-2be4-4b94-bc26-a46d8d6654f9n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2722 bytes --]
prev parent reply other threads:[~2026-06-30 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 12:42 [bitcoindev] [BIP Proposal] Strict circular economy within the Bitcoin network Ricard
2026-06-30 8:19 ` Nuh.dev [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=f857d6e6-2be4-4b94-bc26-a46d8d6654f9n@googlegroups.com \
--to=ar.nazeh@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