From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Fraud proofs for block size/weight
Date: Wed, 22 Mar 2017 08:47:30 +0000 [thread overview]
Message-ID: <201703220847.31303.luke@dashjr.org> (raw)
Despite the generalised case of fraud proofs being likely impossible, there
have recently been regular active proposals of miners attacking with simply
oversized blocks in an attempt to force a hardfork. This specific attack can
be proven, and reliably so, since the proof cannot be broken without also
breaking their attempted hardfork at the same time.
While ideally all users ought to use their own full node for validation (even
when using a light client for their wallet), many bitcoin holders still do
not. As such, they are likely to need protection from these attacks, to ensure
they remain on the Bitcoin blockchain.
I've written up a draft BIP for fraud proofs and how light clients can detect
blockchains that are simply invalid due to excess size and/or weight:
https://github.com/luke-jr/bips/blob/bip-sizefp/bip-sizefp.mediawiki
I believe this draft is probably ready for implementation already, but if
anyone has any idea on how it might first be improved, please feel free to
make suggestions.
Luke
next reply other threads:[~2017-03-22 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 8:47 Luke Dashjr [this message]
2017-03-22 20:49 ` [bitcoin-dev] Fraud proofs for block size/weight 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
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=201703220847.31303.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.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