Via Network (prev. Viacoin)

Matter Labs recently announced that ZKsync EraVM is being retired, and its legacy execution environment is entering end-of-life Via v2 (prev known as Viacoin), running on a public testnet, is built on ZKsync Era Its successor, ZKsync OS, introduces a fundamentally different architecture A new Rust-based state-transition implementation, compiled for native execution in the sequencer & RISC-V execution for zero-knowledge proving through “Airbender” For additional context, a Code4rena security audit conducted in 2023 and published in 2024 identified 6 high-severity vulnerabilities in ZKsync Era. More recently, ZKsync's Security Council disclosed 5 preventative security upgrades in 2026 that address further vulnerabilities involving circuit soundness, cryptographic weaknesses & VM behavior. These findings reinforce the importance of maintaining a secure, up-to-date execution and proving stack. ZKsync's successor, ZKsync OS, introduces a fundamentally different architecture: a new Rust-based state-transition implementation targeting native execution and RISC-V proving through Airbender With upstream (zksync) development moving to this new architecture, Via will (or rather has to) adopt ZKsync OS This is important given the rapid advances in AI-assisted vulnerability discovery. As vulnerability discovery and exploitation become increasingly automated, maintaining an aging, increasingly unsupported execution and proving stack carries security risks I don't consider taking on that long-term responsibility a sensible option, especially for software intended to secure user funds. This is not a straightforward version upgrade. Large parts of Via's current implementation will need to be replaced or adapted, particularly where our Bitcoin settlement, data availability, and proving infrastructure interact with the execution layer This will require substantial engineering effort The goal is not only to migrate Via to ZKsync OS, but also to establish a more maintainable architecture and a sustainable process for staying in sync with upstream going forward Consider this announcement positive, as Via inherits ZKsync OS newly improved architecture

External nodes on Via were syncing Bitcoin settlement but not showing it as a result, not on the block explorer either Bugs fixed: they now report commit, proof and accepted execution per batch, with the batch's own timestamp, matching the main node

Migrated Via testnet DA to Celestia Mocha-5 this weekend. Mocha-4 is being retired Mocha-5 starts from genesis, meaning it's a fresh light node datastore

Infrastructure update: Grafana monitoring now also checks Bitcoin deposits, withdrawals, bridge coverage, and rollup progress, instead of just service health Allowing, in the future, for ai agents to monitor the chain

Infrastructure update: Unused GCP load balancers that served downloads for an already-retired external node were removed, reducing recurring cloud costs. Via still publishes database dumps and state snapshots for node bootstrap and recovery.

Over the past few days, we’ve been migrating most of our content from blog.onvia.org to our new domain, vianetwork.xyz/blog as part of our move to Webflow

500+ members so far, and counting! 🙌 🫡 Join us on Discord 👇 discord.gg/vianetwork

Merry Christmas everyone🎄 Take a moment to unplug, spend time with your people, and recharge. We’ll be back to building the future of Bitcoin tomorrow ⚒️

Let’s quickly revisit what was done most recently. Because new updates about Via Bridge are coming 🔜 👇