Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Bram24732]

Wooow there is Mr. 67 68, perhaps we can call him the god of puzzles. With the power of 25K GPU in his hands, he is probably equal to Snap Tanos, who is able to wipe out most creatures in the universe.

Way too intense, as usual.
Also, it’s spelled Thanos.

[parcok]

not Thanos but tan Or shit yellow (feces)

Wooow there is Mr. 67 68, perhaps we can call him the god of puzzles. With the power of 25K GPU in his hands, he is probably equal to Snap Tanos, who is able to wipe out most creatures in the universe.

Way too intense, as usual.
Also, it’s spelled Thanos.

[goresat2025]

Here you go @goresat2025
 

The death of the monitoring bots for the low bit challenge/puzzles such as the 66, 67, 68 bits.
The sure fire way to get all of your hard earned 6.6 BTC into one of your safe wallets...or is it a sure fire way?
Let me know what you think.

...

thank you

this also apply to key 71, bot can brute force private key in seconds with pubkey?
or it takes time? like haf hour[/color]

[kTimesG]

this also apply to key 71, bot can brute force private key in seconds with pubkey?
or it takes time? like haf hour[/color]

Hundreds of milliseconds (less than a second, to be clear for some people around here).

[0xastraeus]

Who knew somebody with "cok" in their name could handle it and take it so well...relax buddy

not Thanos but tan Or shit yellow (feces)

Wooow there is Mr. 67 68, perhaps we can call him the god of puzzles. With the power of 25K GPU in his hands, he is probably equal to Snap Tanos, who is able to wipe out most creatures in the universe.

Way too intense, as usual.
Also, it’s spelled Thanos.

[0xastraeus]

There's some people here who's sole purpose is to monitor and use their bots to snipe and replace the transaction. As of right now, it still applies for this range.

this also apply to key 71, bot can brute force private key in seconds with pubkey?
or it takes time? like haf hour[/color]

Hundreds of milliseconds (less than a second, to be clear for some people around here).

[SecretAdmirere]

Does anyone have benchmark data for a 1080 Ti GPU running multiple publicly available programs? I have been unable to find comprehensive results.

The closest I found is on the website https://btcpuzzle.info/benchmark, which lists 652 million k/s for VanitySearch and BitCrack. Another source, https://github.com/sp-hash/Bitcrack/releases, claims 705 million k/s. There is also a forum topic started by Zielar (https://asktom.cf/index.php?topic=5218972.msg53649803#msg53649803) that claims 900 million k/s - though I suspect that figure uses endomorphism, which is useless for a specific range search.

I have compiled and run many of these publicly available tools myself but could not achieve key rates close to the claimed figures. Has anyone run a different program on a 1080 Ti and obtained a benchmark number?

With the program I developed, I can achieve a stable 760 to 775 million k/s on stock settings and power target (250W max power draw), varying slightly with GPU temperature. By simply unlocking the power target from 100% to 110%, I get a stable 800 million k/s. Increasing it to 150% allows me to reach 850 million k/s on my 1080 Ti.

I want to know if I am approaching the maximum limit of what the 1080 Ti can do, which is why I am asking.

For clarity, when I refer to keys per second (k/s), I mean hash160 comparisons per second. I am tracking the number of comparisons performed against a target hash160.

[stillhere@2009]

Does anyone have benchmark data for a 1080 Ti GPU running multiple publicly available programs? I have been unable to find comprehensive results.

The closest I found is on the website https://btcpuzzle.info/benchmark, which lists 652 million k/s for VanitySearch and BitCrack. Another source, https://github.com/sp-hash/Bitcrack/releases, claims 705 million k/s. There is also a forum topic started by Zielar (https://asktom.cf/index.php?topic=5218972.msg53649803#msg53649803) that claims 900 million k/s - though I suspect that figure uses endomorphism, which is useless for a specific range search.

I have compiled and run many of these publicly available tools myself but could not achieve key rates close to the claimed figures. Has anyone run a different program on a 1080 Ti and obtained a benchmark number?

With the program I developed, I can achieve a stable 760 to 775 million k/s on stock settings and power target (250W max power draw), varying slightly with GPU temperature. By simply unlocking the power target from 100% to 110%, I get a stable 800 million k/s. Increasing it to 150% allows me to reach 850 million k/s on my 1080 Ti.

I want to know if I am approaching the maximum limit of what the 1080 Ti can do, which is why I am asking.

For clarity, when I refer to keys per second (k/s), I mean hash160 comparisons per second. I am tracking the number of comparisons performed against a target hash160.

make sure your program is working correctly

[Bram24732]

Does anyone have benchmark data for a 1080 Ti GPU running multiple publicly available programs? I have been unable to find comprehensive results.

The closest I found is on the website https://btcpuzzle.info/benchmark, which lists 652 million k/s for VanitySearch and BitCrack. Another source, https://github.com/sp-hash/Bitcrack/releases, claims 705 million k/s. There is also a forum topic started by Zielar (https://asktom.cf/index.php?topic=5218972.msg53649803#msg53649803) that claims 900 million k/s - though I suspect that figure uses endomorphism, which is useless for a specific range search.

I have compiled and run many of these publicly available tools myself but could not achieve key rates close to the claimed figures. Has anyone run a different program on a 1080 Ti and obtained a benchmark number?

With the program I developed, I can achieve a stable 760 to 775 million k/s on stock settings and power target (250W max power draw), varying slightly with GPU temperature. By simply unlocking the power target from 100% to 110%, I get a stable 800 million k/s. Increasing it to 150% allows me to reach 850 million k/s on my 1080 Ti.

I want to know if I am approaching the maximum limit of what the 1080 Ti can do, which is why I am asking.

For clarity, when I refer to keys per second (k/s), I mean hash160 comparisons per second. I am tracking the number of comparisons performed against a target hash160.

I’ll rent a cloud 1080Ti real quick and let you know
Edit : Only 1080Ti I could find on vast / clore are power limited so I cant run a real benchmark for you. I have a 1080Ti somewhere at my house, but swaping my 5090 is not worth the hassle

[SecretAdmirere]

make sure your program is working correctly

In terms of testing and correctness, it passes every test I can think of. I'm not sure what else to throw at it.

I’ll rent a cloud 1080Ti real quick and let you know
Edit : Only 1080Ti I could find on vast / clore are power limited so I cant run a real benchmark for you. I have a 1080Ti somewhere at my house, but swaping my 5090 is not worth the hassle

Thank you for the quick reply and for trying to check the benchmark. Yes, swapping the 5090 for a 1080 Ti, and possibly dealing with driver changes, isn’t very appealing, especially for some random person on the internet. This is the only GPU I have available, so I’m limited to 2017-era hardware. I’ll try to squeeze a bit more performance out of my 1080 Ti, though I'm not sure how much is possible at this point.

For a quick comparison between hashing and non-hashing (hashing EC coordinates vs. computing only EC coordinates), the difference is substantial. Using the lowest values: 760M hashes/s vs. 1.6B EC coordinates/s (both are measurements of comparisons per second). This means operations without hashing are roughly 2.1 times faster than those with hashing. On my 1080 Ti. Improving either part would result in more processed keys and addresses, but I’m at a point where even a 1% gain is a massive win for me, because I’m stuck on what to possibly improve. I guess I have to try harder and learn more.

Overall, I was just wondering if I’m on the right track. Based on publicly available benchmarks, I seem to be, but not everything is public, which is why I asked here. I suppose the next step is finally upgrading my PC or, as I mentioned, trying harder to improve the code.