Upcoming Vana Network Upgrade: Vega Part I

Activation block: 10,229,958

Estimated: Monday, 21 September 2026 at approximately 12:29 UTC

Network: Vana mainnet (chain ID 1480)

Hello Vana Operators,

Vana is completing the security hardening we previously communicated following the July 31 incident. In the same maintenance window, we will also deploy Vega Part I, the network upgrade published in our January roadmap (vana2026roadmap.org). Deploying both updates together allows us to complete the work with a single period of network downtime rather than two separate maintenance windows. There are no changes to token supply or emissions.

The upgrade activates at block 10,229,958, estimated for Monday, 21 September 2026 at approximately 12:29 UTC. The block height is what triggers the upgrade; the date is an estimate based on the current 6-second block time.

What’s changing for your node

Prysm v7 support. The mainnet chain config gains four settings that Prysm v7 requires. Without them a v7 node either refuses to start or — worse — starts and follows the chain by range sync while participating in no gossip at all.
Vana beacon node build. The beacon node moves to Vana’s build of Prysm, v7.1.8-vega.1.
Security hardening. The deposit contract is migrated to a new address as part of ongoing security work.

Schedule

When	What happens
Now → 21 Sep
Recommendation: update the node by Sep 15-16 in order to leave buffer for any assistance from the Vana team.	Upgrade your node. Pull the updated configuration and image and restart. Nodes can be upgraded at any point in this window — there is no coordinated restart.
Block 10,229,958	Activation. Upgraded nodes switch automatically. No operator action at the block itself.
After activation	Nodes still on the old client will fall out of sync and stop serving correct data. Upgrade before the block.

What You Need to Do

Everything required ships in the vana repository. For a standard Docker Compose deployment, this is a one-variable change and a beacon restart.

1. Update the repository

This brings in the new chain configuration and the updated docker-compose.yml.

# from your vana directory
git pull origin main