Re: Pubkey scaling/subtracting/other tips for reducing search time
⭐ Merited by COBRAS (1)
you just explained that it has already been spend found. whe testing that key or what, what addition to add if found to get the right pvk. address. thanks
This is another good example with privrange ( ((2^60) - 986458768829923488 ) pubkey:
0x db09b0615ad40a0 * 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918
=
0348e843dc5b1bd246e6309b4924b81543d02b16c8083df973a89ce2c7eb89a10d(this is has a range 2^60 (address - 1Kn5h2qpgw9mWE5jKpk8PP4qvvJ1QVy8su))
This is a part of privkey - 986458768829923488 in hex db09b0615ad40a0.
No one can't find a privkey of 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ?
dec = 104856515000339101452906010972016177983340459646873053037069757574992766929113
hex = E7D2AF2FC9FF9CAF795D2EED256567679873FC547A513AA85A8A2E2776AB88D9
pubkey = 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918