From: "Jorge Timón" <jtimon@jtimon•cc>
To: Mark Friedenbach <mark@friedenbach•org>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Original Vision
Date: Sun, 28 Jun 2015 17:51:54 +0200 [thread overview]
Message-ID: <CABm2gDq31doL62a2HwY8kSuB1zPMhz6OPR0Qa9X7thbZBdNTOQ@mail.gmail.com> (raw)
In-Reply-To: <CAOG=w-vQ+bCyT8mLNBvLDhhQzCHXxaRos-3VFDGkCsxvCiX3jA@mail.gmail.com>
On Sun, Jun 28, 2015 at 5:23 PM, Mark Friedenbach <mark@friedenbach•org> wrote:
> UTXO commitments are the nominal solution here. You commit the validator state in each block, and then you can prove things like a negative by referencing that state commitment. The trouble is this requires maintaining a hash tree commitment over validator state, which turns out to be insanely expensive. With the UTXO commitment scheme (the others are not better) that ends up requiring 15 - 22x more I/O during block validation. And I/O is presently a limiter to block validation speed. So if you thought 8MB was what bitcoin today could handle, and you also want this commitment scheme for fraud proofs, then you should be arguing for a block size limit decrease (to 500kB), not increase.
What about a TXO and a STXO O(1)-append commitment? That shouldn't
cause that much overhead and you can build UTXO from TXO - STXO.
I know it's not so efficient in some respects but it scales better I think.
next prev parent reply other threads:[~2015-06-28 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 0:14 Santino Napolitano
2015-06-28 1:52 ` Aaron Voisine
2015-06-28 2:13 ` Patrick Strateman
2015-06-28 4:54 ` Eric Lombrozo
2015-06-28 5:29 ` Patrick Strateman
2015-06-28 5:32 ` Eric Lombrozo
2015-06-28 5:48 ` Eric Lombrozo
2015-06-28 15:23 ` Mark Friedenbach
2015-06-28 15:51 ` Jorge Timón [this message]
2015-06-28 16:15 ` Mark Friedenbach
2015-06-28 21:53 ` Santino Napolitano
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=CABm2gDq31doL62a2HwY8kSuB1zPMhz6OPR0Qa9X7thbZBdNTOQ@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=mark@friedenbach$(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