Update EIP-3074: allow authorized to send value

[lightclient]

The authors have gone back and forth about allowing this behavior in the first iteration of the EIP. The limitation was originally added to de-risk 3074. Over time, we've come to find that the concern around sending value was overblown.

Yes, it breaks a protocol invariant which exists today (e.g. you can statically determine if a list of txs are valid). However, the cost of breaking this is minimal.

In the rationale we outline an attack which is possible today and how 3074 decreases the cost and difficulty.

Currently an attacker can queue many transactions in the tx pool, across many accounts, and invalidate them all at once with a block where each of the queued accounts send a tx moving their entire balance. This attack will become easier and cheaper after this EIP, because it will no longer require direct access to the block builder and will not cost a full 21000 gas to originate each tx. However, the attack does not have a substantial impact on the network, so reducing the difficulty and cost are not of concern.

If there is further concern of this attack, we can modify the gas cost of sending value with AUTHCALL so that it deters attackers using it to invalidate pending transactions.

[eth-bot]

✅ All reviewers have approved.

[eth-bot]

All Reviewers Have Approved; Performing Automatic Merge...