Received, thanks!
Topic: Faulty infographic from Zerohedge.... (Read 487 times)
The infographic gives the hash of "The root of all evil" as 6d0a1899086a.... That is the beginning of
6d0a1899086ad3337062a61f7cb5ec3b8fe94e36a2d73ce26b7b06a8a2d389d2, the correct SHA-256 hash. But Bitcoin always double-hashes, so it should have been 045bbb133c6739d2b298eee99cbe3bc40b959e47506587f0b1216b6769510bbb.
(To be really pedantic, Bitcoin reverses the hash before displaying it, resulting in bb0b5169676b21b1f0876550479e950bc43bbe9ce9ee98b2d239673c13bb5b04.)
6d0a1899086ad3337062a61f7cb5ec3b8fe94e36a2d73ce26b7b06a8a2d389d2, the correct SHA-256 hash. But Bitcoin always double-hashes, so it should have been 045bbb133c6739d2b298eee99cbe3bc40b959e47506587f0b1216b6769510bbb.
(To be really pedantic, Bitcoin reverses the hash before displaying it, resulting in bb0b5169676b21b1f0876550479e950bc43bbe9ce9ee98b2d239673c13bb5b04.)
Well done. That's the 'subtle' one.
Anyone else like to take a shot at the less subtle one?
Put your hand down crary, your nickel should be forthcoming.
The infographic gives the hash of "The root of all evil" as 6d0a1899086a.... That is the beginning of
6d0a1899086ad3337062a61f7cb5ec3b8fe94e36a2d73ce26b7b06a8a2d389d2, the correct SHA-256 hash. But Bitcoin always double-hashes, so it should have been 045bbb133c6739d2b298eee99cbe3bc40b959e47506587f0b1216b6769510bbb.
(To be really pedantic, Bitcoin reverses the hash before displaying it, resulting in bb0b5169676b21b1f0876550479e950bc43bbe9ce9ee98b2d239673c13bb5b04.)
6d0a1899086ad3337062a61f7cb5ec3b8fe94e36a2d73ce26b7b06a8a2d389d2, the correct SHA-256 hash. But Bitcoin always double-hashes, so it should have been 045bbb133c6739d2b298eee99cbe3bc40b959e47506587f0b1216b6769510bbb.
(To be really pedantic, Bitcoin reverses the hash before displaying it, resulting in bb0b5169676b21b1f0876550479e950bc43bbe9ce9ee98b2d239673c13bb5b04.)
You sir are a prime example of why some newbies should be white-listed
The infographic gives the hash of "The root of all evil" as 6d0a1899086a.... That is the beginning of
6d0a1899086ad3337062a61f7cb5ec3b8fe94e36a2d73ce26b7b06a8a2d389d2, the correct SHA-256 hash. But Bitcoin always double-hashes, so it should have been 045bbb133c6739d2b298eee99cbe3bc40b959e47506587f0b1216b6769510bbb.
(To be really pedantic, Bitcoin reverses the hash before displaying it, resulting in bb0b5169676b21b1f0876550479e950bc43bbe9ce9ee98b2d239673c13bb5b04.)
6d0a1899086ad3337062a61f7cb5ec3b8fe94e36a2d73ce26b7b06a8a2d389d2, the correct SHA-256 hash. But Bitcoin always double-hashes, so it should have been 045bbb133c6739d2b298eee99cbe3bc40b959e47506587f0b1216b6769510bbb.
(To be really pedantic, Bitcoin reverses the hash before displaying it, resulting in bb0b5169676b21b1f0876550479e950bc43bbe9ce9ee98b2d239673c13bb5b04.)
Crary, I need more detail.
Instead of "56 more characters" it should be "52 more characters", forming a total of 64 characters.
I'm thinking that's just a typo, so I'm going to say no.
On the first hash generated for "The root of all evil", not only it is wrong (just like the user crary said), but the result would also be wrong in size... Instead of "56 more characters" it should be "52 more characters", forming a total of 64 characters.
In case I'm right: 1FSwkwBJXy5L7PoKTjrBNxxjjL1rNuvAg5
In case I'm right: 1FSwkwBJXy5L7PoKTjrBNxxjjL1rNuvAg5
I just noticed that there are actually two errors on that infographic. One is more subtle than the other. Correctly describing either error will win the prize.
Aside from the fact that coinbase is 25 now, not 50, this seems pretty accurate. I guess there's also that the hash example uses only one round of SHA256, not two.
(12t5NM2Qnb496JMKSFafoHUCvgKqYaMJ8j if I win.)
(12t5NM2Qnb496JMKSFafoHUCvgKqYaMJ8j if I win.)
http://www.zerohedge.com/sites/default/files/images/user3303/imageroot/2013/05/20130512_BTC.jpg
Let's see who can spot the error first!
Winning post gets a bit-nickel from myself. (BTC 0.05)
Rules are as follows....
Post a description of what you think the error is, more detail is better. If two entries are close in time (i.e. within an hour) I reserve the right to choose the more accurate, but later, entry.
Only those with a post count under 100 are eligible, and current or former mods are not eligible no matter how many posts they are willing to delete to get under 100.
Please don't delete your post history to play, this will get you disqualified if I can catch you.
I am the only judge, and my decisions are final.
Please include a valid bitcoin address.
Let's see who can spot the error first!
Winning post gets a bit-nickel from myself. (BTC 0.05)
Rules are as follows....
Post a description of what you think the error is, more detail is better. If two entries are close in time (i.e. within an hour) I reserve the right to choose the more accurate, but later, entry.
Only those with a post count under 100 are eligible, and current or former mods are not eligible no matter how many posts they are willing to delete to get under 100.
Please don't delete your post history to play, this will get you disqualified if I can catch you.
I am the only judge, and my decisions are final.
Please include a valid bitcoin address.
Jump to: