Quote from: BTC_Backdoor on Today at 06:13:53 AM

Here is the public key which has the private key next to your
043BFE84C13671C55CF8F0710D2959890CD16B63176365EF9D98810D8E987C82E1C8C921E2A46BB 2041B7CE321E0D48CD30AD1BDBD767E684920CF2181021D960C

Here is the public key for the private key if you +100 to your private key.

04FD76543436A87E6A30CBBF7FD327C0643ED530CA6D2288BC9798B104E62B262B6344608EB6143 5BD96D9096833346AAE121A542E95EAD7C15FFA779F94C804FC

Neither of you have provided an actual private key for the uncompressed public key, so no one can verify that these keys are "next to each other". All this looks very much like ill-conceived quackery, where one person creates two accounts to prove his point in some ridiculous way.

Quote from: NotATether on April 15, 2023, 03:04:35 PM

ECDSA is *NOT* used to create addresses from private keys, it is used to create transactions and signed messages.

Any exploit on ECDSA is not able to affect the key generation part of Bitcoin.

Thank you for the correction, I was talking about standard operations such as elliptic curve addition, doubling and multiplication that are used to convert the generator point into a public key which we later convert to a bitcoin address performing additional hashing and encoding. But explain your second statement: isn't the key generation algorithm a main part of ECDSA? I mean, if we were to find an exploit in signature generation algorithm, it would most likely be related to private-public keys manipulation.