Quote from: cryptoDEADBEEFFFFF on Today at 02:33:31 PM

Quote from: GR Sasa on Today at 01:56:56 PM

Quote from: digaran on Today at 01:10:18 PM

Quote from: WanderingPhilospher on Today at 12:05:39 PM

Edit:
Example of a strange public key:

Code:

0400000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c633f3979bf72ae8202983dc989aec7f2ff2ed91bdd69ce02fc0700ca100e59ddf3

Code:

0400000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63c0c686408d517dfd67c2367651380d00d126e4229631fd03f8ff35eef1a61e3c

Find their difference, also after that check 69 and 96 as hex, convert them to decimal and compare their values and difference in values, as I have said before this is an ocean, and somehow the designers of EC and the math involved either used magic to come up with these equations, or I am still unable to fathom the infrastructure underneath them all, yet. Do not rely on existing tools, if you can come up with new solutions, share them if they can not be used to endanger coins other than puzzle coins. Otherwise you should not reveal anything if it can be exploited to steal coins from people.

That's bullshit mate. These are freaking completely normal VALID public keys and have of course private keys that are connected to the them. There is nothing strange with them or what so ever....

Just because a public key has many zeros does not make it "weird" or "strange".

Here's a VALID private key with many zeros. Is it weird?

Code:

000000000000000000000000000000000ffff000000000001111111111100000

It's actually interesting to see public keys that follow this pattern. The keys produce the following addresses when they are uncompressed:

Code:

./calculatefrompublickey 0400000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c633f3979bf72ae8202983dc989aec7f2ff2ed91bdd69ce02fc0700ca100e59ddf3
address 16qakrWzEAPvDsY1yMdCrkgAWZ6DxpTK4z

./calculatefrompublickey 0400000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63c0c686408d517dfd67c2367651380d00d126e4229631fd03f8ff35eef1a61e3c
address 14szHdohyNkdE3XdiwUw1wNmuBUamPBXiS

at compressed format they produce the following addresses (and they had an out transaction meaning they have a valid private key)

Code:

./calculatefrompublickey 0200000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63
address 13see6qjfupx1YWgRefwEkccZeM8QGTAiJ
./calculatefrompublickey 0300000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63
address 1LVAsnUyEtJgZ9HzLfbtiJZuZMzHLX1n6k

Just like there is invalid private keys, soecifically those after the key fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364140 .. there are also invalid public keys. The reason is o there are pub keys that lie outside the curve. But i gotta agree that the mentioned pubs above are interesting, especially knowing that one of their addresses is a used one. The only thing I'm not so fond of is the idea of.trying to figure out a mathematical formula to solve the puzzle. Sometimes it's possible to find a pattern in chaos, but most times you can't.

It feels weird for me to say that especially that i believe numbers are the solution to everything and the base behind the universe existence. I once was joking saying to my cousin that God is Math! Lol.

Problem with big numbers like the ones we're dealing with right now is it's bigger than human imagination. The lowest number of keys we're going after here is #66 which evaluates to 36.8 Million Trillions. And according to WanderingPhilosopher's calculations, the lowest number here is #125, using kangaroo, this number has gotten smaller: 2^63.05 .. if we manage to solve any of these two puzzles, we will literally make history.