Commitment rules (#863)

* Simplify commitment controller * Remove last commitment l1 height table * Cleanup sequencer * Invoke commitment after each L2 block This would let commitment controller decide whether to go through with the commitment or not. * Unwrap or zero * Logging * Fix failing tests * Disable risc0 logging * Restore test logging * Update zerovec-derive to resolve security issue * Fix wait heights * Cleanup test * Rename LastSequencerCommitment table
chainwayxyz · Jul 9, 2024 · 624ff0a · 624ff0a
1 parent 97c1d36
commit 624ff0a
Show file tree

Hide file tree

Showing 9 changed files with 158 additions and 354 deletions.
diff --git a/bin/citrea/provers/risc0/guest-bitcoin/Cargo.lock b/bin/citrea/provers/risc0/guest-bitcoin/Cargo.lock
diff --git a/bin/citrea/provers/risc0/guest-mock/Cargo.lock b/bin/citrea/provers/risc0/guest-mock/Cargo.lock
diff --git a/bin/citrea/src/lib.rs b/bin/citrea/src/lib.rs
@@ -23,6 +23,7 @@ pub fn initialize_logging(level: Level) {
             "alloy_transport_http=info".to_owned(),
             // Limit output as much as possible, use WARN.
             "risc0_zkvm=warn".to_owned(),
+            "risc0_circuit_rv32im=info".to_owned(),
             "guest_execution=info".to_owned(),
             "jsonrpsee-server=info".to_owned(),
             "reqwest=info".to_owned(),