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
{{ message }}
Repository navigation
Commit 4fc4b7b
Browse filesBrowse the repository at this point in the historyBrowse files
prover: LogUp k4 is the default on the STARK base tables
`LAMBDA_VM_ZF_LOGUP` unset now selects k4 (up to four LogUp interactions per
aux column where the arity rule admits it); `=pair` keeps the previous bytes
and is the rollback. The setting reaches the block's base tables only
(block_base_options); the LFM chips keep pairs. Measured as the opt-in:
median phase B -9.56 s (BIG 600, t -27), 1x base -0.97 s (FAST 861).
Every consumer derives the layout from the options, not from the proof: the
base AIRs pick the arity in AirWithBuses::new from options.format.logup, the
host verifier and the block verifier build those AIRs from
block_base_options, and the tree's leaf programs size each base sub-proof
(aux width, composition parts, constraint program) from the same AIRs.
Tests: the default base options build exactly the k4 programs and the pair
spelling builds the golden pair list; a pair proof is refused under the k4
layout (the reverse of N3); the production-sites test expects the base
format's arity; the pinned tree ids derive under pair, the format they were
recorded under.
0 commit comments