[CLOSED] Governance Fund Mission Request: Open-source Monitoring & alerting

Grants 🔴 Governance Fund Missions
4

WakeUp Labs Governance Fund Mission Application: Open-source Monitoring & alerting

Team Lead

Contact info

Team members & previous work:

  • WakeUp Core Engineers (10 FTEs): Solidity, TypeScript, Node.js, React, infra & monitoring. Delivered Optimism RFG1 Indexer (open source), Interop Alerts SDK (cross-chain monitoring for OP Stack), Arbitrum Stylus SDK (AssemblyScript integration), Velora/ParaSwap DAO automation (PIP-55), Starknet Privacy ERC20, among others.
  • UX/UI Designer (1 FTE): Responsible for the dashboard interface and usability.
  • DevOps Engineer (1 FTE): RPC infra, AWS nodes, and deployment automation.
  • Project Manager (1 FTE): Coordination, milestone reporting, and DAO communication.

Repos: WakeUp Labs · GitHub
Website: https://wakeuplabs.io
X: x.com/wakeuplabs

What makes your team best-suited to execute this Mission?

WakeUp Labs is a long-standing Optimism contributor focused on developer tooling and open infrastructure.

The team has a proven record of delivering Optimism-funded projects such as the RetroPGF Indexer and the Interop Alerts SDK, and also builds core infrastructure for Coinbase, Arbitrum, Starknet, Aztec, ParaSwap, Rootstock, among others .

Unlike solo-developer competitors, WakeUp brings a multidisciplinary structure with engineering, UX, DevOps, and project management, along with established trust within Optimism governance.

With this Mission, WakeUp aims to deliver an open source Monitoring & Alerting SDK + Dashboard that helps every protocol on Optimism detect anomalies, track on-chain health, and respond faster. The proposal builds directly on our prior work with Optimism and reinforces our long-term commitment to strengthening the Superchain’s reliability.

Proposed solution

Protocols on Optimism currently lack a standardized, open source tool to monitor smart contract health and receive timely alerts. Existing approaches are ad-hoc or closed source, making incident detection slow and inconsistent.

WakeUp Monitoring & Alerting SDK + Dashboard will provide a complete and extensible monitoring system:

  • SDK for invariant checks: Define customizable rules to observe on-chain conditions and detect anomalies in real time. The SDK connects to Optimism nodes via WebSocket subscriptions (eth_subscribe) for real-time event streaming, while maintaining compatibility with standard JSON-RPC polling when WebSocket endpoints are unavailable.

  • Slack notifications (extensible): Out-of-the-box Slack alerts, with a modular design ready for future channels (Telegram, PagerDuty, Webhooks).

  • Integration hooks: Trigger off-chain responses or user-defined scripts when invariants fail, enabling automated reactions without requiring contract ownership or admin privileges. WakeUp will not require contract ownership; all responses occur off-chain through safe, configurable hooks.

  • Dashboard-first UX: A web interface to configure rules, view alert history, manage users, and visualize contract data, designed for both developers and operations teams.

  • Multiple RPC endpoints: Support for configuring multiple RPC providers for load balancing and redundancy, ensuring reliable performance even under high network activity.

  • Example invariants: Provide reference templates for Uniswap v3 (pool price ratios, liquidity range) and Aave v3 (health-factor thresholds, oracle-update delays) to demonstrate the SDK’s flexibility.

  • Superchain-ready architecture: Built to support monitoring across multiple OP Stack chains in the future.

This approach balances immediate usability with extensibility, helping Optimism standardize security practices while remaining fully open source.

Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each piece of work:

Phase 1 (Weeks 1–5) – MVP & Basic Alerts

  • Build the core SDK in TypeScript.
  • Implement ERC-20 transfer monitoring using WebSocket subscriptions for real-time detection, with Slack alerts as the first supported notification channel.
  • Deliverable: SDK repo, documentation, and working demo.

Phase 2 (Weeks 6–12) – Rule Framework & Protocol Examples

  • Implement modular rule definition (JSON/YAML configs).
  • Develop example invariants for Uniswap v3 (price ratios, liquidity checks) and Aave v3 (health factor, oracle frequency).
  • Extend dashboard for rule creation and management.
  • Deliverable: SDK, dashboard, and reference examples.

Phase 3 (Weeks 13–16) – Full Release

  • Finalize dashboard (rule editing, visualization, alert history).
  • Conduct end-to-end testing and publish documentation.
  • Deliverable: Monitoring & Alerting Suite v1.0 (open source release on npm and GitHub).
  • Documentation & contribution guidelines: Publish extensive developer documentation, usage examples, and contribution guides to help the community extend the SDK with new rules or alert channels.

Estimated timeline: November 2025 → February 2026.

Milestones

  1. M1 – MVP (end of Nov 2025): SDK live in repo; WebSocket-based event streaming operational; Slack alerts working end-to-end.
  2. M2 – Rule Framework + Libraries (end of Dec 2025): Modular rule system implemented; Uniswap v3 and Aave v3 templates validated.
  3. M3 – Full Release (Feb 2026): Dashboard and SDK 1.0 published; documentation, contribution guidelines, and public announcement complete.
  • Long-Term Support:
    WakeUp Labs will provide two years of maintenance and production support post-release, ensuring ongoing compatibility with future OP Stack versions and addressing bug fixes or security updates.

Support requested

  • Introductions to teams such as Uniswap and Aave for validation of reference invariants.
  • Optional audit support if a minimal on-chain helper contract is introduced.
  • Delegate and community feedback to guide future alert-channel extensions.

Terms

  • :check_box_with_check: I understand my grant for completing this Governance Fund Mission will be locked for one year from the date funds are transferred to the locked multisig wallet.
  • :check_box_with_check: I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant
  • :check_box_with_check: I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the Collective Grant Policies
  • :check_box_with_check: I confirm that I have read and understand the Collective Grant Policies
4 Likes