Neo Core Developers discuss dynamic block intervals, post-quantum cryptography, and Neo 3.9 features in recent meeting

A recording of the latest Neo Core Developer meeting, held on Nov. 6, is now available to the public. In the session, contributors discussed the status of several Neo 4 proposals, upcoming features for Neo 3.9, and structural adjustments to the repository workflow. Among the items covered were progress on dynamic block intervals, standardized token interfaces, and preparations for post-quantum cryptographic compatibility.

The meeting opened with a detailed examination of the dynamic block interval proposal, a major planned upgrade for Neo 4. Developers explored how best to decouple gas reward calculations from block height and instead tie them to block timestamps, debating implementation strategies that balance protocol precision with real-time reward calculations. The conversation highlighted the need to maintain accurate reward data for tools like explorers and wallets, while still enabling block times to adjust automatically based on network load. Although participants expressed divergent views on how dynamic intervals should behave under low or high transaction volumes, consensus was reached that the codebase should be prepared to support configurable behavior—even if the feature is not immediately critical for current throughput.

Post-quantum cryptography was also discussed, with contributors outlining next steps for integrating hash-based and lattice-based algorithms such as SHA3-512 and BLAKE2b-512. The group agreed that while quantum threats are not imminent, preparing the infrastructure is a priority aligned with Neo’s long-term roadmap. Discussions included the possibility of a more generic account model, allowing users to choose from a range of cryptographic schemes without compromising compatibility with existing addresses.

The team also touched on the proposed contract charging mechanism, noting that while implementation is pending, a formal Neo Enhancement Proposal document (NEP) will be needed before the work can proceed further. This aligns with recent efforts to better define the scope and intent of protocol changes prior to development.

Regarding the Neo 3.9 release, several features were confirmed for inclusion, including NEP-25 support for contract manifests and a whitelist contract system for free transactions. The execution fee factor adjustment with decimal support was also approved, though developers acknowledged minor inconsistencies in internal GAS accounting. The flattened GAS reward mechanism, aimed at equalizing voter rewards regardless of which consensus node is selected, remains under discussion. While it is expected to be introduced in Neo 3.10, developers are assessing whether partial implementation could be brought forward to 3.9.

A brief but important discussion addressed repository management, with agreement to consolidate development on the master branch and eliminate the separate master-n3 branch. Future releases, such as Neo 3.9, will be tagged with new branches at the time of release.

The team also discussed the proposal to add a GetRandom(MaxValue) method to the standard library contract. Although the feature was seen as potentially useful, concerns about implementation risks and extended review timelines led to its exclusion from the 3.9 release. The enhancement made be included in a future version.

The full discussion can be found below: