feat: runtime multi version

[lispc]

No description provided.

[lispc]

seems we have too many xx_commitments.rs.. is there an easy way to unify them or we do this in later refactor?

[roynalnaruto]

We can have a single commitments.rs that defines multiple modules:

mod chunk {
    pub const EXE_COMMIT /* */
}
mod batch {
    pub const EXE_COMMIT /* */
}
/* */

[lispc]

We can have a single commitments.rs that defines multiple modules:

mod chunk {
    pub const EXE_COMMIT /* */
}
mod batch {
    pub const EXE_COMMIT /* */
}
/* */

nonono, batch program verifies chunk commitment, so they are dependent. Cannot be in same crate i think.

[roynalnaruto]

@lispc

Cannot be in same crate i think.

I meant for prover and verifier crates

[noel2004]

feat/phase2-stable has been merged

[noel2004]

e2e tests passed

[noel2004]

We can have a single commitments.rs that defines multiple modules:

mod chunk {
    pub const EXE_COMMIT /* */
}
mod batch {
    pub const EXE_COMMIT /* */
}
/* */

nonono, batch program verifies chunk commitment, so they are dependent. Cannot be in same crate i think.

So we need to update files in at least 3 separated crates. If the bundle / batch / chunk dep for circuits/types has been separated we can:

• put commitment of chunk in circuits/types/batch
• put commitment of batch in circuits/types/bundle
• comitment of bundle is not needed by circuits and can be updated in prover (or verifier) crate

[lispc]

one final idea is, "legacy" is not a good word. We will have v8 v9 ... in future.

V6 is much more clear.

See https://github.com/scroll-tech/scroll-contracts/blob/1a44cc4cd5bb29067051f59c09dd4407511f1a3a/src/L1/rollup/ScrollChain.sol#L397
we either use "v6" "v7" or "euclidV1" "euclidV2"