Development

We've moved Via's Bitcoin stack from a one-time "genesis import" to a live governance-driven state. System wallets (sequencer, verifiers, bridge, governance) are no longer hardcoded facts learned at startup. They're tracked as state, validated against on-chain inscriptions, and updated atomically at runtime.

Another major infrastructure upgrade to the Via L2 network. Due to this new upgrade, every part in the network, including sequencer addresses, verifier keys, bridge controllers, and governance wallets, is tied to governance-approved Bitcoin transactions, creating an immutable, queryable history of who had authority at any point in time. The

Major upgrade to Via L2 zkEVM Rollup bringing governed runtime updates and Taproot-powered resilience into production. * Governed wallet updates, applied live via Bitcoin events. * Database-backed, insert-only audit log with efficient “latest-by-role” reads. * Taproot + MuSig2 Bridge: private key-path spends, script-path fallback for recovery. * Zero downtime for rotations, upgrades, or incident response.

We've rolled out yet another major upgrade to the Via Verifier Network, which makes chain progression more reliable under load while reducing network overhead by half during batch ingestion. The upgrade also strengthens chain integrity and closes a subtle TOCTOU window, which makes head selection deterministic. TL;DR

We've rolled out an upgrade patch for deterministic finality, lower memory, and faster verification for the Via Verifier Network. As we fixed a subtle consensus edge case in our verifier network: duplicate canonical batches We've introduced partial unique indexes in PostgreSQL to enforce a key rule

We’ve upgraded Via’s verifier selection logic to eliminate race-condition forks and drastically improve performance. Part of Patch 221 hardens canonical chain selection by replacing correlated SQL subqueries with a CTE that finds the canonical chain tip in O(log n) time (instead of O(n²)) and prevents forks