From: Chris Pacia <ctpacia@gmail.com>
To: Luke Dashjr <luke@dashjr.org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fraud proofs for block size/weight
Date: Sun, 26 Mar 2017 10:16:15 -0400 [thread overview]
Message-ID: <CAB+qUq7=aEoDEhQ7bFz5V5q7CKNtkYYiXc14w3frn0TSqhsUPw@mail.gmail.com> (raw)
In-Reply-To: <201703250516.26362.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
On Mar 25, 2017 12:17 AM, "Luke Dashjr via bitcoin-dev" <bitcoin-dev@lists.
linuxfoundation.org> wrote:
Any ideas? :/
Can't the size be aggregated up the tree such that each midstate hash is
the hash of branches below plus the agreegate of the sizes below.
This would make the root hash(left + right + size/weight) and the proof
would just be the preimage.
[-- Attachment #2: Type: text/html, Size: 992 bytes --]
next prev parent reply other threads:[~2017-03-26 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 8:47 [bitcoin-dev] Fraud proofs for block size/weight 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 [this message]
2017-03-28 22:35 ` Matt Corallo
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='CAB+qUq7=aEoDEhQ7bFz5V5q7CKNtkYYiXc14w3frn0TSqhsUPw@mail.gmail.com' \
--to=ctpacia@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=luke@dashjr.org \
/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