Automatically merged updates to draft EIP(s) 1283

Hi, I'm a bot! This change was automatically merged because:

 - It only modifies existing Draft or Last Call EIP(s)
 - The PR was approved or written by at least one author of each modified EIP
 - The build is passing
This commit is contained in:
Wei Tang 2018-08-10 23:42:25 +08:00 committed by EIP Automerge Bot
parent b569c4fa82
commit 6ecbcaa6e9
1 changed files with 11 additions and 12 deletions

View File

@ -49,12 +49,10 @@ recommended for Constantinople.
* For Version I, it covers most common usages, and we have two edge
cases it do not cover, one of which may potentially be useful.
* For Version II, it covers nearly all usages for a transient
storage. We only have one rare edge case (resetting a storage back
to its original value and then set it again) not covered. Clients
that are easy to implement EIP-1087 will also be easy to implement
Version II. Some other clients might require a little bit extra
refactoring on this. Nonetheless, no extra memory or processing cost
is needed on runtime.
storage. Clients that are easy to implement EIP-1087 will also be
easy to implement Version II. Some other clients might require a
little bit extra refactoring on this. Nonetheless, no extra memory
or processing cost is needed on runtime.
Usages that benefits from this EIP's gas reduction scheme includes:
@ -211,9 +209,9 @@ that for some edge cases dirtiness will not be tracked:
frame for the same contract won't benefit from gas reduction. For
Version II, this type of gas reduction is properly tracked and
applied.
* If a storage slot is changed, and it's reset to its original
value. The next SSTORE to the same storage slot won't benefit from
gas reduction.
* If a storage slot is changed, and it's reset to its original value,
the next SSTORE will effectively move gas to refund counter. This
case still benefits from this EIP's gas reduction.
Examine examples provided in EIP-1087's Motivation:
@ -226,9 +224,10 @@ Examine examples provided in EIP-1087's Motivation:
ending balances
* If the token contract has multi-send function, it will cost
`5000 * 3 + 200 - 4800 = 10400` gas.
* If this transfer from A to B to C is invoked by a third-party
contract, and the token contract has no multi-send function, then
it won't benefit from this EIP's gas reduction.
* For Version I, if this transfer from A to B to C is invoked by a
third-party contract, and the token contract has no multi-send
function, then it won't benefit from this EIP's gas reduction. For
Version II, this gas reduction is properly tracked and applied.
## Backwards Compatibility