Neo has just pushed out a new update for its test network, version 0.4.1. It’s not a flashy, headline-grabbing release, but it does include some meaningful changes. Perhaps most importantly, it features a fully audited version of that zero-knowledge protocol they’ve been talking about—the one that powers their so-called Anti-MEV system.
If you’re not deep into the crypto space, MEV might sound like jargon. But it’s a real issue. Basically, it’s when the people who produce blocks can sneakily manipulate the order of transactions to make a profit at the expense of regular users. A common trick is called a sandwich attack, where a victim’s trade gets squeezed between two others. This new system from Neo is designed to put a stop to that, or at least make it a whole lot harder.
What’s New in This Version
The update brings the results of a recent multi-party computation ceremony into verifier contracts. I think the goal here is to make things more consistent for everyone running a validator node. They’ve also gone ahead and updated the cryptographic precompiles for the BLS12–381 curve to follow the Prague specification. It’s a technical change, sure, but an important one for keeping everything current.
On top of that, the team has restored access to some of the older Anti-MEV keystores. They’ve also integrated the newly audited ZK-DKG version 0.3.0 and refreshed the system contract that handles all those key management operations using zero-knowledge proofs. It feels like a lot of behind-the-scenes housekeeping, getting everything in order for what’s next.
Squashing a Few Bugs
No update is complete without its share of fixes, and this one has a few key ones. They’ve resolved an error that could cause the system to crash while trying to recover DKG messages. They also fixed some version mismatches that could pop up during resharing operations. And finally, they’ve patched things up to prevent invalid zero values from being used in Anti-MEV activities. Small things, but the kind that can cause big headaches if left alone.
The plan now is to get this version, v0.4.1, deployed to the Neo X MainNet soon. That’s when the full Anti-MEV functionality will really get its moment in the production environment. It’s a significant step, even if it doesn’t look like much from the outside.
For anyone who wants to read the official details, the original announcement is up on Medium.
