[Mission Request] decentralized alternative for contract attestation

Delegate Mission Request Summary: This is to get a decentralized alternative to contract attestation. Being able to deploy anywhere on OP Stack and have your contract attested would be a good example of interop promoting decentralization.

S6 [Intent 22](Season 6: Intents Ratification): Intent 1 - Progress toward decentralization

Proposing Delegate/Citizen: Jackanorak

Total grant amount: 40k

Should this Mission be fulfilled by one or multiple applicants:
One

How will this Mission Request help accomplish the above Intent?
The use-case is straightforward: if we intend to do retro funding and some governance across chains, thus increasing the utility of OP across them, we need this tooling to exist to make stuff easier. There is also enormous surface area for impact of this kind of attestation work more broadly across applications.

What is required to execute this Mission Request?
Plan for fully decentralized, open-source, cross-superchain ability to do contract attestation.

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

Milestones:

  • Spec definition, approved by grant council
  • MVP

Metrics:

  • Number of attestations
  • Number of chains using these

Impact:

  • Whether retro funding uses these attestations
  • Attestations occurring across chains
  • Number of contracts using attestations

Has anyone other than the proposer contributed to this Mission Request?
No

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 total amount of OP delegated from new addresses using the grantee’s protocol, as it helps assess the aggregated effect that this initiative has on the total votable supply. This metric was suggested by the Foundation and approved by the Grants Council.

1 Like

hey @jackanorak . May I know what is the expected difference with EAS? thank you

A North Star Metric has been added at the bottom of this Mission Request in an effort to enable the Collective to make data-driven decisions. By using a single metric for each Mission Request, the Collective is better able to evaluate the performance of all the Season 6 missions in a standardized manner, which will be critical when the Collective makes decisions about Intents, budgets, or other critical components of governance.

1 Like

Hello @jackanorak . Is it possible to provide a little more information what is the goal of this mission request? What is meant by “contract attestation”? And what exactly is the current status quo and it problems?

Hi @jackanorak, we are considering applying for this Mission Request, but we’d appreciate more details, specifically to better understand what type of contract attestations you’re referring to. We want to ensure our project aligns with your expectations.
Thanks in advance!

For clarity – this was much delayed, apologies.

ok, basically, this should work as an alternative to the rpgf contract attestation

currently there are two options:

  • manually verify and sign all the deployed contracts to claim their ownership (as a project)
  • use opensource observer

Both these options aren’t onchain, so technically the verification is done in a web-2 manner and stored in a centralized db

Mode solved a similar problem using their SFS Mode Docs deployment, they register the contracts they deploy and can claim any revenue from these.

Something similar to this would help—and it’s an improvement in UX over existing solutions.

2 Likes