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. Building Atlas Modules
  2. DappControl

Required Functions

The DAppControl contract must define the following functions:

  1. BidFormat: This function defines the base currency (or currencies) of the auction.

  2. BidValue: This function defines how to rank bids so that they may be sorted by the auctioneer.

  3. AllocateValue: After a Solver's operation is executed successfully, this function is called to allocate any value that has accrued to the Execution Environment. It is completely customizable. For instance, they may opt to use a portion of the MEV to refund the bundler's gas cost, the winning solver's gas cost, allocate another portion to offset the impermanent loss of the protocol's liquidity providers, and use the remaining portion to purchase that protocol's token for the originator.

PreviousEntitiesNextOptional Functions

Last updated 1 year ago