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

Governance Fund Missions 🏹
,
5

Walnut Governance Fund Mission Application: Open-source Monitoring & alerting

Team Lead: @RomanRoman Mazur

Contact info: Email: roman@walnut.dev | Teleg@rmazuram: @rmazur

L2 recipient address: 0x368ac9da9f793baa41fa75cb2d75a7d6229cf35b

Team Members and Previous Work:

Walnut Labs is a team of experienced Web3 developers specializing in Ethereum, EVM internals, transaction debugging, compiler technology, simulations and monitoring.

We have ongoing multi-year partnerships with StarkWare and Offchain Labs, contributing to projects around Cairo and Cargo Stylus, and our team includes design and product expertise to deliver complete, production-ready tools end-to-end.

Core team members for this project:

  • Roman Mazur — Product Lead 10+ years of experience (ex-Argent, Microsoft). Full-time in Web3 since 2020 with deep expertise in Ethereum/EVM, RPCs, transaction simulations. [LinkedIn] https://www.linkedin.com/in/mazurroman

  • Simon Arvaux — Full-Stack Web3 Developer 10+ years of professional experience (5+ in Web3). Strong background in EVM, blockchain indexing, Foundry, and Anvil. [GitHub] https://github.com/saimeunt

  • Marija Mijailovic — Full-Stack / Web3 Engineer 8 years of experience (5 in Web3). Skilled in Rust, Python, Node.js; strong experience with infra, nodes and transaction monitoring. [GitHub] https://github.com/marijamijailovic

Selected projects:

  • walnut.dev – Web-based transaction debugger and simulator for Starknet, live for 2+ years and widely used across the ecosystem.

  • GitHub: walnuthq – Collection of open-source projects built in collaboration with Offchain Labs, Miden, Optimism, Starknet and others.

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

  • Proven Track Record: Established team with a history of delivering and maintaining high-quality developer tools across Ethereum, with long-term partnerships with Offchain Labs and Starkware.

  • Technical & Product Expertise: Deep experience in web3 development, infra, monitoring, and compiler internals, combined with BD skills to ensure both technical excellence and adoption.

  • Established Network of Partnerships: Our connections with Solidity developers and Rollup infra teams through Walnut ensure we build what’s needed and that the tool gets used. Already discussed with the OP Labs Infra team (they actually pointed us to this mission), guaranteeing adoption and continuity beyond the grant.

  • Long-Term Alignment & Sustainability: Monitoring is part of our roadmap for Walnut, our open-source transaction debugger and simulator. We plan to integrate this tooling directly into Walnut which will bring distribution, sustained use and recurring revenue to fund further development.

  • Already Completed Technical Exploration: We’ve already researched the monitoring framework in depth, focusing on the Ruleset SDK design. This work shaped our proposal to cover all key features — including cross-chain monitors and data persistence across executions. See Technical Exploration Document.

Please describe your proposed solution based on the above:

We propose to build a fully open-source monitoring framework (Apache 2.0) that allows developers to define, deploy, and manage blockchain-specific monitors.

Our proposal is highly inspired and influenced by our discussions with OP Labs infra team, their in-house monitoring implementation (link) and recently open sourced openzeppelin-monitor.

Features:

  • Real-time Monitoring: Continuously observe blockchain activity for defined events and transactions.

  • Custom Rulesets (Invariants): Define flexible logic to detect on-chain conditions and behaviors that matter to your system.

  • Cross-Chain Monitors: Initial support for monitoring SuperchainERC20 transfers and related cross-chain activity.

  • Data Persistence: Each monitor execution can store data in a DataBag, allowing context to be shared between executions.

  • Multi-channel Alerts: Send notifications through Slack, Discord, Telegram, Email, Webhooks, or custom integrations.

  • Web UI: Manage monitors, explore historical actions, and visualize trends through rich interactive charts. See mockups.

  • Extensible Framework: Easily extend support for additional chains, monitor types, and integrations.

We will also implement 17 initial monitors to provide a rich reference. There will be basic monitors, advanced, cross-chain as well as specific monitors to Uniswap and Aave. See this document for full list with detailed descriptions and pseudocode implementation.

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

Phase 1 (Months 1-2) – Core SDK & Action Integrations

  • Finalize spec for monitors, invariants, actions, and the config schema; review with OP Labs.

  • Implement TypeScript SDK primitives: data sources (OP RPC), evaluation engine, scheduling hooks.

  • Implement action connectors: Slack, Telegram, PagerDuty.

  • Provide sample monitors: ERC20 balances (including SuperchainERC20), Global Events and Fault proof withdrawals.

  • CI/CD, tests, docs, example repo; pilot on an OP test env and validate real alert delivery.

Deliverables: SDK v0.1 + docs, 3 action connectors, 3 sample monitors, pilot report.

ETA: December 2025

Phase 2 (Months 1-2) – Ruleset Framework & Reference Monitors

  • Build ruleset composition/validation (JSON/YAML schema).

  • Publish 17 reference monitors covering protocol-level invariants, including Uniswap V3 and Aave V3 reference rulesets (see full list with details).

  • Cross-chain validation via custom RPCs; performance testing and tuning.

  • Expand docs with canonical templates and troubleshooting.

Deliverables: Ruleset framework + schema docs, 17 reference monitors, Uniswap V3 & Aave V3 rulesets.

ETA: February 2026

Phase 3 (Months 1-2) – Orchestration Service & Web UI

  • Build monitor orchestration service (register/schedule/execute, alert routing, persistence of results).

  • Expose REST APIs for monitor lifecycle, alert history, and querying results.

  • Deliver Web UI for managing monitors, actions, and viewing state/alert history.

  • Multi-RPC support, basic auth, audit logs; packaging for self-host (Docker Compose/k8s yaml).

  • Internal acceptance with OP Labs; open-source release under Apache-2.0.

Deliverables: Orchestration service v1.0, UI v1.0, deployment manifests, full docs, acceptance sign-off.

ETA: March 2026

Please define the critical milestone(s) that should be used to determine whether you’ve executed on this proposal:

Milestone 1: Core SDK and Action Integrations

  • TypeScript SDK and configuration schema for defining monitors, invariants, and actions is created.

  • Basic monitor types (e.g., ERC20/SuperchainERC20 balances, Global events, Fault proof withdrawals) are implemented.

  • Integrations for Slack, Telegram, and PagerDuty alerts.

Milestone 2: Ruleset Framework and Reference Monitors

  • Framework for composing and validating complex rulesets (combinations of monitors and actions) is created.

  • 17 reference monitors demonstrating protocol-level use cases (for full list see this) are developed.

  • Flexibility of the framework across multiple OP Chains via custom RPCs (and multiple) is available.

Milestone 3: Web Service and UI

  • Build the monitor orchestration service (APIs for scheduling, execution, and persistence).

  • Web-based UI for managing monitors, alerts, and actions is created.

  • Historical data visualization and alert history view (leverage Grafana) is created.

Please list any additional support your team would require to execute this mission:

We do not require any additional support to successfully execute this mission. We are already in contact with the OP Labs DevOps team, who can provide early feedback for the project. That said, introductions to other developers who might find this useful — or feedback on our approach — is always welcome and appreciated.

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