diff options
| -rw-r--r-- | docs/frequently-asked-questions.rst | 6 | ||||
| -rw-r--r-- | docs/introduction-to-smart-contracts.rst | 2 |
2 files changed, 2 insertions, 6 deletions
diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst index ea8d2e53..e0bdcfb4 100644 --- a/docs/frequently-asked-questions.rst +++ b/docs/frequently-asked-questions.rst @@ -554,12 +554,6 @@ The correct way to do this is the following:: } } -Can a regular (i.e. non-contract) ethereum account be closed permanently like a contract can? -============================================================================================= - -No. Non-contract accounts "exist" as long as the private key is known by -someone or can be generated in some way. - What is the difference between ``bytes`` and ``byte[]``? ======================================================== diff --git a/docs/introduction-to-smart-contracts.rst b/docs/introduction-to-smart-contracts.rst index 7335ea07..eeea85a7 100644 --- a/docs/introduction-to-smart-contracts.rst +++ b/docs/introduction-to-smart-contracts.rst @@ -469,3 +469,5 @@ target and then the storage and code is removed from the state. .. 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. + +.. note:: Currently **external accounts** cannot be removed from the state. |