Applying vault acts in order on a concurrent verifier
In ycashd, a block is connected while holding one lock, and the vault acts inside it are applied one after another to a single overlay of state. Zakura is built differently: the transactions in a block are verified concurrently, each on its own, and only afterwards does the block reach contextual validation, where it's checked against the chain it extends.
Why order matters
A vault act can depend on an earlier act in the same block: a signer set changes its members, then a vault under that set is released. Checked in parallel, the second act would see the wrong set. The rules also include per-block rate limits and liveness counters, which only mean something when acts are counted in order.
What Kogany does
- Scripts stay parallel. Signature checks, including the post-quantum ones, still run concurrently. They read a snapshot of the parent block's vault state, fetched once per block and shared by every script, which the verifier waits for the same way Zakura already waits for other block information.
- Acts run in sequence in contextual validation, applying a vault delta to the non-finalized state in transaction order. A block that breaks a vault rule is rejected there with ban score 100.
- The snapshot follows forks. It is keyed by the parent block's hash, not its height, so a reorganization never feeds one chain's state into another.
- Every commit path computes deltas, including checkpointed blocks, and no checkpoint list reaches the vault epoch.
- The mempool checks too. The harness found that Kogany's mempool admitted a vault transaction ycashd refuses, because the vault rules ran only in block validation. The mempool now runs them over the tip's snapshot as well.
Where it stands
This work merged in wave W4 on 2026-11-02 and ships in koganyd v1.8.0-ycash.beta2. The mixed vault scripts (vault_primitive, vault_slashing, vault_dos, vault_undo_prune, vault_pq_reorg) pass with the vault state hash equal to ycash6's at every sync point.
The cost
Waiting for the parent snapshot serializes part of the work on blocks after Vault activates. W4 merged without measuring how much, and beta2 has no measurement either, so the cost is still open.
