We’re thrilled to announce that Velocore V2 has successfully launched on Linea, and we are now fully ready for our V2 migration on zkSyncEra. With the introduction of real-time voting without epochs, a unique AMM using the token vault system, and a vote-escrow system without any lock-ups, we’re proud to say that Velocore V2 has truly pioneered a new horizon in the veDEX landscape. For our dedicated Velcrew members on zkSyncEra who’ve been eagerly awaiting Velocore V2, the migration process is about to start!
This article will provide a comprehensive guide on the migration schedule, methodology, and detailed steps to ensure a seamless transition from V1 to V2.
Why the Need for Migration?
As we launched the first zkEVM ve(3,3) DEX and continued to operate after launch, we felt a strong desire to overhaul and innovate every aspect of V1, from its AMM structure and voting system to its UI/UX. This led us to the realization that a fresh, independent codebase for Velocore V2 was essential. This meant a natural upgrade from V1 was impossible, necessitating a migration to V2. Hence, we first launched V2 on Linea, excluding the V1 to V2 migration process.