Post
Topic
Board Bitcoin Discussion
Re: == Bitcoin challenge transaction: ~100 BTC total bounty to solvers! ==UPDATED==
by
WanderingPhilospher
on 30/12/2022, 01:03:03 UTC

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...