From: Peter Todd <pete@petertodd•org>
To: Erik Aronesty <erik@q32•com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] OP_CHECKUTXOSETHASH idea
Date: Fri, 3 Oct 2025 16:12:27 +0000 [thread overview]
Message-ID: <aN_16-lBQzY5K9XL@petertodd.org> (raw)
In-Reply-To: <CAJowKgLE4kb7qT1NxXrmEssr8+fQGd-=7=m-BAsjePoti8TRRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
On Mon, Sep 29, 2025 at 05:09:15PM -0700, Erik Aronesty wrote:
> A soft fork could introduce a new opcode, `OP_CHECKUTXOSETHASH`, allowing
> miners to optionally commit a deterministic hash of the current UTXO set
> into a block. If present, all nodes must verify its correctness or reject
> the block; if absent, the block is still valid. Old nodes treat the opcode
> as unspendable, so backward compatibility is preserved.
>
> Because computing the full UTXO root is costly, this makes each checkpoint
> intentionally expensive to produce, ensuring that miners will only include
> them when compensated with sufficient fees. Additionally, it could be
> limited to one per block.
No, it's costly for everyone to compute: everyone needs to recompute this to
validate that the block is valid.
Anyway, just as an aside, if you really need to do something like this, make
the commitment be computable in advance by using a UTXO set root from the
*prior* interval, to give nodes plenty of time to compute it. I outlined this
approach before in the form of delayed txo commitments:
https://petertodd.org/2016/delayed-txo-commitments
--
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/aN_16-lBQzY5K9XL%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-03 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <GDC-d847c0e8-4e35-40c5-87e7-2ab89e13ea09@google.com>
2025-09-30 0:09 ` Erik Aronesty
2025-10-02 22:40 ` 'moonsettler' via Bitcoin Development Mailing List
2025-10-02 23:39 ` Erik Aronesty
2025-10-03 16:12 ` Peter Todd [this message]
2025-10-03 22:15 ` Erik Aronesty
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=aN_16-lBQzY5K9XL@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=erik@q32$(echo .)com \
/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