Quote from: Ovixx on Today at 09:12:27 AM

Quote from: digaran on May 05, 2023, 08:48:50 PM

0279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798
02bcace2e99da01887ab0102b696902325872844067f15e98da7bba04400b88fcb
02c994b69768832bcbff5e9ab39ae8d1d3763bbf1e531bed98fe51de5ee84f50fb
0379be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798
03bcace2e99da01887ab0102b696902325872844067f15e98da7bba04400b88fcb
03c994b69768832bcbff5e9ab39ae8d1d3763bbf1e531bed98fe51de5ee84f50fb

When you fuck around enough, you will find out! Lol, so I was playing with some tools and since I have no clue what I'm doing, I managed to find some twins for our beloved G. I call them alternative G spots. Funny they all have the same y coordinates.

From
addr: c. 1MRxjnjFDhZfjtjgpxBNczsMGVEtYqfFyS u. 1Jy6aHcRTWjiPN9DpjZztk2F8xY9iNsaj2
020000000000000000000000000000000000000000000000000000000000000001
040000000000000000000000000000000000000000000000000000000000000001483ada7726a3c 4655da4fbfc0e1108a8fd17b448a68554199c47d08ffb10d4b8
```````
```````all hex range of x
```````
```````
to
addr: c. 1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw u. 1F18os1CipgxyUj9wBMY4yK1HEVUaub2Nr
02ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
04ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff483ada7726a3c 4655da4fbfc0e1108a8fd17b448a68554199c47d08ffb10d4b8

there are addresses with public keys where the coordinate y is the same.

More interesting is the fact that, the public key 02ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff is the correspondence for the same addresses 1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw as 0200000000000000000000000000000000000000000000000000000001000003d0 and continuing like this, if we change the value of the y-coordinate of the public key, for each even/odd value it seems the compressed address is the same:
1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw
0400000000000000000000000000000000000000000000000000000001000003d00000000000000 000000000000000000000000000000000000000000000000002

1KmKgQHBMbequmyi9uP1yfa1vsNjdsjyEz
0400000000000000000000000000000000000000000000000000000001000003d00000000000000 000000000000000000000000000000000000000000000000003

1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw
0400000000000000000000000000000000000000000000000000000001000003d00000000000000 000000000000000000000000000000000000000000000000004

1KmKgQHBMbequmyi9uP1yfa1vsNjdsjyEz
0400000000000000000000000000000000000000000000000000000001000003d00000000000000 000000000000000000000000000000000000000000000000005
`````
`````an so on
1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw
0400000000000000000000000000000000000000000000000000000001000003d0fffffffffffff fffffffffffffffffffffffffffffffffffffffffffffffffff

I could conclude from here that any compressed public address exists as many times as there are for each uncompressed address and vice versa, and the mathematical space of the corresponding keys that generate them is much larger and can be treated as a three-dimensional space.

Did you change the keys somehow? It seems most of them are invalid, I don't know where you got them, but you should put each public key inside a code bracket to better identify them.

You don't happen to have any of their private keys do you? For a second I thought you just found hash collisions.🤣