Conversation
chore: update emulator submodule, link omp chore: update step submodule and rename fields chore: update bindings, fix tests chore: update CHECKPOINT_ADDRESS
- debian 12 (bookworm) -> 13 (trixie) - boost 1.81 -> 1.83
- This commit bumps Foundry on the CI and Dockefile. This is to align with the version of Foundry used on rollups-contracts, so that the node team can also bump Foundry (given that it uses the devnet image built in the dave repo still).
- Honeypot 3.0.1 fixes a bug in the rootfs Dockerfile that would lead to its build to fail. The resulting image is the same as 3.0.0 but we can now build the custom Honeypot rootfs image with devnet config.
- This commit alters the database schema to include the final state of the machine on the settlement_info table. This is a breaking change which will require nodes to run from a brand-new database.
The rollups node becomes a single crate: worker modules synchronize through the storage module (the only SQL surface), and one spec-oracled engine (src/engine: structure, stf, ruler, and the dispute facade) serves both the runner's forward schedule and the dispute path's random access. - One leaf semantics: process_input and the second geometry implementation are gone. The runner schedules the engine's collect() per input window; the window-root quartet row is the only durable level-0 artifact; settlement and dispute serving read the same rows (frontier fold, strict and prefix-bounded). - The boundary store (stage+rename, write-once cells, clone-based revert) carries both regimes' revert insurance; corruption tripwires panic through the loud process exit, never retry. - Revert on RX_REJECTED only, matching AdvanceStatus.sol - the chain never reverts an exception. - The staged settlement protocol: the epoch manager drives sentry claim, stage, and accept per tick, each step guarded and idempotent; a sentry always claims the locally computed post-epoch hash, never the staged value. settlement_info carries final_state, captured from the boundary store at roll (the new epoch's initial boundary IS the post-epoch state). - Absorbs prt/client-rs (the tournament reader/sender/gc and the hero's react loop, traced against the contracts - the audit ledger records verdicts and clean checks) and common-rs (merkle, arithmetic, and kms become node modules; the node was their only consumer). - Chain recordings - raw devnet log ranges captured after e2e disputes settle - are committed fixtures for the tournament fold, decoded through the production bindings. Replaces the epoch-manager/state-manager/blockchain-reader/ prt-node crates, prt/client-rs, and common-rs.
Move durable invariants into living documentation, retain only active review aids, include the devnet fingerprint in release archives, and remove stale tooling references.
Move the leaf-seal counter with the event counters, confine raw slot reads to white-box test probes, and document deployment-generation compatibility.
State transaction priority as a same-tick property, explain the intentional empty lane during join finality gaps, and document successful log completeness as part of the configured RPC trust boundary. Align the Solid cursor and child-validation wording with the implementation.
Expose the trusted factory parameter table without repeating total depth in tournament clones. Validate the compiled root stride and machine span before the node opens its database, and report factory deployment fingerprints.
Make the root justfile authoritative for the CI and doctor Foundry version, and have the setup action query that pin after installing Just.
Upgrade the emulator and Solidity step together, derive geometry from the release, compose the state transition directly, and keep source preparation network-free. Pin the compatible Honeypot fixture and retain the computation-hash and proof-format conformance gates so this revision stands alone.
Preserve the exact measured candidate and its release-pinned evidence while describing that provenance independently of later rebases or squashes.
Exercise real terminal states and coordinate boundaries, then mutate the composed data-availability, CMIO, ustep, and reset witness seams against Solidity.
Keep Justfiles as the public task graph while scripts own diagnostics, worktree lifecycle, bootstrap, gas measurement, E2E preflight, and generated binding inputs. Use scoped doctors and semantic binding stamps so expensive ignored artifacts are rebuilt only when their real producer inputs change.
Benchmark warmed stress-ng workloads, isolate each machine-image producer, and verify receipts and corpus roles with focused regression scripts. Keep pull-request CI focused, release publication gated, and the full E2E battery manually dispatched until its cost and signal justify scheduling.
GCdePaula
marked this pull request as ready for review
August 21, 2026 17:01
guidanoli
approved these changes
Aug 21, 2026
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
4 participants
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.
No description provided.