From: Erik Aronesty <erik@q32•com>
To: Peter Todd <pete@petertodd•org>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] OP_CHECKUTXOSETHASH idea
Date: Fri, 3 Oct 2025 15:15:31 -0700 [thread overview]
Message-ID: <CAJowKgLpix4KjzJGKNzR3JpiKLDJKSiuuOdcebCyGJnDuw0wJw@mail.gmail.com> (raw)
In-Reply-To: <aN_16-lBQzY5K9XL@petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
agreed! UTXO set root from the *prior* interval is the best way to go.
the whole point is it's supposed to be old, safe beyond reorg and for
lightweight sync with no centralized checkpoint producers.
i do think that incremental-hashing can be used to speed things up a lot.
Merkleized, Merklix trie, or an accumulator like Utreexo: you can maintain
the root incrementally by only touching the leaves that correspond to
changed UTXOs
should be very fast, not heavy at all
--
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/CAJowKgLpix4KjzJGKNzR3JpiKLDJKSiuuOdcebCyGJnDuw0wJw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 1206 bytes --]
prev parent reply other threads:[~2025-10-03 22:46 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
2025-10-03 22:15 ` Erik Aronesty [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=CAJowKgLpix4KjzJGKNzR3JpiKLDJKSiuuOdcebCyGJnDuw0wJw@mail.gmail.com \
--to=erik@q32$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=pete@petertodd$(echo .)org \
/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