From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Pull request: faster initial blockchain download
Date: Mon, 5 Sep 2011 16:41:24 -0400 [thread overview]
Message-ID: <CABsx9T2vS4a3k6_6T7KvA+eoc8Rc61HGKRc0nBVMqLeGeTPftQ@mail.gmail.com> (raw)
I'd appreciate review/feedback on this:
https://github.com/bitcoin/bitcoin/pull/492
This change skips ECDSA signature verification for transactions during
the initial block-chain download, which makes downloading the block
chain much faster.
"Initial block chain download" is all blocks up to 120 blocks before
the last blockchain lock-in point.
Reasoning for why this is safe:
If an attacker tries to feed a client bad transactions during the
initial block-chain download (transactions with invalid signatures),
then they change the merkle tree, and at the first blockchain lock-in
the bad chain will be rejected.
Transactions are still checked for orphan blocks that come in during
initial block-chain-download (ConnectInputs will be called with
fBlock=FALSE) and for mined blocks (ConnectInputs called with
fMiner=TRUE).
--
--
Gavin Andresen
reply other threads:[~2011-09-05 20:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABsx9T2vS4a3k6_6T7KvA+eoc8Rc61HGKRc0nBVMqLeGeTPftQ@mail.gmail.com \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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