Skip to content

Conversation

@roynalnaruto
Copy link
Collaborator

No description provided.

@roynalnaruto roynalnaruto requested a review from lispc as a code owner August 27, 2025 09:15
@@ -0,0 +1,209 @@
use alloy_primitives::{B256, keccak256};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we have almost identical code between validium.rs and v7.rs?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, almost identical (for now).

There are a few bound constraints in v7 that are not applicable for validium (like upper bound on number of bytes from witness). Also, future versions (v2) of validium could diverge massively, hence I have preferred creating a new module and types altogether.

@github-actions github-actions bot added crate-chunk-circuit Updates to the guest program chunk-circuit crate-circuits Any update made to the circuits, i.e. commitments reflect a change labels Aug 27, 2025
@github-actions github-actions bot added crate-batch-circuit Updates to the guest program batch-circuit crate-bundle-circuit Updates to the guest grogram bundle-circuit crate-integration Updates to the integration crate labels Aug 27, 2025
// blockhash is unused for scroll domain.
if version.domain == Domain::Scroll {
assert_eq!(self.prev_blockhash, B256::ZERO);
assert_eq!(self.post_blockhash, B256::ZERO);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just populate them? may be useful for future

domain: Domain::Validium,
stf_version: STFVersion::V1,
fork: ForkName::Feynman,
codec: Codec::V9,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this Codec::V9 enum is something fully inner. We don't put a '0x9' byte at the beginning of DA? (instead we use 65?)

// Conditionally decode depending on the flag set in the envelope.
let payload_bytes = if envelope.is_encoded & 1 == 1 {
vm_zstd::process(&envelope.unpadded_bytes)
.expect("zstd decode should succeed")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

haha we should rename this crate later vm_zstd::process to like rust_zstd_decompressor

@lispc
Copy link
Collaborator

lispc commented Aug 27, 2025

the framework seems good. though some details i may revisit later.

@roynalnaruto roynalnaruto merged commit df6c966 into feat/validium Sep 3, 2025
4 checks passed
lispc added a commit that referenced this pull request Oct 29, 2025
* cargo check

* fix

* fix

* x

* exchange code

* fix rebase

* fmt

* actually Infallible

* fmt

* add validium

* mark todo

* add test data

* add test

* upgrade

* update openvm guest

* fmt & check

* update batch program

* build

* build

* fix: remove tiny-keccak (#168)

* fix merge

* fix build

* remove generic as no need for rkyv

* fmt

* make ecies openvm irrelevant

* add makefile

* fix download-release.sh

* proving 0.5.2

* fix tx data len

* feat: update sbv bincode (#169)

* update ref

* revert chunk_exe_commit.rs

* rewrite vk in testing

* sync

* add script

* add script

* cleanup

* clean much old codes

* lint

* clippy

* update sbv

* 0.6.0

* docker ignore

* build

* add exe_commit.rs

* update

* validium batch-bundle (#175)

* preliminary work

* chore: clippy fix

* update versioned public inputs

* fix: compilation for crate/integration

* fix: further changes to support integration tests

* fix: dir name for validium

* test: with euclid-v2 for older testdata

* commitment

* fix: update due to upstream

---------

Co-authored-by: Zhuo Zhang <mycinbrin@gmail.com>

* clean

* unify openvm to v1.4.0

* add old feynman witness structs

* fix gpu

* fix

* move blob_consistency/types.rs

* fix

* minor improvements

* clean

* fmt

* better logging

* commits

* add feature=host for types crate

* fix merge

* sanity check for blob

* test: more data (feynman) for validium

* fix: path to witnesses

* feat: update public for validium

* make ValidiumInputs public

* chore: export version module

* chore: serde for version types

* chore: commitments

* release: update release name to validium

* fix: script syntax ?

* chore: restore changes

* fix building scripts

* swtich back to non-force mode in gen verifier.bin

* it is 1.3.. a bit tricky.. will explain later.

* update guest commits

* [Fix] Issues for validium mode (#194)

* fix issues in e2e test with coordinator

* add debug fields

* update commits

* Soundness issues in Validium (#196)

* fix: soundness issues in validium mode

* chore: rename method validium pi_hash

* chore: rename another pi_hash validium

* update commit

---------

Co-authored-by: Zhuo Zhang <mycinbrin@gmail.com>
Co-authored-by: Rohit Narurkar <rohit.narurkar@proton.me>

* update sbv and reth

* Merge remote-tracking branch 'origin/master' into feat/validium

* release.sh be compatible with sh

* resume features removed by mistake
allow chunk can be built in host

* fix soundness issue
update commit

* fix batch gen. in integration

* hack some test stuff to fit the integration tests

---------

Co-authored-by: Zhang Zhuo <mycinbrin@gmail.com>
Co-authored-by: Rohit Narurkar <rohit.narurkar@proton.me>
Co-authored-by: Velaciela <git.rover@outlook.com>
Co-authored-by: Ho <fan@scroll.io>
Co-authored-by: Ho <noelwei@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

crate-batch-circuit Updates to the guest program batch-circuit crate-bundle-circuit Updates to the guest grogram bundle-circuit crate-chunk-circuit Updates to the guest program chunk-circuit crate-circuits Any update made to the circuits, i.e. commitments reflect a change crate-integration Updates to the integration crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants