You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want celestia-recursive-sync to upgrade along with SP1 updates, so it can benefit from performance improvements. However, SP1 updates break the recursion capability: you cannot verify an old SP1 stark proof inside of a new SP1 stark proof.
On this line, celestia-recursive-sync performs recursive verification of the previous SP1 STARK.
The fix for verifying an old version in a new version is to use groth16 as an intermediate step when we need to perform recursion of heterogenous versions of SP1.
Create logic in the program to accept a groth16, use this SP1 verifier Rust crate, and patch it with the SP1 bn254 precompile.
Start the migration by verifying this proof in the newest version of SP1, and continue the constant computing of recursive consensus proofs
The text was updated successfully, but these errors were encountered:
We want celestia-recursive-sync to upgrade along with SP1 updates, so it can benefit from performance improvements. However, SP1 updates break the recursion capability: you cannot verify an old SP1 stark proof inside of a new SP1 stark proof.
On this line, celestia-recursive-sync performs recursive verification of the previous SP1 STARK.
The fix for verifying an old version in a new version is to use groth16 as an intermediate step when we need to perform recursion of heterogenous versions of SP1.
Create logic in the program to accept a groth16, use this SP1 verifier Rust crate, and patch it with the SP1 bn254 precompile.
Start the migration by verifying this proof in the newest version of SP1, and continue the constant computing of recursive consensus proofs
The text was updated successfully, but these errors were encountered: