AxLabs launches Neo Bridge Indexer for Neo X native bridge

AxLabs has launched the Neo Bridge Indexer, a public dashboard that tracks the live status of the native bridge between Neo N3 and Neo X. Both the frontend and backend codebases have been open-sourced on GitHub under the bane-labs organization. The tool gives users, developers, and dApp operators a validator-independent way to confirm whether the bridge is operating normally, delayed, or stuck, covering all three bridge types supported on the native connection between the two chains.

The native bridge itself is not new. Neo X launched its MainNet with the bridge in place, and subsequent tooling, like the Oracle Gateway and the NeoFS Fund Proxy, has expanded what flows across it. What the Neo Bridge Indexer adds is public visibility into whether those flows are healthy at any given moment.

Why bridge indexers matter

Cross-chain infrastructure typically depends on a set of validators, relayers, or message passers that observe events on one chain and finalize them on another. When that machinery slows down or halts, the failure is often silent to end users: a transaction confirms on the source chain, appears to succeed, and then simply does not arrive on the destination side for an extended period.

Bridge indexers are a class of tooling designed to make that kind of drift visible. In the broader blockchain ecosystem, analogous dashboards include LayerZero’s public scan interface and the Wormhole status and scan dashboards, each of which surfaces cross-chain message state independently of the validator set operating the bridge. The Neo Bridge Indexer serves the same role for the Neo N3-to-Neo X connection, providing any participant with a non-privileged view of whether operations are being mirrored correctly in both directions.

How the indexer tracks bridge health

The dashboard presents two directional views: Neo N3 to Neo X, which compares on-chain bridge state with Neo N3 as source and Neo X as destination, and Neo X to Neo N3, which inverts that comparison. Both views require the operation count and the state root to match on each side for the bridge to be reported as fully synced.

Under the hood, the backend indexes only on-chain data.

Its README states explicitly that monitoring does not rely on validators or relayers, and it supports three bridge types that run on the native connection: the Native Bridge for native asset transfers, the Token Bridge for token transfers, and the Message Bridge for cross-chain message passing.

Operations are matched across chains by nonce, a unique per-operation identifier that ties a source-chain event to its destination-chain counterpart. The backend flags an operation as stuck when a source-chain event does not appear on the destination chain within a configurable threshold, set to five minutes by default.

For each indexed operation, the backend captures the bridge type, direction (deposit or withdrawal), nonce, source and destination chain and block height, transaction hashes on completion, token contract and amount, addresses, timestamps, and per-bridge-type pause state.

An alerting subsystem can send notifications via SMTP email or Discord webhooks when the monitoring logic detects a problem.

Both the backend and frontend repositories are open source from the outset.

Where it fits in the Neo X tooling arc

The Neo Bridge Indexer is the third Neo X bridge-adjacent tool added to the ecosystem in recent months. It follows 3vm, a Message Bridge inspector originally oriented around the Oracle Gateway and later extended to NeoFS deposits, and the NeoFS Fund Proxy.

The three tools serve distinct audiences: 3vm is developer-facing and built around debugging individual message bridge transactions, the NeoFS Fund Proxy is infrastructure for a specific deposit flow, and the bridge indexer is a user- and ecosystem-facing health dashboard covering all three bridge types in a single surface.

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