Timeline for Why are selfdestructs used in contract programming?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 3, 2019 at 19:43 | comment | added | makevoid | @ender in the etherscan (or etherchain) contract page you see the contract source only if it's uploaded by a user (it gets compared and verified by etherscan byw). The only way to interact with that contract / code is to fetch the bytecode from the block in which it was deployed thou and re-deploy it if you want to "resurrect" it, you still the ABI and you won't be able tor estore any state / ethers / tokens sent to the contract. | |
| Oct 28, 2019 at 6:17 | comment | added | Ender | @makevoid thanks, I found the answer on the same date. Ppl can see it after destructed. For example etherscan.io/address/… | |
| Oct 27, 2019 at 5:22 | comment | added | makevoid |
@ender - yes, the purpose/benefit of selfdestruct() is that if you have a dangerously buggy contract you can "terminate" it
|
|
| Sep 21, 2019 at 19:46 | history | edited | Paul Razvan Berg | CC BY-SA 4.0 |
Explain suicide vs selfdestruct better
|
| Jul 22, 2019 at 8:55 | comment | added | Ender | will a self-destruct smart contract no longer exists in blockchain?. I think, people can still see it, but it's a non-functionality smart contract. Is that true? | |
| Oct 8, 2018 at 18:11 | history | edited | natewelch_ | CC BY-SA 4.0 |
added 26 characters in body
|
| Apr 4, 2018 at 23:50 | history | edited | makevoid | CC BY-SA 3.0 |
added 357 characters in body
|
| Jun 12, 2017 at 19:22 | comment | added | Jossie Calderon | This should be the accepted answer. | |
| Jan 22, 2016 at 11:01 | history | answered | makevoid | CC BY-SA 3.0 |