A January. 8 mail service published by the Ethereum Foundation (EF) revealed that developers are working on a new implementation of the Vyper compiler, due to "multiple serious bugs" in the existing version. The Vyperlang team responded by noting that existing Vyper smart contracts were not affected by these bugs.

Vyper is an alternative programming linguistic communication for Ethereum originally conceived by Vitalik Buterin. It focuses on existence as human-readable every bit possible, even at the cost of missing some of the more advanced features found in Solidity, the principal language.

While initially office of the master Ethereum (ETH) code stack, it has since spun-off into an independent repository post-obit an Oct. 2022 preliminary audit by Consensys Diligence. The written report found 31 problems with the Vyper compiler, the software that translates the language into computer lawmaking for the Ethereum Virtual Automobile (EVM).

Ethereum Foundation developers explained in their blog mail how they gradually became disillusioned with Vyper maintainers:

"After a few months of work we were skeptical that the python codebase was likely to deliver on the thought that Vyper promised. The codebase independent a pregnant amount of technical and architectural debt, and from our perspective it didn't seem like the existing maintainers were focused on fixing this."

Fifty-fifty before the study, the EF team began work on a new Vyper compiler based on the Rust language. The determination was motivated past increased portability to EWASM, a new virtual machine implementation replacing the EVM that is set to exist introduced with Ethereum ii.0.

Compiler bugs not critical, debate Vyper maintainers

Bugs found in the Vyper compiler were especially significant due to its employ in the Ethereum 2.0 eolith contract, a critical component of the Proof-of-Stake (PoS) arrangement.

Notwithstanding, Vyper developers clarified in a Twitter thread that a separate audit was conducted for the contract itself by Runtime Verification, which establish no unfixed bugs. It used the compiled car code of the contract to perform the analysis, meaning that any anomaly introduced by the compiler would've been detected.

Furthermore, the Vyperlang team released an update on Jan. 7, claiming to have fixed over 75 percent of the bugs outlined by the Consensys audit.

Development of both the Rust and Python versions of Vyper volition continue, though EF developers remain hopeful that both implementations will work toward a single Vyper language — a goal that is likely to require close cooperation betwixt the two teams.