R3E Community’s Rust-based Neo N3 node implementation, neo-rs, has reached full protocol parity with the Neo N3 specification at v0.16.0. The milestone covers all 11 native contracts, all eight hardforks by way of Huyao, and all 41 system calls, verified with actual CPU pricing and permission gates. Alongside the node launch, R3E printed NeoRust v3.0.0, a correctness-focused SDK replace with three breaking API adjustments, and Neo Signer RS v0.2.0, a supervised council signing service designed for hardware-isolated environments.
The releases, printed between Aug. 28 and Sept. 4, advance R3E’s broader effort to construct an entire Rust-based toolchain for Neo, spanning neo-rs for node infrastructure, NeoRust for utility improvement, and devoted signing infrastructure for council operations.
neo-rs v0.16.0: production-readiness milestone
The v0.16.0 launch represents the primary time neo-rs has handed its full take a look at suite with zero failures throughout the whole Neo N3 protocol floor. NNT has beforehand coated the challenge as a Rust implementation of the Neo N3 blockchain node and an integral part of R3E’s initiative to introduce Rust to the Neo ecosystem.
Protocol alignment now extends throughout all 11 normal native contracts, ContractManagement, NeoToken, GasToken, PolicyContract, RoleManagement, OracleContract, Notary, TreasuryContract, LedgerContract, CryptoLib, and StdLib, with strict validation enforced throughout all eight Neo N3 hardforks from Aspidochelone by way of Huyao.
The discharge additionally formalizes dBFT 2.0 consensus dealing with, implementing Main preliminary timer gating, monotonic ChangeView processing, off-view commit isolation, and three-set deduplication in Restoration messages. A quick-sync P2P end-to-end take a look at suite has been added for network-level validation.
Notable fixes embody Faun hardfork timestamp migration for PolicyContract.BlockAccount conduct, storage prefix search semantics aligned with RocksDB, and unified multi-signature contract parsing with Secp256r1 curve validation. A container picture is on the market at ghcr.io/r3e-network/neo-rs:v0.16.0.
With this launch, neo-rs joins neo-cli and neo-go as a production-qualified Neo N3 node implementation, contributing to consumer variety for the community.
NeoRust v3.0.0: correctness, safety hardening
The NeoRust SDK’s v3.0.0 launch prioritizes correctness and safety over new options, introducing three breaking API adjustments that mirror a maturation level for the challenge. NNT coated the SDK’s earlier production-hardening replace at v2.1.0 in July.
Among the many most vital fixes, fuel estimation accuracy has been corrected by roughly 1e8 by way of actual decimal-to-base-unit conversion, a discrepancy that might trigger transactions to fail or overpay for execution. Steadiness queries not fail on normal nodes when an tackle holds third-party NEP-17 tokens, because the SDK now fetches token metadata individually. The preview_state_changes technique now decodes actual addresses and quantities from notification state quite than fabricating switch previews, and wait_for_confirmation accurately returns an error on VM FAULT as an alternative of treating it as success.
Safety enhancements embody pockets and backup recordsdata created with 0600 permissions on Unix, proscribing entry to the file proprietor. HD pockets WIF intermediates are actually zeroized after account derivation, and mnemonic entropy is scrubbed from reminiscence on drop.
The three breaking adjustments have an effect on DerivationPath::new_neo, which now returns a End result kind as an alternative of risking panics for indexes above 2^31; EventData, which gained a Disconnected variant for exhausted reconnect makes an attempt; and EcosystemClient, which now makes use of human-decimal models on Neo X quite than uncooked Wei values.
Neo Signer RS v0.2.0: supervised council signing
Neo Signer RS v0.2.0 transforms R3E’s council signing instrument right into a supervised, restart-safe service with elective each day $GAS aggregation. The service is designed for deployment in hardware-isolated environments, supporting each Intel SGX and AWS Nitro Enclaves.
The discharge introduces twin impartial RPC supplier verification, requiring stability, top, VM consequence, and price settlement from two separate Neo nodes earlier than continuing with financial operations. A disk-backed anti-equivocation journal prevents duplicate transactions, together with throughout restarts, whereas KMS recipient attestation binds pockets unlock to a deployed Nitro Enclave Picture File.
Jimmy Liao, R3E Community core developer, described the discharge as providing “fail-closed Neo N3 signing for SGX and AWS Nitro Enclaves: hardware-isolated keys, measured-EIF KMS attestation, sturdy anti-equivocation, and dual-RPC $GAS sweep checks.”
A notable repair corrects the Neo N3 transaction ID derivation, which was utilizing double-SHA256 as an alternative of the right single-SHA256, inflicting broadcast affirmation lookup failures. The discharge additionally migrates from an unbounded in-memory journal to a 16 MiB-cache redb journal, with 869,417 legacy data validated throughout migration.
Consensus signing stays obtainable even when financial signing is disabled, guaranteeing council participation shouldn’t be disrupted by the $GAS aggregation function.
Launch notes for every challenge could be discovered on the hyperlinks beneath:
https://github.com/r3e-network/neo-rs/releases/tag/v0.16.0
https://github.com/r3e-network/neo-rust-sdk/releases/tag/v3.0.0
https://github.com/r3e-network/secure-sign-service-rs/releases/tag/v0.2.0
