Skip to main content

Bridge Monitor

Monitor cross-chain bridge health, TVL, transaction status, and liquidity pools. Get alerts on bridge anomalies and stuck transactions.

Supported Protocols

  • Stargate — LayerZero-based cross-chain liquidity transport
  • Wormhole — Guardian-network message passing across EVM chains

Additional bridges (Across, Hop, and native L2 bridges like Arbitrum/Optimism/Polygon PoS) are on the roadmap. Follow our changelog for updates.

Configuration

{
  "name": "Stargate ETH → Polygon",
  "bridgeProtocol": "stargate",
  "sourceChainId": 1,
  "destChainId": 137,
  "sourceRpcUrl": "https://eth.llamarpc.com",
  "destRpcUrl": "https://polygon-rpc.com",
  "trackedAddresses": ["0x8731d54E9D02c286767d56ac03e8037C07e01e98"],
  "checkIntervalSeconds": 120,
  "stuckThresholdMinutes": 60
}

trackedAddresses are the bridge contracts or user wallets whose transactions you want to correlate across source and destination chains.

Metrics Monitored

MetricDescriptionAlert
Bridge TVLTotal locked value30% drop
Transaction StatusPending tx time>1 hour
LiquidityAvailable for bridging50% drop
Failure RateFailed transactions>10%

Alert Examples

Bridge TVL Drop

Bridge TVL Alert

Bridge: Stargate
Route: Ethereum -> Polygon

TVL: $850M (was $1.2B)
Change: -$350M (-29%)
Timeframe: 24 hours

Possible Issues:
- Mass withdrawal event
- Security concern
- Alternative bridge preferred

[View Bridge] [Check Activity]

Stuck Transaction

Bridge Transaction Delayed

Bridge: Wormhole
TX: 0xabcd...ef01
Amount: 5 ETH

Status: Pending
Time: 2 hours 15 minutes
Expected: ~15 minutes

Action: Check bridge status

[View Transaction]

Use Cases

1. Bridge Health Monitoring

Monitor: All major bridges
Alert: TVL drops, delays
Channel: Slack #bridge-alerts
Action: Notify users

2. Personal Transaction Tracking

Monitor: Your bridge txs
Alert: Pending > 1 hour
Channel: Telegram personal
Action: Manual investigation

3. Protocol Integration

Monitor: Partner bridges
Alert: Liquidity low
Action: Redirect to backup bridge

Best Practices

  • Monitor Both Directions: L1→L2 and L2→L1
  • Track Multiple Bridges: Have alternatives ready
  • Set Realistic Timeouts: Official bridges can take 7 days
  • Check Liquidity: Low liquidity causes delays

Protocol Comparison

ProtocolTypical TimeTrust ModelChains Covered
Stargate~1-3 minLayerZero oracle + relayerEthereum, Polygon, BSC, Arbitrum, Optimism, Base, Avalanche, Fantom
Wormhole~15 minGuardian network (19 validators)All 8 BlackTide-supported EVM chains

Next Steps