DO NOT MERGE - PROD tracking - Beta v4.0 prod branch

[amkCha]

This is the tracer branch to use for future prod releases to follow up with beta-v4.0-rc16 (the branch name has rc13 in it as legacy from 1st prod release)

VERSION beta-v4.0-rc16

• contains besu version update to 25.10.0-linea2

releaseVersion=beta-v4.0-rc16
besuVersion=25.10.0-linea2
shomeiVersion=2.4-develop
besuShomeiPluginVersion=v0.7.4

go-corset is 1.1.23 (hash 93c23f239542f79c1db60eb5b8250ab20e30f046)
constraints hash is f79e3b2f96bac51abab9add89bc1ec3571ab63ae

---

HOW TO

If there is a hotfix or a Besu version update, here is how you can proceed to release beta-v4.0-rcN

• checkout latest version of beta-v4.0-rc13-branch (check you have the latest commit)
• checkout latest version of beta-v4.0-rc13-constraint-branch (check you have the latest commit)
• apply the fix/update on tracer or constraints :
• if it's a Besu update, just change besuVersion in gradle.properties
• if edit on constraints, push thebeta-v4.0-rc13-constraint-branch branch with your new commit so it stays up-to-date on the repo
• change releaseVersion in gradle.properties to beta-v4.0-rcN
• push the tracer branch beta-v4.0-rc13-branch so it stays up-to-date on the repo
• to keep consistency between prod and our arith-dev branch : cherry-pick the commit of the fix from the beta-v4.0-rc13-branch, open a new branch from arith-dev, apply it and open a PR that you merge on arith-dev
• Make a release, link here : draft new release, create a tag beta-v4.0-rcN, choose Target branch beta-v4.0-rc13-branch, add release title as beta-v4.0-rcN, edit notes to add the changes since previous release, publish as latest
• check that the units and replays are passing on the manual-release CI (the tests are now triggered for all releases)
• run the Daily blockchain tests on branch beta-v4.0-rc13-branch, and check they are passing

---

VERSION beta-v4.0-rc14

• contains besu version update to 25.10.0-linea1

VERSION beta-v4.0-rc13

The tracer for beta-v4.0-rc13 is the same as for beta-v4.0-rc12 on top of which we've applied :

• Olivier's commits to reintegrate the columns for the prover team (from beta-v4.0-rc11-TRACER-only-columns-hotfix)

---

Note

Adds Prague execution-spec blockchain tests and expands CI, propagates prover transaction max counters in tracing, updates Besu/release versions, and aligns testing with new Besu APIs.

• CI/CD:
  • Manual release workflow: add permissions, build without tests, upload artifacts, run spotless, and store distributions; introduce unit test matrix per fork and a fast replay test job; adjust publish dependencies.
  • Reference tests: add a specialized Prague job generating and running execution-spec blockchain tests; fix artifact names/typos in reusable workflow.
• Arithmetization/Tracing:
  • RLP/TxnData (Cancun): propagate proverUserTxnNumberMax and proverRelativeUserTxnNumberMax; track per-block tx counts via BlockSnapshot; update tracing signatures accordingly.
• Tests/Build:
  • Add tasks to download execution-spec fixtures and generate/run tests; update templates to support configurable tests source path; remove general state template; expand/conditionalize ignored tests by fork.
  • Update testing code to new Besu APIs (protocol spec builders, preExecutionProcessor.process(..., Optional.empty())); adjust Engine API parentBeaconBlockRoot handling.
• Versions/Submodules:
  • Bump releaseVersion to beta-v4.0-rc17, besuVersion to 25.10.0-linea3; update linea-constraints submodule.

^{Written by Cursor Bugbot for commit 5a4b09d. This will update automatically on new commits. Configure here.}