MVP Relayer Tracking Issue

[evan-forbes]

Summary

The QBG is significantly simpler than the normal gravity bridge, and can therefore fit into a significantly simpler design. Notably, since the bridge is only one way, it only requires one or more relayers.

Core

• Create an RPC endpoint for DataCommitment #620

App

• Copy over portions of the gravity module #197
• Add a parameter that indicates the frequency for which the validators are expected to sign DataCommitments #198
• Add MsgSubmitDataCommitment and corresponding functionality #199
• Document the new qgb functionality #217

QGB

• Remove unused functionality #327
• Modify the relayer to also query for and submit data commitments #328
• Orchestrator changes for new contract blobstream-contracts#9
• Write ADR for MVP of the QGB

Even though the gravity bridge supports certain types of slashing, I didn't include this in MVP as it is not strictly necessary.

[evan-forbes]

I think we can close this imo. We continue to write specific ADRs which are the only tasks left, and then we can write specific issues for the new relayer design that are tbd