reth
reth copied to clipboard
Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol, in Rust
Ensure that the Ecotone spec is passed into revm L1 cost calculations when this active, as this hardfork introduced a [new cost function](https://github.com/bluealloy/revm/blob/84d1372e072564ae4f3334a60e9074d2790f6293/crates/revm/src/optimism/l1block.rs#L148-L149).
- `use_self` clippy lint checks for unnecessary repetition of structure name when a replacement with `Self` is applicable. - Why is this bad? - Unnecessary repetition. Mixed use of `Self`...
### Describe the feature ref https://github.com/ethereum/execution-apis/pull/484 this should be similar to `eth_callMany` https://github.com/paradigmxyz/reth/blob/79d505adb29a84674df6f293909fab2192af2431/crates/rpc/rpc/src/eth/api/call.rs#L81-L83 and/or `trace_callMany` https://github.com/paradigmxyz/reth/blob/79d505adb29a84674df6f293909fab2192af2431/crates/rpc/rpc/src/trace.rs#L127-L131 ### Additional context _No response_
- Skips tx root validation for filtered out transactions in bodies stage - Fixes method `FileClient::bodies_iter_mut` that could cause undefined behaviour
The RLP decoding of transactions in EngineAPI is not strict, it allows excess bytes to be appended to a transaction and still decode successfully. According to the Yellow Paper, the...
When validating if a given `ForkId` is compatible with a `ForkFilter`, the field `next` can represent a timestamp or a block, and there isn't enough distinction about which one it...
We are configuring the exclusive mode of `libmdbx` with `exclusive: args.exclusive.unwrap_or_default()`. `args.exlusive` is `Option`, so, if it is not set by an argument from the command line, `unwrap_or_default()` will set...
When configuring `libdbmx` on `DatabaseEnv::open`, the `shrink_threshold` field is set to `None`, which actually results in the default of −1 being passed through to the underlying implementation at https://github.com/paradigmxyz/reth/blob/main/crates/storage/libmdbx-rs/src/environment.rs#L643 According...
EIP-4844 transactions have a restriction that they should not allow CREATE transactions. In this PR the `to` field in `TxEip4844` is changed from `TxKind` to `Address`, so that it can't...
- Fixes help for cli args for tx fetcher. - Makes help less implementation specific.