I saw this ages ago, its great!
What is is is Norse have a bunch of honeypots and they track attacks on the site DEFCON/War Games style, its really quite awesome and pretty to look at.
Its mostly china targeting the US though and you see a few attacks against other countries but they all seem to stem from third world attacking first world.
I think a lot are relatively harmless (people entering wrong IPs or maybe just someone scanning a range of IPs or something like that)... but every once in a while you'll see 5+ from the same IP, those are probably srs bsns... I saw one string of about 50+ from Russia, that was probably VRY srs bsns |
|
|
|
oh, it's on  |
|
|
|
the one I've been having issues with is 'BQS', which does things like so: 2014-07-28 09:13:29 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 09:13:29 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 09:22:29 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 09:22:29 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 09:31:50 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 09:31:50 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 09:41:10 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 09:41:10 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 09:50:30 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 09:50:30 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 09:59:50 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 09:59:50 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 10:08:50 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 10:08:50 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 10:18:10 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 10:18:10 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 10:27:31 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 10:27:31 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 10:36:51 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 10:36:51 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 10:46:11 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 10:46:11 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 10:55:31 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2014-07-28 10:55:31 ProcessMessage(ping, 0 bytes) FAILED peer=20713
2014-07-28 13:04:52 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
& 2014-07-26 21:55:39 Added connection to 188.40.12.226:38943 peer=18016
2014-07-26 21:55:39 send version message: version 70002, blocks=312616, us=xx.xx.xx.xx:8333, them=188.40.12.226:38943, peer=18016
2014-07-27 01:00:19 Misbehaving: 188.40.12.226:38943 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-27 03:44:58 Added connection to 188.40.12.226:46300 peer=18517
2014-07-27 03:44:58 send version message: version 70002, blocks=312662, us=xx.xx.xx.xx:8333, them=188.40.12.226:46300, peer=18517
2014-07-27 05:04:56 Misbehaving: 188.40.12.226:46300 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-27 05:48:47 connection from 188.40.12.226:39379 dropped (banned)
2014-07-27 05:51:59 connection from 188.40.12.226:51636 dropped (banned)
2014-07-27 07:18:32 Added connection to 188.40.12.226:44293 peer=18814
2014-07-27 07:18:32 send version message: version 70002, blocks=312683, us=xx.xx.xx.xx:8333, them=188.40.12.226:44293, peer=18814
2014-07-27 09:11:04 Misbehaving: 188.40.12.226:44293 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-27 11:14:54 Added connection to 188.40.12.226:52359 peer=19145
2014-07-27 11:14:54 send version message: version 70002, blocks=312705, us=xx.xx.xx.xx:8333, them=188.40.12.226:52359, peer=19145
2014-07-27 12:31:54 Misbehaving: 188.40.12.226:52359 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-27 12:34:47 connection from 188.40.12.226:48999 dropped (banned)
2014-07-27 12:45:46 connection from 188.40.12.226:34948 dropped (banned)
2014-07-27 14:36:41 Added connection to 188.40.12.226:39096 peer=19373
2014-07-27 14:36:41 send version message: version 70002, blocks=312732, us=xx.xx.xx.xx:8333, them=188.40.12.226:39096, peer=19373
2014-07-27 16:03:20 Misbehaving: 188.40.12.226:39096 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-27 16:30:54 connection from 188.40.12.226:56096 dropped (banned)
2014-07-27 17:19:32 connection from 188.40.12.226:46075 dropped (banned)
2014-07-27 18:01:07 Added connection to 188.40.12.226:37497 peer=19648
2014-07-27 18:01:07 send version message: version 70002, blocks=312754, us=xx.xx.xx.xx:8333, them=188.40.12.226:37497, peer=19648
2014-07-27 20:43:56 Misbehaving: 188.40.12.226:37497 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-27 20:51:42 connection from 188.40.12.226:33495 dropped (banned)
2014-07-27 23:21:33 Added connection to 188.40.12.226:35127 peer=20044
2014-07-27 23:21:33 send version message: version 70002, blocks=312776, us=xx.xx.xx.xx:8333, them=188.40.12.226:35127, peer=20044
2014-07-28 01:04:16 Misbehaving: 188.40.12.226:35127 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-28 03:35:34 Added connection to 188.40.12.226:59147 peer=20312
2014-07-28 03:35:34 send version message: version 70002, blocks=312798, us=xx.xx.xx.xx:8333, them=188.40.12.226:59147, peer=20312
2014-07-28 05:49:35 Misbehaving: 188.40.12.226:59147 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-28 06:21:25 connection from 188.40.12.226:37116 dropped (banned)
2014-07-28 08:54:52 Added connection to 188.40.12.226:47199 peer=20713
2014-07-28 08:54:52 send version message: version 70002, blocks=312830, us=xx.xx.xx.xx:8333, them=188.40.12.226:47199, peer=20713
2014-07-28 10:57:31 Misbehaving: 188.40.12.226:47199 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-28 14:22:45 Added connection to 188.40.12.226:33599 peer=21149
2014-07-28 14:22:45 send version message: version 70002, blocks=312869, us=xx.xx.xx.xx:8333, them=188.40.12.226:33599, peer=21149
2014-07-28 15:45:03 Misbehaving: 188.40.12.226:33599 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-28 17:26:29 connection from 188.40.12.226:39673 dropped (banned)
2014-07-28 17:41:02 Added connection to 188.40.12.226:39551 peer=21434
2014-07-28 17:41:02 send version message: version 70002, blocks=312887, us=xx.xx.xx.xx:8333, them=188.40.12.226:39551, peer=21434
2014-07-28 20:44:36 Misbehaving: 188.40.12.226:39551 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-28 21:22:02 connection from 188.40.12.226:33597 dropped (banned)
2014-07-28 22:45:04 Added connection to 188.40.12.226:52955 peer=21819
2014-07-28 22:45:04 send version message: version 70002, blocks=312916, us=xx.xx.xx.xx:8333, them=188.40.12.226:52955, peer=21819
2014-07-28 23:17:35 Misbehaving: 188.40.12.226:52955 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-28 23:54:27 connection from 188.40.12.226:47368 dropped (banned)
2014-07-29 03:35:45 Added connection to 188.40.12.226:60518 peer=22136
2014-07-29 03:35:45 send version message: version 70002, blocks=312949, us=xx.xx.xx.xx:8333, them=188.40.12.226:60518, peer=22136
2014-07-29 04:45:12 Misbehaving: 188.40.12.226:60518 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-29 07:32:33 Added connection to 188.40.12.226:41216 peer=22409
2014-07-29 07:32:33 send version message: version 70002, blocks=312975, us=xx.xx.xx.xx:8333, them=188.40.12.226:41216, peer=22409
2014-07-29 08:29:21 Misbehaving: 188.40.12.226:41216 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-29 08:54:33 connection from 188.40.12.226:46403 dropped (banned)
2014-07-29 08:54:48 connection from 188.40.12.226:47370 dropped (banned)
2014-07-29 08:56:02 connection from 188.40.12.226:52084 dropped (banned)
2014-07-29 10:51:52 Added connection to 188.40.12.226:57688 peer=22696
2014-07-29 10:51:52 send version message: version 70002, blocks=312997, us=xx.xx.xx.xx:8333, them=188.40.12.226:57688, peer=22696
2014-07-29 12:19:52 Misbehaving: 188.40.12.226:57688 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-29 12:55:10 connection from 188.40.12.226:53337 dropped (banned)
2014-07-29 13:53:31 connection from 188.40.12.226:36099 dropped (banned)
2014-07-29 14:48:06 Added connection to 188.40.12.226:49371 peer=22972
2014-07-29 14:48:06 send version message: version 70002, blocks=313018, us=xx.xx.xx.xx:8333, them=188.40.12.226:49371, peer=22972
2014-07-29 16:30:06 Misbehaving: 188.40.12.226:49371 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-29 17:32:27 connection from 188.40.12.226:49839 dropped (banned)
2014-07-29 17:35:09 connection from 188.40.12.226:60271 dropped (banned)
2014-07-29 18:51:41 Added connection to 188.40.12.226:45856 peer=23263
2014-07-29 18:51:41 send version message: version 70002, blocks=313043, us=xx.xx.xx.xx:8333, them=188.40.12.226:45856, peer=23263
2014-07-29 20:47:24 Misbehaving: 188.40.12.226:45856 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-29 21:55:59 connection from 188.40.12.226:46913 dropped (banned)
2014-07-29 22:44:13 Added connection to 188.40.12.226:35368 peer=23532
2014-07-29 22:44:13 send version message: version 70002, blocks=313072, us=xx.xx.xx.xx:8333, them=188.40.12.226:35368, peer=23532
2014-07-30 00:45:08 Misbehaving: 188.40.12.226:35368 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-30 01:20:13 connection from 188.40.12.226:36136 dropped (banned)
2014-07-30 02:24:11 connection from 188.40.12.226:52747 dropped (banned)
2014-07-30 03:22:10 Added connection to 188.40.12.226:49804 peer=23816
2014-07-30 03:22:10 send version message: version 70002, blocks=313098, us=xx.xx.xx.xx:8333, them=188.40.12.226:49804, peer=23816
2014-07-30 04:14:04 Misbehaving: 188.40.12.226:49804 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-30 04:58:38 connection from 188.40.12.226:54100 dropped (banned)
2014-07-30 08:54:34 Added connection to 188.40.12.226:57900 peer=25759
2014-07-30 08:54:34 send version message: version 70002, blocks=313140, us=xx.xx.xx.xx:8333, them=188.40.12.226:57900, peer=25759
2014-07-30 11:31:09 Misbehaving: 188.40.12.226:57900 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-30 11:31:31 connection from 188.40.12.226:57044 dropped (banned)
2014-07-30 11:42:04 connection from 188.40.12.226:41208 dropped (banned)
2014-07-30 11:43:28 connection from 188.40.12.226:46636 dropped (banned)
2014-07-30 15:18:30 Added connection to 188.40.12.226:57297 peer=26246
2014-07-30 15:18:30 send version message: version 70002, blocks=313186, us=xx.xx.xx.xx:8333, them=188.40.12.226:57297, peer=26246
2014-07-30 16:37:18 Misbehaving: 188.40.12.226:57297 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-30 17:05:30 connection from 188.40.12.226:47897 dropped (banned)
2014-07-30 17:07:36 connection from 188.40.12.226:56015 dropped (banned)
2014-07-30 18:07:06 connection from 188.40.12.226:60463 dropped (banned)
2014-07-30 19:18:45 Added connection to 188.40.12.226:55029 peer=26550
2014-07-30 19:18:45 send version message: version 70002, blocks=313220, us=xx.xx.xx.xx:8333, them=188.40.12.226:55029, peer=26550
2014-07-30 21:27:10 Misbehaving: 188.40.12.226:55029 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-31 03:07:25 Added connection to 188.40.12.226:53562 peer=27077
2014-07-31 03:07:25 send version message: version 70002, blocks=313269, us=xx.xx.xx.xx:8333, them=188.40.12.226:53562, peer=27077
2014-07-31 05:44:24 Misbehaving: 188.40.12.226:53562 (200 -> 300) BAN THRESHOLD EXCEEDED
2014-07-31 06:54:09 connection from 188.40.12.226:55539 dropped (banned)
2014-07-31 09:02:01 Added connection to 188.40.12.226:33634 peer=27532
2014-07-31 09:02:01 send version message: version 70002, blocks=313306, us=xx.xx.xx.xx:8333, them=188.40.12.226:33634, peer=27532
2014-07-31 10:36:55 Misbehaving: 188.40.12.226:33634 (200 -> 300) BAN THRESHOLD EXCEEDED
Also "Perone" which continually attempts to send invalid transactions, 2014-07-29 10:08:07 Added connection to 108.45.93.68:35206 peer=22621
2014-07-29 10:08:11 send version message: version 70002, blocks=312993, us=5.9.24.81:8333, them=108.45.93.68:35206, peer=22621
2014-07-29 10:08:11 receive version message: /Perone:0.0.1/: version 60002, blocks=0, us=0.0.0.0:8333, peer=22621
2014-07-29 10:08:11 ProcessMessages(None, 0 bytes) : CHECKSUM ERROR nChecksum=e2e0f65d hdr.nChecksum=00000000
2014-07-29 10:08:15 ProcessMessage(version, 99 bytes) FAILED peer=22621
2014-07-29 10:08:15 ProcessMessages(None, 0 bytes) : CHECKSUM ERROR nChecksum=e2e0f65d hdr.nChecksum=00000000
2014-07-29 10:08:15 ProcessMessage(version, 100 bytes) FAILED peer=22621
2014-07-29 10:08:44 Added connection to 108.45.93.68:44198 peer=22622
2014-07-29 10:08:48 send version message: version 70002, blocks=312993, us=5.9.24.81:8333, them=108.45.93.68:44198, peer=22622
2014-07-29 10:08:48 receive version message: /Perone:0.0.1/: version 60002, blocks=0, us=0.0.0.0:8333, peer=22622
2014-07-29 10:08:48 ProcessMessages(None, 0 bytes) : CHECKSUM ERROR nChecksum=e2e0f65d hdr.nChecksum=00000000
2014-07-29 10:08:51 ProcessMessage(version, 99 bytes) FAILED peer=22622
2014-07-29 10:08:51 ProcessMessages(None, 0 bytes) : CHECKSUM ERROR nChecksum=e2e0f65d hdr.nChecksum=00000000
2014-07-29 10:08:51 ProcessMessage(version, 100 bytes) FAILED peer=22622
very persistent, too 2014-07-29 06:03:36 send version message: version 70002, blocks=312968, us=xx.xx.xx.xx:8333, them=108.45.93.68:48962, peer=22314
2014-07-29 09:53:17 Added connection to 108.45.93.68:53714 peer=22579
2014-07-29 09:53:17 send version message: version 70002, blocks=312991, us=xx.xx.xx.xx:8333, them=108.45.93.68:53714, peer=22579
2014-07-29 09:53:48 Added connection to 108.45.93.68:53785 peer=22580
2014-07-29 09:53:48 send version message: version 70002, blocks=312991, us=xx.xx.xx.xx:8333, them=108.45.93.68:53785, peer=22580
2014-07-29 09:54:19 Added connection to 108.45.93.68:48949 peer=22581
2014-07-29 09:54:21 send version message: version 70002, blocks=312991, us=xx.xx.xx.xx:8333, them=108.45.93.68:48949, peer=22581
2014-07-29 09:54:52 Added connection to 108.45.93.68:45567 peer=22583
2014-07-29 09:54:54 send version message: version 70002, blocks=312991, us=xx.xx.xx.xx:8333, them=108.45.93.68:45567, peer=22583
2014-07-29 09:55:25 Added connection to 108.45.93.68:40856 peer=22584
2014-07-29 09:55:27 send version message: version 70002, blocks=312991, us=xx.xx.xx.xx:8333, them=108.45.93.68:40856, peer=22584
2014-07-29 09:56:02 Added connection to 108.45.93.68:37665 peer=22585
2014-07-29 09:56:10 send version message: version 70002, blocks=312992, us=xx.xx.xx.xx:8333, them=108.45.93.68:37665, peer=22585
2014-07-29 09:56:41 Added connection to 108.45.93.68:33608 peer=22587
2014-07-29 09:56:45 send version message: version 70002, blocks=312992, us=xx.xx.xx.xx:8333, them=108.45.93.68:33608, peer=22587
2014-07-29 09:57:18 Added connection to 108.45.93.68:60662 peer=22589
2014-07-29 09:57:21 send version message: version 70002, blocks=312992, us=xx.xx.xx.xx:8333, them=108.45.93.68:60662, peer=22589
2014-07-29 09:57:55 Added connection to 108.45.93.68:47991 peer=22590
2014-07-29 09:57:57 send version message: version 70002, blocks=312992, us=xx.xx.xx.xx:8333, them=108.45.93.68:47991, peer=22590
2014-07-29 09:58:32 Added connection to 108.45.93.68:56927 peer=22593
2014-07-29 09:58:35 send version message: version 70002, blocks=312992, us=xx.xx.xx.xx:8333, them=108.45.93.68:56927, peer=22593
2014-07-29 09:59:07 Added connection to 108.45.93.68:37331 peer=22594
2014-07-29 09:59:12 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:37331, peer=22594
2014-07-29 09:59:42 Added connection to 108.45.93.68:46084 peer=22595
2014-07-29 09:59:48 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:46084, peer=22595
2014-07-29 10:02:19 Added connection to 108.45.93.68:45583 peer=22602
2014-07-29 10:02:19 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:45583, peer=22602
2014-07-29 10:02:50 Added connection to 108.45.93.68:40929 peer=22604
2014-07-29 10:02:52 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:40929, peer=22604
2014-07-29 10:03:24 Added connection to 108.45.93.68:36324 peer=22605
2014-07-29 10:03:27 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:36324, peer=22605
2014-07-29 10:03:58 Added connection to 108.45.93.68:59002 peer=22606
2014-07-29 10:04:00 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:59002, peer=22606
2014-07-29 10:04:32 Added connection to 108.45.93.68:54253 peer=22608
2014-07-29 10:04:36 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:54253, peer=22608
2014-07-29 10:05:09 Added connection to 108.45.93.68:50509 peer=22610
2014-07-29 10:05:13 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:50509, peer=22610
2014-07-29 10:05:45 Added connection to 108.45.93.68:46643 peer=22613
2014-07-29 10:05:48 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:46643, peer=22613
2014-07-29 10:06:21 Added connection to 108.45.93.68:35701 peer=22614
2014-07-29 10:06:24 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:35701, peer=22614
2014-07-29 10:06:56 Added connection to 108.45.93.68:44695 peer=22617
2014-07-29 10:07:00 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:44695, peer=22617
2014-07-29 10:07:32 Added connection to 108.45.93.68:53990 peer=22619
2014-07-29 10:07:37 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:53990, peer=22619
2014-07-29 10:08:07 Added connection to 108.45.93.68:35206 peer=22621
2014-07-29 10:08:11 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:35206, peer=22621
2014-07-29 10:08:44 Added connection to 108.45.93.68:44198 peer=22622
2014-07-29 10:08:48 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:44198, peer=22622
2014-07-29 10:09:21 Added connection to 108.45.93.68:53507 peer=22623
2014-07-29 10:09:25 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:53507, peer=22623
2014-07-29 10:09:57 Added connection to 108.45.93.68:34219 peer=22624
2014-07-29 10:10:01 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:34219, peer=22624
2014-07-29 10:10:31 Added connection to 108.45.93.68:43703 peer=22625
2014-07-29 10:10:35 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:43703, peer=22625
2014-07-29 10:11:08 Added connection to 108.45.93.68:52972 peer=22626
2014-07-29 10:11:13 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:52972, peer=22626
2014-07-29 10:11:45 Added connection to 108.45.93.68:34106 peer=22627
2014-07-29 10:11:49 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:34106, peer=22627
2014-07-29 10:12:22 Added connection to 108.45.93.68:43276 peer=22628
2014-07-29 10:12:26 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:43276, peer=22628
2014-07-29 10:12:57 Added connection to 108.45.93.68:52498 peer=22629
2014-07-29 10:12:59 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:52498, peer=22629
2014-07-29 10:17:09 Added connection to 108.45.93.68:59345 peer=22635
2014-07-29 10:17:10 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:59345, peer=22635
2014-07-29 10:17:42 Added connection to 108.45.93.68:53285 peer=22636
2014-07-29 10:17:44 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:53285, peer=22636
2014-07-29 10:18:18 Added connection to 108.45.93.68:48540 peer=22637
2014-07-29 10:18:22 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:48540, peer=22637
2014-07-29 10:18:54 Added connection to 108.45.93.68:44511 peer=22638
2014-07-29 10:18:57 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:44511, peer=22638
2014-07-29 10:25:04 Added connection to 108.45.93.68:54593 peer=22649
2014-07-29 10:25:12 send version message: version 70002, blocks=312993, us=xx.xx.xx.xx:8333, them=108.45.93.68:54593, peer=22649
2014-07-29 10:28:46 Added connection to 108.45.93.68:55362 peer=22654
2014-07-29 10:28:55 send version message: version 70002, blocks=312995, us=xx.xx.xx.xx:8333, them=108.45.93.68:55362, peer=22654
2014-07-29 10:31:55 Added connection to 108.45.93.68:57815 peer=22658
2014-07-29 10:32:02 send version message: version 70002, blocks=312996, us=xx.xx.xx.xx:8333, them=108.45.93.68:57815, peer=22658
2014-07-29 10:32:31 Added connection to 108.45.93.68:32943 peer=22660
2014-07-29 10:32:34 send version message: version 70002, blocks=312996, us=xx.xx.xx.xx:8333, them=108.45.93.68:32943, peer=22660
2014-07-29 10:34:45 Added connection to 108.45.93.68:43237 peer=22663
2014-07-29 10:34:54 send version message: version 70002, blocks=312996, us=xx.xx.xx.xx:8333, them=108.45.93.68:43237, peer=22663
2014-07-29 10:38:16 Added connection to 108.45.93.68:40164 peer=22670
2014-07-29 10:38:27 send version message: version 70002, blocks=312996, us=xx.xx.xx.xx:8333, them=108.45.93.68:40164, peer=22670
2014-07-29 10:43:07 Added connection to 108.45.93.68:55088 peer=22677
2014-07-29 10:43:14 send version message: version 70002, blocks=312997, us=xx.xx.xx.xx:8333, them=108.45.93.68:55088, peer=22677
2014-07-29 10:46:58 Added connection to 108.45.93.68:47480 peer=22687
2014-07-29 10:47:05 send version message: version 70002, blocks=312997, us=xx.xx.xx.xx:8333, them=108.45.93.68:47480, peer=22687
2014-07-29 10:50:04 Added connection to 108.45.93.68:53210 peer=22692
2014-07-29 10:50:07 send version message: version 70002, blocks=312997, us=xx.xx.xx.xx:8333, them=108.45.93.68:53210, peer=22692
2014-07-29 10:51:39 Added connection to 108.45.93.68:36302 peer=22695
2014-07-29 10:51:44 send version message: version 70002, blocks=312997, us=xx.xx.xx.xx:8333, them=108.45.93.68:36302, peer=22695
2014-07-29 10:53:34 Added connection to 108.45.93.68:60510 peer=22699
2014-07-29 10:53:36 send version message: version 70002, blocks=312997, us=xx.xx.xx.xx:8333, them=108.45.93.68:60510, peer=22699
2014-07-29 11:04:26 Added connection to 108.45.93.68:32953 peer=22717
2014-07-29 11:04:33 send version message: version 70002, blocks=312999, us=xx.xx.xx.xx:8333, them=108.45.93.68:32953, peer=22717
2014-07-29 11:09:46 Added connection to 108.45.93.68:53183 peer=22725
2014-07-29 11:09:50 send version message: version 70002, blocks=313000, us=xx.xx.xx.xx:8333, them=108.45.93.68:53183, peer=22725
2014-07-29 11:15:16 Added connection to 108.45.93.68:60638 peer=22730
2014-07-29 11:15:26 send version message: version 70002, blocks=313001, us=xx.xx.xx.xx:8333, them=108.45.93.68:60638, peer=22730
2014-07-29 11:19:13 Added connection to 108.45.93.68:39886 peer=22734
2014-07-29 11:19:20 send version message: version 70002, blocks=313001, us=xx.xx.xx.xx:8333, them=108.45.93.68:39886, peer=22734
2014-07-29 11:23:35 Added connection to 108.45.93.68:47335 peer=22741
2014-07-29 11:23:43 send version message: version 70002, blocks=313001, us=xx.xx.xx.xx:8333, them=108.45.93.68:47335, peer=22741
2014-07-29 11:27:22 Added connection to 108.45.93.68:54765 peer=22745
2014-07-29 11:27:31 send version message: version 70002, blocks=313002, us=xx.xx.xx.xx:8333, them=108.45.93.68:54765, peer=22745
2014-07-29 11:29:15 Added connection to 108.45.93.68:33940 peer=22747
2014-07-29 11:29:22 send version message: version 70002, blocks=313002, us=xx.xx.xx.xx:8333, them=108.45.93.68:33940, peer=22747
2014-07-29 11:31:14 Added connection to 108.45.93.68:41112 peer=22752
2014-07-29 11:31:24 send version message: version 70002, blocks=313003, us=xx.xx.xx.xx:8333, them=108.45.93.68:41112, peer=22752
2014-07-29 11:34:00 Added connection to 108.45.93.68:48305 peer=22757
2014-07-29 11:34:07 send version message: version 70002, blocks=313003, us=xx.xx.xx.xx:8333, them=108.45.93.68:48305, peer=22757
2014-07-29 11:39:12 Added connection to 108.45.93.68:55994 peer=22762
2014-07-29 11:39:17 send version message: version 70002, blocks=313003, us=xx.xx.xx.xx:8333, them=108.45.93.68:55994, peer=22762
2014-07-29 11:40:59 Added connection to 108.45.93.68:34992 peer=22765
108.45.93.67, 108.45.93.68, 108.45.93.69, etc. for Perone (guess need to block 108.45.93.0 at least, if not 108.45.0.0, but I don't want to since it's Verizon), 188.40.12.226 and 88.198.17.7 for BQS. |
|
|
|
My internet speed is solid at around 10-15 mb/sec. How long would it take for me to download the entire blockchain for the original bitcoin wallet?
Time taken to verify the blocks can take more time than downloading it. Your peers' latency and speed can also affect your blockchain download speed. Even if you have lightning fast internet, if your peers have slow internet, you would likely to take a longer time to download. You can always use a lightweight wallet if you prefer not to wait for so long. That can always be fixed by temporarily setting maxconnections=1 and connect=(fast server). You avoid getting all the 'orphan blocks' that way as well, from multiple nodes sending you blocks. You can use 5.9.24.81, 75.102.27.50, 107.155.104.194, or 199.233.245.125 right now, if you like |
|
|
|
These blockchain.info phishing sites are popping up like weeds.
Yeah, usually see at least a few every month. I guess it's an easy scam really. Wouldn't be so much of it if it wasn't so lucrative. I've always used inspect element on random links. |
|
|
|
It seems like emails from random retards based on blockchain.info information can get your Hetzner server blocked! www.nogleg.com/hetzner.txtoh, the shame |
|
|
|
www.nogleg.com/hetzner.txti've got a few more msgs from them also have to fix it to include it all. just going to leave everything as is, nothing to hide etc ed: ok, all included now
|
|
|
|
> Date: Sat, 2 Aug 2014 20:54:08 +0200 > From: abuse@hetzner.de> To: hosis@<redacted> > Subject: Abuse Message [AbuseID:111E82:12]: AbuseNormal: this guy robbed me all my bitcoins > > Dear Mr James <redacted>, > > As you could not solve the problem within the given time or the maximum number of tests, the ticket will be forwarded for manual testing to our technician who will coordinate how to proceed further. > > If we received multiple complaints, the situation can be lead to a server blocking. > > Important note: > When you reply to us, please leave the abuse ID [AbuseID:111E82:12] unchanged in the subject line. > > Best regards, > > Hetzner-Support > > Hetzner Online AG > Industriestr. 25 > 91710 Gunzenhausen > Tel: +49 (9831) 505-0 > Fax: +49 (9831) 505-3 > abuse@hetzner.de> www.hetzner.de> > Register Court: Registergericht Ansbach, HRB 3204 > Management Board: Dipl. Ing. (FH) Martin Hetzner > Chairwoman of the Supervisory Board: Diana Rothhan |
|
|
|
stupid twats > Date: Fri, 1 Aug 2014 10:53:54 +0200 > From: abuse@hetzner.de> To: hosis@<redacted> > Subject: Abuse Message [AbuseID:111E82:12]: AbuseNormal: this guy robbed me all my bitcoins > > Dear Mr James <redacted>, > > We have received information regarding spam and/or abuse from samm.engine@gmail.com. > > Please would you take all necessary measures to avoid this in future. > > Furthermore, we request that you send a short response within 24 hours to us and to the complainant. This response should contain information about how this issue could happen and what you intend to do about it. > > How to proceed: > > - Solve the problem. > - Send a response to us using the following link: http://abuse.hetzner.de/statements/?token=faced2477bfcdd49eb2573f03709cb2f> - Send a response by email to the complainant > > A technician will check the data and coordinate further proceedings. If multiple complaints have been received, the situation could lead to the server being blocked. > > Important note: > When replying to us, please leave the abuse ID [AbuseID:111E82:12] unchanged in the subject line. > > > Best regards, > > Dominik Prüßner > > Hetzner Online AG > Industriestr. 25 > 91710 Gunzenhausen > Tel: +49 (9831) 505-0 > Fax: +49 (9831) 505-3 > abuse@hetzner.de> www.hetzner.de> > Register Court: Registergericht Ansbach, HRB 3204 > Management Board: Dipl. Ing. (FH) Martin Hetzner > Chairwoman of the Supervisory Board: Diana Rothhan > > ----- attachment ----- > > Return-path: < samm.engine@gmail.com> > Envelope-to: abuse@hetzner.de> Delivery-date: Thu, 31 Jul 2014 22:55:06 +0200 > Received: from [209.85.220.51] (helo=mail-pa0-f51.google.com) > by lms.your-server.de with esmtps (TLSv1:RC4-SHA:128) > (Exim 4.74) > (envelope-from < samm.engine@gmail.com>) > id 1XCxNR-0002xa-N4 > for abuse@hetzner.de; Thu, 31 Jul 2014 22:55:06 +0200 > Received: by mail-pa0-f51.google.com with SMTP id ey11so4397394pad.10 > for < abuse@hetzner.de>; Thu, 31 Jul 2014 13:54:55 -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=20120113; > h=mime-version:date:message-id:subject:from:to:content-type; > bh=gVampOjFFYoXcs5UyrQQ/erdsQewzSTZuGkU1e1GlYQ=; > b=YugGlzUr6fjWh7z2UkjkTtM4wkBvXujtf+wb9qWNTMEAjd0jDq5zb7WIt/nTy2fVXE > AdzQWbSnC+uWNfvHX6MT+bir97XGYAcygvcrh6Fr+Zw21WK0q1MWKxy4y0aIZV72WRQl > QkWMhhiB6F/2j3/PJEG1AmwAR+5zU9XsRe7ycy77NM9i1sXX8u+VD6kOtmbOrg3+R4A2 > 4QZG9ytitN/dw+GXret0mGoKzT6Sf1L6Wr8xBEicChQ5uysvaqLxmnDWNh7Ts0ckVl7r > mc9r//TU4XMkgF7g2MM3GBye6tV+WQ0RFqHnCObHGnFj9koygBEJTlXWpC/VZhzpAyLh > I53Q== > MIME-Version: 1.0 > X-Received: by 10.66.180.98 with SMTP id dn2mr766883pac.83.1406840095409; Thu, > 31 Jul 2014 13:54:55 -0700 (PDT) > Received: by 10.70.127.236 with HTTP; Thu, 31 Jul 2014 13:54:55 -0700 (PDT) > Date: Thu, 31 Jul 2014 17:54:55 -0300 > Message-ID: <CAD7O+conmqOQVqRsdE-+XR+1Ou=-9=O1WKoB8kosMt=JhBkoKw@mail.gmail.com> > Subject: this guy robbed me all my bitcoins > From: Sammir Bruzzone < samm.engine@gmail.com> > To: abuse@hetzner.de> Content-Type: multipart/alternative; boundary=047d7bdc9dee253efd04ff837c4e > X-Virus-Scanned: Clear (ClamAV 0.98.1/19250/Thu Jul 31 18:01:16 2014) > X-Spam-Score: 0.5 (/) > Delivered-To: he1-abuse@hetzner.de> > --047d7bdc9dee253efd04ff837c4e > Content-Type: text/plain; charset=UTF-8 > > hi this guy are robbed coins around the world, you can see how much has > robbed in coupe hours > https://blockchain.info/es/tx/77fb92156ab79f6c44609dd9801a7f96f85330a406fb9b4312ef6da78ccc1fd6/0> (there is my coins) > > https://blockchain.info/es/ip-address/5.9.24.81?offset=100 (all the > trasactions done) > |
|
|
|
Maybe it should be changed to "udp://open.demonii.com:1337" like all the newer torrents? This new tracker is accessible worldwide.
udp://open.demonii.com:1337 is by far the best also udp://tracker.openbittorrent.com:80/announce udp://tracker.publicbt.com:80/announce http: //open.nyaatorrents.info:6544/announce , which i guess you can use for things other than anime udp://tracker.ex.ua:80/announce udp://coppersurfer.tk:6969/announce udp://9.rarbg.com:2710/announce udp://glotorrents.com:6969/announce and istole.it still works i guess |
|
|
|
|
haha, grats to the two other people that used my pool, i was able to sell 300,000 aliencoins for 500.
ofc it's down now, as it's no longer worth mining. ya'll is too late , and such
P2pool is back up at sloth.nogleg.com:1911
It is better than MPOS, which is POS, because of fools stealing all your coins
|
|
|
|
BTCJam wants me to strike a pose with my driver's license, which isn't going to happen. If I don't need to do it to open an online banking account, then I shouldn't need to do it to register for BTCJam. Aha, my BTC Jam account: https://btcjam.com/users/28002Actually, I'd prefer to do this through BTCJam, but I'm hesitant to accost a friend or some bum on the side of the road to strike a pose. Ideas? |
|
|
|
We have to download a special client? Sooooo.... You want us to be part of your botnet... Thanks, but no.
Hitleap is trusted. I have been using it for website hits. Just because it works doesn't mean there's nothing going on in the background that you don't know about. Thanks for the input. But I'm still gonna stay away from this one. The amount that the OP is offering is very small, and not worth even the small risk of a virus. Is there some cheap dual Opteron or dual Xeon config out there with 32 threads? I know the 5639 is cheap as hell for 24... so run VMWare or some such, 24 * 1440 * 0.000001 = 0.03456BTC a day? Where am I off here? |
|
|
|
So, is it wrong for me to think that user X out of Africa or user Y out of Croatia that created their eBay account one month ago, is just doing 'reputation' loans to build up to a worthwhile amount to run off with? It's like a big ponzi, but since you can take out multiple loans, the first ones in even lose sometimes. ed: I can't even ask for a loan, since apparently I'm supposed to photograph myself holding up my DL. LOL, gmafb. Any chump can do that, it doesn't mean they're legit. https://btcjam.com/users/28002Any day over most of those verified profiles |
|
|
|
TOR is much better option than VPN
VPN is much faster than TOR. TOR gave me migraines w/ its slowness. VPNs are cheap. |
|
|
|
I don't know what they did in their driver that needs such a large queue. I'd recommend a queue of 1 for every piece of hardware, always, on p2pool, unless there is some unique issue with the device that really needs it larger. S3 might fall into that category. Scan and expiry do nothing useful on today's hardware, today's stratum mining or with p2pool. All recommendations you may read are misguided. Bitmain really is using an older cgminer; they just kept working with the codebase they forked when they first created their own cgminer driver fork for S1.
EDIT: Virtually all manipulations of queue are also misguided, even if for other pools; the default is best there.
Thanks for your help. If I understand you correctly, the following are your recommendations: - For p2pool, queue depth of 1.
- Certain hardware that uses their own customized fork of cgminer may have different queue depth requirements due to driver implementation
- Scan time and expiry settings are pointless on modern mining hardware
Your guidance is much appreciated. They're pointless, but if you set expiry to 1 you may have some issues. Was scan-time set to 1 and expiry set to 1 *ever* good? I just did a quick google search and it looks like a lot of these GPU miner guides actually recommend that crap. I always used a scan time of 30, expiry of 60 and queue of 1. Was I wrong that whole time? haha |
|
|
|
I think the most secure way to keep your bitcoin safe is to make it so as few people as possible know that you own bitcoins. They will keep you from being subjected from most attacks
What if i get randomly keylogged or infected? They dont need to know it, they will check it. If your not online the keylogger cant reach you. I personally think that "keeping" your bitcoin stored on an offline computer is unnecessary. I think the chances are greater that you will suffer losses from price declines of bitcoin then that you would suffer losses from theft of your coins. Other than just backing up your wallet on a couple different devices (another HDD, USB flash drives, 360KB floppy, w/e), I agree... except every step that bitcoin takes towards being 'mainstream' you'll get people that are less and less tech savvy/computer knowledgeable in general. God knows how much crap they have on their computers already from clicking on random Facebook pictures. ... and then there's the whole thing about wireless, esp. in public areas. |
|
|
|
The only thing you need to copy over to avoid needing to redownload the blockchain is the blocks directory, everything else will be automatically regenerated (except the wallet; if you want to use the same one instead of using a separate one for the other computer, copy wallet.dat as well). If you're moving everything to a different computer and keeping the same wallet, you can copy over everything and it shouldn't need to reindex (saving you ~30min-2hr, depending on your computer). There's no "detatch" command necessary, but Bitcoin-Qt should be closed while you're copying the files.
I've always copied over chainstate... so you're saying you don't need to copy over chainstate on a --reindex? |
|
|
|
|
48 bytes/s? Uh, maybe if you use something that requires really high difficulty to count as a share.. But incoming data should still be just as high..
Anyway, Cudaminer bursted up to around 8kb/s upstream, w/ an average of around 1kb/s, probably. I was using relatively low share difficulty, averaged maybe one every 3 seconds.
|
|
|
|
|
copy & paste them all
you should update your bitcoin version though, 0.8.xx is old
|
|
|
|
|
Show Posts
