From: Lucas Barbosa <lucasbarbosafurtado0@gmail•com>
To: Donald Dienst <dddienst@pm•me>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP Proposal] Proof-of-Activity Reclamation (PoAR)
Date: Tue, 15 Jul 2025 16:07:59 -0300 [thread overview]
Message-ID: <CAPbyeOHQcehNYU26W4rC_wxTpfrZSCBgMuCecmBqHpOgETYSsA@mail.gmail.com> (raw)
In-Reply-To: <a186c724-eef7-4964-9aba-85ae9cce2249n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 3670 bytes --]
This type of proposal, is fundamentally incompatible with Bitcoin's ethos
for several reasons.
1. Sovereignty and Immutability of Property
In Bitcoin, ownership of a coin is guaranteed exclusively by possession of
the corresponding private key. The idea that funds can be "reclaimed" or
"recycled" after a period of inactivity amounts to automated confiscation,
albeit disguised as economic efficiency. This undermines trust in the
inviolability of property—something sacred to long-term users.
2. The 21 Million Rule is Inviolable, but the Supply is also Deterministic
Although the proposal claims to respect the 21 million cap, it alters the
nature of supply distribution. The fact that UTXOs are lost is part of the
economic reality of BTC—the actual circulating supply is lower than the
theoretical one, and this is priced in. Attempting to "correct" this is a
form of monetary intervention without legitimate authority in the system.
3. Perverse Precedent and Attack on Finality
Allowing a UTXO to be reused after N years sets a very dangerous precedent:
ownership of BTC is no longer absolute and becomes conditional on activity.
This directly attacks the finality of transactions and the ledger—one of
the pillars of the system.
4. Negative Impact on Long-Term Trust
People who store BTC for the future—whether for decades, for reasons of
inheritance, security, or trust in the network—would lose the guarantee
that their BTC will remain untouched. This reduces Bitcoin's perceived
value as a solid and reliable store of value.
5. This Has Already Been Considered and Rejected
Similar proposals (such as coin expiry or reclaimable outputs) have been
discussed in the past, and the Bitcoin community has consistently rejected
them based on the above principles.
Em ter., 15 de jul. de 2025, 15:26, 'Donald Dienst' via Bitcoin Development
Mailing List <bitcoindev@googlegroups.com> escreveu:
> 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
> dddienst@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/a186c724-eef7-4964-9aba-85ae9cce2249n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/a186c724-eef7-4964-9aba-85ae9cce2249n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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/CAPbyeOHQcehNYU26W4rC_wxTpfrZSCBgMuCecmBqHpOgETYSsA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4943 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 'Donald Dienst' via Bitcoin Development Mailing List
2025-07-15 18:48 ` Christian Riley
2025-07-15 19:07 ` Lucas Barbosa [this message]
2025-07-15 19:28 ` [bitcoindev] " Boris Nagaev
2025-07-15 21:58 ` '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=CAPbyeOHQcehNYU26W4rC_wxTpfrZSCBgMuCecmBqHpOgETYSsA@mail.gmail.com \
--to=lucasbarbosafurtado0@gmail$(echo .)com \
--cc=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