Pages:
Author

Topic: For fun: the lowest block hash yet - page 3. (Read 21206 times)

staff
Activity: 4172
Merit: 8419
August 01, 2014, 08:59:57 PM
#52
Oh, nice!
May I ask how you are calculating/estimating the total work done by the network?
The smallest block hash yet found is an estimate of the total work done by the network.  Also, the sum of the difficulties (well *2^32) on the blocks so far is an estimate, which is the one returned in the bitcoin core logs or in the getblockchaininfo rpc.
legendary
Activity: 1246
Merit: 1004
August 01, 2014, 03:15:38 PM
#51
00000000000000000000b7de9e5c19e52be073156924b7cf235efb27ae8a202a

math.log((2**256)/0x00000000000000000000b7de9e5c19e52be073156924b7cf235efb27ae8a202a,2) = 80.47746080768307

"Apparent difficulty" of 391,895,084,984,304.

And pretty much just on track with the regular block measured work: UpdateTip: new best=00000000000000000000b7de9e5c19e52be073156924b7cf235efb27ae8a202a  height=313338  log2_work=79.978295  tx=43580048  date=2014-07-31 13:29:05 progress=0.999999

This is the first block solution we've found which is a >80 bit partial preimage of 0.

Oh, nice!

May I ask how you are calculating/estimating the total work done by the network?
legendary
Activity: 1260
Merit: 1019
August 01, 2014, 04:02:43 AM
#50
We should start "Guinness facts for Bitcoin" project with an answers to all popular (and even dumb) questions

1. What is the lowest block hash seen?
2. What is the maximum tx (in bytes, in funds, in fees)
3. What is the longest scriptPub and scriptSig?
4. How many zeros does your publicKey have in hex representation?
5. The first and last (alphabet order) address (need signature verifying)
6. Maximum transactions count in block
... etc
staff
Activity: 4172
Merit: 8419
August 01, 2014, 03:30:35 AM
#49
00000000000000000000b7de9e5c19e52be073156924b7cf235efb27ae8a202a

math.log((2**256)/0x00000000000000000000b7de9e5c19e52be073156924b7cf235efb27ae8a202a,2) = 80.47746080768307

"Apparent difficulty" of 391,895,084,984,304.

And pretty much just on track with the regular block measured work: UpdateTip: new best=00000000000000000000b7de9e5c19e52be073156924b7cf235efb27ae8a202a  height=313338  log2_work=79.978295  tx=43580048  date=2014-07-31 13:29:05 progress=0.999999

This is the first block solution we've found which is a >80 bit partial preimage of 0.
staff
Activity: 4172
Merit: 8419
newbie
Activity: 5
Merit: 0
July 06, 2014, 05:20:27 PM
#47
Currently, the highest achieved difficulty has block 266381:

https://blockchain.info/block/000000000000000000028c32e6952731326747bae4be8db0f832d6eea0362050

Achieved difficulty: 110,484,089,548,580
newbie
Activity: 5
Merit: 0
July 02, 2014, 03:54:59 PM
#46
Ok, I scan the blockchain in python and calculated the achieved difficulty for each block.

If anyone is interested I can put the data here.

Interesting thing is that the block 0 (genesis block) have achieved difficulty equal to 2536.
newbie
Activity: 26
Merit: 0
June 24, 2014, 12:38:53 AM
#45
What is the best block for litecoin?
staff
Activity: 4172
Merit: 8419
June 22, 2014, 02:17:23 AM
#44
Not too much has happened, I was waiting to get one with apparent work > 2^80 to update again.

Best right now is 0x000000000000000000049bb3b6b9c135f66536e066704369905043df809c2441 ... or about 2^77.79, the cumulative block measured work level on the network is at 2^79.3 so we're behind.
full member
Activity: 147
Merit: 100
June 22, 2014, 01:05:13 AM
#43
Update please  Smiley
sr. member
Activity: 302
Merit: 250
November 07, 2013, 09:52:31 AM
#42
Really the network has only done about 73.6 bits of work so far, our lowest is lucky. Smiley

Statistically, as the block hashes (I assume) form some kind of distribution, I would say in laymans terms, that we are likely within the 73.6 bits of work done so far to have some outliers or 'lucky' results.

My question would therefore be, would the amount of 'luck' required for our lowest yet fall outside the expected distribuition (and therefore be truely 'lucky') or is this "expected luck"?
staff
Activity: 4172
Merit: 8419
November 06, 2013, 11:13:24 PM
#41
Really the network has only done about 73.6 bits of work so far, our lowest is lucky. Smiley
hero member
Activity: 709
Merit: 503
November 06, 2013, 10:45:02 PM
#40
This basically mean that brute-forcing something of 78.65 bits (80 almost) is possible?
Um, short of (getting all of that computing power to cooperate to brute-force attack is unlikely in the extreme) but even 78.65 bits (rounding up to 80 is not reasonable; it is over 2.5x harder)  is a very long way from 160.  Whatever computing power it took to get to this 78.65 bit result is 81.35 bits short, i.e. over 3 billion trillion times.  If you can gather even 1/65536th of it I'd be stunned but that would put you at 62.65 bits, i.e. over 200 trillion trillion times short.  Spend your energy pursuing something a little more likely to bear fruit.
hero member
Activity: 938
Merit: 501
November 06, 2013, 06:58:52 PM
#39
2013-10-27 14:55:42 SetBestChain: new best=000000000000000000028c32e6952731326747bae4be8db0f832d6eea0362050  height=266381  log2_work=73.237967  tx=26093998  date=2013-10-27 14:49:44 progress=0.999972

In [592]: math.log((2**256)/0x000000000000000000028c32e6952731326747bae4be8db0f832d6eea0362050,2)
Out[592]: 78.65083195521588


This basically mean that brute-forcing something of 78.65 bits (80 almost) is possible?
kjj
legendary
Activity: 1302
Merit: 1025
November 05, 2013, 05:37:00 PM
#38
Since I finally figured out how to read the block chain...

How did you figure out how to read the block chain? can you recommend any sites? 

It is like that scene in the Matrix.  Just set your terminal to green and let it scroll by for a while.  After a while you'll be able to just "see" things.
full member
Activity: 182
Merit: 100
November 05, 2013, 02:22:28 PM
#37
Since I finally figured out how to read the block chain, I decided it would be fun to find the lowest hash produced, yet.  The hash for a block doesn't have to be AT that difficulty, it just has to beat it, and I figured there's gotta be some blocks with major overkill in terms target hash, just by luck.  Well here it is, block 125,552:

http://blockexplorer.com/block/00000000000000001e8d6829a8a21adc5d38d0a473b144b6765798e61f98bd1d

If I did the difficulty calculation correctly (no guarantees), I believe this block would've been valid even at difficulty 35,987,768,035  (current difficulty is 1,564,057).  Can someone verify that?


How did you figure out how to read the block chain? can you recommend any sites? 
staff
Activity: 4172
Merit: 8419
November 05, 2013, 01:39:41 PM
#36
2013-10-27 14:55:42 SetBestChain: new best=000000000000000000028c32e6952731326747bae4be8db0f832d6eea0362050  height=266381  log2_work=73.237967  tx=26093998  date=2013-10-27 14:49:44 progress=0.999972

In [592]: math.log((2**256)/0x000000000000000000028c32e6952731326747bae4be8db0f832d6eea0362050,2)
Out[592]: 78.65083195521588
staff
Activity: 4172
Merit: 8419
September 20, 2013, 07:17:49 PM
#35
2013-09-16 06:36:03 SetBestChain: new best=0000000000000000004bb6e7e2661661ba9809062d90c3121933d6d02c8bd763  height=258283  log2_work=71.955296  tx=23869863  date=2013-09-16 06:35:37 progress=0.999997

We're pretty lucky now with a 73.75 bit solution on 71.95 in effort. Tongue
hero member
Activity: 709
Merit: 503
September 09, 2013, 04:16:34 PM
#34
N trailing 0's should appear with an average of 1:2^(4N).

N 0's anywhere in 64 hexdigits is 1:2^(4N-6).

Excluding the leading 0's cuts into our odds.
legendary
Activity: 1232
Merit: 1084
September 09, 2013, 03:10:20 PM
#33
The Block 2162 hash 00000000aaf0ab905dcdd85a8aac5bfff33b22211222bcdf94b571c00d93d999 is loaded with triples; F's, 2's, 2's again, and 9's (trailing) but still the trailing triple 0's eludes us.

Three zeros should happen once every 4096 blocks on average, so there should be loads.
Pages:
Jump to: