Implementation of EIP-2929 #1387
Conversation
Legacy State tests before constantinople were moved to a child directory. We still need to validate against those. Generate and execute those tests under a "LegacyX" class series. Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
* deprecate old yoloV1 options * replace with yoloV2 options * clear the yolo bootnode * expose experimental EIPs flag to EVM Tool Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
* store warmed addresses and slots in the MessageFrame * probably need to do a gas calculator refactor at some point Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Recipient and sender are (almost) always the same. We want sender and contract (which should be recipient, unless it's a create, when we do want the contract) Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
* 0x0 is not a precompile. * Call operations need to check against to, not value recipient (which can be null) Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
* keep order of test cases * show all memory Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Dear mocking frameworks, I hate you. Also, reference tests: chillax on the memory load. Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Filled from hyperledger/besu#1387 Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
|
Should this have a changelog entry? |
ethereum/core/src/main/java/org/hyperledger/besu/ethereum/mainnet/BerlinGasCalculator.java
Show resolved
Hide resolved
ethereum/core/src/main/java/org/hyperledger/besu/ethereum/mainnet/BerlinGasCalculator.java
Show resolved
Hide resolved
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
|
Changelog entry added. |
| final Address address = account.getAddress(); | ||
| final Bytes32 key = frame.popStackItem(); | ||
| final boolean slotIsWarm = frame.warmUpStorage(address, key); | ||
| final Optional<Gas> optionalCost = slotIsWarm ? warmCost : coldCost; |
There was a problem hiding this comment.
This might be related to a question I asked in a previous pr but I can't remember. Do these need to be optional everywhere? For example, isn't the warmCost and coldCost always present here?
There was a problem hiding this comment.
It's a mix. We need the optional for the return value but we need the value during gas calculations. The gas cost is not optional within the method but on the return, for some errors we return an empty cost (such as when we can't know because of a stack underflow).
There was a problem hiding this comment.
Ah, I see, could we push the optional wrapping to as late as possible? I think it makes it clearer for which sections it is guaranteed to be defined. The intent is a bit unclear when the warmCost and coldCost fields are Optional.
There was a problem hiding this comment.
The optionals are re-used across requests. If we wrapped in the execute method it would result in object churn.
PR description
Signed-off-by: Danno Ferrin danno.ferrin@gmail.com
builds off of #1386
Changelog