Logic assembles the pyramid , side A of D

                                                                    1378
                                                                15314ce0
                                                            1d3202483a7b
                                                        1460293068f3c936
                                                    1764f3080d5749fd2c55
                                                1ba5342de40f556e52dc2a04
                                            1fa5ee5340326e6ac3875d916ce8
                                        17e2551e3d94cd647d4fe747b862a62e
                                    1a96ca8d834a65911d4aed211709de820a7c
                                1757756a9322382facd04b5f8303e9e9ae4933d6
                            153869acc5b2a221c58d8f6bd3b27c591e02b35a358f
                        122fca143c052ec18388d5446cd610b53cbaade6d7ce3b9b
                    174176b015f4d22bd43c2e935475070a1a009d4efae164cb9e3c
                180788e47e326c236fb6d5ad1f436abe1f9b67e1149d18b63ac4ffdf
            1eb25c90795d61c2c675b852189a217496cbb87cab44ffc07a1825367bbe
        13c96a3742f64906363d541eb611abee7cce5efdaccf6808f7051f27b09112d4
    1a838b13505b268672832ed74f2b5e35ee730fc235c1942c1aebebb3940cd0fc1491
101d83275fb2bc7e0c349b84b6431a6c4ef10000000000000000000000000000000000.00

           "1,3,7,8,15,21,49"
.001÷.003007^8 = 1496003381521                                                            
                                                        It is the Geometry that yields the treasure

The waters flow uphill

46346217550346335726 × 65.9565 = 3056834297859418092311.919

Well, since you found the match, the probability is 100% to have exactly 1 of those prefixes, in an interval of size one, starting at the key you've found.

I have spent a lot of time and money on puzzles, and with the discussions I have seen in the forum, I really can't trust anyone except the forum administrator. I would like to ask the forum administrator to introduce me to a way to communicate before it's too late. Thank you.

approximately 400,000

Guess who win first
135 or 71
And  your comments, reason ?

Hello, guys!
Ultra lightweight CUDACyclone is ready, speed is 1.3Gkeys/s on RTX4060.
Key feature - extremely low VRAM usage for rented gpu. Less than 500Mb VRAM on RTX4090.
It will work even if Vanity or Keyhunt doesn’t start.
And also this is a good studying sample for your education (why not)? Total 7 small files.
Link: https://github.com/Dookoo2/CUDACyclone

wtf i try the nvidia h200 and is just doing 2.8–3.0 billion keys/sec i was expecting more how can i gpu of  $31,000 to $32,000 do such low or im doing something wrong??

Guys i wanna share with you a tool that i was developing

its a GPU binary transformator for searching bitcoin puzzle

https://github.com/puzzleman22/bitcoin_puzzle_transformation

Compute and store 2**80 H160s (from different private keys) and you'll reach the 50% threshold to get your first H160 collision between some of the stored items. Not there yet? Keep crunching at it until it pops.

NB: you might have some difficulty storing more data than the combined capacity of all storage devices in existence allows.

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 8 )
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

It's great as long as you're not paying for the electricity!