Hello guys,
I’ve been doing analyses over the past year related to our favorite puzzles.
I’ve probably found something interesting, but due to limited resources and weak hardware, I can’t continue my experiments.
I have a test pseudo-solver, which isn’t even really optimized.
During the course of this experiment, I managed to predefine a distinct offset (not 100% guaranteed success) that seems to align with the actual direction of the public key.
I can’t even properly explain how I came to this or how it works, but I will show you some examples.

I used my script, and it turned out that in a certain range there are 7–8 consistent matches, specifically:

---

**#55**
Key found privkey 7f183c47701240
Publickey 0393f63f7cc69a05d4a7447648c815d955a512c5c234a4ed1bbc3f4eebd3027296
Key found privkey 7f3900e315f594
Publickey 02f933ba845beaf6f875f17c1a25bfe09707bd34099ea6c8cfe2486402038d1145
Key found privkey 7f59c57ebbd8e8
Publickey 0249f74ad1e79a86e7c6326b36a3bf687b2b512f3144fd3233d5b86ffac5790432
Key found privkey 7f7a8a1a61bc3c
Publickey 03d82f7a4f1b28f1279b0abb32dad3fce0ea22e2232c494fc49efd989515902a30
Key found privkey 7f9b4eb6079f90
Publickey 024155be90fb71d0bd44bf7188a708decf7d422563b188c8c74c0951ebd74ffb8a
Key found privkey 7fbc1351ad82e4
Publickey 03f56a151fa8494fbec6abb9d25b04f09eeb855aa1b196a9295d946b2ecaa9df95
Key found privkey 7fdcd7ed536638
Publickey 036dbf40fec342c00ac120f4b0015f66c7c8782f8a9a722e1831caadd273dd3b6d
Key found privkey 7ffd9c88f9498c
Publickey 02a788404280b4949c656b72a52292fcd881eff5e69837a0838ca73040a71c096d

---

**#59**
Key found privkey 7f15c5939f7c2cf
Publickey 0331d096dd0e0562fb36479021749284f3c0c4fd63cd0fc94526152f16346ff993
Key found privkey 7f368a2f455f80f
Publickey 03cbc12fa846a5518ae3d4a65f321a47d3e1a08161f0e0e8df2549d270567168ad
Key found privkey 7f574ecaeb42d4f
Publickey 0329908e2bc64ad1573a68648c1f77b04ac598c61f5e2002779e3791d35b323392
Key found privkey 7f781366912628f
Publickey 0200fbc37270ef51b22702c29ee51636427646af1545094edabde09c20efff7a9a
Key found privkey 7f98d80237097cf
Publickey 0363911bc2601b69512b0b22d58f49381e1cd1feb9f4aa7b4b27642eb6c7f03307
Key found privkey 7fb99c9ddcecd0f
Publickey 03a359ac3a4449ab37706571796b4dca840ef15fbc4e27197b8b7f2e69734f49f0
Key found privkey 7fda613982d024f
Publickey 02b9a9ce45af5dc35fa5a2d6610e994368c7fb7cdc4220d0196951cc2fa30fd73c
Key found privkey 7ffb25d528b378f
Publickey 02f606be9de74e28276ddf7ae4ebc7932c1e06453da5174911289fd58614b6d92d

---

**#63** (this is where the margin of error appears, only 7 keys instead of
Key found privkey 7f1c31ef56cb4f78
Publickey 03e9dcd8d1f8fefc9af93e30765dffcfcccd469ec870ee6714f39ed4a0799494ff
Key found privkey 7f3cf68afcaea370
Publickey 02e6c79c88c2e8cac421295b96ebc87d4286c3e2fb884c763c280c0567e5f1ddd8
Key found privkey 7f5dbb26a291f768
Publickey 03a79083ac65a4020b445c28d106c68448bc82612945699ee636c70faf005a8884
Key found privkey 7f7e7fc248754b60
Publickey 02ad76f61e23f3c7714a9d20cc855f234495be68acaeb89d1ec011525b7e315c67
Key found privkey 7f9f445dee589f58
Publickey 03c92f4e4d080c680abdf10415fa06cea5bf596ea94619b5f851ef49ffd2d2e176
Key found privkey 7fc008f9943bf350
Publickey 031cf7da5a14f4101b8ce1244cc0baeb72e5eb4f3ae7370c40cd32d723551c1120
Key found privkey 7fe0cd953a1f4748
Publickey 0289923508d3fe2dfaddf172bcfe19836bb2d51f457a5b822e49a969447267ea3b

---

**#67**
Key found privkey 7f17f35cab0d01194
Publickey 03b90da1172571bfd86424c8097e295ba0fc5f967a4978d245938842fdd5c0e9f9
Key found privkey 7f38b7f850f055111
Publickey 02b8ef9ea2f15f692ba99ca6d919797da52a30b548bdec63587f0aa20e4982873f
Key found privkey 7f597c93f6d3a908e
Publickey 02d861490aa4657cbfcf172db710b6dc28010f236ac2054fd9a71b2f5ee270d8ae
Key found privkey 7f7a412f9cb6fd00b
Publickey 03c3170b03e3d9c7a5f6004029f5a051eaf47b71ad011308cb543631bf19b151bd
Key found privkey 7f9b05cb429a50f88
Publickey 038c3ad15c436b73a743ab68da3e148640f1049505897d328c5e6d1494cfca63c9
Key found privkey 7fbbca66e87da4f05
Publickey 03d34f3078c36bfa5556cca630339e7351b63b7ad30601b8579421da498b9eb96c
Key found privkey 7fdc8f028e60f8e82
Publickey 0340246482f3081fe4f03cce3a79a4f3347fbf6e3cf50511ae5388d7667f1e00dc
Key found privkey 7ffd539e34444cdff
Publickey 03fe8222ad71f7d543cc5a1453d1bc75ba0583c584b4476e5809379f25e325e94f

(This example leans toward the final result, and I’m showing you obvious data starting with 7f1 or 7f3 and so on.)
If it’s still unclear what kind of nonsense I’m writing here — well, I found a specific mixing pattern that helps indicate the location of a public key with an offset (similar to `keysubtracter`).
In fact, I was able to pull a public key from range 85 into range 63, and just like with `keysubtracter`, my script only outputs valid public keys within the range.
Out of 10 generated keys, 7–8 are always correct. Why 7? Because success is not 100%, there are still errors I could possibly fix.

**Who might be interested in this?**
Probably people who have solid hardware. For example, our retired friend RC could potentially shift a public key from 135 to 120. I can’t give exact numbers because I’m limited by my hardware.

A few answers in advance:

1. This is not some random AI-generated Python code — I wrote it myself in C++.
2. My code isn’t good enough yet to publish on GitHub.
3. I used mathematical approaches during development, and I wouldn’t call this a collision, but it works very well for solving our puzzle in small ranges.
4. I don’t know what will happen with development next. I will share the solver, ideas, and calculations in DMs only with people who are serious about taking it further.
5. The 7-out-of-8 error happens because I must be missing something — I’ve seen so much data that the iterations almost always give correct answers, but I’m still not sure where the actual issue lies.
6. Only `keyhunt`? No, I also used `RCkangaroo` and JLP’s `Kangaroo`.
7. My hardware is just an RTX 3060 — you understand what kind of speed that means.

I’m not asking anyone for money, but if someone decides to support me and help realize this idea, maybe even buy a couple of RTX 4090s, I’d really appreciate it.
bc1qndszla0ry9f8zjczpg8lz74r94xv8xk28djj0k

The debt is not for equipment to search for a private key, it's much more complicated than that..

Calm down already—aren’t you ashamed to be posting nonsense on this forum?
I understand that each of you has your own goals and intentions, but it seems this thread was created to solve puzzles, not to start arguments.
Personally, one thing is clear to me: this is a simple test of the reliability of ECDLP, and they’ve given us the opportunity to try and break it for a reward.
I’m trying to find the private key myself, because I have over $35,000 in government debt, and it keeps growing every day. My salary isn’t enough to cover the debt or feed my family. Most likely, I’ll lose my home in 1–2 months…
There are smart people here who know what they’re doing and have proven they can solve it—that’s why they’ve earned their reward. Then there are others (like me) who are spending their last hope, gambling on luck.

Pay To Public Key

"outputs": [
    {
      "address": "1Lo1VC2YNkqELDNGHpsKDD8KEzbNKBjzpF",
      "pkscript": "41040000356cb2e0d0c0a0167693b14c338f548da20fea024a04449907140fa270ebff37ae70d00 db8137b5c60d9563b743b090f162f7bf1b51650d20cd7022d695dac",
      "value": 5000000000,
      "spent": false,
      "spender": null
    }
  ],

pkscript = public key

Yes, I agree — there’s no shortcut. Even mathematically, it’s 50/50 — but denying that fact would be foolish, because there’s no definitive solution, and probability is still a real factor.



And those people most likely believe in probability — and that’s their right

If you’ve already got a few million in your pocket, it’s better you leave this forum and stop getting in the way of others trying to find different solutions. But if you’re also someone who enjoys solving complex puzzles — then welcome to the club.

In essence, we’re all here for the same reason: to play someone else’s game, trying to break *secp256k1*. But no one really seems to have grasped that yet. Still, there are also people here just hoping to get lucky and catch that elusive BTC left for us by a mysterious stranger. And it’s really simple — some are here to attempt the impossible, and others are just testing their luck in hopes of getting rich.

From what I understand, there are often conflicts here over different topics, but I have one request: don’t stop others from trying their luck, even if it’s only 0.00000000000001%. Because even they have a chance — and one of them might just find the key faster than Bram24732 with his 2000 GPUs.

Okay, thanks for the hate, I guess — but can you show me even one person who’s getting this kind of speed on a CPU like mine?
https://ibb.co/VYP4vh7h

I don’t owe anyone any proof.
I’ll say it straight — right now, I’m searching for 135.
https://ibb.co/whQdZcpC

Sorry, but not right now — if I had a couple thousand in support, I’d be able to speed up work on the project.

I have doubts about the computational power — with that many GPUs, you could’ve soloed 69 and come out ahead. Maybe I’m wrong (though it’s unlikely), simply because I don’t know your actual speed. But in reality, the ranges can be narrowed from the very beginning (and if you’re a cryptographer, you should have noticed something).

I apologize in advance, I don’t want to offend anyone.
I just want to make one thing clear: it doesn’t matter whether someone has over 2,000 GPUs or just one old GT card — the chances are almost the same for everyone. The only difference is that the one with more computing power pays more — they take on more risk, and yes, they have a slightly higher chance. But for the rest, there’s practically no risk at all.

The whole idea behind this "game" was to show just how "perfectly" the network functions. And if someone finds a vulnerability, the goal is to fix it as fast as possible for the sake of security. So, in a way, we’re bug hunters — and I’m genuinely impressed by RC. He went much further to tackle more complex ranges.

Everyone has their own approach to searching for private keys in this game. I, for example, don’t use a GPU. I based my work on keyhunt with heavy modifications, and now I’ve reached 400 Pkeys/s on an old CPU, even though initially I couldn’t get above 60 Pkeys/s.

P.S. Please don’t ask for the code just yet — I’m still working on improvements, and once it’s ready, I’ll share it with you.
P.S.2. RC, your SOTA method is very impressive and flashy, but not very efficient (sorry). It’s a good method though, and I did start using it myself — until I found a new solution.
P.S.3. Bram, there’s so much buzz around you, but I still have some doubts.

Because I'll lose my search progress from Keyhunt.

Can you compile it into an .exe file? I have some good working hardware and I'd like to try it out.
My Keyhunt at 10% power produces about 300 Pkeys/s. And I want to test the speed of your Cyclone.