Topic: Blockchain.info is innacurate (Read 1459 times)
reserved
https://bitcointalksearch.org/topic/peer-82130xxxx-connected-to-me-3-times-sending-constant-pings-110390
oh, i just noticed someone replied to my thread.
no, they aren't mining blocks. they just aren't verifying blocks they relayed.
one of the reasons i took 5.9.24.81 down
well, and this:
5.9.24.81/lollercopter.txt
that was my own decision though, since i was using untested code (i have misbehavior changed to 102, to avoid disconnecting someone that relays one tx with invalid signature amongst other things. socket closed is all my other connections disowning me for relaying something that was retrieved from some node's memory pool)
and i think i'll add that pool nodes should be a little more proactive in banning these peers that obv arent verifying blocks, i mentioned this in several threads over the last 3 or 4 days (re: the Snoopy nodes)
oh, i just noticed someone replied to my thread.
no, they aren't mining blocks. they just aren't verifying blocks they relayed.
one of the reasons i took 5.9.24.81 down
well, and this:
5.9.24.81/lollercopter.txt
that was my own decision though, since i was using untested code (i have misbehavior changed to 102, to avoid disconnecting someone that relays one tx with invalid signature amongst other things. socket closed is all my other connections disowning me for relaying something that was retrieved from some node's memory pool)
and i think i'll add that pool nodes should be a little more proactive in banning these peers that obv arent verifying blocks, i mentioned this in several threads over the last 3 or 4 days (re: the Snoopy nodes)
http://blockchain.info/pools states
Hashrate distribution An estimation of hashrate distribution amongst the largest mining pools
The graph below shows the market share of the most popular bitcoin mining pools. It should only be used as a rough estimate and for various reasons will not be 100% accurate. A large portion of Unknown blocks does not mean an attack on the network, it simply means we have been unable to determine the origin. If you can identify any of the ips in the unknown list please post here.
they say they aren't accurate
-bolding by me
most people only look at http://blockchain.info not http://blockchain.info/pools so would not see that
Hashrate distribution An estimation of hashrate distribution amongst the largest mining pools
The graph below shows the market share of the most popular bitcoin mining pools. It should only be used as a rough estimate and for various reasons will not be 100% accurate. A large portion of Unknown blocks does not mean an attack on the network, it simply means we have been unable to determine the origin. If you can identify any of the ips in the unknown list please post here.
they say they aren't accurate
-bolding by memost people only look at http://blockchain.info not http://blockchain.info/pools so would not see that
I agree with gmaxwell in that the activity from 82.130.102.160 is interesting whether they are mining blocks or not.
As the last person to post in the thread before it was locked, I am not sure if I agree with the actual locking
Snoopy is up to something. I supsect they are trying to match transactions to IP addresses.
I don't think that Blockchain.info is innaccurate per se, just easy to mis-interpret.
As the last person to post in the thread before it was locked, I am not sure if I agree with the actual locking
Snoopy is up to something. I supsect they are trying to match transactions to IP addresses.
I don't think that Blockchain.info is innaccurate per se, just easy to mis-interpret.
This has come up so many times I think it is time for a sticky, something like
"PLEASE READ BEFORE YOU POST ABOUT RANDOM IPS ON BLOCKCHAIN.INFO FINDING MASSIVE AMOUNTS OF BLOCKS"
obviously people are interested in who is generating blocks - I sure am
BUT blockchain.info looks at the 1st relay which may or may not be the actual miner.
Jesus. Why does everyone freak out stupidly every time someone notices an instance of a bunch of misreported blocks on blockchain.info. The blockchain.info relayed from fields are frequently wrong and if you understand how it works you won't be surprised by this.
I've locked this thread. The relaying activity of 82.130.102.160 is interesting; but it's almost certainly not mining blocks at all. Start a new thread that doesn't begin with the erroneous assumption that the blockchain.info relayed by field means anything reliable please.
agreed
Though generally it is through lack of information , you and I might understand how "blockchain.info relayed from fields are frequently wrong " but obviously newer miners or people that haven't explored Bitcoin as much as we have may not. Perhaps a sticky with some explanation could help these people understand?
Now it is locked the last thread on this will drop off the page....and the next one will be started :/
For useful info on where the blocks came from I use http://blockorigin.pfoe.be/index.php takes longer but they verify where the blocks come from rather than use a "best guess" method.
at best blockchain.info should be used as a guide - it certainly is not definitive
Best wishes
Graet
"PLEASE READ BEFORE YOU POST ABOUT RANDOM IPS ON BLOCKCHAIN.INFO FINDING MASSIVE AMOUNTS OF BLOCKS"
obviously people are interested in who is generating blocks - I sure am
BUT blockchain.info looks at the 1st relay which may or may not be the actual miner.
Quote from: gmaxwell
Jesus. Why does everyone freak out stupidly every time someone notices an instance of a bunch of misreported blocks on blockchain.info. The blockchain.info relayed from fields are frequently wrong and if you understand how it works you won't be surprised by this.
I've locked this thread. The relaying activity of 82.130.102.160 is interesting; but it's almost certainly not mining blocks at all. Start a new thread that doesn't begin with the erroneous assumption that the blockchain.info relayed by field means anything reliable please.
Though generally it is through lack of information , you and I might understand how "blockchain.info relayed from fields are frequently wrong " but obviously newer miners or people that haven't explored Bitcoin as much as we have may not. Perhaps a sticky with some explanation could help these people understand?
Now it is locked the last thread on this will drop off the page....and the next one will be started :/
For useful info on where the blocks came from I use http://blockorigin.pfoe.be/index.php takes longer but they verify where the blocks come from rather than use a "best guess" method.
at best blockchain.info should be used as a guide - it certainly is not definitive
Best wishes
Graet
Jump to: