EIP 161: State trie clearing - makes it possible to remove a large number of empty accounts that were put in the state at very low cost as a result of earlier DoS attacks. With this EIP, 'empty' accounts are removed from the state whenever 'touched' by another transaction. Removal of the empty accounts greatly reduces blockchain state size, which will provide client optimizations such as faster sync times. The actual removal process will begin after the fork by systematically performing `CALL` to the empty accounts that were created by the attacks.

可以删除由于早期DoS攻击攻击者以非常低的成本放入状态的大量空帐户。有了这个EIP，“空”账户在被另一个交易“触及”时就会从状态中删除。删除空帐户大大减少了区块链状态大小，这将提供更快的同步时间等客户端优化。实际的删除过程将在fork之后开始，系统地对攻击者创建的空帐户执行“调用”，一次来删除空账户。

eip-158与它相关，都是空账户的清除，161取代了158

Hard fork

Spurious Dragon

Parameters

• FORK_BLKNUM: 2,675,000
• CHAIN_ID: 1 (main net)

Specification

a. Account creation transactions and the CREATE operation SHALL, prior to the execution of the initialisation code, increment the nonce over and above its normal starting value by one (for normal networks, this will be simply 1, however test-nets with non-zero default starting nonces will be different).

帐户创建事务和创建操作在执行初始化代码之前，应将nonce在其正常初始值之上增加1个(对于正常的网络，这将是简单的1，但是具有非零默认启动nonces的测试网将是不同的)

b. Whereas CALL and SUICIDE would charge 25,000 gas when the destination is non-existent, now the charge SHALL only be levied if the operation transfers more than zero value and the destination account is dead.

虽然CALL和SUICIDE会在destination账户不存在的情况下收取25,000美元的燃气费用，但现在只有在操作转账超过零值且destination账户状态为dead时才会收取费用。

c. No account may change state from non-existent to existent-but-empty. If an operation would do this, the account SHALL instead remain non-existent.

任何帐户都不能将不存在状态更改为存在但为空状态。如果某个操作会这样做，则该帐户将保持不存在

d. At the end of the transaction, any account touched by the execution of that transaction which is now empty SHALL instead become non-existent (i.e. deleted).

在交易结束时，任何之前与交易执行有关但现在为空的账户都将变为不存在状态

Where:

An account is considered to be touched when it is involved in any potentially state-changing operation. This includes, but is not limited to, being the recipient of a transfer of zero value.

当涉及到任何可能改变状态的操作时，帐户被认为是被触动的。这包括，但不限于，作为零值转移的接收者

An account is considered empty when it has no code and zero nonce and zero balance.

如果帐户没有代码，且没有nonce和零余额，则认为该帐户为空。

An account is considered dead when either it is non-existent or it is empty.

如果一个帐户不存在或者它是空的，那么它就被认为是dead的

At the end of the transaction is immediately following the execution of the suicide list, prior to the determination of the state trie root for receipt population.

在交易结束后，在确定receipt population的状态树root之前立即执行自杀清单。

An account changes state when:

• it is the target or refund of a SUICIDE operation for zero or more value;

　　它是价值为零或更多的SUICIDE操作的目标账户或资金退还账户，

• it is the source or destination of a CALL operation or message-call transaction transferring zero or more value;

　　它是一个调用传递0或更多值的操作或消息调用事务的源或目的地

• it is the source or creation of a CREATE operation or contract-creation transaction endowing zero or more value;

　　它是创建赋予零或以上价值的操作或合同创建事务的来源或创建账号;

• as the block author ("miner") it is the recipient of block-rewards or transaction-fees of zero or more value.

　　作为块作者(“矿工”)，它是价值为零或更多的块奖励或交易费用的接受者。

Notes

In the present Ethereum protocol, it should be noted that very few state changes can ultimately result in accounts that are empty following the execution of the transaction. In fact there are only four contexts that current implementations need track:

在当前的Ethereum协议中，应该注意到很少的状态改变最终会导致在执行事务后账户为空。实际上，当前的实现只需要跟踪4个上下文

• an empty account has zero value transferred to it through CALL;

　　空帐户通过call转移到它的值为零

• an empty account has zero value transferred to it through SUICIDE;
• an empty account has zero value transferred to it through a message-call transaction;
• an empty account has zero value transferred to it through a zero-gas-price fees transfer.

Rationale基本原理

Same as #158 except that several edge cases are avoided since we do not break invariants:与#158相同，只是由于我们没有打破不变量，避免了一些边缘情况

• that an account can go from having code and storage to not having code or storage mid-way through the execution of a transaction; [corrected]
• that a newly created account cannot be deleted prior to being deployed.无法在部署之前删除新创建的帐户

CREATE avoids zero in the nonce to avoid any suggestion of the oddity of CREATEd accounts being reaped half-way through their creation.

CREATE方法避免nonce为0，以避免在创建过程中中途收到任何关于创建帐户的奇怪建议

Addendum (2017-08-15)附录

On 2016-11-24, a consensus bug occurred due to two implementations having different behavior in the case of state reverts.[3] The specification was amended to clarify that empty account deletions are reverted when the state is reverted.

在2016年11月24日，由于两个实现在状态恢复的情况下具有不同的行为，导致了一个一致的bug。规范进行了修改，以声明在状态恢复时将恢复空帐户删除。

References

1. EIP-158 issue and discussion: https://github.com/ethereum/EIPs/issues/158
2. EIP-161 issue and discussion: https://github.com/ethereum/EIPs/issues/161
3. https://blog.ethereum.org/2016/11/25/security-alert-11242016-consensus-bug-geth-v1-4-19-v1-5-2/

Details: Geth was failing to revert empty account deletions when the transaction causing the deletions of empty accounts ended with an an out-of-gas exception. An additional issue was found in Parity, where the Parity client incorrectly failed to revert empty account deletions in a more limited set of contexts involving out-of-gas calls to precompiled contracts; the new Geth behavior matches Parity’s, and empty accounts will cease to be a source of concern in general in about one week once the state clearing process finishes.

当导致空帐户删除的交易以out-of-gas异常结束时，Geth未能还原空帐户删除。在奇偶校验中发现了另一个问题，奇偶校验客户机在一组更有限的上下文中没有正确地恢复空帐户删除，这些上下文中涉及到对预编译合约的out-of-gas调用；新的Geth行为与奇偶性匹配，一旦状态清除过程完成，空账户将在大约一周内不再是普遍关注的问题