edr-0.20.0

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@nomicfoundation/edr@0.20.0

Minor Changes

• e1974f4: Added an optional blockTimestamp field to logs, as specified by ethereum/execution-apis#639. Logs returned by eth_getLogs, eth_getFilterLogs, eth_getFilterChanges, eth_subscribe("logs") and in transaction receipts now carry the timestamp of the block the log is in, as a hex QUANTITY.

  Matching the spec, the field is populated for locally mined blocks. When forking, it is passed through from the remote node, which every major client now serves; a log from a node that predates the spec change keeps the field absent rather than defaulting it, so a missing timestamp stays distinguishable from a real one.

• 9637a17: Added a synchronous, native Keccak-256 implementation: keccak256.

• e1974f4: Added a version subdirectory to the RPC response cache on disk, to invalidate outdated cache types. Cache entries now live under rpc_cache/v2, so everything else in rpc_cache is ignored and can be deleted.

• def04e7: Fixed interval mining accepting a [min, max] range that it could not honour. A range with min > max crashed the provider on its first interval-mined block, and [0, 0] starved the provider of incoming requests. A range must now satisfy 1 <= min <= max, and is rejected when the provider is created, when evm_setIntervalMining is called (JSON-RPC error -32602), and when a recorded scenario is loaded. Both bounds remain inclusive.

  Fixed evm_setIntervalMining not restarting the interval timer when called with the interval that was already configured. A range draws a new interval before each block, so an unchanged configuration does not imply an unchanged schedule.

  BREAKING CHANGE: [0, 0] and [0, N] interval ranges are no longer accepted. Neither previously worked as configured, but a configuration that is forwarded today will now fail when the provider is created. A scalar 0 still disables interval mining; a zero minimum inside a range must be normalised by the caller.

Patch Changes

• 7fff2bd: Moved JSON-RPC request handling onto a dedicated provider thread, reducing the JS scenario benchmark by ~27%