== Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==

[albert0bsd]

...believe me these are all the collisions of #64

It is not a collision until all the 160 bits of the rmd hash match with the target....

[cryptoDEADBEEFFFFF]

I just found 66

well congrats, what are you waiting for to claim the btc? 

[LetTheDOGEsOut]

I just found 66

Great prove by sending here bc1qpgx42f0tvq09kdv8t4gr9gm2umj3hhkm0zdlj2

 

[hZti]

I just found 66

Very cool that people still successfully solve these private keys after this is already running for such a long time. Will be interesting to see when the last one is found

[albert0bsd]

I just found 66

Good prove it making a signature here: https://reinproject.org/bitcoin-signature-tool/#sign

Regards!

[Ynotcleta]

I did NOT just find 66

Turns out it was a label 66 not actually puzzle #66 
I got excited 😆 sorry
Good prove it making a signature here: https://reinproject.org/bitcoin-signature-tool/#sign

Regards!

[zielar]

Hello!
I haven't looked here for a long time due to the fact that I don't have much time or opportunity to actively participate in the search. Nevertheless, I am posting this post for two reasons, namely first - I would like to wish you all a Merry Christmas and a Happy New Year! May it be happier for you than this one and your dreams come true.
Second - I fired up one of the computers - on which, as it turned out, I found saved kangaroo progress files that allowed me to find key 115 in the past! A lot of people have asked about these files before, because as JeanLucPons develops - they are very useful with the key to 120! Previously, I thought I deleted them because it was 361.41GB of data and at that time they were no longer useful, but wanting to free up space on my 1TB disk by accident and looking for the reason for its 95% fullness, it turned out that these files were they take up my disk :-) So for interested groups/individuals - I have these progress files and I will sell them for 2ETH (upfront payment). If you are interested, please contact me via private message. To be fair - I sell files only once.

Regards

[casinotester0001]

So for interested groups/individuals - I have these progress files and I will sell them for 2ETH (upfront payment). If you are interested, please contact me via private message. To be fair - I sell files only once.

The buyer will sell it several times 

[zielar]

So he would have to be a special idiot to buy progress files and then resell them, reducing his chances. In addition, this offer is rather addressed to people / groups who have been working on 120 for a long time, for whom these files will significantly increase the chance of finding the key faster, and not for people who will try to earn money on it. I put it only because some time ago someone somewhere asked me about these files, but then after searching my devices and being aware of how much space it took - I decided that I had to delete them (and that's how I answered this person). Yesterday it turned out something else - so my offer landed here :-) Oh and I would like to point out that I did not undertake work on #120 and definitely will not undertake it, so the buyer has no worries that I will somehow I will compete in finding the key.

[WanderingPhilospher]

So he would have to be a special idiot to buy progress files and then resell them, reducing his chances. In addition, this offer is rather addressed to people / groups who have been working on 120 for a long time, for whom these files will significantly increase the chance of finding the key faster, and not for people who will try to earn money on it. I put it only because some time ago someone somewhere asked me about these files, but then after searching my devices and being aware of how much space it took - I decided that I had to delete them (and that's how I answered this person). Yesterday it turned out something else - so my offer landed here :-) Oh and I would like to point out that I did not undertake work on #120 and definitely will not undertake it, so the buyer has no worries that I will somehow I will compete in finding the key.

I had asked last year about said progress files. So I was one of those individuals. However, the issue now is, since you did not know if you had them, work was started but not in the 115 range. Maybe someone else who inquired about the files, started working in the 115 bit range and can use them.
Best of luck to all.

[Ynotcleta]

So he would have to be a special idiot to buy progress files and then resell them, reducing his chances. In addition, this offer is rather addressed to people / groups who have been working on 120 for a long time, for whom these files will significantly increase the chance of finding the key faster, and not for people who will try to earn money on it. I put it only because some time ago someone somewhere asked me about these files, but then after searching my devices and being aware of how much space it took - I decided that I had to delete them (and that's how I answered this person). Yesterday it turned out something else - so my offer landed here :-) Oh and I would like to point out that I did not undertake work on #120 and definitely will not undertake it, so the buyer has no worries that I will somehow I will compete in finding the key.

I had asked last year about said progress files. So I was one of those individuals. However, the issue now is, since you did not know if you had them, work was started but not in the 115 range. Maybe someone else who inquired about the files, started working in the 115 bit range and can use them.
Best of luck to all.

I have the key for Puzzle#115 saved in my files dated 10/03 with a timestamp....  My question is do you have a record of the date and time that #115 was found?  I see a lot of maybes and no exact source.  I would like to be able to learn the proper protocol for participating in challenges and disclosure if I where to be so lucky?

[Ynotcleta]

And finaly the #115 was found. Congratulations Zielar and Jean_Luc_Pons  We are all wondering which was the privkey 

Many thanks!
A valid private key that is solution #115 has already been placed in the main post table.

for #115 , you've got the wrong date in the main post

I saved #115 on  0ctober 3rd the private key and timestamp and I never did find any other source before that, I may be wrong can I find the official record?

[albert0bsd]

I saved #115 on  0ctober 3rd the private key and timestamp and I never did find any other source before that, I may be wrong can I find the official record?

#115 ( 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv ) Solved 16/06/2020: Priv=0x60F4D11574F5DEEE49961D9609AC6

You can find the timestamp directly in the blockchain

[msomnia]

this thread makes me want to drink heavily and hurts my head because of this pattern:

[rando new person]: I did it! I figured it out! <Insert not-plausible solution here>

[person with established account and actual contributions towards the puzzle]: dude, that's not how math works.

At any rate, congrats to whomever solved 64 this fall.   
I was looking for roto-cuda and found a couple repos with forks of it: https://github.com/search?q=rotor-cuda

I know linking to how to search github is essentially a lmgtfy move but some of youz guyz seemed to need that level of help.

Also ran into this, which looks to be at least a spiritual cousin if not a direct descendant to roto-cuda: https://github.com/graffitilogic/KeyScanner

This person's code looks to be informal with plenty of commented out paths of experimentation but I appreciated that it actually compiled for me in visual studio with minimum effort.
The random number generator was... novel? but the majority of the rest looks to be forked riffs on VanitySearch and BitCrack in the older commits.

anywho happy hunting you crazy kids.

[WanderingPhilospher]

this thread makes me want to drink heavily and hurts my head because of this pattern:

[rando new person]: I did it! I figured it out! <Insert not-plausible solution here>

[person with established account and actual contributions towards the puzzle]: dude, that's not how math works.

At any rate, congrats to whomever solved 64 this fall.   
I was looking for roto-cuda and found a couple repos with forks of it: https://github.com/search?q=rotor-cuda

I know linking to how to search github is essentially a lmgtfy move but some of youz guyz seemed to need that level of help.

Also ran into this, which looks to be at least a spiritual cousin if not a direct descendant to roto-cuda: https://github.com/graffitilogic/KeyScanner

This person's code looks to be informal with plenty of commented out paths of experimentation but I appreciated that it actually compiled for me in visual studio with minimum effort.
The random number generator was... novel? but the majority of the rest looks to be forked riffs on VanitySearch and BitCrack in the older commits.

anywho happy hunting you crazy kids.

Yeah, seems like it could be a cool project/spiritual cousin however, I am not sure I trust the math/numbers that his program is showing lol

Code:

GPU          : GPU #0 NVIDIA GeForce RTX 3070 (46x128 cores) Grid(256x256)
  Base Key     : Randomly changes 65536 start Private keys every 1,000,000,000 on the counter
  ROTOR Random : Min 42 (bit) 20000000000
  ROTOR Random : Max 42 (bit) 3FFFFFFFFFF

  [00:01:39] [R: 392] [3D70309E4B8] [F: 0] [GPU: 573.08 Mk/s] [T: 4,623,532,294,144]
  =================================================================================
  PubAddress: 1E32GPWgDyeyQac4aJxm9HVoLrrEYPnM4N
  Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9zzYEemjCVJ3vo9
  Priv (HEX): 2A221C58D8F
  PubK (HEX): 03EEC88385BE9DA803A0D6579798D977A5D0C7F80917DAB49CB73C9E3927142CB6
  =================================================================================
  [00:01:40] [R: 392] [3FF4FC9A22C] [F: 1] [GPU: 573.31 Mk/s] [T: 4,624,471,818,240]

Let me know when you see it lol.

[MrFreeDragon]

Hello!
...
I found saved kangaroo progress files that allowed me to find key 115 in the past!
...
So for interested groups/individuals - I have these progress files and I will sell them for 2ETH (upfront payment). If you are interested, please contact me via private message. To be fair - I sell files only once.

Regards

Just distribute these files for free and clean your disk space. No need to sale 

[msomnia]

Yeah, seems like it could be a cool project/spiritual cousin however, I am not sure I trust the math/numbers that his program is showing lol

Code:

GPU          : GPU #0 NVIDIA GeForce RTX 3070 (46x128 cores) Grid(256x256)
  Base Key     : Randomly changes 65536 start Private keys every 1,000,000,000 on the counter
  ROTOR Random : Min 42 (bit) 20000000000
  ROTOR Random : Max 42 (bit) 3FFFFFFFFFF

  [00:01:39] [R: 392] [3D70309E4B8] [F: 0] [GPU: 573.08 Mk/s] [T: 4,623,532,294,144]
  =================================================================================
  PubAddress: 1E32GPWgDyeyQac4aJxm9HVoLrrEYPnM4N
  Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9zzYEemjCVJ3vo9
  Priv (HEX): 2A221C58D8F
  PubK (HEX): 03EEC88385BE9DA803A0D6579798D977A5D0C7F80917DAB49CB73C9E3927142CB6
  =================================================================================
  [00:01:40] [R: 392] [3FF4FC9A22C] [F: 1] [GPU: 573.31 Mk/s] [T: 4,624,471,818,240]

Let me know when you see it lol.

ha - great eye - yeah, the total completed and hashrate do not jive with the time completed.

it will be 2023 in a few days and progress bars, time remaining and items complete (simple division) remain of the bane of meaningful UI feedback.  Funny, though the version I built didn't seem to have a fairytale hash rate but it also didn't have what I was looking for in terms of gpu-accelerated random-private key production. The key assembly is still CPU bound from vectors of gpu-built device_vector of 16 or 32 bit-length unsigned ints.  Mildy sympathetic.. I haven't figured out a pure GPU method of initial key production, either.

 

[WanderingPhilospher]

Yeah, seems like it could be a cool project/spiritual cousin however, I am not sure I trust the math/numbers that his program is showing lol

Code:

GPU          : GPU #0 NVIDIA GeForce RTX 3070 (46x128 cores) Grid(256x256)
  Base Key     : Randomly changes 65536 start Private keys every 1,000,000,000 on the counter
  ROTOR Random : Min 42 (bit) 20000000000
  ROTOR Random : Max 42 (bit) 3FFFFFFFFFF

  [00:01:39] [R: 392] [3D70309E4B8] [F: 0] [GPU: 573.08 Mk/s] [T: 4,623,532,294,144]
  =================================================================================
  PubAddress: 1E32GPWgDyeyQac4aJxm9HVoLrrEYPnM4N
  Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9zzYEemjCVJ3vo9
  Priv (HEX): 2A221C58D8F
  PubK (HEX): 03EEC88385BE9DA803A0D6579798D977A5D0C7F80917DAB49CB73C9E3927142CB6
  =================================================================================
  [00:01:40] [R: 392] [3FF4FC9A22C] [F: 1] [GPU: 573.31 Mk/s] [T: 4,624,471,818,240]

Let me know when you see it lol.

ha - great eye - yeah, the total completed and hashrate do not jive with the time completed.

it will be 2023 in a few days and progress bars, time remaining and items complete (simple division) remain of the bane of meaningful UI feedback.  Funny, though the version I built didn't seem to have a fairytale hash rate but it also didn't have what I was looking for in terms of gpu-accelerated random-private key production. The key assembly is still CPU bound from vectors of gpu-built device_vector of 16 or 32 bit-length unsigned ints.  Mildy sympathetic.. I haven't figured out a pure GPU method of initial key production, either.

 

Right!
Yeah, I played with it a year or so ago and the GPU is not ideal. Python is the purest form of generating 1 random at a time (that I have played with and used, maybe something in C would work faster, maybe albert0bsd could create something), versus generating random starting keys and checking x amount from the starting key until it's rekeyed. Even the CPU with these programs doesn't create a random key and check and a new random key and check...the CPU still creates random starting keys, etc.

My VBC can solve a 36 bit pretty fast in random mode, but that is a small space compared to 66 bit and beyond. Soooo for now, I am checking each and every key, spread out over the entire key space. 30 quadrillion keys and counting lol...

[digaran]

Hi nerds 🤣 I have a question, I just started to code this morning, could anyone give me advice and tell me what I am doing wrong here? Thank you.

Code:

import ecdsa
import hashlib
import re

# Hexadecimal string range to use as input
start_hex_string = "0000000000000000000000000000000000000000000000020000000000000000"
end_hex_string = "000000000000000000000000000000000000000000000003ffffffffffffffff" 

# Convert hexadecimal strings to integers
start_int = int(start_hex_string, 16)
end_int = int(end_hex_string, 16) 

# Target public key to find a match for
target_public_key = "13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so"

# Iterate through the range of integers
for i in range(start_int, end_int+1):
  # Convert integer to hexadecimal string
  hex_string = hex(i)[2:]
  # Check if the string contains only hexadecimal characters
  if re.match(r'^[0-9a-fA-F]+$', hex_string):
    # Convert hexadecimal string to bytes
    hex_bytes = bytes.fromhex( '200000000000000000000000000000000000000000000003ffffffffffffffff')
  else:
    print("Invalid hexadecimal string")
    continue
  # Use SHA256 hash function to generate a private key from the bytes
  private_key = hashlib.sha256(hex_bytes).digest()
  # Use the ECDSA algorithm to create a public key from the private key
  sk = ecdsa.SigningKey.from_string(private_key, curve=ecdsa.SECP256k1)
  vk = sk.get_verifying_key()
  # Encode the public key as a hexadecimal string
  public_key = vk.to_string().hex()
  # Compare the generated public key with the target public key
  if public_key == target_public_key:
    print("Match found! Private key:", private_key.hex())
    # Save the private key here (e.g. write it to a file)
    break

  else:
    print("No match found")

[BlackHatCoiner]

Hi nerds 🤣

That isn't a kind start, is it? Don't be YouTube. 

I just started to code this morning, could anyone give me advice and tell me what I am doing wrong here?

Did you code all that or did you... you know just grabbed it from some git something. If you coded, then asking for help isn't the right place (and maybe no place is right other than your desk). If someone else did, could you provide a link? There has to be a brief explanation of this script.

Code:

# Target public key to find a match for
target_public_key = "13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so"

That doesn't seem right. That variable must expect a public key, not an address.