[Mission Request] - Crosschain alert monitoring

Governance Fund Missions šŸ¹
,
1

Delegate Mission Request Summary: Products built on top of Interop require alerting and monitoring for messages/transactions leaving their canonical chain. This is critical if we want to approach serious teams interested in products requiring superior functionality, security, and UX to build crosschain protocols servicing the Superchains.

S6 Intent 42: Please list the Intent your Request aligns with here

Proposing Delegate/Citizen: Delegate name/pseudonym, linked to delegate profile

Total grant amount: 60k OP

Should this Mission be fulfilled by one or multiple applicants: Up to two for now

How will this Mission Request help accomplish the above Intent?

The guiding hypothesis is that just like Fault Proofs are a bottleneck for capital to onboard onto Superchain, fully functional interop is a bottleneck for developers to generate true crosschain projects. OP Mainnet has lacked a guiding identity since the proliferation of new chains on Superchain, but one area will forever reside within OP-owned chains: protocols and tokens that are inherently crosschain, those that require a neutral positioning to fully service the Superchain. This tooling is a step in that direction.

In effect, this is a classic dev experience request. Currently such tooling is either very expensive, limited in functionality, or limited in chain coverage. Developers will enjoy the peace of mind and added value when adopting OP Stack / Superchain for their new products, and they will be more enabled to enhance crosschain services.

What is required to execute this Mission Request?

Tools that help teams track the following:

  • Whether interop messaging is down or paused
  • Whether interop messages have delays or are suffering degraded performance
  • Whether interop messages didnā€™t fulfill and require active intervention
  • Core metrics
    • latency between sender/receiver chains
    • gas usage of the sender/receiver, ideally aggregated at a project/layer level natively (i.e., we should not rely on external tools that might refuse or delay the onboarding/indexing of new chains)
  • Health alerts
    • Whether an event is issued and didnā€™t arrive
    • Whether an event should not have occurred
    • Whether an event is expected

How should governance participants measure impact upon completion of this Mission?

  • Milestones:
    • If an adapted product that already exists, milestones should track launch and outreach to users.
  • Metrics: Metrics should track the performance of the product, type I and II errors in reporting relative to accurately tracked events, and adjustments in response to user / governance requests.
    1. Number of active developer addresses interacting with granteeā€™s contracts (may have to be adapted depending on how onchain a product will be)
  • Impact:
    • Number of protocols making active use of this product
    • New Superchain protocols using this product within a month of Launch

Has anyone other than the proposer contributed to this Mission Request? Stas from Velodrome contributed to this. Itā€™s a clear ask from a user of Superchain.

3 Likes
2

hey @jackanorak ! remember that the MR proposal must be included in this forum post.

3

For the metrics team to be able to compare multiple approved applicantā€™s success in this mission request we need you to propose only one metric from this table as the Northstar:

  1. Number of addresses voting for the first time
  2. Number of addresses delegating for the first time
  3. Total amount of OP delegated from new addresses using the granteeā€™s protocol
  4. TVL in the granteeā€™s protocol
  5. Number of transactions emitting event logs
  6. Number of active addresses interacting with granteeā€™s contracts
  7. Total amount of gas fees generated from granteeā€™s contracts
  8. Percentage of retained active addresses interacting with granteeā€™s contracts
  9. DAA/MAA ratio
  10. Number of testnet transactions emitting event logs
  11. Number of active developer addresses interacting with granteeā€™s contracts
1 Like
4

Itā€™s there, just not embedded

5

GM! I would also recommend adding the full question and paragraph because it makes it easier for others to find the information hehe for example:

Which metric will the success of this Mission Request be evaluated against?

The North star metric against which this Mission Request should be evaluated is TVL in granteeā€™s protocol as this Mission Request plans to grow the amount of TVL on the Superchain via the migration of more RWAs and YBAs to Optimism.

1 Like
6

@jackanorak Is this assuming the OPā€™s latest interop hardfork is used? As far as I know, it is not yet online. If not, I donā€™t know what service is being listened to here. How these metrics could captured?

7

Tagging @op_julian to let him know this MR is closed as the budget was fully allocated at the end fo Cycle 29.