public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Erik Aronesty <erik@q32.com>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] UTXO checkpoint transactions
Date: Mon, 27 Jan 2025 21:50:41 -0800	[thread overview]
Message-ID: <CAJowKgLC9LdAu2mrQB-yW2Qoa3jU3BwZyL+QT4WW8f257Jkfhw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

Has it been considered to add a UTXO checkpoint transaction

Here's how it would work

Someone submits a transaction that contains a large fee and a hash of the
UTXO set along with block height as opcode parameter

Miners refuse to include this transaction unless the hash of the UTXO set
matches

Because performing that hash is expensive, it should have an extremely high
cost factor, equivalent to say a 100KB transaction or something

These checkpoints are explicitly for the purpose of fast-synchronizing
extremely lightweight nodes.  It's reasonable to refuse to use a checkpoint
that isn't at least several months old.   It should be easy for anyone to
find a sufficiently aged checkpoint and synchronize from that point onward.


Or is this just a solution without a problem?

-- 
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/CAJowKgLC9LdAu2mrQB-yW2Qoa3jU3BwZyL%2BQT4WW8f257Jkfhw%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 1957 bytes --]

             reply	other threads:[~2025-01-28  6:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28  5:50 Erik Aronesty [this message]
2025-01-28  6:42 ` [bitcoindev] UTXO checkpoint transactions Eric Voskuil
     [not found] <CAJowKgJO6MbxPnyzEYYD5YxzEhPq_AkbOsmRc8a+oVMVeKC9Ew@mail.gmail.com>
     [not found] ` <128AF3BD-F034-46AB-B5BD-E00B405CB854@voskuil.org>
2025-01-28 17:34   ` 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=CAJowKgLC9LdAu2mrQB-yW2Qoa3jU3BwZyL+QT4WW8f257Jkfhw@mail.gmail.com \
    --to=erik@q32.com \
    --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