|
behindtext (OP)
|
 |
May 13, 2013, 10:45:41 PM |
|
We've just released the second btcd component, btcjson, the JSON-RPC library.
May I ask, why don't you just release the whole client at once? Do you have it already and testing - or not yet finished, but you think it will be finished soon? Unless it's not 'ask a question' type of topic, in which case: sorry, it will probably pop up my ignore digit  we chose not to release all the code at once because it was put together rather quickly. one of the main goals with btcd is to have easy-to-understand code along with full test coverage. having full test coverage runs directly in the face of the "making it work", so we made it work first, and are now polishing the individual pieces and releasing them. i'm not sure if you have checked out the test coverage on btcwire but it exercises every single line of code in the package in the tests. this includes negative testing in order to give all the code a run-through. the btcjson package is similar in quality: 88% of the code has test coverage and that should improve to 100% in the next several days. per my earlier posts in this thread, btcd is up and running against a single local bitcoind node. it can pull the whole blockchain down but you may have noticed that it cannot handle chain forking properly yet. we expect this to be working well and release it soon. full tx verification is under development, a number of experiments are being done to determine how to make it run faster. since these experiments involve changing (sqlite) db schema, it doesn't make sense to release in such a half-baked form, especially when it means users would have to rebuild/restructure their whole db. we expect to have btcd interoperating nicely with bitcoind before June 1st. note that this will not include wallet functionality, we expect that to be ready before July 1st and likely before June 15th. since you're a developer yourself you know how timelines can slip, so be aware these are estimates. |
|
|
|
|
|
|
|
|
|
|
|
|
Make sure you back up your wallet regularly! Unlike a bank account, nobody can help you if you lose access to your BTC.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
Cyrus
Ninja
Administrator
Legendary
 Online
Activity: 3752
Merit: 2948
|
|
May 13, 2013, 11:04:17 PM |
|
Congrats and also, best of luck with taking btcd to the finish line.
|
|
|
|
jcv
Jr. Member
 Offline
Activity: 34
Merit: 1
|
|
May 14, 2013, 12:14:35 AM |
|
We've just released the second btcd component, btcjson, the JSON-RPC library.
May I ask, why don't you just release the whole client at once? Do you have it already and testing - or not yet finished, but you think it will be finished soon? Unless it's not 'ask a question' type of topic, in which case: sorry, it will probably pop up my ignore digit we chose not to release all the code at once because it was put together rather quickly. one of the main goals with btcd is to have easy-to-understand code along with full test coverage. having full test coverage runs directly in the face of the "making it work", so we made it work first, and are now polishing the individual pieces and releasing them. i'm not sure if you have checked out the test coverage on btcwire but it exercises every single line of code in the package in the tests. this includes negative testing in order to give all the code a run-through. the btcjson package is similar in quality: 88% of the code has test coverage and that should improve to 100% in the next several days. Just to build on behindtext's answer, by releasing btcd in pieces, we can get the code out there much faster as parts that are more mature don't have to wait for other parts to come out. Doing it this way also forces us to keep the code in distinct, reusable pieces rather than us building one monolithic thing, which we think will help the overall quality. And it means that if someone else had a project where they want some of the code, they only have to understand the component that they need and not worry about the others at all since they are all separate Go packages. |
|
|
|
|
piotr_n
Legendary
Offline
Activity: 2053
Merit: 1354
aka tonikt
|
|
May 14, 2013, 06:14:34 PM
Last edit: May 14, 2013, 06:42:36 PM by piotr_n |
|
We've just released the second btcd component, btcjson, the JSON-RPC library.
May I ask, why don't you just release the whole client at once? Do you have it already and testing - or not yet finished, but you think it will be finished soon? Unless it's not 'ask a question' type of topic, in which case: sorry, it will probably pop up my ignore digit we chose not to release all the code at once because it was put together rather quickly. one of the main goals with btcd is to have easy-to-understand code along with full test coverage. having full test coverage runs directly in the face of the "making it work", so we made it work first, and are now polishing the individual pieces and releasing them. i'm not sure if you have checked out the test coverage on btcwire but it exercises every single line of code in the package in the tests. this includes negative testing in order to give all the code a run-through. the btcjson package is similar in quality: 88% of the code has test coverage and that should improve to 100% in the next several days. per my earlier posts in this thread, btcd is up and running against a single local bitcoind node. it can pull the whole blockchain down but you may have noticed that it cannot handle chain forking properly yet. we expect this to be working well and release it soon. full tx verification is under development, a number of experiments are being done to determine how to make it run faster. since these experiments involve changing (sqlite) db schema, it doesn't make sense to release in such a half-baked form, especially when it means users would have to rebuild/restructure their whole db. we expect to have btcd interoperating nicely with bitcoind before June 1st. note that this will not include wallet functionality, we expect that to be ready before July 1st and likely before June 15th. since you're a developer yourself you know how timelines can slip, so be aware these are estimates. That's fair enough - thanks for explaining. I wish you all the best with the project guys, though if you do not have tx verification fully implemented yet, I think your dates might be a bit too optimistic. Also, from my own experience, I think sqlite might not be the best choice, as for a DB backend for bitcoin. I would rather advise you to look into Go ports of LevelDB. Unfortunately none of them is quite finished yet. Myself, I was trying everything; from mysql to each available port of leveldb - but at the end I decided that they all suck and created my own database engine. You're welcome to use it, if you want, though I should warn you that it has about 0% of test coverage, and a great appetite for system memory. You can order it to free the mem, but then it will be much slower when you need the data. And that's why I recently bought 8 more gigs of RAM, just so I would not need to free the mem... at least for the next couple of months  |
Check out gocoin - my original project of full bitcoin node & cold wallet written in Go.PGP fingerprint: AB9E A551 E262 A87A 13BB 9059 1BE7 B545 CDF3 FD0E
|
|
|
jcv
Jr. Member
Offline
Activity: 34
Merit: 1
|
|
May 15, 2013, 02:28:49 PM |
|
Also, from my own experience, I think sqlite might not be the best choice, as for a DB backend for bitcoin. I would rather advise you to look into Go ports of LevelDB. Unfortunately none of them is quite finished yet.
We've definitely looked at LevelDB and seem to alternate between being excited about it and disappointed that the Go ports aren't done enough yet. Those will be pretty interesting once they get a little more mature though. |
|
|
|
|
piotr_n
Legendary
Offline
Activity: 2053
Merit: 1354
aka tonikt
|
|
May 15, 2013, 02:51:21 PM |
|
We've definitely looked at LevelDB and seem to alternate between being excited about it and disappointed that the Go ports aren't done enough yet. Yep, I know exactly what you mean And it's even more disappointing when you know that both; Go and LevelDB are products developed by Google. |
Check out gocoin - my original project of full bitcoin node & cold wallet written in Go.PGP fingerprint: AB9E A551 E262 A87A 13BB 9059 1BE7 B545 CDF3 FD0E
|
|
|
Mike Hearn
Legendary
Offline
Activity: 1526
Merit: 1129
|
|
May 16, 2013, 01:04:06 AM |
|
What do you mean by port? Aren't the bindings sufficient? https://github.com/jmhodges/levigo#readmeThe README makes that sound reasonably complete. "Port" to me implies "rewrite". Why would anyone do that? |
|
|
|
|
|
Zeilap
|
|
May 16, 2013, 01:51:26 AM |
|
Hang on - why are you trying to put the blockchain in a leveldb database?
|
|
|
|
|
jcv
Jr. Member
Offline
Activity: 34
Merit: 1
|
|
May 16, 2013, 01:41:43 PM |
|
"Package" is the word I meant, not "Port". Sorry about that. |
|
|
|
|
jcv
Jr. Member
Offline
Activity: 34
Merit: 1
|
|
May 16, 2013, 01:44:42 PM |
|
Hang on - why are you trying to put the blockchain in a leveldb database?
We are actually putting things in an sqlite database, but we've been evaluating all sorts of other things, including leveldb. The ideal case of course would be a native go implementation of something so we wouldn't need cgo, but we haven't had much luck finding something like that (although I have not done any of the database work, so I can't say what problems we've seen or what missing features any of the other packages had). |
|
|
|
|
ElectricMucus
Legendary
Offline
Activity: 1666
Merit: 1057
Marketing manager - GO MP
|
|
May 16, 2013, 01:47:19 PM |
|
How long will it take for a functional release?
I myself am learning go and this will go a long way helping me. Thanks!
|
|
|
|
|
jcv
Jr. Member
Offline
Activity: 34
Merit: 1
|
|
May 16, 2013, 02:24:16 PM |
|
How long will it take for a functional release?
I myself am learning go and this will go a long way helping me. Thanks!
If you mean a full release of btcd, I can't really say (that's more behindtext's place). But, we do have two functioning packages on github (btcwire and btcjson) which you might want to checkout. Hopefully those can help you get started on something in Go a bit faster. We've really tried to be good with both documenting and adding tests to both of them (of course any comments or bugs you have with them are very welcome). There is also a third component that will be out soon. |
|
|
|
|
|
|
hf
Member
Offline
Activity: 98
Merit: 10
there will be no fucking vegetables
|
|
June 15, 2013, 12:39:40 AM |
|
Awesome clean, documented code.
Keep up the awesome work!
|
|
|
|
|
jcv
Jr. Member
Offline
Activity: 34
Merit: 1
|
|
July 19, 2013, 02:19:28 PM |
|
We've just released the chain selection/block handling code from btcd. Here is the link to btcchain: https://blog.conformal.com/btcchain-the-bitcoin-chain-package-from-bctd/The plan is for btcd itself to come out next. Just like before, any comments or questions on the code or documentation are always welcome. We've tried very hard to match the rules as implemented by bitcoind exactly, but as this is very important, we'd appreciate any reviews or comments on the code. Enjoy. |
|
|
|
|
LightRider
Legendary
Offline
Activity: 1500
Merit: 1021
I advocate the Zeitgeist Movement & Venus Project.
|
|
July 21, 2013, 07:32:39 AM |
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This is awesome. Keep up the great work!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQIcBAEBAgAGBQJR647tAAoJENpjtAbv5/sY080P/2wJbztJ5iLHQujloFiH4vZh
dLV3lJ8mU8xZXhJ7qfUL59LdRD7Id3O91hyn6WpkKaWsUXHRl7P1/ZAnXkkMrHIP
EZgIKeybxGgHxEV/lfIj5vlw3hBEOMcBjCGzWDA5budnbAYmUJoSFDNQQSgiHjVc
QMwPK9viaUbv35gtPrYbpuuPzSPxX+cvxcly8xwehqx5Uu994WmPmXBJj9sJvCM8
EWi3jtTR6o527hwJECaYHuGMvUsP7DbDMT6OyzD1xgWvr8XcR3qrOfl4wSnJx5PU
4jMlCF4v56P4DLtVyHiki7Zr2fpnChYh/rxYMlCoDi3K9bzTidNkrm7Xd4GZ/W5X
q/LsyupEVFeFwDdIlyyekV8HYDtc3IRLC8HjlEwc2zwjT3jKRGPZeoXVDLAZ4KQN
o8hjDaEdIT5qtRL2VXalbfpauaStj+GZL5vdhf6zshX0ZyQOHh4H58OuUN3OLFqh
CdJUtL3YU+DHQSrX5m8H2bgK6Hy/8waTLRsVfoMTF8jewjZRl+F4HH/UfMJTp5Qa
ZaSCrrmYidjj94e1Ww0/bYkYFUUneUrq7vdHQi6NwoTA86BS8C5PFpIkVTb+BzSo
O5PF7RY9N7ybvw/oyzzSJBygvhYgAsRqg3AWMem+sEPA0Vcrhj2N9hVbu8+Vz4Ma
vsUR5/PoKcO2Qql+WU9/
=+tO/
-----END PGP SIGNATURE-----
|
|
|
|
hazek
Legendary
Offline
Activity: 1078
Merit: 1002
|
|
September 04, 2013, 09:41:48 PM |
|
|
My personality type: INTJ - please forgive my weaknesses (Not naturally in tune with others feelings; may be insensitive at times, tend to respond to conflict with logic and reason, tend to believe I'm always right)
If however you enjoyed my post: 15j781DjuJeVsZgYbDVt2NZsGrWKRWFHpp
|
|
|
|
|
justusranvier
Legendary
Offline
Activity: 1400
Merit: 1009
|
|
December 17, 2013, 06:24:54 PM |
|
Is it normal for inbound peers to consistently quit after approximately 20 seconds? 08:16:36 2013-12-17 [INF] BTCD: Version 0.4.0-alpha
08:16:36 2013-12-17 [INF] BTCD: Loading block database from '/var/lib/bitcoin/.btcd/data/mainnet/blocks_leveldb'
08:16:38 2013-12-17 [INF] BTCD: Block database loaded with block height 275386
08:16:38 2013-12-17 [INF] BMGR: Generating initial block node index. This may take a while...
08:16:57 2013-12-17 [INF] BMGR: Block index generation complete
08:16:57 2013-12-17 [INF] SRVR: Server listening on 192.168.135.17:8333
08:16:57 2013-12-17 [INF] AMGR: Loaded 16016 addresses from '/var/lib/bitcoin/.btcd/data/mainnet/peers.json'
08:18:40 2013-12-17 [INF] BMGR: New valid peer 192.168.135.21:55152 (inbound)
08:18:40 2013-12-17 [INF] BMGR: Syncing to block height 275386 from peer 192.168.135.21:55152
08:19:15 2013-12-17 [INF] BMGR: New valid peer 174.54.52.15:8333 (outbound)
08:20:14 2013-12-17 [INF] BMGR: New valid peer 95.154.245.77:61910 (inbound)
08:20:32 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:48323 (inbound)
08:20:34 2013-12-17 [INF] BMGR: Lost peer 95.154.245.77:61910 (inbound)
08:20:42 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:48323 (inbound)
08:21:22 2013-12-17 [INF] BMGR: New valid peer 173.79.167.42:8333 (outbound)
08:21:22 2013-12-17 [INF] BMGR: New valid peer 68.228.71.101:8333 (outbound)
08:21:34 2013-12-17 [INF] BMGR: New valid peer 95.154.245.77:62066 (inbound)
08:22:04 2013-12-17 [WRN] BMGR: Got unrequested transaction 1c7caddc5b7111e8073ef9afef5ead5b73a378ea95a82b2918cfddf0b1ddb47a from 95.154.245.77:62066 -- disconnecting
08:22:04 2013-12-17 [INF] BMGR: Lost peer 95.154.245.77:62066 (inbound)
08:22:28 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:59544 (inbound)
08:22:45 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:59544 (inbound)
08:23:12 2013-12-17 [INF] BMGR: Processed 1 block in the last 6m33.27s (320 transactions, height 275387, 2013-12-17 08:22:09 +0000 UTC)
08:24:18 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:37172 (inbound)
08:24:28 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:37172 (inbound)
08:25:42 2013-12-17 [INF] BMGR: New valid peer 85.17.207.181:8333 (outbound)
08:26:07 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:49392 (inbound)
08:26:18 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:49392 (inbound)
08:26:34 2013-12-17 [INF] BMGR: Processed 1 block in the last 3m22.93s (142 transactions, height 275388, 2013-12-17 08:23:19 +0000 UTC)
08:27:12 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:56321 (inbound)
08:27:12 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:56321 (inbound)
08:27:20 2013-12-17 [INF] BMGR: Processed 1 block in the last 45.05s (38 transactions, height 275389, 2013-12-17 08:29:10 +0000 UTC)
08:29:25 2013-12-17 [WRN] PEER: Peer 68.228.71.101:8333 (outbound) no answer for 5 minutes, disconnecting
08:29:25 2013-12-17 [INF] BMGR: Lost peer 68.228.71.101:8333 (outbound)
08:30:29 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:33235 (inbound)
08:30:44 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:33235 (inbound)
08:31:32 2013-12-17 [INF] BMGR: New valid peer 89.238.82.194:8333 (outbound)
08:32:03 2013-12-17 [INF] BMGR: New valid peer 50.179.47.222:8333 (outbound)
08:32:12 2013-12-17 [INF] BMGR: New valid peer 204.45.120.178:8333 (outbound)
08:34:10 2013-12-17 [INF] BMGR: New valid peer 146.247.64.250:8333 (outbound)
08:35:33 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:37558 (inbound)
08:35:44 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:37558 (inbound)
08:36:39 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:57856 (inbound)
08:36:39 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:57856 (inbound)
08:38:47 2013-12-17 [INF] BMGR: Processed 1 block in the last 11m27.84s (399 transactions, height 275390, 2013-12-17 08:37:48 +0000 UTC)
08:46:56 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:32893 (inbound)
08:47:07 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:32893 (inbound)
08:52:02 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:60783 (inbound)
08:52:02 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:60783 (inbound)
08:54:27 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:51488 (inbound)
08:54:37 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:51488 (inbound)
08:56:30 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:52733 (inbound)
08:56:31 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:52733 (inbound)
08:59:08 2013-12-17 [INF] BMGR: Processed 1 block in the last 20m20.39s (4 transactions, height 275391, 2013-12-17 08:58:48 +0000 UTC)
09:03:35 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:55559 (inbound)
09:03:46 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:55559 (inbound)
09:06:01 2013-12-17 [INF] BMGR: Processed 1 block in the last 6m52.85s (1105 transactions, height 275392, 2013-12-17 09:04:48 +0000 UTC)
09:06:08 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:46141 (inbound)
09:06:18 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:46141 (inbound)
09:09:36 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:44179 (inbound)
09:09:46 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:44179 (inbound)
09:09:49 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:46203 (inbound)
09:10:00 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:46203 (inbound)
09:12:56 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:34110 (inbound)
09:13:07 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:34110 (inbound)
09:17:23 2013-12-17 [INF] BMGR: Processed 1 block in the last 11m22.68s (480 transactions, height 275393, 2013-12-17 09:16:40 +0000 UTC)
09:21:50 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:51372 (inbound)
09:22:00 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:51372 (inbound)
09:25:21 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:51477 (inbound)
09:25:31 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:51477 (inbound)
09:25:58 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:49644 (inbound)
09:26:00 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:49644 (inbound)
09:27:53 2013-12-17 [INF] BMGR: Processed 1 block in the last 10m29.54s (256 transactions, height 275394, 2013-12-17 09:27:12 +0000 UTC)
09:29:35 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:59208 (inbound)
09:29:45 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:59208 (inbound)
09:32:40 2013-12-17 [INF] BMGR: New valid peer 162.243.95.129:52718 (inbound)
09:32:40 2013-12-17 [INF] BMGR: Lost peer 162.243.95.129:52718 (inbound)
09:38:36 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:57651 (inbound)
09:38:47 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:57651 (inbound)
09:42:28 2013-12-17 [INF] BMGR: Processed 1 block in the last 14m35.58s (539 transactions, height 275395, 2013-12-17 09:41:24 +0000 UTC)
09:47:25 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:52905 (inbound)
09:47:26 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:52905 (inbound)
09:48:00 2013-12-17 [INF] BMGR: Processed 1 block in the last 5m31.65s (177 transactions, height 275396, 2013-12-17 09:47:35 +0000 UTC)
09:49:45 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:36937 (inbound)
09:49:56 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:36937 (inbound)
09:50:08 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:48738 (inbound)
09:50:18 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:48738 (inbound)
09:54:17 2013-12-17 [INF] BMGR: Processed 1 block in the last 6m16.72s (261 transactions, height 275397, 2013-12-17 09:53:55 +0000 UTC)
09:55:01 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:60835 (inbound)
09:55:11 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:60835 (inbound)
09:56:36 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:51081 (inbound)
09:56:37 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:51081 (inbound)
09:57:36 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:45653 (inbound)
09:57:52 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:45653 (inbound)
09:58:54 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m37.04s (208 transactions, height 275398, 2013-12-17 09:58:09 +0000 UTC)
10:07:19 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:35775 (inbound)
10:07:29 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:35775 (inbound)
10:12:13 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:60577 (inbound)
10:12:24 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:60577 (inbound)
10:12:46 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:35030 (inbound)
10:13:06 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:35030 (inbound)
10:13:27 2013-12-17 [INF] BMGR: Processed 1 block in the last 14m32.97s (574 transactions, height 275399, 2013-12-17 10:12:49 +0000 UTC)
10:17:37 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m9.77s (50 transactions, height 275400, 2013-12-17 10:16:39 +0000 UTC)
10:24:10 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:50355 (inbound)
10:24:20 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:50355 (inbound)
10:24:40 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:58662 (inbound)
10:24:51 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:58662 (inbound)
10:26:17 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:49290 (inbound)
10:26:18 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:49290 (inbound)
10:30:29 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:42752 (inbound)
10:30:54 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:42752 (inbound)
10:37:03 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:49568 (inbound)
10:37:13 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:49568 (inbound)
10:39:42 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:36136 (inbound)
10:40:07 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:36136 (inbound)
10:48:57 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:57198 (inbound)
10:49:19 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:57198 (inbound)
10:52:36 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:44489 (inbound)
10:52:47 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:44489 (inbound)
10:55:05 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:44309 (inbound)
10:55:06 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:44309 (inbound)
10:56:56 2013-12-17 [INF] BMGR: Processed 1 block in the last 39m19.07s (77 transactions, height 275401, 2013-12-17 10:56:22 +0000 UTC)
10:57:16 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:56714 (inbound)
10:57:17 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:56714 (inbound)
10:58:15 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:48871 (inbound)
10:58:32 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:48871 (inbound)
11:01:25 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m28.92s (1324 transactions, height 275402, 2013-12-17 11:00:28 +0000 UTC)
11:04:45 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:37040 (inbound)
11:04:56 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:37040 (inbound)
11:07:05 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:37198 (inbound)
11:07:26 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:37198 (inbound)
11:08:33 2013-12-17 [INF] BMGR: Processed 1 block in the last 7m7.9s (296 transactions, height 275403, 2013-12-17 11:09:51 +0000 UTC)
11:13:23 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m50.12s (200 transactions, height 275404, 2013-12-17 11:12:37 +0000 UTC)
11:17:45 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:41196 (inbound)
11:17:56 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:41196 (inbound)
11:19:10 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:56071 (inbound)
11:19:20 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:56071 (inbound)
11:19:33 2013-12-17 [INF] BMGR: Processed 1 block in the last 6m10.74s (280 transactions, height 275405, 2013-12-17 11:19:02 +0000 UTC)
11:19:44 2013-12-17 [INF] BMGR: Processed 1 block in the last 10.6s (35 transactions, height 275406, 2013-12-17 11:19:21 +0000 UTC)
11:25:14 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:44104 (inbound)
11:25:15 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:44104 (inbound)
11:25:42 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:57427 (inbound)
11:25:54 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:57427 (inbound)
11:27:04 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:58350 (inbound)
11:27:15 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:58350 (inbound)
11:34:54 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:37796 (inbound)
11:35:14 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:37796 (inbound)
11:39:55 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:36411 (inbound)
11:40:06 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:36411 (inbound)
11:41:13 2013-12-17 [INF] BMGR: Processed 1 block in the last 21m28.46s (532 transactions, height 275407, 2013-12-17 11:39:32 +0000 UTC)
11:46:04 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:49892 (inbound)
11:46:14 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:49892 (inbound)
11:52:37 2013-12-17 [INF] BMGR: Processed 1 block in the last 11m24.59s (537 transactions, height 275408, 2013-12-17 11:52:46 +0000 UTC)
11:54:37 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:41133 (inbound)
11:54:39 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:41133 (inbound)
11:56:48 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:50346 (inbound)
11:56:59 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:50346 (inbound)
11:58:26 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:52682 (inbound)
11:58:45 2013-12-17 [INF] BMGR: Processed 1 block in the last 6m7.93s (266 transactions, height 275409, 2013-12-17 11:59:19 +0000 UTC)
11:58:45 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:52682 (inbound)
12:04:02 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:60513 (inbound)
12:04:14 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:60513 (inbound)
12:04:22 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:33312 (inbound)
12:04:33 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:33312 (inbound)
12:07:53 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:59572 (inbound)
12:07:55 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:59572 (inbound)
12:12:03 2013-12-17 [INF] BMGR: Processed 1 block in the last 13m17.55s (470 transactions, height 275410, 2013-12-17 12:13:03 +0000 UTC)
12:12:04 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:34846 (inbound)
12:12:04 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:34846 (inbound)
12:16:45 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:59936 (inbound)
12:16:56 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:59936 (inbound)
12:17:00 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:34047 (inbound)
12:17:13 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:34047 (inbound)
12:20:39 2013-12-17 [INF] BMGR: Processed 1 block in the last 8m36.78s (348 transactions, height 275411, 2013-12-17 12:20:04 +0000 UTC)
12:20:46 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:51893 (inbound)
12:20:57 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:51893 (inbound)
12:24:03 2013-12-17 [INF] BMGR: Processed 1 block in the last 3m24.02s (141 transactions, height 275412, 2013-12-17 12:23:55 +0000 UTC)
12:24:24 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:39874 (inbound)
12:24:25 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:39874 (inbound)
12:25:12 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m8.37s (115 transactions, height 275413, 2013-12-17 12:24:46 +0000 UTC)
12:25:25 2013-12-17 [INF] BMGR: Processed 1 block in the last 13.3s (112 transactions, height 275414, 2013-12-17 12:25:08 +0000 UTC)
12:28:27 2013-12-17 [INF] BMGR: Processed 1 block in the last 3m2.02s (143 transactions, height 275415, 2013-12-17 12:27:59 +0000 UTC)
12:32:26 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:49284 (inbound)
12:32:37 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:49284 (inbound)
12:32:45 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m18.25s (235 transactions, height 275416, 2013-12-17 12:35:27 +0000 UTC)
12:36:19 2013-12-17 [INF] BMGR: Processed 1 block in the last 3m33.48s (160 transactions, height 275417, 2013-12-17 12:35:35 +0000 UTC)
12:37:00 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:57971 (inbound)
12:37:10 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:57971 (inbound)
12:37:41 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m21.95s (132 transactions, height 275418, 2013-12-17 12:37:29 +0000 UTC)
12:40:24 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:52799 (inbound)
12:40:36 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:52799 (inbound)
12:43:55 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:43584 (inbound)
12:44:05 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:43584 (inbound)
12:50:30 2013-12-17 [INF] BMGR: Processed 1 block in the last 12m48.97s (486 transactions, height 275419, 2013-12-17 12:49:44 +0000 UTC)
12:52:43 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:58666 (inbound)
12:52:53 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:58666 (inbound)
12:53:02 2013-12-17 [INF] BMGR: Processed 1 block in the last 2m32.53s (104 transactions, height 275420, 2013-12-17 12:52:20 +0000 UTC)
12:53:14 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:34777 (inbound)
12:53:15 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:34777 (inbound)
12:56:02 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:51096 (inbound)
12:56:14 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:51096 (inbound)
13:00:56 2013-12-17 [INF] BMGR: Processed 1 block in the last 7m53.98s (342 transactions, height 275421, 2013-12-17 13:00:18 +0000 UTC)
13:02:40 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m43.35s (105 transactions, height 275422, 2013-12-17 13:02:53 +0000 UTC)
13:02:52 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:33038 (inbound)
13:03:02 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:33038 (inbound)
13:06:49 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:60032 (inbound)
13:07:00 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:60032 (inbound)
13:10:57 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:35038 (inbound)
13:11:07 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:35038 (inbound)
13:18:39 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:46458 (inbound)
13:18:40 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:46458 (inbound)
13:19:55 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:52904 (inbound)
13:20:05 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:52904 (inbound)
13:23:16 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:33944 (inbound)
13:23:17 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:33944 (inbound)
13:23:40 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:40173 (inbound)
13:23:50 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:40173 (inbound)
13:27:24 2013-12-17 [INF] BMGR: Processed 1 block in the last 24m43.85s (86 transactions, height 275423, 2013-12-17 13:30:09 +0000 UTC)
13:28:54 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m30.62s (1146 transactions, height 275424, 2013-12-17 13:27:20 +0000 UTC)
13:28:55 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:40714 (inbound)
13:28:55 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:40714 (inbound)
13:31:25 2013-12-17 [INF] BMGR: Processed 1 block in the last 2m31.33s (233 transactions, height 275425, 2013-12-17 13:31:03 +0000 UTC)
13:33:24 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:36712 (inbound)
13:33:34 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:36712 (inbound)
13:36:38 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:51705 (inbound)
13:36:48 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:51705 (inbound)
13:44:00 2013-12-17 [INF] BMGR: Processed 1 block in the last 12m34.41s (595 transactions, height 275426, 2013-12-17 13:43:33 +0000 UTC)
13:45:17 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:35516 (inbound)
13:45:27 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:35516 (inbound)
13:47:42 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:39959 (inbound)
13:47:52 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:39959 (inbound)
13:51:31 2013-12-17 [INF] BMGR: Processed 1 block in the last 7m31.2s (342 transactions, height 275427, 2013-12-17 13:50:40 +0000 UTC)
13:52:28 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:58017 (inbound)
13:52:29 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:58017 (inbound)
13:57:02 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:39994 (inbound)
13:57:12 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:39994 (inbound)
13:57:40 2013-12-17 [INF] BMGR: Processed 1 block in the last 6m9.26s (315 transactions, height 275428, 2013-12-17 13:57:04 +0000 UTC)
14:01:17 2013-12-17 [INF] BMGR: Processed 1 block in the last 3m36.79s (171 transactions, height 275429, 2013-12-17 13:59:57 +0000 UTC)
14:03:31 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:39079 (inbound)
14:03:42 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:39079 (inbound)
14:04:04 2013-12-17 [INF] BMGR: Processed 1 block in the last 2m46.55s (230 transactions, height 275430, 2013-12-17 14:07:33 +0000 UTC)
14:04:20 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:36175 (inbound)
14:04:30 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:36175 (inbound)
14:11:50 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:37553 (inbound)
14:12:01 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:37553 (inbound)
14:12:39 2013-12-17 [INF] BMGR: Processed 1 block in the last 8m35.29s (532 transactions, height 275431, 2013-12-17 14:12:09 +0000 UTC)
14:18:03 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:33002 (inbound)
14:18:14 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:33002 (inbound)
14:22:05 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:41464 (inbound)
14:22:06 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:55562 (inbound)
14:22:07 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:55562 (inbound)
14:22:15 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:41464 (inbound)
14:26:34 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:42300 (inbound)
14:26:44 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:42300 (inbound)
14:26:53 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:44827 (inbound)
14:27:04 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:44827 (inbound)
14:29:19 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:46077 (inbound)
14:29:21 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:46077 (inbound)
14:31:46 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:39364 (inbound)
14:31:56 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:39364 (inbound)
14:33:36 2013-12-17 [INF] BMGR: Processed 1 block in the last 20m57.26s (900 transactions, height 275432, 2013-12-17 14:32:43 +0000 UTC)
14:36:37 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:46275 (inbound)
14:36:48 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:46275 (inbound)
14:39:02 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:35902 (inbound)
14:39:21 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:35902 (inbound)
14:46:11 2013-12-17 [INF] BMGR: Processed 1 block in the last 12m34.96s (626 transactions, height 275433, 2013-12-17 14:45:45 +0000 UTC)
14:50:31 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:53365 (inbound)
14:50:41 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:53365 (inbound)
14:51:17 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:36558 (inbound)
14:51:27 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:36558 (inbound)
14:51:58 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:54034 (inbound)
14:51:59 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:54034 (inbound)
14:57:17 2013-12-17 [INF] BMGR: Processed 1 block in the last 11m5.4s (526 transactions, height 275434, 2013-12-17 14:56:04 +0000 UTC)
14:57:17 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:43871 (inbound)
14:57:35 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:43871 (inbound)
15:01:19 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m2.45s (269 transactions, height 275435, 2013-12-17 15:01:44 +0000 UTC)
15:02:08 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:49590 (inbound)
15:02:18 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:49590 (inbound)
15:02:35 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m16.11s (82 transactions, height 275436, 2013-12-17 15:03:04 +0000 UTC)
15:09:45 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:47612 (inbound)
15:09:56 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:47612 (inbound)
15:10:05 2013-12-17 [INF] BMGR: Processed 1 block in the last 7m29.66s (361 transactions, height 275437, 2013-12-17 15:09:43 +0000 UTC)
15:16:13 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:60260 (inbound)
15:16:23 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:60260 (inbound)
15:21:01 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:49467 (inbound)
15:21:02 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:49467 (inbound)
15:23:13 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:40808 (inbound)
15:23:24 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:40808 (inbound)
15:28:09 2013-12-17 [INF] BMGR: Processed 1 block in the last 18m3.67s (512 transactions, height 275438, 2013-12-17 15:27:29 +0000 UTC)
15:28:36 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:52526 (inbound)
15:28:48 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:52526 (inbound)
15:33:08 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:41694 (inbound)
15:33:12 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:42626 (inbound)
15:33:18 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:41694 (inbound)
15:33:22 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:42626 (inbound)
15:38:05 2013-12-17 [INF] BMGR: Processed 1 block in the last 9m56.55s (651 transactions, height 275439, 2013-12-17 15:37:37 +0000 UTC)
15:39:42 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:54034 (inbound)
15:39:43 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:54034 (inbound)
15:40:23 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:36239 (inbound)
15:40:33 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:36239 (inbound)
15:43:21 2013-12-17 [INF] BMGR: Processed 1 block in the last 5m16.1s (285 transactions, height 275440, 2013-12-17 15:43:43 +0000 UTC)
15:44:07 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:43091 (inbound)
15:44:28 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:43091 (inbound)
15:44:36 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m14.98s (107 transactions, height 275441, 2013-12-17 15:44:25 +0000 UTC)
15:45:59 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:39667 (inbound)
15:46:10 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:39667 (inbound)
15:51:24 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:49972 (inbound)
15:51:25 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:49972 (inbound)
15:53:01 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:37560 (inbound)
15:54:06 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:37560 (inbound)
15:54:12 2013-12-17 [INF] BMGR: Processed 1 block in the last 9m36.18s (256 transactions, height 275442, 2013-12-17 15:52:48 +0000 UTC)
15:56:53 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:48324 (inbound)
15:57:03 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:48324 (inbound)
16:05:40 2013-12-17 [INF] BMGR: Processed 1 block in the last 11m28.02s (577 transactions, height 275443, 2013-12-17 16:07:07 +0000 UTC)
16:05:40 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:42246 (inbound)
16:05:44 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:42246 (inbound)
16:07:46 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:40208 (inbound)
16:07:56 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:40208 (inbound)
16:09:45 2013-12-17 [INF] BMGR: Processed 2 blocks in the last 4m4.66s (339 transactions, height 275445, 2013-12-17 16:09:15 +0000 UTC)
16:12:05 2013-12-17 [INF] BMGR: Processed 1 block in the last 2m19.96s (125 transactions, height 275446, 2013-12-17 16:11:51 +0000 UTC)
16:13:18 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m12.64s (104 transactions, height 275447, 2013-12-17 16:13:03 +0000 UTC)
16:14:55 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m37.38s (101 transactions, height 275448, 2013-12-17 16:14:39 +0000 UTC)
16:15:20 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:37822 (inbound)
16:15:30 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:37822 (inbound)
16:19:24 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m28.44s (277 transactions, height 275449, 2013-12-17 16:18:42 +0000 UTC)
16:20:50 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:44259 (inbound)
16:21:03 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:47589 (inbound)
16:21:05 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:47589 (inbound)
16:21:10 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:39347 (inbound)
16:21:15 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:44259 (inbound)
16:21:21 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:39347 (inbound)
16:23:29 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m5.54s (215 transactions, height 275450, 2013-12-17 16:22:23 +0000 UTC)
16:35:18 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:41783 (inbound)
16:35:28 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:41783 (inbound)
16:37:15 2013-12-17 [INF] BMGR: Processed 1 block in the last 13m46.29s (682 transactions, height 275451, 2013-12-17 16:44:08 +0000 UTC)
16:41:23 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:52276 (inbound)
16:41:34 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:52276 (inbound)
16:43:07 2013-12-17 [INF] BMGR: Processed 1 block in the last 5m51.41s (438 transactions, height 275452, 2013-12-17 16:42:27 +0000 UTC)
16:45:19 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:43067 (inbound)
16:45:29 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:43067 (inbound)
16:47:12 2013-12-17 [INF] BMGR: Processed 1 block in the last 4m4.91s (287 transactions, height 275453, 2013-12-17 16:47:29 +0000 UTC)
16:50:09 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:43088 (inbound)
16:50:10 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:43088 (inbound)
16:50:15 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:41651 (inbound)
16:50:26 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:41651 (inbound)
16:51:13 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:56279 (inbound)
16:51:14 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:56279 (inbound)
16:51:18 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:45776 (inbound)
16:51:28 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:45776 (inbound)
16:52:19 2013-12-17 [INF] BMGR: Processed 1 block in the last 5m7.57s (225 transactions, height 275454, 2013-12-17 16:52:02 +0000 UTC)
16:52:57 2013-12-17 [INF] BMGR: Processed 1 block in the last 37.57s (71 transactions, height 275455, 2013-12-17 16:52:27 +0000 UTC)
16:58:37 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:42320 (inbound)
16:58:57 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:42320 (inbound)
17:00:24 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:49947 (inbound)
17:00:24 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:50005 (inbound)
17:00:35 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:49947 (inbound)
17:00:35 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:50005 (inbound)
17:06:23 2013-12-17 [INF] BMGR: Processed 1 block in the last 13m25.78s (650 transactions, height 275456, 2013-12-17 17:05:53 +0000 UTC)
17:13:31 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:41436 (inbound)
17:13:41 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:41436 (inbound)
17:15:02 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:49495 (inbound)
17:15:13 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:49495 (inbound)
17:15:47 2013-12-17 [INF] BMGR: Processed 1 block in the last 9m24.35s (431 transactions, height 275457, 2013-12-17 17:15:05 +0000 UTC)
17:20:17 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:42573 (inbound)
17:20:18 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:42573 (inbound)
17:24:25 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:52384 (inbound)
17:24:33 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:54069 (inbound)
17:24:35 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:52384 (inbound)
17:24:43 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:54069 (inbound)
17:26:03 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:43014 (inbound)
17:26:14 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:43014 (inbound)
17:26:32 2013-12-17 [INF] BMGR: Processed 1 block in the last 10m44.69s (604 transactions, height 275458, 2013-12-17 17:25:59 +0000 UTC)
17:27:09 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:37228 (inbound)
17:27:32 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:37228 (inbound)
17:29:21 2013-12-17 [INF] BMGR: Processed 1 block in the last 2m49.55s (62 transactions, height 275459, 2013-12-17 17:28:48 +0000 UTC)
17:32:23 2013-12-17 [INF] BMGR: Processed 1 block in the last 3m1.87s (43 transactions, height 275460, 2013-12-17 17:31:41 +0000 UTC)
17:36:27 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:52045 (inbound)
17:36:47 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:52045 (inbound)
17:37:06 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:34619 (inbound)
17:37:17 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:34619 (inbound)
17:43:27 2013-12-17 [INF] BMGR: Processed 1 block in the last 11m3.5s (648 transactions, height 275461, 2013-12-17 17:42:27 +0000 UTC)
17:49:15 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:54038 (inbound)
17:49:25 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:54038 (inbound)
17:50:01 2013-12-17 [INF] BMGR: New valid peer 178.18.90.41:40265 (inbound)
17:50:02 2013-12-17 [INF] BMGR: Lost peer 178.18.90.41:40265 (inbound)
17:51:52 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:59657 (inbound)
17:52:03 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:59657 (inbound)
17:53:12 2013-12-17 [INF] BMGR: Processed 1 block in the last 9m45.37s (617 transactions, height 275462, 2013-12-17 17:52:08 +0000 UTC)
17:58:36 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:43809 (inbound)
17:58:46 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:43809 (inbound)
17:59:45 2013-12-17 [INF] BMGR: Processed 1 block in the last 6m32.56s (455 transactions, height 275463, 2013-12-17 17:59:04 +0000 UTC)
18:02:01 2013-12-17 [INF] BMGR: New valid peer 178.79.147.171:40585 (inbound)
18:02:02 2013-12-17 [INF] BMGR: Lost peer 178.79.147.171:40585 (inbound)
18:02:51 2013-12-17 [INF] BMGR: Processed 1 block in the last 3m6.88s (72 transactions, height 275464, 2013-12-17 18:02:25 +0000 UTC)
18:03:28 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:35060 (inbound)
18:03:52 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:35060 (inbound)
18:04:16 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m24.89s (209 transactions, height 275465, 2013-12-17 18:03:35 +0000 UTC)
18:04:52 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:41868 (inbound)
18:05:03 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:41868 (inbound)
18:05:48 2013-12-17 [INF] BMGR: Processed 1 block in the last 1m31.77s (59 transactions, height 275466, 2013-12-17 18:05:11 +0000 UTC)
18:14:06 2013-12-17 [INF] BMGR: New valid peer 31.220.26.209:49539 (inbound)
18:14:19 2013-12-17 [INF] BMGR: Lost peer 31.220.26.209:49539 (inbound)
18:17:24 2013-12-17 [INF] BMGR: New valid peer 23.226.234.12:42112 (inbound)
18:17:34 2013-12-17 [INF] BMGR: Lost peer 23.226.234.12:42112 (inbound) |
|
|
|
|
cczarek123
Newbie
Offline
Activity: 42
Merit: 0
|
|
December 17, 2013, 09:23:04 PM |
|
What strategy are you using to make sure that you're implementing the distributed algorithm consistently with the reference software?
|
|
|
|
|
|
