2022-05-04 20:57:07 +02:00
|
|
|
#![allow(incomplete_features)]
|
2022-06-07 14:20:51 -07:00
|
|
|
#![allow(clippy::needless_range_loop)]
|
2022-05-04 20:57:07 +02:00
|
|
|
#![allow(clippy::too_many_arguments)]
|
|
|
|
|
#![allow(clippy::type_complexity)]
|
2022-12-02 17:06:30 -08:00
|
|
|
#![allow(clippy::field_reassign_with_default)]
|
2022-11-22 08:48:48 -05:00
|
|
|
#![allow(clippy::upper_case_acronyms)]
|
2022-09-01 09:32:18 -07:00
|
|
|
#![feature(let_chains)]
|
2022-05-04 20:57:07 +02:00
|
|
|
#![feature(generic_const_exprs)]
|
|
|
|
|
|
2022-05-18 09:22:58 +02:00
|
|
|
pub mod all_stark;
|
2022-06-29 11:56:48 +10:00
|
|
|
pub mod arithmetic;
|
2023-01-21 14:17:01 +07:00
|
|
|
pub mod bn254_pairing;
|
2022-05-04 20:57:07 +02:00
|
|
|
pub mod config;
|
|
|
|
|
pub mod constraint_consumer;
|
2022-05-18 09:22:58 +02:00
|
|
|
pub mod cpu;
|
2022-05-06 17:36:32 +02:00
|
|
|
pub mod cross_table_lookup;
|
2023-03-20 11:55:43 -07:00
|
|
|
pub mod extension_tower;
|
Shrink STARK proofs to a constant degree
The goal here is to end up with a single "root" circuit representing any EVM proof. I.e. it must verify each STARK, but be general enough to work with any combination of STARK sizes (within some range of sizes that we chose to support). This root circuit can then be plugged into our aggregation circuit.
In particular, for each STARK, and for each initial `degree_bits` (within a range that we choose to support), this adds a "shrinking chain" of circuits. Such a chain shrinks a STARK proof from that initial `degree_bits` down to a constant, `THRESHOLD_DEGREE_BITS`.
The root circuit then combines these shrunk-to-constant proofs for each table. It's similar to `RecursiveAllProof::verify_circuit`; I adapted the code from there and I think we can remove it after. The main difference is that now instead of having one verification key per STARK, we have several possible VKs, one per initial `degree_bits`. We bake the list of possible VKs into the root circuit, and have the prover indicate the index of the VK they're actually using.
This also partially removes the default feature of CTLs. So far we've used filters instead of defaults. Until now it was easy to keep supporting defaults just in case, but here maintaining support would require some more work. E.g. we couldn't use `exp_u64` any more, since the size delta is now dynamic, it can't be hardcoded. If there are no concerns, I'll fully remove the feature after.
2022-12-27 18:15:18 -08:00
|
|
|
pub mod fixed_recursive_verifier;
|
2022-06-15 09:33:52 -07:00
|
|
|
pub mod generation;
|
2022-05-04 20:57:07 +02:00
|
|
|
mod get_challenges;
|
2022-05-18 09:22:58 +02:00
|
|
|
pub mod keccak;
|
2022-08-29 18:10:51 -07:00
|
|
|
pub mod keccak_sponge;
|
2022-06-13 10:34:33 -07:00
|
|
|
pub mod logic;
|
2022-06-21 14:35:19 -07:00
|
|
|
pub mod lookup;
|
2022-06-13 14:37:29 -07:00
|
|
|
pub mod memory;
|
2022-05-04 20:57:07 +02:00
|
|
|
pub mod permutation;
|
|
|
|
|
pub mod proof;
|
|
|
|
|
pub mod prover;
|
|
|
|
|
pub mod recursive_verifier;
|
|
|
|
|
pub mod stark;
|
|
|
|
|
pub mod stark_testing;
|
|
|
|
|
pub mod util;
|
|
|
|
|
pub mod vanishing_poly;
|
|
|
|
|
pub mod vars;
|
|
|
|
|
pub mod verifier;
|
2022-11-28 13:19:40 -08:00
|
|
|
pub mod witness;
|
2022-12-04 10:15:28 -08:00
|
|
|
|
2023-03-27 17:30:11 -06:00
|
|
|
use eth_trie_utils::partial_trie::HashedPartialTrie;
|
2022-12-04 10:15:28 -08:00
|
|
|
// Set up Jemalloc
|
|
|
|
|
#[cfg(not(target_env = "msvc"))]
|
|
|
|
|
use jemallocator::Jemalloc;
|
|
|
|
|
|
|
|
|
|
#[cfg(not(target_env = "msvc"))]
|
|
|
|
|
#[global_allocator]
|
|
|
|
|
static GLOBAL: Jemalloc = Jemalloc;
|
2023-03-27 17:30:11 -06:00
|
|
|
|
2023-03-28 14:38:58 -06:00
|
|
|
pub type Node = eth_trie_utils::partial_trie::Node<HashedPartialTrie>;
|