From: Boris Nagaev <bnagaev@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: [BIP Proposal] Proof-of-Activity Reclamation (PoAR)
Date: Tue, 15 Jul 2025 12:28:14 -0700 (PDT) [thread overview]
Message-ID: <344a8917-5cb2-44c7-adbd-04ff091ad947n@googlegroups.com> (raw)
In-Reply-To: <a186c724-eef7-4964-9aba-85ae9cce2249n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 2416 bytes --]
Hi Donald,
Thanks for sharing your proposal!
There are several additional objections worth considering:
1. It would require a hard fork. Older nodes would reject blocks with a
higher-than-expected miner reward. By contrast, SegWit and Taproot were
implemented as soft forks.
2. It breaks long-term inheritance schemes. Imagine a newborn inheriting
1000 BTC from a wealthy relative. The relative sets a 30-year timelock to
ensure the funds are not misused during childhood. This proposal would
interfere with that intention and potentially strip the heir of their
rightful inheritance.
3. It penalizes long-term planning and low time preference. Users who
intentionally lock up funds for decades (whether for inheritance, security,
or economic reasons) would be disproportionately impacted.
4. It changes who pays for network security. Miners are expected to be
compensated in the long term by transaction fees paid by active transaction
senders. This proposal would instead take value from long-term holders who
aren't participating in the transaction flow, effectively taxing them
without consent.
Best regards,
Boris
On Tuesday, July 15, 2025 at 3:26:35 PM UTC-3 Donald Dienst wrote:
Dear Bitcoin developers,
I would like to propose a new BIP titled "Proof-of-Activity Reclamation
(PoAR)," which aims to address the long-term economic effects of lost and
abandoned UTXOs.
This proposal introduces a fully automated and rule-based mechanism to
gradually recycle coins that have been provably inactive for over 20 years.
These coins are returned to the undistributed pool and slowly reintroduced
via future block rewards—extending miner incentives while respecting the 21
million BTC cap.
You can view the full proposal here:
https://gist.github.com/Brandchatz/56c39d289db9e56190c13922850815b8
I welcome your thoughts, suggestions, and critiques.
Best regards,
Donald Dienst
dddi...@protonmail.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/344a8917-5cb2-44c7-adbd-04ff091ad947n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3018 bytes --]
next prev parent reply other threads:[~2025-07-15 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 22:55 [bitcoindev] [BIP Proposal] Proof-of-Activity Reclamation (PoAR) 'Donald Dienst' via Bitcoin Development Mailing List
2025-07-15 18:48 ` Christian Riley
2025-07-15 19:07 ` Lucas Barbosa
2025-07-15 19:28 ` Boris Nagaev [this message]
2025-07-15 21:58 ` [bitcoindev] " 'Donald Dienst' via Bitcoin Development Mailing List
2025-07-15 22:02 ` [bitcoindev] " Murch
2025-07-16 20:49 ` Peter Todd
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=344a8917-5cb2-44c7-adbd-04ff091ad947n@googlegroups.com \
--to=bnagaev@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