From: "'Donald Dienst' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Proof-of-Activity Reclamation (PoAR)
Date: Thu, 10 Jul 2025 15:55:37 -0700 (PDT) [thread overview]
Message-ID: <a186c724-eef7-4964-9aba-85ae9cce2249n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1133 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 1432 bytes --]
next reply other threads:[~2025-07-15 18:26 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 [this message]
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
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=a186c724-eef7-4964-9aba-85ae9cce2249n@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