Timeline for What if I had the private key that had the public address of a contract?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 26, 2021 at 6:11 | comment | added | eth♦ | @the0roamer The cost of brute-forcing is "1 year, of Bitcoin mining. This is $10 billion in June 2021." | |
| Jun 26, 2021 at 6:06 | history | edited | eth♦ | CC BY-SA 4.0 |
eip has been drafted which can change this answer, when the eip is implemented
|
| Aug 1, 2019 at 16:23 | comment | added | ihatecsv | Usually contracts do not have keys, but it's technically possible to find that key by brute-forcing. Contracts and wallets (externally owned accounts) share the exact same address space, in that they produce addresses in the same range of numbers, so it's possible, but astronomically unlikely, to find the key for a contract by iterating over private keys until the wallet address matches the contract address. You could also do the opposite, iterating over the owner of a contract until the resulting contract would have an address the same as an existing wallet. | |
| Apr 22, 2019 at 16:14 | comment | added | ehsan0x | according to your answer here there are no keys associated with a contract account address. Then how can a private key end up generating the same address as a contract's one that is created via "The sender and nonce are RLP encoded and then hashed with Keccak-256"? | |
| Jun 4, 2018 at 3:39 | history | edited | Achala Dissanayake | CC BY-SA 4.0 |
Formatting improvements
|
| Jan 21, 2016 at 17:19 | vote | accept | linagee | ||
| Jan 21, 2016 at 10:28 | history | answered | eth♦ | CC BY-SA 3.0 |