From: Light <bitcoin-dev@lightco.in>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Re: The Bitcoin Lost and Found
Date: Tue, 05 May 2026 16:07:15 -0400 [thread overview]
Message-ID: <66cf83b4-c304-4a77-802b-96873b17ec6f@app.fastmail.com> (raw)
In-Reply-To: <d0fb6249-d436-48c2-9dc1-0ed6fa25c988n@googlegroups.com>
Hi waxwing, thank you for your comments.
> I'm probably against Recirculation as an idea. If even thinking about
> confiscation is a mistake (your "meta" comment; I agree), then maybe
> that's also true about changing system incentives with different
> redistributions. Maybe.
An important distinction to me is whether the change is happening "in consensus" or as a result of decisions made at the application layer. Since this is an application layer standard, I'm less opinionated about what people choose to do with coins they come into control of. That said, I would agree that if the technical consensus is that some action would be overall *harmful* to the network then we shouldn't encourage it (and creating a standard like this is just short of encouragement). I haven't been convinced that Recirculation is definitively or even more likely to be *harmful* to bitcoin than no Recirculation (at least no more harmful than any other sudden influx of revenue for miners) but I am open to exploring this further if there is more to the analysis than that. I will say, I do like the relative neutrality of the no-Recirculation option ("lost coins are a donation to everyone", instead of only miners benefiting).
> I'm thinking about taproot sans bip32. If can satisfy a script path spend then you could in theory prove with (merkle proof + validating spend) inside a QR ZKP. No?
Yes, excellent point. This should be added as a spending condition for the Recovery address. Noted!
--
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/66cf83b4-c304-4a77-802b-96873b17ec6f%40app.fastmail.com.
prev parent reply other threads:[~2026-05-05 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 11:38 [bitcoindev] The Bitcoin Lost and Found Light
2026-05-05 13:23 ` [bitcoindev] " waxwing/ AdamISZ
2026-05-05 20:07 ` Light [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=66cf83b4-c304-4a77-802b-96873b17ec6f@app.fastmail.com \
--to=bitcoin-dev@lightco.in \
--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