build(deps): bump @ethereumjs/rlp from 5.0.1 to 10.1.3

[dependabot]

Bumps @ethereumjs/rlp from 5.0.1 to 10.1.3.

Release notes

Sourced from @​ethereumjs/rlp's releases.

@​ethereumjs/rlp v10.1.3

Release round overview

Welcome to 10.1.3 — a coordinated release across all active @ethereumjs/* libraries on the 10.1.x line. If you have been experimenting with the upcoming Amsterdam hardfork, this is our close-to-ready preview: the full 14-EIP Hardfork.Amsterdam bundle is implemented and aligned with tests-glamsterdam-devnet@v8.1.0 and glamsterdam-devnet-8. Public APIs and spec alignment are largely stable — a good time to try BAL builder/validator flows, two-dimensional block gas, builder requests, and the rest of the Amsterdam surface — but Amsterdam remains experimental and must not be used in production; spec or API shifts can still happen in later 10.1.x patches.

The sections below cover this package only; for the full EIP list, examples, and release ↔ spec tracking, see the @​ethereumjs/vm Amsterdam overview. On Osaka or earlier hardforks? Nothing changes unless you explicitly select Hardfork.Amsterdam.

@ethereumjs/rlp

@ethereumjs/rlp is the monorepo's canonical RLP encoder/decoder. Within the 10.1.3 round this package bumps in version only — no public API changes. BAL and block RLP extensions continue to live in @ethereumjs/util and @ethereumjs/block.

At a glance

• Maintenance release, version sync for @ethereumjs/* 10.1.3.

Amsterdam (experimental)

Amsterdam fork work lives in @​ethereumjs/vm and related packages. RLP continues to provide generic encode/decode primitives unchanged.

@​ethereumjs/rlp v10.1.2

Release round overview

Welcome to 10.1.2 — a coordinated release across all active @ethereumjs/* libraries on the 10.1.x line. If you have been following the upcoming Amsterdam hardfork, this is our first experimental preview ready to try out: a largely complete nine-EIP Hardfork.Amsterdam bundle, 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.x releases 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 select Hardfork.Amsterdam.

@ethereumjs/rlp

@ethereumjs/rlp is the monorepo's canonical RLP encoder/decoder — a dependency of nearly every other package and often used directly when serializing trie nodes, block bodies, or devp2p payloads. Within the 10.1.2 round this package fixes a decoding edge case in hexToBytes and bumps in version with the rest of the monorepo. There are no Amsterdam-specific API changes here; BAL and block RLP extensions are handled in @ethereumjs/util and @ethereumjs/block.

At a glance

• Fix hexToBytes edge case in RLP decoding paths, see PR #4276.
• Monorepo version sync for @ethereumjs/* 10.1.2.

Amsterdam (experimental)

Amsterdam fork work lives in @​ethereumjs/vm and related packages. RLP continues to provide generic encode/decode primitives unchanged.

@​ethereumjs/rlp v10.1.1

• Deprecate Node.js 18 support, minimum Node.js version is now 20, see PR #4180
• Add Node.js 24 support, see PR #4194

@​ethereumjs/rlp v10.1.0

Maintenance release, no active changes.

@​ethereumjs/rlp v10.0.0

Overview

This release is part of the v10 breaking release round making the EthereumJS libraries compatible with the Pectra hardfork going live on Ethereum mainnet on May 7 2025. Beside the hardfork update these releases mark a milestone in our release history since they - for the first time ever - bring the full Ethereum protocol stack - including the EVM - to the browser without any restrictions anymore, coming along with other substantial updates regarding library security and functionality.

... (truncated)

Commits

• 29f404f Release v10.1.3 — close-to-ready Amsterdam preview (glamsterdam-devnet v8.1.0...
• ff3354c DEVELOPER.md Rework / Better AI Release Instructions (#4375)
• ec47d61 Api Docs + Main README Overhaul (#4374)
• 513028f Amsterdam Examples + API Additions/Enhancements (#4372)
• f4a6a6d Examples / Code Conventions (#4371)
• 8b3f292 Test Coverage (#4370)
• c4f93a3 Security Stuff (#4369)
• f3a7f5e BAL ordering fix (#4368)
• e9263e1 fix(util): incorrect storage key ordering (#4341)
• c3d0a7e fix(evm): snapshot step event memory (#4354)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: M-dependabot. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.