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 are open source on GitHub under the bane-labs organization. The tool provides users, developers and dApp operators with a validator-independent way to confirm whether the bridge is normal, delayed or stuck, and includes all three bridge types supported on the native connection between the two chains.
The native bridge itself is not new. Neo What the Neo Bridge Indexer adds is public visibility into whether these flows are healthy at any given time.
Why bridge indexers matter
Cross-chain infrastructure typically relies on a series of validators, relayers, or message passers that observe events on one chain and finalize them on another chain. When that machinery slows down or stalls, the failure often remains silent for the end users: a transaction is confirmed on the source chain, appears to succeed, and then simply does not arrive at the destination side for an extended period of time.
Bridge indexers are a class of tools designed to make that kind of drift visible. In the broader blockchain ecosystem, analog dashboards include LayerZero’s public scanning interface and Wormhole status and scanning dashboards, each of which displays cross-chain message status independently of the validator set controlling the bridge. The Neo Bridge Indexer serves the same role for the Neo N3-to-Neo
How the indexer keeps track of the status of the bridge
The dashboard offers two directional views: Neo N3 to Neo X, which compares the bridge status on the chain with Neo N3 as source and Neo Both views require that the number of operations and the status root on each side match so that the bridge can be reported as fully synchronized.
Under the hood, the backend only indexes data in the chain.
The README explicitly states 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 passing messages across the chain.
Operations are compared across chains by nonce, a unique per-operation identifier that links a source chain event to its counterpart in the destination chain. The backend marks an operation as fixed when a source chain event does not appear on the target chain within a configurable threshold, defaulting to five minutes.
For each indexed operation, the backend records the bridge type, direction (deposit or withdrawal), nonce, source and destination chain and block height, transaction hashes at completion, token contract and amount, addresses, timestamps, and pause status per bridge type.
An alert subsystem can send notifications via SMTP email or Discord webhooks when the monitoring logic detects a problem.
Both the backend and frontend repositories have been open source from the start.
Where it fits into the Neo
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 that originally targeted the Oracle Gateway and later expanded to NeoFS deposits, and the NeoFS Fund Proxy.
The three tools serve different audiences: 3vm is aimed at developers and built around debugging individual message bridge transactions, the NeoFS Fund Proxy is an infrastructure for a specific deposit flow, and the bridge indexer is a user- and ecosystem-focused health dashboard that includes all three bridge types on one surface.
The full announcement can be found via the link below:
https://x.com/ax_labs/status/2047265749262012725