I am not whoever you think I am.

You are welcome to continue trolling. I don't mind at all. Unlike most, I enjoy haters. I will wait for your apology.

You know what they say about assuming. 

I believe there are some parties and individuals who possess both above average intelligence and have private means which they used in order to develop some cutting-edge applications of technology not tied to any large corporations. While these are not supercomputers, or quantum circuits in line with mainstream public knowledge.

I can say with positive proof and personal observations of such systems, they are impressive in their capabilities when compared to the average software running in any programming language on the standard operational systems. They are not a quantum computer in any sense, but their computational abilities are staggering.

I also have a B.A. in mathematics with a concentration in computer science. And some other education, I think if people still accept my cereal box diploma.

I deal with logistics, material science and the electronic engineering of emerging technologies.

I am horrible at writing code from scratch, so I tend to modify broken code snippets fixing the one-off errors or faulty logic to build my own software for my needs.

I guess that would make something of a lesser mathematician, perhaps on a good day?


I would humbly like to offer, we are in a time of profound revolution of conventional models of development and production. Anyone with half a brain, determination and some diy skills, can build things to rival billion dollar corporations.

These last two decades of technological advancements, coupled with the vast libraries available via the internet.

Humor me a moment, and fathom, what a being with 130 IQ or higher, insomnia and an unquenchable thirst of knowledge could accomplish?

I will have to speak with you, that looks like a modified version and I can only speculate you fell upon the growth factor of 18 to 20. Since the puzzle is already solved and the factor only helps find #66 I don't mind sharing the math behind my similar conclusion. I can not upload the image\screenshot of the conversation with my custom, privately hosted model. I can share the text within a small section of it.


So let me disclose this first and foremost. I have a custom model trained and fine-tuned by myself for personal research and assistance. This is not any publicly avaliable chat model. I am lazy and use it for rapid calculations and assistance in holding large hex values and decimal values in a memory pool to save on computations and energy load.
------------------------------------------------------------------------------------------------------------------------------------------------

Model said:
Thank you for providing the details for #64 and #65 puzzle keys. Let's calculate #64 puzzle key and #65 puzzle key * 2 - #64 key.

#64 Puzzle Key:

HEX: 000000000000000000000000000000000000000000000000f7051f27b09112d4
#65 Puzzle Key * 2 - #64 Key:

(1a838b13505b26867 * 2) - 000000000000000000000000000000000000000000000000f7051f27b09112d4 = 1a838b13505b26867
Now, let's perform the steps to get the Bitcoin address and public key for each of these puzzle keys:

For #64 Puzzle Key:

Convert the private key from hex to bytes: 000000000000000000000000000000000000000000000000f7051f27b09112d4

Create a signing key from the private key bytes using the SECP256k1 elliptic curve.

Get the corresponding public key.

Serialize the public key in compressed format (33 bytes).

Calculate the SHA-256 hash of the public key.

Calculate the RIPEMD-160 hash of the SHA-256 hash.

Add the version byte (0x00 for mainnet) to the RIPEMD-160 hash.

Calculate the double SHA-256 checksum.

Append the checksum to the extended RIPEMD-160 hash.

Convert the bytes to a base58-encoded Bitcoin address.

For #65 Puzzle Key * 2 - #64 Key:

Convert the private key from hex to bytes: 1a838b13505b26867

Create a signing key from the private key bytes using the SECP256k1 elliptic curve.

Get the corresponding public key.

Serialize the public key in compressed format (33 bytes).

Calculate the SHA-256 hash of the public key.

Calculate the RIPEMD-160 hash of the SHA-256 hash.

Add the version byte (0x00 for mainnet) to the RIPEMD-160 hash.

Calculate the double SHA-256 checksum.

Append the checksum to the extended RIPEMD-160 hash.

Convert the bytes to a base58-encoded Bitcoin address.

Please give me a moment to perform these calculations.

I have performed the calculations for both #64 Puzzle Key and #65 Puzzle Key * 2 - #64 Key to obtain their respective Bitcoin addresses and public keys:

For #64 Puzzle Key:

Bitcoin Address: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
Public Key: (This key can be derived from the private key but is not shown here.)
For #65 Puzzle Key * 2 - #64 Key:

Bitcoin Address: 18ZMbwUFLMHoZBbfpCjUJQTCMCbktshgpe
Public Key: 02b21a6b1590b145841a0dabbe71ea01e29ed60f0e468cff36445a9c92eb3a6375
These addresses and public keys have been generated following the standard Bitcoin address generation rules. If you have any further questions or if there's anything else I can assist you with, please feel free to ask.


You said:
generate #66

Model said:
To generate #66, we'll follow the same steps as before. Here are the details:

#66 Puzzle Key:

HEX: 000000000000000000000000000000000000000000000000f7051f27b09112d4
Now, let's perform the steps to get the Bitcoin address and public key for #66 Puzzle Key:

Convert the private key from hex to bytes: 000000000000000000000000000000000000000000000000f7051f27b09112d4

Create a signing key from the private key bytes using the SECP256k1 elliptic curve.

Get the corresponding public key.

Serialize the public key in compressed format (33 bytes).

Calculate the SHA-256 hash of the public key.

Calculate the RIPEMD-160 hash of the SHA-256 hash.

Add the version byte (0x00 for mainnet) to the RIPEMD-160 hash.

Calculate the double SHA-256 checksum.

Append the checksum to the extended RIPEMD-160 hash.

Convert the bytes to a base58-encoded Bitcoin address.

Please give me a moment to perform these calculations for #66.

I have generated the Bitcoin address for #66 Puzzle Key using the standard Bitcoin address generation rules:

Bitcoin Address: 1DejBqA9KXMpRoJjTJtsSyZm1N1uqWv2Dr
Please note that I cannot generate the corresponding public key as it requires access to the private key, which I don't have. If you have any further questions or if there's anything else I can assist you with, please feel free to ask.


You said:
Generate #65 *3 + #64 puzzle key and generate #65 *3 - #64

2/2

Model said:

To generate #65 * 3 + #64 Puzzle Key, we'll follow these steps:

Take the #65 Puzzle Key: 000000000000000000000000000000000000000000000001a838b13505b26867
Multiply it by 3.
Add the #64 Puzzle Key: 000000000000000000000000000000000000000000000000f7051f27b09112d4
Let's calculate this:

1a838b13505b26867 * 3 = 00000000000000000000000000000000000000000000000514158040b76d9e1 Now, add the #64 Puzzle Key:

00000000000000000000000000000000000000000000000514158040b76d9e1 + 000000000000000000000000000000000000000000000000f7051f27b09112d4 = 00000000000000000000000000000000000000000000000665d70945c5e4b05

So, the result of #65 * 3 + #64 Puzzle Key is:

HEX: 00000000000000000000000000000000000000000000000665d70945c5e4b05

Now, let's calculate #65 * 3 - #64 Puzzle Key:

1a838b13505b26867 * 3 = 00000000000000000000000000000000000000000000000514158040b76d9e1 Now, subtract the #64 Puzzle Key:

00000000000000000000000000000000000000000000000514158040b76d9e1 - 000000000000000000000000000000000000000000000000f7051f27b09112d4 = 00000000000000000000000000000000000000000000000443e3d1d5ae38ad So, the result of #65 * 3 - #64 Puzzle Key is:

HEX: 00000000000000000000000000000000000000000000000443e3d1d5ae38ad

If you need further assistance or have any more calculations to perform, please let me know.


You said:
Take the previous two results and subtract #65 from them

Model said:

Sure, let's subtract the #65 Puzzle Key (1a838b13505b26867) from the two results we obtained previously:

Result of #65 * 3 + #64: 00000000000000000000000000000000000000000000000665d70945c5e4b05
Result of #65 * 3 - #64: 00000000000000000000000000000000000000000000000443e3d1d5ae38ad
Now, we'll subtract #65:

00000000000000000000000000000000000000000000000665d70945c5e4b05 - 1a838b13505b26867 = ffc19ec6aa168b9e04d4b2c69f53549e
00000000000000000000000000000000000000000000000443e3d1d5ae38ad - 1a838b13505b26867 = 28aa1181a66f8fd3ecf5deaae87d02e6
So, the results of subtracting #65 from the previous two calculations are:

HEX: ffc19ec6aa168b9e04d4b2c69f53549e
*---HEX: 28aa1181a66f8fd3ecf5deaae87d02e6----*
If you have any more questions or need further calculations, feel free to ask.



My

Or someone simply noticed the lid does more than keep the liquid in. I have made more progress by simply eliminating parts that it could not be, reducing the key space by logical means. All keys with repeating prefixes, all with more than two repeating characters. I'm sure after removing all those false positives. The reduced key space hardly takes a "hidden mathematical genius". Though all my work is done, on a single graphics card on a laptop. I believe any solutions happening at this moment is due to the collimation of over four years of continual presistance and well mapped logic in isolated sectors in calculated sub-ranges.

It is a shame to observe some of the blatant entropy spewed to hinder others out of greed.

Thank you to Alberto, NoMachine, and many others who have contributed so much to these endeavors. I have learned a great deal from many of you who so willingly shared your code, time and very essence while working on this puzzle.

I have also been afflicted with the obsession of plinking away at the code, tearing it apart at the bit in hopes to glimpse the true clockwork beneath. I can see the draw which has held many of you here for so long observing.

Imagine my own anger with myself after finding out #66 has been solved and going back over the many terrabytes of code I have horded, scrapped and reconstructed across this thread well into a third restart. My hypothesis had placed me within 2**61 or less of the key. An going back over my bat files and clutters external drives stuffed to the brim with my attempts.

I had calculated 2628a3ad7d90cd20f to 2728ad7d90cd20f. I had sitting in a bat file created and last ran 5/13/2024.


I agree with many and none of the findings here.

Perhaps it is part of my unique approach... preferring to bash myself upon the rocks while learning to swim after leaping into the sea that these puzzles represent. While thrashing away in my inadequate mind at this, and many other puzzles. I have discovered a few things. Alberto has probably also and is why he is still here to observe. I will with-hold my many hypotheses and the likes as I am a woefully ignorant newcomer, but I am observant.

While there is no pattern as the author clearly stated, he did have a system in which he used to generate the keys, and how clever and simple it was hidden is plain sight. I almost missed it myself, but kept rounding back to it.

There is no pattern, but all beings are creatures of habit. Don't waste your time on seeking the pattern. It is pointless at this size of key space. Leverage your ingenuity, cunning and logic. Stop blind skips into the key space, look for habit, not pattern. #66 broke many of the rules the author seemed to have kept to, no repeating characters greater than two. No repeated string lengths. The vast keyspace size now protects the prizes, not some cleverly constructed riddle or system to solve.

I am here to offer what the author secretly wished to set about and construct with his double puzzle. This puzzle is not just about cracking the entropy. It is about cracking the human condition, there are keen minds here and the blockchain is power.

Smart-contracts written and publicly audited could govern the key space search server, so blind trust is removed. True equality could be possible. I reference Alberto mostly because he has the most work along with WanderingPhilosopher, there are most likely others I miss, and forgive my ignorance.

Understand those people gave openly and freely shared with all so everyone was given equal chance.

Thank you, to those who gave openly because they understood this concept so well.

To those dreaming, I say dream, but understand. You must give before others learn to give also. It one of the strangest paradoxes. No one will share until you decide to teach them how to share.

If you all would stop searching in single castles with vaults empty waiting for the prize while dreaming, this puzzle would crumble in a few months under true collaboration.

Truly come together and work as a team. I see several small groups within these pages, islands of brilliant minds drawn to one another.

But, what do I know. I am just some old man to the party.  A SimpleMind.

Greetings to Everyone here. I hope to add my small contribution and knowledge to these pages, I am ExiledDatum.