TL;DR
We’re building a Crosschain Alert Monitoring toolkit for the Superchain. It provides a deterministic heartbeat across OP Stack L2s, generating real‑time health signals, latency and gas metrics, and actionable alerts for interop messages. Delivered as a TypeScript SDK plus services, it helps teams detect outages, delays, or failures fast, and gives operators and devs clear visibility into cross‑chain communication.
What Are We Building?
A developer‑first toolset that tracks cross‑chain messaging across Superchain chains and exposes:
- Interop Status: down / paused / active; degraded vs healthy.
- Core Metrics: p50/p95 latency between chains; gas usage on sender/receiver chains (aggregated at layer/project level).
- Health Alerts: missing/late/unexpected messages with severities and routing hooks (Slack/webhooks/email/etc).
Product Components
- Tracking Module
Constantly monitors canonical interop paths and collects normalized message results. - Metrics Generation Module
Aggregates raw results into latency distributions, success/failure rates, and overall health. - Alert Generation Module
Lightweight rules engine that emits alerts based on thresholds (timeouts, excessive latency, unexpected events). - Developer SDK
A simple, documented TS SDK to query metrics, subscribe to alerts, and embed monitoring in apps/services.
Tech
- Node.js + TypeScript
- Runs well on AWS (portable to other platforms)
- viem under the hood
Why It Matters
As Superchain interop grows, reliable cross‑chain messaging becomes table stakes for serious products. Today, available tools are either expensive, limited, or lack chain coverage. This mission upgrades the developer experience for OP Stack builders with clear, timely, and composable observability.
- Helps teams ship safer cross‑chain protocols and operations.
- Reduces meantime‑to‑detect (MTTD) for outages and degraded performance.
- Encourages ecosystem‑wide standards for interop health and alerting.
How It Works (SDK Heartbeat)
We send synthetic “pings” between OP Stack L2s using the canonical L2CrossDomainMessenger path to produce a deterministic health signal:
- Build a minimal payload and call sendMessage on the origin chain.
- Wait for origin confirmation and derive a messageHash for correlation.
- Watch the destination messenger for RelayedMessage.
- If no signal arrives within the timeout window, mark timeout and emit an alert.
Metrics Produced
- Status: success | fail | timeout
- Latency: wall‑clock and chain‑observed
- Gas: sender/receiver usage
- Event Traces: origin/destination txs for diagnostics
This synthetic heartbeat is independent of third‑party traffic and provides a consistent baseline to monitor health—no reliance on fast relayers or external indexers.
Kickoff and Milestone 1 Delivered
The mission is officially underway, and our first milestone, Research, is complete. During this stage we explored the landscape of interop messaging across the Superchain, defined the architecture of the toolkit, and considered complex failure cases along with contingency plans to address them. We also documented the constraints we encountered: the canonical L2ToL2CrossDomainMessenger is not yet enabled on mainnet or testnets, so for now we’ve implemented a temporary relay setup on testnets to keep the SDK development flow intact. With this groundwork in place, we’re moving confidently into the development of the Tracking Module.
Milestones
Our work is organized into a clear set of milestones, each building upon the previous one to gradually shape the Crosschain Alert Monitoring toolkit into a production‑ready resource for the Superchain. Rather than just ticking boxes, each milestone has been designed to bring something tangible to developers and the ecosystem.
- Research (completed): established the architecture, clarified constraints, and prepared fallback procedures.
- Tracking Module: the next step, where the first synthetic heartbeat across chains will come to life, storing normalized results for analysis.
- Metrics Generation Module: transforms raw data into actionable insights—latency distributions, success and timeout rates, and health assessments.
- Alert Generation Module: layers a rules engine on top of metrics, issuing alerts when performance thresholds are breached or anomalies are detected.
- SDK Creation: turns all of this into a clean, accessible package that any developer can integrate.
- Publish Demo: showcases the system in action through a live testnet deployment and minimal dashboard.
- Internal QA & Feedback: focuses on stabilization, performance tuning, and incorporating feedback from the community.
- Final Release: delivers a polished, production-ready toolkit with changelogs and versioning.
- Long-Term Commitment: ensures the project’s sustainability, with WakeUp Labs maintaining the repos, fixing bugs, and supporting users for at least two years.
Measuring Impact
Success will be measured by adoption across protocols and chains, SDK usage and developer activity, the accuracy of monitoring (minimizing false positives/negatives), and the quality of feedback we incorporate from the community. Ultimately, the value of this mission lies in making interop reliable and transparent for everyone building on the Superchain.
Next Steps
With the research milestone complete, our immediate focus shifts to bringing the Tracking Module to life. This will be the beating heart of the toolkit, responsible for sending and correlating synthetic pings across chains. Alongside this development, we will begin sharing an early version of the SDK API so the community can review, test, and provide feedback on how best to shape it for real developer needs. In parallel, we’ll coordinate closely with OP Labs on timelines for enabling the canonical messenger, ensuring that our work remains aligned with the broader Superchain roadmap.
Follow @WakeUpLabs on X and LinkedIn for updates.
GitHub: 
Docs: