CUDAPool GPU mining pool for solving 70bit puzzles

Hey folks, I want to share CUDAPool with you all. It's a distributed GPU-based brute-force mining pool set up to tackle the Satoshi puzzle, which is all about searching for secp256k1 keys. What started as just a personal project has turned into a community-driven effort that's already achieving some pretty impressive results. So, what's the deal? The pool hands out work ranges (2^40 blocks) to clients. Clients leverage optimized CUDA kernels to brute-force those secp256k1 private keys (the secp256k1 library works great with both JLP and FixedPaul). All results are sent back to the pool securely, including ranges, speeds, and potential matches. Performance-wise, The optimized client can hit around 8-9 Gkeys/s on a single RTX 5090 (thanks to power limits and consumption). With a boost from a respected community member, we recently topped out at 4 Tkeys/s in total speed. Even during regular operation, it's common to see speeds over 50-100 Gkeys/s with active users. Now, onto security. The pool has protections against spoofing and fake submissions: Every request comes HMAC-signed with a secret. We're using TLS with SPKI pinning to keep MITM attacks at bay. The server monitors all assignments and checks every returned range. Plus, each worker ID and slot is unique (per GPU, per PID). For monitoring and getting involved, Check out the pool's live stats bot: https://t.me/+t9Ss2oR3O_cwMmEy Registration/auth bot is @Satoshis_Quest_auth_bot. If you're curious about the client code, it's available here: https://github.com/Dookoo2/Distibuted-CUDACyclone In short, CUDAPool is an open, community-driven project aiming to rally GPU power for one of the most recognizable cryptographic challenges. We're open to all contributions, whether you're looking to run the client or help improve things.

Hi Fam, I’ve mostly just been watching and learning here, but this time I felt it’s the right moment to speak up and spread the word. Most of you already know about the legendary BTC Puzzle (1–160). It’s one of the most famous challenges in the crypto world, and many people have been grinding away at it for years. Right now though, I believe we’ve got the biggest opportunity yet, thanks to Sir DooKoo2. 👉 For anyone who doesn’t know him – DooKoo2 is a legend in this space. He created the fastest CPU solver, and now he’s pushed GPU speeds to crazy new levels: RTX 5090 → 6–7 Billion keys/sec 🚀 RTX 4090 → 5–6 Billion keys/sec ⚡ That’s insane performance – and it changes the game for us. Why We Need YOU The software is here. Advanced, stable, and ready to use. What we’re missing is contribution. Even I don’t have much time to contribute right now, so this is a call for all of you to jump in and support the pool. At the moment, the stable pool speed is around 40,756.5 Mkeys/s. You can check the live stats on Telegram  https://t.me/+t9Ss2oR3O_cwMmEy Guides for all platforms are being worked on and will be shared soon. For now, the best place to ask questions and get updates is the Telegram group (search: https://t.me/privatekeydirectorygroup ) The Math Behind It: Here’s the current target range we’re working on: Start: 0000000000000000000000000000000000000000000000400000000000000000 End: 00000000000000000000000000000000000000000000007fffffffffffffffff Difference: ≈ 1.18e18 (about 71 bits) That’s what we’re up against. Big numbers, but not impossible with enough power from the community. Pool Performance The all-time high pool speed hit 8 trillion/sec – all thanks to DooKoo2 and contributors like: 0xdeadbeef | 4075120 1EbXXX     | 484 1dmqztjw   | 1301 CDMLCM     | 9983 D123456    | 3060 LaVidaLoca | 2938 OmniVerse1 | 9050 deadly117  | 2295 drw3bX     | 489 offXXX     | 686 With more people on board, we can reach and even beat that record again. How to Join Setup guide is available on Telegram (search: https://t.me/privatekeydirectory/1884) Pool link can be found here: https://t.me/c/3082083307/971 💡 The more of us contributing, the faster we can bring 71 down to 72 – and maybe even crack this puzzle in the months to come. Let’s grind together, support each other, and make some history. Wishing you all a great Sunday – see you in the pool! – Shub

What w0rd? Advising people to join a broken vulnerable unsafe pool where any other participant can keep the private key for himself by simply using kangaroo after hitting the public key match, while telling the pool that nothing was found and to continue scanning other ranges? Cool. Those are not crazy new levels, they are very slow speeds even for an underpowered GPU. Which translates to wasting more resources and electricity than required.

🔐 Security update — what’s new • TLS + SPKI pinning → prevents MITM attacks. 🛡️ • Per-user HMAC credentials → tied to each Telegram ID. 🔑 • Rate limits & anomaly detection → automated anti-abuse. 👮‍♂️ • Strict input validation (IDs & payout addresses). ✅ • Append-only audit logs — tamper-evident record. 📜 • Service isolation → least-privilege operation. 🔒 • Continuous monitoring & instant alerts. ✨ • Open-source client — verify checksums yourself. 🔍 Regarding disclosure & operational concerns: We will not disclose the discovery of any private key until funds are secured. If the pool announces “we found the key” prematurely, that could trigger immediate, chaotic activity and put funds at risk — we want to avoid that. ⚠️ I can reproduce test-keys with tools like RCkang, so transparency without adequate protections invites exploits. If you don’t want to participate, that’s completely fine — participation is voluntary. 👍 Also: sir dookooo is already flooding many GPUs; everyone running is currently earning significantly more, which helps them continue grinding GPUs and keeping the operation going. 💸🔥 Quick intro — who are you? Have we exchanged messages before? :V

The client side  has open source code, you should check it out and be a bit more pointed on your evaluation. Secondly, the client may not be the absolute perfect fastest to your standard but consider that there will be a dogpile of workers with some clever involvement with the community, and other platforms. Just watch and eat crow later, join and profit even though it's not perfect or your idea, or lose out. You always have something spicy to say without checking out the source code or asked about a hypothetical that the dev team took care of with Openssl encrypted replies to the work server. I even noticed something in the open source that has a minor impact. And they will correct it. That's the thing about open source code, it's a collaborative effort, not an angry neighbor that comes over to tell you that your flowers suck and grass is mowed improperly to your standards. There's an old saying at Intel labs, "Don't bitch unless you got the fix." All I see is complaining and no coding or ideas on how to get the puzzle solved faster that everyone can understand or participate in. I know that saying is true, even if you aren't a coder, even QA can spot a bad interaction with software or systems and pre-empt workflow snafus, and make it work easier for everyone to understand it. Your motherboard BIOS boots because of firmware I tested, debugged, and even coded some for the chipset, PXE, and Ethernet drivers for the first gigabit adapter.

First of all, I'm not running a BIOS, but thank you for your contribution to the hardware industry! Secondly, before you spend 20 minutes writing nonsense about SSL, here's a spicy line of code out of the client code: Now please explain why someone can not simply print the public key to the screen if it hashes down to Puzzle 71, and TRAP the kernel, giving zero fucks about whether the program continues or not. I don't think you understand the essential problem, frankly.

If you are using an Intel or AMD motherboard you are using/running a BIOS and some of that code I helped make that is there is running before you finish POST and then load  whichever OS. Unless you are a arm/phone user only. I saw the first alpha of UEFI in the lab and saw the gap they had to close to making it user friendly. It's always a possibility that there are high level programmers stealing your credit card information with zero day infections and bot nets also watching the browser or OS, just unlikely.  But we know it "possible" but if it was so simple, then why isn't it possible for everyone since greed and theft is a mainline for most people out there? Bitcoin is open source, and why hasn't it crashed to zero or be reverse hacked or have the works mucked up to a stall?

I'm not using an Intel or AMD motherboard, neither is it a phone or tablet. Maybe expand your view, have you heard of Apple Silicon? It beats all high-end Intel CPUs for some years now. No BIOS, no Intel shell codes on the SoC. Anyway, back to the topic. Why is it so hard to understand that a non-vulnerable H160 pool is close to impossible to implement? Even if you secure the client process to private memory and download some signed GPU code from a server every 5 seconds, in the most secure way possible, I can guarantee you the public key needs to be available on the client side one way or another, hence it is subject to be exploited without the server ever knowing it was found. In effect, making the pool un-trustable, even if you throw off 100 security layers on top. Someone who messed around with logic gates on motherboards would surely grasp this, right?

Yes, I have used 74xxx gates and glue logic on motherboards since 1982. Your Mac ARM machine that I mentioned as an exception was once powered by Intel motherboards and firmware back in the G5 era. It still only works since the rest of the internet has Intel and AMD boards running servers and desktops to feed your giggle device. Snazzy and not flawless as it is. Still why you poke at things, the pool is speed. == CUDAPool =================================== Range  : 400000000000000000:7FFFFFFFFFFFFFFFFF Target : 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU Port   : 15763 C_pow  : 2^40 TTL    : 10800 == WORKING == In-flight ranges      :       3799 Total computed ranges :     545804 Total percent         :   0.0539 % == Ranges ==================================== Client ID      | Assigned | Completed | ---------------+----------+-----------+ 0xdeadbeef     |     3765 |    515544 | 1EbXXX         |       15 |       122 | 1dmqztjw       |        1 |       486 | ALMSIVI        |        0 |        35 | Algein01       |        0 |       343 | AlphaBTC       |        0 |         1 | Anonymus00     |        1 |        46 | CDMLCM         |        0 |      1868 | D123456        |        1 |      1992 | DooKoo2        |        2 |     13643 | Gasper01       |        0 |       144 | J2XXXX         |        0 |         1 | JOKERSJ2       |        0 |         3 | JOKERX         |        0 |         1 | Kingkinder     |        1 |        71 | Kingkinder1990 |        0 |        67 | LaVidaLoca     |        1 |      2344 | Mehdi256       |        0 |       105 | NSH007         |        0 |         6 | OffXXX         |        0 |        23 | OmniVerse1     |        6 |      4284 | PuzzRUs        |        0 |        10 | Shub08         |        0 |        13 | TikTok         |        0 |      1502 | V1pER0X        |        1 |        26 | btc1001        |        2 |       112 | deadly117      |        1 |       766 | drw3bX         |        1 |       239 | happyswiss     |        0 |        69 | mrjamesbond    |        0 |      1498 | offXXX         |        1 |       489 | shub08         |        0 |        49 | testspeed      |        0 |        14 | th3pr0fit      |        0 |         2 | == Speed ===================================== Client ID  |    Speed 0xdeadbeef | 18138490 1EbXXX     |      534 1dmqztjw   |      984 Anonymus00 |      638 D123456    |     2541 DooKoo2    |    16551 Kingkinder |      309 LaVidaLoca |     3095 OmniVerse1 |    12043 V1pER0X    |      580 btc1001    |     1546 deadly117  |     3137 drw3bX     |      490 offXXX     |     2236 Total pool speed: 18183176.9 Mkeys/s