From: "'Donald Dienst' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: [BIP Proposal] Proof-of-Activity Reclamation (PoAR)
Date: Tue, 15 Jul 2025 14:58:40 -0700 (PDT) [thread overview]
Message-ID: <b1bdc366-bc27-44dd-b1c6-83776cb9d55fn@googlegroups.com> (raw)
In-Reply-To: <344a8917-5cb2-44c7-adbd-04ff091ad947n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 4884 bytes --]
Boris,
Thank you for taking the time to raise these thoughtful objections. They
highlight important edge cases, particularly around long-term inheritance
planning and time-locked contracts, that deserve further discussion.
The intent of this proposal is not to seize anyone’s Bitcoin but to create
a rules-based mechanism for reintroducing truly abandoned coins—those
locked away forever due to lost keys—back into the economy. If a private
key is irrecoverably lost, the associated Bitcoin is effectively removed
from circulation and, arguably, no longer owned. In such cases, the
so-called "security tax" affects no active participant.
That said, your concerns are valid. One potential refinement would be to
extend the inactivity window significantly—perhaps even to 100 years—to
better accommodate multi-generational ownership and time-locked smart
contracts. The core idea is that a sufficiently long timeframe, paired with
clear expectations and wallet alerts, can strike a balance between
preserving ownership rights and sustaining economic viability.
It's also possible that this proposal—or one like it—may only be
realistically implemented as part of a broader hard fork in the distant
future, potentially bundled with other critical changes such as
post-quantum security upgrades. I hope that when that moment comes, a
mechanism for reclaiming permanently lost coins is part of that discussion.
To those who object on purely ideological grounds, I would offer this
reflection: if something can happen, it will happen—and it will continue to
happen. People will keep losing keys. And one day, someone will lose the
private key to the very last satoshi. Long before that point, Bitcoin may
become functionally unusable—not because of inflation like fiat currencies,
but due to irreversible deflation and economic ossification.
In that light, maintaining the myth that permanently lost coins should
remain sacrosanct is not ideological purity—it’s advocating for a slow
march toward irrelevance. To preserve Bitcoin’s utility as both a store of
value and a medium of exchange, we must confront this eventuality with
reasoned, transparent, and opt-in solutions.
Sincerely,
*Donald D. Dienst*
On Tuesday, July 15, 2025 at 3:42:15 PM UTC-4 Boris Nagaev wrote:
> 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/b1bdc366-bc27-44dd-b1c6-83776cb9d55fn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 5786 bytes --]
next prev parent reply other threads:[~2025-07-15 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 22:55 [bitcoindev] " '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 ` [bitcoindev] " Boris Nagaev
2025-07-15 21:58 ` 'Donald Dienst' via Bitcoin Development Mailing List [this message]
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=b1bdc366-bc27-44dd-b1c6-83776cb9d55fn@googlegroups.com \
--to=bitcoindev@googlegroups.com \
--cc=dddienst@pm$(echo .)me \
/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