fix(deps): update dependency @ethereumjs/tx to v10.1.2#1020
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.
This PR contains the following updates:
10.1.1→10.1.2Release Notes
ethereumjs/ethereumjs-monorepo (@ethereumjs/tx)
v10.1.2: @ethereumjs/tx v10.1.2Compare Source
Release round overview
Welcome to
10.1.2— a coordinated release across all active@ethereumjs/*libraries on the10.1.xline. If you have been following the upcoming Amsterdam hardfork, this is our first experimental preview ready to try out: a largely complete nine-EIPHardfork.Amsterdambundle, currently aligned with tests-bal@v7.1.0 and BAL devnet-7.Amsterdam is still in flux — please do not use this in production yet — and we expect further
10.1.xreleases as the spec and official tests evolve. The sections below cover this package only; for the full fork picture (EIP list, examples, release ↔ spec tracking), see the @ethereumjs/vm Amsterdam overview. On Osaka or earlier hardforks? Nothing changes unless you explicitly selectHardfork.Amsterdam.@ethereumjs/tx@ethereumjs/txdefines typed transactions, intrinsic gas calculation, and pre-execution validation — the layer that decides whether a transaction is well-formed and what minimum gas it must carry before the VM ever runs it. Within the10.1.2round, Amsterdam adds two floor-pricing EIPs that tighten those minimums and feed directly into EIP-8037 regular-gas accounting downstream.If you construct or validate transactions for Amsterdam testnets or EST fixtures, these floors are usually why a seemingly small tx suddenly needs a higher
gasLimitor a non-zerobaseFeePerGason the containing block.At a glance
(20 × addresses + 32 × keys) × 4 tokens per byte.getValidationErrors()and intrinsic gas helpers whenHardfork.Amsterdamis active.Amsterdam (experimental)
The calldata floor means
txRegularGasin the VM becomes (conceptually)max(raw_regular_gas, calldata_floor)under EIP-8037. When writing tests, setbaseFeePerGas: 1non the block header and ensuregasPrice/maxFeePerGason the tx is high enough to satisfy EIP-1559 checks alongside the new floors:See the Amsterdam transaction validation section for the full token arithmetic and interaction with EIP-8037.
Changes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.