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
It is useful to use op-succinct to generate proofs, but in certain circumstances it isn't required that those proofs are written to the L1. Specifically, during testing it would be great to just be able to run op-succinct in a a mode where we can generate the proofs locally and verify them from the database.
Feature
Add a new flag --skip-l1-proposal (though the name is up to you), which simply skips the L1 transaction step, and instead emits a INFO-level log and still writes the resulting proof information to the database.
The text was updated successfully, but these errors were encountered:
crStiv
added a commit
to crStiv/op-succinct
that referenced
this issue
Dec 17, 2024
- Added SKIP_L1_PROPOSAL environment variable with default value false
- When SKIP_L1_PROPOSAL=true, sets OP_SUCCINCT_SKIP_L1=true
- Added logging when L1 transactions are skipped
Closessuccinctlabs#258
Description
It is useful to use op-succinct to generate proofs, but in certain circumstances it isn't required that those proofs are written to the L1. Specifically, during testing it would be great to just be able to run op-succinct in a a mode where we can generate the proofs locally and verify them from the database.
Feature
Add a new flag
--skip-l1-proposal
(though the name is up to you), which simply skips the L1 transaction step, and instead emits a INFO-level log and still writes the resulting proof information to the database.The text was updated successfully, but these errors were encountered: