Repository navigation
chore: bump deps - #22
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
eth_sendRawTransactionpanicked on malformed input from Basic (JWT) users. It now decodes exact EIP-2718 bytes and returns-32602 invalid params.reth-rpc-api(unused) andreth-primitives(one call, replaced by alloy). Onlyscroll-alloy-rpc-typesstill comes from the reth fork.alloydefault features. This removesalloy-contract,alloy-providerandreqwest.jsonwebtokento 10.4 (rust_cryptobackend) and runcargo update.hickoryadvisories and stops buildingalloy-dyn-abi(RUSTSEC-2025-0073) andzstd.#![expect(clippy::double_must_use)]in the modules that use#[rpc]. jsonrpsee 0.26.1 still triggers this lint on Rust 1.99.Behavior change
Raw transaction bytes must be exactly one EIP-2718 transaction. The proxy rejects the p2p network format and trailing bytes. Now the checked transaction is always the forwarded one.
Testing
-D warnings) and tests pass with--locked.Known remaining
cargo auditstill listszstdandalloy-dyn-abi. Both are optional lock entries that are not compiled. Still open:crypto-bigint(needs alloy 2.x) andrsa(no fix; JWT uses HMAC only).