From: "mbde@bitwatch•co" <mbde@bitwatch•co>
To: Bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Synchronization: 19.5 % orphaned blocks at height 197'324
Date: Sun, 10 Aug 2014 15:42:41 +0200 [thread overview]
Message-ID: <53E776D1.1010503@bitwatch.co> (raw)
Hello all,
I'm currently synchronizing a new node and right now, at a progress of a
height of 197'324 blocks, I count in my debug.log an aweful amount of
38'447 orphaned blocks which is about 19.5 %.
It has been I while since I watched the synchronization process closely,
but this number seems pretty high to me.
I'm wondering about the following: would it be possible for a malicious
party to generate chains of blocks with low difficulity which are not
part of the main chain to slow down the sync process?
Build and version information:
https://github.com/jmcorgan/bitcoin/tree/026686c7de76dfde6fcacfc3d667fb3418a946a7
(sipa/jmcorgan address index)
Rebased with:
https://github.com/bitcoin/bitcoin/tree/94e1b9e05b96e4fe639e5b07b7a53ea216170962
(almost up-to-date mainline)
Compressed debug.log attached:
https://www.dropbox.com/s/uvtd91xiwmdmun7/debug.7z?m=
(filesize: 7.67 MB, uncompressed: 41.3 MB)
next reply other threads:[~2014-08-10 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 13:42 mbde [this message]
2014-08-10 14:07 ` Bob McElrath
2014-08-10 18:07 ` Pieter Wuille
2014-08-10 14:20 ` Jeff Garzik
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=53E776D1.1010503@bitwatch.co \
--to=mbde@bitwatch$(echo .)co \
--cc=Bitcoin-development@lists$(echo .)sourceforge.net \
/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