From: Peter Todd <pete@petertodd.org>
To: Murch <murch@murch.one>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [BIP Proposal] Proof-of-Activity Reclamation (PoAR)
Date: Wed, 16 Jul 2025 20:49:44 +0000 [thread overview]
Message-ID: <aHgQaJOEe0x0b0HY@petertodd.org> (raw)
In-Reply-To: <634ea7a6-1695-46e8-a337-1fef1ac17a66@murch.one>
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
On Tue, Jul 15, 2025 at 03:02:04PM -0700, Murch wrote:
> Hi Donald and all,
>
> The idea of recycling dormant coins is one that has made the rounds several
> times before, including in the form of the "Bitcoin Dormant Recovery
> Proposal" just a couple months ago:
> https://github.com/bitcoin/bips/pull/1852
>
> I don’t have the impression that the idea has been particularly popular, and
> as BIPs go, this one is missing crucial parts, e.g.:
>
> • A more comprehensive motivation based on thorough analysis how
> redistributing dormant coins improves the system as this constitutes a
> departure of the status quo for the supply schedule
Worth noting that from an economic point of view redistributing genuinely lost
coins, and creating coins out of thin air, is essentially the same thing:
either way you are introducing coins into the active economy that were
previously not in economic circulation. In both cases you are diluting the
value of non-lost coins by increasing the total active supply, decreasing their
purchasing power proportionally.
If you want to argue for actually redistributing coins rather than just
creating new ones out of thin air - for whatever reason - you need to justify
why you want to risk confiscating coins that were not in fact lost.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
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/aHgQaJOEe0x0b0HY%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-07-16 21:05 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 ` [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 [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=aHgQaJOEe0x0b0HY@petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoindev@googlegroups.com \
--cc=murch@murch.one \
/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