Atlas Draft
  • What is Atlas?
    • Overview
  • Roles
    • Roles in Atlas
      • Operations Relay (OR)
      • Originator
      • Auctioneer
      • Bundler
      • Solver
  • Atlas Infrastructure Overview
    • Operations Relay
    • SDK
  • Atlas EntryPoint Concepts
    • Permit69
    • atlETH
  • Integrating Atlas
    • Integration Overview
    • Integrating a frontend or API
    • Integrating a smart contract protocol
  • Building Atlas Modules
    • DappControl
      • Entities
      • Required Functions
      • Optional Functions
    • Execution Base
      • Functions
    • Reputation
    • Ex-Post Bids
  • Resources
    • Whitepaper
    • Source code
Powered by GitBook
On this page
  1. Atlas Infrastructure Overview

Operations Relay

PreviousSolverNextSDK

Last updated 11 months ago

Atlas is infrastructure-agnostic; each app may choose how the User Operations and Solver Operations are aggregated. Examples include:

  1. On Chain: When gas cost is not an issue, Solver Operations may be sent on-chain, and then aggregated by any party, including a smart contract.

  2. On Another Chain: Solver Operations may be posted and aggregated on another chain, and the output can be used to settle the atlas transaction on the settlement chain.

  3. Service Providers: When Atlas is launched, service providers like BloXroute's BDN and others will support the aggregation of User and Solver Operations for rapid bundling.

  4. SUAVE: Once live, Operations can be sent to the SUAVE network, bundled into a transaction by the SUAVE Atlas implementation, and then made available for use by bundlers.

If you are interested in integrating a service provider as an OR you can check out the specs for doing so and if interested in learning more about becoming an ops relay. We also have a of an OR in Go that we are working on (pre-alpha).

here
contact us
reference implementation