From: Matt Corallo <lf-lists@mattcorallo•com>
To: "Luke Dashjr" <luke@dashjr•org>,
bitcoin-dev@lists•linuxfoundation.org,
"Jorge Timón" <jtimon@jtimon•cc>
Subject: Re: [bitcoin-dev] Fraud proofs for block size/weight
Date: Tue, 28 Mar 2017 22:35:05 +0000 [thread overview]
Message-ID: <134ac169-08ed-706b-b64d-409fef942c73@mattcorallo.com> (raw)
In-Reply-To: <201703250516.26362.luke@dashjr.org>
I dont think thats true? Sure, you have to assume the block is valid
aside from a too-large size, but it seems sane.
You don't strictly need to show that a leaf is a parseable transaction,
as long as you can assume that the block is valid and that you cannot
forge a SHA256 midstate which, when combined with data with a given
length tag, would result in a hash of a given value (this is a pretty
strong assumption, IMO, IIRC this was not a studied nor a claimed
feature of SHA256).
The only issue is that, since parts of the merkle tree are repeated, you
need to be sure that the counting for minimum number of transactions is
accurate, though I did not review your proposal text to check that.
On 03/25/17 05:16, Luke Dashjr wrote:
- snip -
> The only way to establish the number of transactions at all, is to show that a
> leaf is a parsable transaction. Which this doesn't actually show, so it's
> broken. :( Need to think on this. Any ideas? :/
>
> Luke
>
prev parent reply other threads:[~2017-03-28 22:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 8:47 Luke Dashjr
2017-03-22 20:49 ` Bram Cohen
2017-03-22 21:51 ` Matt Corallo
2017-03-23 18:27 ` Jorge Timón
2017-03-25 5:16 ` Luke Dashjr
2017-03-26 14:16 ` Chris Pacia
2017-03-28 22:35 ` Matt Corallo [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=134ac169-08ed-706b-b64d-409fef942c73@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
--cc=luke@dashjr$(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