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. Execution Base

Functions

  1. _availableFundsERC20() is used to check the approved balance of users and DApps to atlas that can be withdrawn via permit69.

  2. _transferDAppERC20() and _transferUserERC20() are functions that can be implemented by Atlas module developers in DAppControl to access the user or DApp funds referenced in _availableFundsERC20()

Module developers can access useful information about the atlas transaction by initializing an ctx struct in their DappControl and accessing these fields: bundler, solverSuccessful, paymentsSuccessful, solverIndex, solverCount, phase, solverOutcome, bidFind, isSimulation, `callDepth`.

  1. The _contribute()function allows actors to sponsor the gas of the transaction by donating ETH to the Atlas Escrow balance. This contribution to the balance is available first to bundlers, with the surplus going to solvers.

  2. The _borrow()function makes flash loans available from the Atlas Escrow balance. The balance must be repaid by the end of the Atlas transaction by the solver or the borrower.

PreviousExecution BaseNextReputation

Last updated 11 months ago