0
How do I get the private key from the data below?
KEY PUBLIC: 04f2327c57013916e94041ee3ee6f7fcb3dd9cc92c1b7900f51ddfa277eac6b1e175d825d8ce295502cee0f912a18c15cdf2051a16b1d658c64d3b4b3aa4536cf5
SHA-256: 673c32048f3643920a724c2be10ff9be1c562e3833be49e41ad7180bdf571a03
RIPEMD160: 713afb1cf583fbfc43ef1de90421e0df9f48352d
+BIT: 00713afb1cf583fbfc43ef1de90421e0df9f48352d
HEX-HASH: 4df94906f14d296f99c032e7ad59d0d2fae3a9f3a83fffee356d484ce4af969d
HEX-HASH: 0ed48be1b086dabb9e5fee3848e082ac4a57b1063cfb9c9f21bf5c539f646767
CHECKSUM: 0ed48be1
HASH160: 00713afb1cf583fbfc43ef1de90421e0df9f48352d0ed48be1
ADDRESS: 1BKi1k4GmLphXHrWwVCG4uoz33e3ymRoXW
I would like to understand better how the calculations are made to arrive at a result between address and public key. Finding in brute force is not the intention.
Can you tell me what you’ve tried? As far as I know, the public key barely speaks of the private key. Encryption is done with public, but can only be decrypted with private, in asymmetric key systems
– Jefferson Quesado
It has some specific algorithms that break some keys, but is dependent on unconventional or time-consuming machines. It matters?
– Jefferson Quesado
No, to find in the brute force is not the intention only I would like to better understand how the calculations are made to arrive at a result between address and public key
– Rose
And quantum? :-)
– Jefferson Quesado