AxLabs has released an open-source plugin for Neo N3 nodes that allows developers to query historical smart contract events and monitor new ones, filtering by contract address, event name, and block range. This is a capability that Ethereum developers have long had access to natively, but that Neo N3 has not offered until now.

The Neo Event Filter Plugin was built by Merl, an AxLabs developer known for prior contributions to the Neo ecosystem, including Nanvil, the NeoFS TypeScript SDK, NFS, NeoFS Mount, NeoFS Streaming, and the Raihno fitness app.

Neo Event Filter Plugin v1.0.0 is now available on GitHub.

The gap it fills

Neo N3’s standard JSON-RPC API has not provided a general-purpose method for querying smart contract events across multiple blocks. While existing plugins provide access to transaction execution logs and token transfer histories, developers seeking arbitrary contract events have typically needed additional indexing infrastructure or external services.

For dApps that need historical event data or want to react to new events in real time, this has often meant building custom indexing infrastructure or relying on third-party services.

Ethereum’s JSON-RPC API has addressed this problem for years with methods such as eth_getLogs, which retrieves historical events matching specified criteria, and eth_newFilter, which creates a filter that developers can poll using eth_getFilterChanges to retrieve newly emitted events.

AxLabs built the Neo Event Filter Plugin to bring equivalent functionality to Neo N3.

What this enables

With the plugin installed on a node, developers can query indexed contract events using a GetLogs-style JSON-RPC endpoint. Supported filter dimensions include contract address, event name, and block range. Rather than scanning block by block, a single API call returns the matching events directly.

The plugin also supports filter subscriptions via an install-and-poll mechanism. A developer registers a filter, then polls for new events matching that filter as new blocks arrive. This pattern enables reactive front-ends and real-time dashboards without custom scanning logic.

For teams porting Ethereum dApps to Neo N3, the familiar query structure lowers the barrier to integration.

AxLabs framed the tool explicitly as an EVM-style API in its announcement, noting that Neo N3 dApp developers had been asking for exactly this.

How it works

When installed on a node, the plugin indexes smart contract notifications as each new block is processed, storing them in a local searchable index. By default, it also performs a historical backfill, replaying past transactions from block zero to index older events.

A filter status dashboard is also available through the node’s command-line interface.

Known limitations

Two technical caveats apply to historical data.

The backfill process replays historical transactions against the current blockchain state, not the state that existed when those transactions were originally executed. For some contracts, this can produce incorrect results or cause events to be missed in historical queries. Events indexed in real time as new blocks arrive do not have this problem.

The backfill process is also computationally intensive. Replaying the full Neo N3 history from block zero requires significant time and resources.

Merl noted that historical backfilling is separate from a full node resync, which rebuilds a node’s blockchain data. The limitations associated with historical backfilling do not affect the normal resync process.

The full announcement can be found at the link below:
https://x.com/ax_labs/status/2123344783275864509