Skip to content

docs(prover): allow 6->2 step-marker transition on the continuation path #883

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MauroToscano wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(prover): allow 6->2 step-marker transition on the continuation path #883

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions prover/src/tests/recursion_smoke_test.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -827,6 +827,13 @@ fn test_recursion_execute_1query() {
/// the `3,4,5,6` cycle (one per table). A transition outside
/// `{1->2, 2->3, 3->4, 4->5, 5->6, 6->3}` means the marker convention broke —
/// wrong immediate decoded, or a stale/mismatched build.
///
/// That transition set is the monolithic path's. The continuation guest
/// (`continuation` feature) re-emits `STEP_AIRS_AND_BUS_BALANCE_DONE` before
/// each epoch's `multi_verify_views` (`continuation::verify_epoch`) and once
/// more before the global-memory verify (`continuation::verify_global`), so
/// there `6->2` is also a valid transition. This test runs the monolithic
/// guest, where those markers never fire.
#[test]
#[ignore = "slow: runs the in-VM STARK verifier (minutes on CI)"]
fn test_recursion_step_markers_observed_in_order() {
Expand Down
Loading