|
Title: [NBL] Client issue, fully synced .. then suddenly! 340,000 blocks remaining! Post by: BitHits on May 30, 2013, 05:58:00 AM http://gyazo.com/59296bfaa2e0dd19458ac599647e085d.png
http://gyazo.com/59296bfaa2e0dd19458ac599647e085d.png Title: Re: [NBL] Client issue, fully synced .. then suddenly! 340,000 blocks remaining! Post by: thisnewcoin on May 30, 2013, 06:01:53 AM someone forked the blockchain, lol
Title: Re: [NBL] Client issue, fully synced .. then suddenly! 340,000 blocks remaining! Post by: Geocen on May 30, 2013, 06:02:04 AM Just people screwing with the network trying to attack the blockchain. It will go away if you leave the client open, eventually the users get removed from your node list.
Title: Re: [NBL] Client issue, fully synced .. then suddenly! 340,000 blocks remaining! Post by: HuuHachu on May 30, 2013, 06:04:56 AM could it be someone trying to copy the litecoin blockchain into the nibble directory ?
Title: Re: [NBL] Client issue, fully synced .. then suddenly! 340,000 blocks remaining! Post by: digitalindustry on May 30, 2013, 06:40:21 AM The Dev hyoshi is ontop of it , also we have set up a server dedicated to a node also update your config files , its of negligible concern , but of a concern , its really interesting to see which currency is seen a a threat ?
Title: Re: [NBL] Client issue, fully synced .. then suddenly! 340,000 blocks remaining! Post by: BitHits on May 30, 2013, 06:52:08 AM Pretty sure this is the relevant section of debug.log
Seems block height just jumps on a few random nodes. --- trying connection 5.135.159.132:9334 lastseen=6.6hrs SetBestChain: new best=f942364a2563ba3a878e height=18467 work=83681940877344 date=05/30/13 06:35:49 ===>> nHeight = 18468 SetBestChain: new best=417b0e5ff9dcb17bda60 height=18468 work=83691149945120 date=05/30/13 06:38:56 ProcessBlock: ACCEPTED Added 380 addresses from 67.168.220.0: 74 tried, 10881 new Added 396 addresses from 67.168.220.0: 74 tried, 10900 new Added 213 addresses from 67.168.220.0: 74 tried, 10912 new Added 382 addresses from 72.78.100.9: 74 tried, 10932 new Added 392 addresses from 72.78.100.9: 74 tried, 10948 new Added 194 addresses from 72.78.100.9: 74 tried, 10950 new Added 406 addresses from 207.12.89.2: 74 tried, 10974 new Added 402 addresses from 207.12.89.2: 74 tried, 10965 new Added 197 addresses from 207.12.89.2: 74 tried, 10963 new Added time data, samples 5, offset -34 (+0 minutes) nTimeOffset = -13 (+0 minutes) receive version message: version 60001, blocks=18468, us=x.x.x.x:44309, them=72.11.149.185:8551, peer=72.11.149.185:8550 getblocks 18468 to 00000000000000000000 limit 500 getblocks 18468 to 00000000000000000000 limit 500 Flushing wallet.dat Flushed wallet.dat 145ms connection timeout trying connection 188.162.36.48:8550 lastseen=3.6hrs getblocks -1 to 00000000000000000000 limit 500 Added 408 addresses from 72.11.149.185: 74 tried, 10998 new Added 445 addresses from 72.11.149.185: 74 tried, 11015 new Added 233 addresses from 72.11.149.185: 74 tried, 11022 new connection timeout trying connection 166.70.41.107:8550 lastseen=0.9hrs connection timeout trying connection 81.156.215.215:9333 lastseen=5.3hrs connection timeout trying connection 166.70.41.107:8550 lastseen=0.9hrs connection timeout trying connection 128.69.0.182:8550 lastseen=2.6hrs connection timeout trying connection 64.107.73.2:8550 lastseen=0.9hrs Added 1 addresses from 67.168.220.0: 74 tried, 11021 new connection timeout trying connection 184.153.8.106:8550 lastseen=0.8hrs connected 184.153.8.106:8550 send version message: version 60001, blocks=18468, us=x.x.x.x:8550, them=184.153.8.106:8550, peer=184.153.8.106:8550 Added time data, samples 6, offset -7 (+0 minutes) receive version message: version 60001, blocks=18468, us=x.x.x.x:42808, them=184.153.8.106:8550, peer=184.153.8.106:8550 trying connection 75.131.211.216:8550 lastseen=0.9hrs Added 318 addresses from 184.153.8.106: 74 tried, 11025 new Added 388 addresses from 184.153.8.106: 74 tried, 11070 new Added 165 addresses from 184.153.8.106: 74 tried, 11067 new connection timeout trying connection 151.237.52.42:8550 lastseen=0.8hrs connected 151.237.52.42:8550 send version message: version 60001, blocks=18468, us=x.x.x.x:8550, them=151.237.52.42:8550, peer=151.237.52.42:8550 Added time data, samples 7, offset -8 (+0 minutes) nTimeOffset = -12 (+0 minutes) receive version message: version 60001, blocks=18468, us=x.x.x.x:37984, them=151.237.52.42:8550, peer=151.237.52.42:8550 trying connection 70.75.239.1:9333 lastseen=5.3hrs connected 70.75.239.1:9333 send version message: version 60001, blocks=18468, us=x.x.x.x:8550, them=70.75.239.1:9333, peer=70.75.239.1:9333 Added time data, samples 8, offset -11 (+0 minutes) Moving 70.75.239.1:9333 to tried receive version message: version 60001, blocks=361774, us=x.x.x.x:45657, them=70.75.239.1:9333, peer=70.75.239.1:9333 trying connection 178.190.161.226:10333 lastseen=4.8hrs Added 426 addresses from 70.75.239.1: 75 tried, 11098 new connection timeout Added 399 addresses from 70.75.239.1: 75 tried, 11121 new trying connection 24.49.138.81:9333 lastseen=4.5hrs Added 308 addresses from 151.237.52.42: 75 tried, 11098 new Added 334 addresses from 151.237.52.42: 75 tried, 11107 new Added 168 addresses from 151.237.52.42: 75 tried, 11104 new Added 183 addresses from 70.75.239.1: 75 tried, 11102 new ERROR: FetchInputs() : 8fff9c30e2 mempool Tx prev not found e784d727e3 stored orphan tx 8fff9c30e2 (mapsz 1) connection timeout trying connection 221.233.196.185:8550 lastseen=1.7hrs Flushed 11177 addresses to peers.dat 72ms connection timeout trying connection 89.155.127.86:8550 lastseen=0.9hrs Added 1 addresses from 72.11.149.185: 75 tried, 11103 new ERROR: FetchInputs() : a46c9d961d mempool Tx prev not found 9333eb1859 ignoring large orphan tx (size: 6877, hash: a46c9d961d) ERROR: FetchInputs() : cad75f7172 mempool Tx prev not found 1c39849890 stored orphan tx cad75f7172 (mapsz 2) connection timeout trying connection 83.67.76.64:8550 lastseen=4.2hrs connection timeout trying connection 68.58.59.48:9333 lastseen=4.2hrs CTxMemPool::accept() : accepted 23f867608f (poolsz 1) received getdata for: tx 23f867608f5b47728de8 connection timeout trying connection 89.215.146.97:10333 lastseen=16.5hrs connection timeout trying connection 24.22.232.249:9333 lastseen=4.2hrs connection timeout trying connection 59.127.132.125:8550 lastseen=0.9hrs connection timeout trying connection 88.152.220.233:9333 lastseen=5.1hrs connection timeout trying connection 89.250.146.130:9333 lastseen=4.4hrs connection timeout trying connection 76.102.246.50:9336 lastseen=7.4hrs ERROR: FetchInputs() : 930b5771b0 mempool Tx prev not found d120b258aa stored orphan tx 930b5771b0 (mapsz 3) connection timeout Added 1 addresses from 67.168.220.0: 75 tried, 11102 new trying connection 95.96.237.164:8550 lastseen=3.6hrs Added 1 addresses from 151.237.52.42: 75 tried, 11102 new ERROR: FetchInputs() : 10f6a43ebb mempool Tx prev not found 6f4ffa730a stored orphan tx 10f6a43ebb (mapsz 4) connection timeout trying connection 218.22.14.66:9333 lastseen=9.5hrs connection timeout trying connection 37.191.131.44:8550 lastseen=0.9hrs connection timeout trying connection 216.19.188.208:9333 lastseen=4.2hrs connected 216.19.188.208:9333 send version message: version 60001, blocks=18468, us=x.x.x.x:8550, them=216.19.188.208:9333, peer=216.19.188.208:9333 Added time data, samples 9, offset -3 (+0 minutes) nTimeOffset = -11 (+0 minutes) receive version message: version 60001, blocks=361774, us=x.x.x.x:37656, them=216.19.188.208:9333, peer=216.19.188.208:9333 trying connection 64.107.73.16:8550 lastseen=0.9hrs Added 371 addresses from 216.19.188.208: 75 tried, 11066 new Added 378 addresses from 216.19.188.208: 75 tried, 11054 new connection timeout Added 222 addresses from 216.19.188.208: 75 tried, 11067 new trying connection 92.206.55.192:8550 lastseen=0.9hrs ERROR: FetchInputs() : b20ed3ad9f mempool Tx prev not found 5985b453c5 stored orphan tx b20ed3ad9f (mapsz 5) connection timeout --- Title: Re: [NBL] Client issue, fully synced .. then suddenly! 340,000 blocks remaining! Post by: HuuHachu on May 30, 2013, 07:13:28 AM "blocks=361774"
this is the exact length of the litecoin chain ... I already saw this behavior with the gemcoin wallet. I don't think someone is using heaps of dedicated hashing power to break this coin. More like someone tried to bypass the downloading of the blockchain by coying its already downloaded litecoin chain. Or it IS an attack, which just try redirect litecoin hashing power onto your coin ... Either ways, checkpoints should prevent that, don't they ? |
