mirror of
https://github.com/status-im/EIPs.git
synced 2025-01-27 23:26:03 +00:00
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:
parent
01cc174d8b
commit
7ecab6a33e
@ -151,13 +151,13 @@ current scheme in this case.
|
||||
|
||||
In current call frame, a **Dirty** storage slot can be reset back to
|
||||
**Fresh** via a SSTORE opcode either on current call frame or a
|
||||
sub-call frame. For Version I, for current call frame, this dirtiness
|
||||
is tracked, so we can issue refunds. For sub-call frame, it is not
|
||||
sub-call frame. For current call frame, this dirtiness is tracked, so
|
||||
we can issue refunds. For Version I's sub-call frame, it is not
|
||||
possible to track this dirtiness reset, so the refunds (for *current
|
||||
call frame*'s initial SSTORE from **Fresh** to **Dirty**) are not
|
||||
issued. This refund is tracked on Version II, and issued properly. In
|
||||
the case where refunds are not issued, the gas cost is the same as the
|
||||
current scheme.
|
||||
issued. For Version II's sub-call frame, This refund is tracked and
|
||||
properly issued. In the case where refunds are not issued, the gas
|
||||
cost is the same as the current scheme.
|
||||
|
||||
When a storage slot remains at **Dirty**, we charge 200 gas. In this
|
||||
case, we would also need to keep track of `R_SCLEAR` refunds -- if we
|
||||
|
Loading…
x
Reference in New Issue
Block a user