diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst index a4315a140..489ad456e 100644 --- a/docs/frequently-asked-questions.rst +++ b/docs/frequently-asked-questions.rst @@ -71,13 +71,6 @@ several blockchain explorers. Contracts on the blockchain should have their original source code published if they are to be used by third parties. -Does ``selfdestruct()`` free up space in the blockchain? -======================================================== - -It removes the contract bytecode and storage from the current block -into the future, but since the blockchain stores every single block (i.e. -all history), this will not actually free up space on full/archive nodes. - Create a contract that can be killed and return funds ===================================================== diff --git a/docs/introduction-to-smart-contracts.rst b/docs/introduction-to-smart-contracts.rst index ad0a96509..7335ea075 100644 --- a/docs/introduction-to-smart-contracts.rst +++ b/docs/introduction-to-smart-contracts.rst @@ -455,13 +455,17 @@ receives the address of the new contract on the stack. .. index:: selfdestruct -``selfdestruct`` -================ +Self-destruct +============= The only possibility that code is removed from the blockchain is when a contract at that address performs the ``selfdestruct`` operation. The remaining Ether stored at that address is sent to a designated -target and then the storage and code is removed. +target and then the storage and code is removed from the state. -Note that even if a contract's code does not contain a call to ``selfdestruct``, -it can still perform that operation using ``delegatecall`` or ``callcode``. +.. warning:: Even if a contract's code does not contain a call to ``selfdestruct``, + it can still perform that operation using ``delegatecall`` or ``callcode``. + +.. note:: The pruning of old contracts may or may not be implemented by Ethereum + clients. Additionally, archive nodes could choose to keep the contract storage + and code indefinitely.