-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
Add CI check that reth-primitives
compiles to RISC-V
#8176
Comments
This would be super useful for us at Sovereign Labs! Note that all of the platforms referenced in the original issue require a 32-bit RISC-V architecture. Our preferred target for the check is the official riscv32im-risc0-zkvm, which captures the constraints of zk execution environments (i.e. limited |
This issue is stale because it has been open for 21 days with no activity. |
This issue is stale because it has been open for 21 days with no activity. |
This issue was closed because it has been inactive for 7 days since being marked as stale. |
Describe the feature
RISC-V is an important target for zkVMs, such as SP1, Risc0, JOLT and others, which prove the execution of RISC-V bytecode in a zero-knowledge proof.
reth-primitives
is an important crate that is meant to be minimal in dependencies and should be compilable to the RISC-V target for use in all zkVMs.While PRs in the past have been merged in to ensure that
reth-primitives
can compile to RISC-V, without a CI check to ensure this compilation is possible, networking dependencies (or other incompatible dependencies) sneak into thereth-primitives
crate.It would be great to add a CI check to ensure this crate (and others that can be added in the future) with appropriate features enabled can be compiled to RISC-V.
h/t to @preston-evans98 for suggesting this issue.
Additional context
No response
The text was updated successfully, but these errors were encountered: