chore(cli,sdk): bump ethrex version to v20.0.0 - #242
Merged
Conversation
ilitteri
force-pushed
the
bump-ethrex-v19.0.0
branch
from
July 15, 2026 17:20
64bb87a to
932db3c
Compare
ilitteri
force-pushed
the
bump-ethrex-v20.0.0
branch
from
July 15, 2026 17:20
380cbdb to
d19c22a
Compare
ManuelBilbao
approved these changes
Jul 15, 2026
ilitteri
added a commit
that referenced
this pull request
Jul 15, 2026
**Motivation** rex releases must stay paired with ethrex releases. This bumps rex to v19.0.0, paired with ethrex v19.0.0 (part of the v17→v21 catch-up). > Stacked ahead of #242 (v20). **Description** - Bump the 7 ethrex crates.io dependencies from `18.0.0` to `19.0.0` (and regenerate `Cargo.lock`). - Bump the ethrex binary used by the CI integration tests to v19.0.0. - Bump the workspace version to 19.0.0 for the upcoming v19.0.0 release. - No breaking changes affect rex's API surface (verified: `cargo check --workspace`, tests, clippy, and fmt all pass against ethrex 19.0.0); no code changes needed.
Signed-off-by: Ivan Litteri <67517699+ilitteri@users.noreply.github.com>
ilitteri
enabled auto-merge (squash)
July 15, 2026 17:41
ilitteri
added a commit
that referenced
this pull request
Jul 15, 2026
#244) **Motivation** rex v21.0.0 pairs with ethrex v21.0.0 — the first release that ships the EIP-8141 `FrameTransaction` type. The current `frame` command hand-rolls its own frame structs + RLP in a stale wire format: it still *compiles* against ethrex 21 (it only borrows a few primitive types), but every transaction it builds is rejected on-chain — a silent failure. v21 must fix this or it ships a broken `frame` command. **Description** 1. **Bump** the 7 ethrex crates.io deps + workspace version to `21.0.0`, and the CI integration ethrex binary to v21.0.0. 2. **Rewrite** `cli/src/commands/frame.rs` onto ethrex's canonical `FrameTransaction` / `Frame` / `FrameSignature` types (EIP-8141 only — single scalar nonce; no keyed nonces / recent-root-references): - Top-level `signatures: Vec<FrameSignature>`; VERIFY frame data empty (was: signature stuffed into VERIFY frame data). - 6-field frames `{mode, flags, target, gas_limit, value, data}`; SENDER frames carry value/data directly (was: 5-field, RLP call-list in data). - secp256k1 signatures reordered `r‖s‖v` → `v‖r‖s` (v = recovery_id + 27). - Sign `compute_sig_hash()` with empty-bytes signature placeholders, then fill the real bytes. - Emit the raw `0x06` tx via `Transaction::FrameTransaction(tx).encode_canonical_to_vec()`. - `Send`/`Build` preserved; `Receipt` → `Inspect` (alias `receipt`) with a decoded frame-by-frame viewer. Added `frame` to the README command list. Verified locally against ethrex 21.0.0: `cargo check --workspace`, `cargo clippy`, `cargo fmt --check` clean; 6 frame unit tests pass (incl. the `sig_hash` empty-msg-elision and `v‖r‖s` ordering invariants). >⚠️ **Draft — do not merge yet.** Stacked after #242 (v20). Once v20 merges I'll rebase this onto `main` (version delta becomes 20→21) and mark it ready for review.
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.
Motivation
rex releases must stay paired with ethrex releases. This bumps rex to v20.0.0, paired with ethrex v20.0.0 (part of the v17→v21 catch-up).
Description
19.0.0to20.0.0(and regenerateCargo.lock).cargo check --workspace, tests, clippy, and fmt all pass against ethrex 20.0.0); no code changes needed.