In March, the Neo core progressed towards a new milestone version, Neo 3.2. Updates were relatively scattered, split between bug fixes, C# compiler enhancements, and some new features. Developers building contracts will find a new addition to the native CryptoLib contract; an implementation of the Murmur hash function, a fast and cost-efficient option when hashing without cryptographic guarantees is required.
One of the most significant changes came in the form of a simple setting adjustment—by altering the maximum transaction per block limit, the N3 TestNet’s TPS limit will receive a substantial increase, ensuring transactions can be processed in a timely manner as more new decentralized applications begin to deploy on the network.
On the tooling front, NGD Enterprise made waves with the release of a new Debugger preview. The preview brought with it several enhancements to the debugging experience in the Neo Blockchain Toolkit, with a focus on changes in the storage view. Developers using compatible compilers (currently only C#) will be able to decorate their code with type information that will be emitted in the standard debug info files during compilation.
The Neo Debugger uses this data to provide an improved overview of contract storage and runtime value types, making it easy for developers to visualize contract data when debugging executions.
Neo SPCC also brought forward several improvements to the developer experience, both for its Go node/SDK implementation and NeoFS client. In the former, developers will find a new contract bindings generator to quickly interact with custom contracts via Go, while the latter received various UX improvements and bug fixes.
Several ecosystem projects underwent security reviews by Red4Sec this month, including contracts for NeoFS, Flamingo, and the new GrantShares DAO project championed by AxLabs.
The full March Neo global monthly development report can be found below.