Skip to main content

Relay Mining

warning

TODO_DOCUMENT(@Olshansk): This is just a placeholder. Use the relay mining presentation and the relay mining paper as a reference for writing this.

Introduction

tl;dr Modulate on-chain difficulty up (similar to Bitcoin) so we can accommodate surges in relays and have no upper limit on the number of relays per session.

Relay Mining is the only solution in Web3 to incentivize read-only requests and solve for the problem of high volume: how can we scale to billions or trillions of relays per session.

This complements the design of Probabilistic Proofs to solve for all scenarios.

Relay Sessions

Sessions effectively group relays into time-wise batches. During each session, Applications and/or Gateways can submit relays to one or more of the Suppliers in the current session for servicing.

Sovereign Application

An Application can act as a "soverign application" (i.e. its own Gateway). In this case, the ring used to sign relay requests is constructed only from the Application's public key.

See: Legend > Sequence Diagram

Delegated Application

An Application can also be delegated to one or more Gateways. In this case the ring used to sign relay requests is constructed from the Application's public key and the public keys of the all Gateways it is delegated to at the start of the session in question.

See: Legend > Sequence Diagram

Legend

Sequence Diagram