Bitcoin puzzle transaction ~32 BTC prize to who solves it

[nc50lc]

Is this make any sense to predict next Puzzle ?

If that's a pattern, P63's last 8bits should also be twice of the first few bytes of P64... and P62's to P63's.. and so on.
But don't take my word on it since I haven't checked all of the puzzle's private keys, just the last few  ;D

Check them all and see if there's a matching pattern.

[Evillo]

P64 = F7051F27B09112D4
P65 = 1A838B13505B26867
Last 2 hex of P64 = D4+D4 = 1A8
First 3 hex of P65 == sum of Last 2 hex of P64

Is this make any sense to predict next Puzzle ?

P65 = 1A838B13505B26867

P66 = 67 + 67 = CE

Out of range .. sorry but doesn't work.

[zahid888]

Maybe it could be 2ce or 3ce.

[Evillo]

Maybe it could be 2ce or 3ce.

Could be anything .. with a range 4 times bigger than 64 bits, the only resort is random search .. range search is gonna eat up time and resources .. the only way to beat 17 random characters is by utilizing randomness itself .. but that's just me.

[rockearth]

clBitCrack.exe -o o.txt -t 0 --keyspace F7051F27B0000000:F7051F27B19112D4 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2022-09-13.11:32:36] [Info] Compression: compressed
[2022-09-13.11:32:36] [Info] Starting at: 000000000000000000000000000000000000000000000000F7051F27B0000000
[2022-09-13.11:32:36] [Info] Ending at:   000000000000000000000000000000000000000000000000F7051F27B19112D4
[2022-09-13.11:32:36] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-09-13.11:32:36] [Info] Compiling OpenCL kernels...
[2022-09-13.11:32:36] [Info] Initializing NVIDIA GeForce GTX 960
[2022-09-13.11:32:36] [Info] Generating 262,144 starting points (10.0MB)
[2022-09-13.11:32:36] [Info] 10.0%
[2022-09-13.11:32:36] [Info] 20.0%
[2022-09-13.11:32:36] [Info] 30.0%
[2022-09-13.11:32:37] [Info] 40.0%
[2022-09-13.11:32:37] [Info] 50.0%
[2022-09-13.11:32:37] [Info] 60.0%
[2022-09-13.11:32:37] [Info] 70.0%
[2022-09-13.11:32:37] [Info] 80.0%
[2022-09-13.11:32:37] [Info] 90.0%
[2022-09-13.11:32:37] [Info] 100.0%
[2022-09-13.11:32:37] [Info] Done
[2022-09-13.11:32:37] [Info] Reached end of keyspace

Very sad thing, does anyone know why?

[nc50lc]

Very sad thing, does anyone know why?

it's a bug in clBitCrack: github.com/brichard19/BitCrack/issues/337

Someone shared a fix but you'll have to edit it yourself and compile the code.
Here's the post: github.com/brichard19/BitCrack/issues/223

[rockearth]

Very sad thing, does anyone know why?

it's a bug in clBitCrack: github.com/brichard19/BitCrack/issues/337

Someone shared a fix but you'll have to edit it yourself and compile the code.
Here's the post: github.com/brichard19/BitCrack/issues/223

Thanks, I have switched to another tool

[citb0in]

Thanks, I have switched to another tool

which one ?

[rockearth]

Thanks, I have switched to another tool

which one ?

VanitySearch

[citb0in]

and how do you run VanitySearch for the intented operation that you did with bitcrack before?

[Evillo]

Very sad thing, does anyone know why?

it's a bug in clBitCrack: github.com/brichard19/BitCrack/issues/337

Someone shared a fix but you'll have to edit it yourself and compile the code.
Here's the post: github.com/brichard19/BitCrack/issues/223

clbitcrack behaves weird on old and low gig cards .. best case scenario is it's gonna search but not find anything when testing a known key in a known range (i.e fail test)
Here is test results:

Rx 5xxx XT - work and pass test
Rx 570 8G - search but fail test
Rx 580 8G - search but fail test
Anything less - do not search

In the NVIDIA family i found anything less than 1xxx 8G to not work or behave weirdly ( yes you can use your NVIDIA card with clbitcrack .. in my case cuda has a config problem that im not so fond of spending time on fixing right now)


Your results may vary.

[tandang2]

16jY7qLJXAVFd7AJXJ5N8xT9DEs24NDaXV  F7051F24C01D5BB2
16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN  F7051F27B09112D4

Got above address 2 times in my lots of search since lots of years but never get actual address.. feeling too much unlucky  I should have taken these green letters seriously.

what tools do you use? how can you not detect it, is there no notification ?

[JDScreesh]

Maybe it could be 2ce or 3ce.

Hello there I remember that the creator of the puzzle said: "There is no pattern.  It is just consecutive keys from a deterministic wallet (masked with leading 000...0001 to set difficulty)."

 

[nc50lc]

-snip-
Hello there I remember that the creator of the puzzle said: "There is no pattern.  It is just consecutive keys from a deterministic wallet (masked with leading 000...0001 to set difficulty)."

Thanks to this reply, the quoted message made it easy to find the single post of the creator of this puzzle transaction.
Link to the post: http://bitcointalk.org/index.php?topic=1306983.msg18765941#msg18765941

He seems legit because of the fact that #161~256 were indeed spent after a few months since that reply.

[Jolly Jocker]

Puzzle 66... ( 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so )


That's a mockery ....!    

13zb1hQbwfhhEryPWBrAioLY5tiFLrhs5o - 0x319AFC9E3FF391B01

[dextronomous]

Puzzle 66... ( 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so )


That's a mockery ....!    

13zb1hQbwfhhEryPWBrAioLY5tiFLrhs5o - 0x319AFC9E3FF391B01

my guess. it should be above this one,
00000000000000000000000000000000000000000000000319AFC9E3FF391B01

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q > ZsnspiitMKGTKUxzXus


KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q > (a) something

ripemd -- 20D45A6A76AEB187FB6E669463E929D7072AB330


13zb1hQbwfhhEryPWBrAioLY5tiFLrhs5o

[Jolly Jocker]

my guess. it should be above this one,
00000000000000000000000000000000000000000000000319AFC9E3FF391B01

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q > ZsnspiitMKGTKUxzXus


KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q > (a) something

ripemd -- 20D45A6A76AEB187FB6E669463E929D7072AB330


13zb1hQbwfhhEryPWBrAioLY5tiFLrhs5o

If you look at how many addresses start with "13zb1hQ..", that's to despair!
There are areas where there are significantly more... that makes it difficult to narrow down the range..

A good example of this was the 64-bit range, which was assumed to be in the middle of this range... unfortunately it was totally wrong ^^

[zahid888]

Puzzle 66... ( 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so )


That's a mockery ....!    

13zb1hQbwfhhEryPWBrAioLY5tiFLrhs5o - 0x319AFC9E3FF391B01

[2022-10-01.14:26:29] [Info] Address     : 13zb1hQbWMzfvBudo1G28SjrDjwpcY8PA9
                             Private key : 319AFC93A46A34462
                             Compressed  : yes
                             Public key  : 03BA713FDDD4D0E475A60D3057F2E33B18A50B40827EF3728B4EE9E86C444D23C5

[Jolly Jocker]

[2022-10-01.14:26:29] [Info] Address     : 13zb1hQbWMzfvBudo1G28SjrDjwpcY8PA9
                             Private key : 319AFC93A46A34462
                             Compressed  : yes
                             Public key  : 03BA713FDDD4D0E475A60D3057F2E33B18A50B40827EF3728B4EE9E86C444D23C5

It's not just about the beginning of the address... There are tons of those... more about the similarities between the beginning and the end of the address..

13zb1hQbwfhhEryPWBrAioLY5tiFLrhs5o

[Evillo]

[2022-10-01.14:26:29] [Info] Address     : 13zb1hQbWMzfvBudo1G28SjrDjwpcY8PA9
                             Private key : 319AFC93A46A34462
                             Compressed  : yes
                             Public key  : 03BA713FDDD4D0E475A60D3057F2E33B18A50B40827EF3728B4EE9E86C444D23C5

It's not just about the beginning of the address... There are tons of those... more about the similarities between the beginning and the end of the address..

13zb1hQbwfhhEryPWBrAioLY5tiFLrhs5o

And the main feature of sha256 hex pvt key that makes it secure in the first place is, once you change even one letter in (input) string, the entire hex output changes! This works both way, if you change the output (the sha256 32 byte) , the input will be hugely different. And to make things even harder, that's just one hash function, now let's continue the process of generating the address: we're doing ripemd of the sha256 of the resulting pub key to get the address .. By design, this means that whatever comes out as an address will change significantly after all that hashing we went through. This means that you can have trillions and trillions of addresses starting with 13zb1hQ.... Spread around the entire 256 bit range leaving you with the fact that none of them is the exact address you're looking for. Someone then might ask then why would we search by prefix instead of addresses?! The answer is simple: it's way faster to look for part of the address. That's the only advantage. But It doesn't say anything about determining the range.