AxLabs has launched 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 are open sourced on GitHub under the bane-labs organization. The tool provides users, developers, and dApp operators with a validator-agnostic way to check if a bridge is working properly, laggy, or stuck, and covers all three bridge types supported for native connections between two chains.
Native bridges themselves are not new. Neo What Neo Bridge Indexer adds is that it lets the public know whether these flows are healthy or not at any given time.
Why bridge indexers are important
Cross-chain infrastructure typically relies on a set of validators, relayers, or message passers that monitor events on one chain and finalize them on another chain. If a machine slows down or stops, the failure is often not noticeable to the end user. The transaction is confirmed on the source chain and appears to be successful, but then simply does not arrive at the destination side for a long time.
Bridge indexers are a type of tool designed to visualize such drift. In the broader blockchain ecosystem, similar dashboards include LayerZero’s public scanning interface, wormhole status and scanning dashboards, each of which displays the state of cross-chain messages independently of the set of validators operating the bridge. The Neo Bridge Indexer plays the same role for Neo N3 to Neo X connections, providing participants with an unprivileged view of whether operations are correctly mirrored in both directions.
How the indexer tracks the state of the bridge
The dashboard displays two directional views. Neo N3 to Neo X, which compares the on-chain bridge state with Neo N3 as the source and Neo X as the destination, and Neo X to Neo N3, which reverses the comparison. In either view, the operation count and state root must match on both sides for the bridge to be reported as fully synchronized.
Internally, the backend indexes only on-chain data.
Its README clearly states that the monitoring is validator- and relayer-agnostic, and supports three bridge types that run on native connections: native bridge for native asset transfer, token bridge for token transfer, and message bridge for cross-chain message passing.
Operations are matched across chains by a nonce, a unique identifier for each operation that connects events in the source chain to corresponding events in the destination chain. backend flags the operation stuck If the source chain event does not appear in the destination chain within a configurable threshold. By default it is set to 5 minutes.
For each indexed operation, the backend captures the bridge type, direction (deposit or withdrawal), nonce, source and destination chain and block heights, transaction hash at completion, token contract and amount, address, timestamp, and suspension state per bridge type.
The alert subsystem can send notifications via SMTP email or Discord webhooks when the monitoring logic detects an issue.
Both the backend and frontend repositories are open source from the beginning.
Where does the Neo X Touring Arc fit?
Neo Bridge Indexer is the third Neo X Bridge adjacency tool added to the ecosystem in recent months. It follows 3vm, a message bridge inspector originally centered around the Oracle gateway, which was later extended to NeoFS Deposit and NeoFS Fund Proxy.
Each of the three tools serves different users. 3vm is aimed at developers and is built around debugging individual message bridge transactions. The NeoFS Fund Proxy is the infrastructure for a specific deposit flow, and the Bridge Indexer is a health dashboard for users and the ecosystem that covers all three bridge types on one surface.
The full announcement can be viewed from the link below.
https://x.com/ax_labs/status/2047265749262012725
