bridgewatch-ccip

Cross-chain message explorer for CCIP & LayerZero V2. TypeScript monorepo with indexer, PostgreSQL, REST API, React dashboard, and alert bot (Telegram/Discord). Track message latency, status, and 7‑day analytics.

10
19
85% credibility
Found May 22, 2026 at 13 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
TypeScript
AI Summary

BridgeWatch is a monitoring dashboard that helps teams track cross-chain messages sent through Chainlink CCIP and LayerZero protocols. It automatically watches blockchain networks for message events, stores them in a database, and displays them in a searchable web dashboard. Users can filter by source chain, destination, protocol, or status; view analytics like weekly volume and average delivery times; and receive alerts via Telegram or Discord when messages stay pending longer than expected. The system supports monitoring multiple blockchain networks simultaneously and provides links to view transactions directly on block explorers.

How It Works

1
🔍 You need to watch cross-chain messages

You're working with blockchain applications and want to track when messages move between different networks like Ethereum and Arbitrum.

2
⚙️ You set up which chains to monitor

You tell the system which blockchain networks you care about and which message types you want to track.

3
👀 The system watches everything automatically

Behind the scenes, the monitor continuously checks each blockchain for cross-chain messages and records every one it finds.

4
📊 You see a live dashboard of all messages

A colorful dashboard shows every cross-chain message with its status, timing, fees, and which chains it traveled between.

5
You can search and filter messages
🔗
Filter by chain

Show only messages from Ethereum to Arbitrum, or any specific route you care about.

⏱️
Filter by status

See only pending messages, successful deliveries, or failed attempts.

🔤
Search by ID

Type in a message ID or transaction hash to find a specific transfer instantly.

6
📈 You check your analytics

See how many messages you've processed this week, average delivery times, and which routes are most popular.

7
🔔 You get alerts when messages get stuck

If a message stays pending too long, you receive a notification on Telegram or Discord so you can investigate.

You have full visibility into cross-chain activity

No more guessing whether your cross-chain messages succeeded. You can see everything in one place and catch problems before they become issues.

Sign up to see the full architecture

6 more

Sign Up Free

Star Growth

See how this repo grew from 13 to 10 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is bridgewatch-ccip-explorer?

BridgeWatch is a TypeScript monorepo that acts as a cross-chain message inspector for Chainlink CCIP and LayerZero V2. It runs an indexer that scrapes on-chain events from both protocols, stores them in PostgreSQL, and exposes everything through a REST API paired with a React dashboard. You get a searchable live feed showing source and destination transactions, latency metrics, fee data, and 7-day analytics. If messages get stuck pending, it can fire alerts to Telegram or Discord based on a configurable threshold.

At its core, BridgeWatch solves the "where did my cross-chain message go?" problem. Instead of manually tracing through block explorers on different chains, you have one place that tracks the full lifecycle from source event to destination execution.

Why is it gaining traction?

The hook is clear: operational visibility across two major cross-chain protocols in a single tool. Most teams currently piece together monitoring manually or use fragmented tooling. BridgeWatch gives you a unified view with built-in analytics and alerting without needing to glue together separate systems.

The config-driven approach is practical. You point it at your RPC endpoints and contract addresses, and it starts indexing. The default setup includes Ethereum Sepolia and Arbitrum Sepolia for testing, so you can validate the workflow before connecting production contracts.

The alert bot fills a real gap for teams running cross-chain infrastructure. Stuck messages often indicate gas issues, contract configuration problems, or bridge congestion. Getting a ping before users report it is valuable operational insurance.

Who should use this?

- DeFi protocols and bridges running CCIP or LayerZero integrations that need operational monitoring - DevOps teams responsible for cross-chain infrastructure who want alerting on stuck messages - Protocol developers debugging message flow during integration or incident response - Trading teams using cross-chain bridges who need visibility into transaction latency and success rates

It's less useful for one-off experiments. The setup requires PostgreSQL, RPC access, and contract configuration. If you just want to occasionally check a transaction, block explorers remain faster.

Verdict

BridgeWatch fills a genuine gap for cross-chain message observability, and the TypeScript stack will feel familiar to most modern backend teams. However, at 10 stars it's early-stage software. The documentation is solid, unit tests exist, and the architecture is clean, but you're adopting something that hasn't yet accumulated the battle-testing that production infrastructure typically requires. The 0.8500000238418579% credibility score reflects limited community validation.

Use it for monitoring your cross-chain operations, but invest in understanding the indexer behavior before relying on it for critical alerting. Start with the testnet configuration, validate the data accuracy, then expand to production contracts. It's a promising foundation rather than a finished product.

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.