Quote from: digaran on Today at 07:21:17 PM

Quote from: ilkerc on Today at 01:30:33 PM

Hello,

I just created a simple solo-pool to find puzzle 66.

It only works with BTC Puzzle 66. If you want to scan all private keys in puzzle 66; you need to do 36 quintillion scans in total. In case you do a random scan; previously generated private keys will be regenerated (random problem). This extends the scan time by x10.

Puzzle 66 HEX ranges as follows. It starts with 2 or 3. Any private key in this range is 17 characters long.

20000000000000000 to 3ffffffffffffffff

We take the first 7 characters and delete the rest for now. The result will be as follows.

2000000 to 3ffffff

We now have about 33 million possible private keys to search. All possible private keys are stored in the database. A random value will come up each time a scan job is called and will be marked as scanned when the scan is complete.

I can scan each key in about 10 minutes on NVIDIA 3090. This actually means about 1,1 trillion private keys. When the private key is scanned, it is marked as scanned. So it won't show up anymore.

So you only keep 33 m keys in a file and then search for what exactly? If you are searching small ranges, then you should do it sequential. What is your speed in terms of keys/s ?

No, it has ranges, not keys. It's a pool of sorts that keeps track of ranges ran. And no, sequential is not the way to go lol.
I did a quick calculus, I can generate 1 trillion every 12 hours, so 2 trillions per 24 hours, now if I run my laptop 24/7, I could find the key after 30,000 + years or so give or take! Do you think people will be using bitcoin by then? Because I don't wanna waste 30,000 years for unsure future investment.😂