R3E Network’s neox-rs, a Rust-based alternative full-node client for Neo X, now blocks calls that use EIP-7702 delegation to run code from blacklisted contracts, closing a gap in Neo X’s governance-controlled Blacklist Policy.

The fix arrives in v2.8.0, released Nov. 16. The release also moves the client onto Reth v2.8.1 and was validated with a full replay of Neo X MainNet from genesis.

Jimmy Liao, Neo core developer and R3E Network founder, announced the release on Nov. 17. It follows neox-rs v2.7.0 in October, which merged 185 upstream Reth commits and closed nine dependency vulnerabilities.

Blacklist extended to delegated execution

The Neo X v0.6.2 node release extended the Blacklist Policy to EVM execution in August (PR #648), so calls to blacklisted contracts revert.

EIP-7702, introduced in Ethereum’s Pectra upgrade, allows a standard account to delegate to a smart contract’s code. Until this release, neox-rs checked only the address being called, so an account delegating to a blacklisted contract could still be used to execute that contract’s code.

Starting with the Prague fork, already active on Neo X MainNet and TestNet, neox-rs now reverts calls to an address whose EIP-7702 delegation points to a blacklisted contract. The check runs before the delegated code executes and applies to every type of EVM contract call.

According to the release notes, the change is consensus-critical, and node operators running neox-rs should upgrade before submitting or validating Prague-era transactions that involve delegated blacklisted contracts.

The same fix was merged into the Neo X Go client, the main Neo X node implementation, on Nov. 16. It closes an issue in the client’s v0.7.0 milestone and has not yet shipped in a tagged release; the latest Go client release is v0.6.2.

dBFT networking and fork preparation

The release raises the maximum size of accepted dBFT consensus messages from 4 MiB to 10 MiB, matching the Go client (PR #655), since the previous cap could have disconnected honest peers sending large dBFT recovery messages, according to the release notes.

A node now pauses its own dBFT participation while a peer reports being more than one block ahead, though it keeps relaying dBFT messages.

Several changes, including those from Go client PR #679, prepare for Amsterdam, a future Ethereum fork not yet scheduled on any public Neo X network. According to the release notes, they have no effect on current public networks.

Rebased on Reth v2.8.1

The client now builds on Reth v2.8.1 while preserving Neo X’s engine, RPC, dBFT, distributed key generation, and Anti-MEV layers.

Reth’s switch to its new evm2 execution engine, and the 243 commits that followed it, have been held back until the Neo X EVM is ported to evm2. Four correctness fixes from that backlog were backported instead (PRs #28148, #28163, #28085, and #28164).

The Go client’s genesis files, Anti-MEV code, and threshold encryption code did not change between the old and new baselines, so earlier cross-client test vectors remain valid.

Validation

Before the release was tagged, Neo X MainNet was replayed from genesis to block 8,321,108 in about 1 hour and 53 minutes with zero errors.

All 32,570 checkpoint block hashes and all fork-boundary state roots matched references verified against the Go client, after which the node followed live dBFT consensus. All 441 Neo X tests passed.

Availability and upgrade notes

According to the release notes, pre-built bundles with SHA-256 checksums are produced for Linux on x86_64 and ARM64 and for macOS on Apple Silicon, while Windows users need to build from source. That differs from v2.7.0, which shipped Linux and Windows x86_64 builds only.

The release notes advise operators to back up their data directory before upgrading. No state migration is required, though downgrade compatibility has not been re-verified.

The neox-rs client runs as a non-validator full node that syncs and verifies Neo X MainNet. Validator mode remains pre-release and requires the --validator.experimental flag on public networks.

The project lists an independent protocol and security review among the steps still required before it will describe the client as ready for validator use or a MainNet release.

The full release notes can be found at the link below:
https://github.com/R3E-Network/neox-rs/releases/tag/neox-v2.8.0