Where to Start as a dApp

This document summarizes the steps needed in order for a dApp to integrate with Atlas.

1. Develop and Deploy a dApp Control Contract

This is the most crucial step. A dApp is required to deploy a smart contract that defines its rules and desired behaviors. This contract is called the dAppControl contract (and commonly referred to as the module).

For many use cases, dApps can reuse one of the existing modules. See the bootstrapping a module guide for more information. For dApps requiring a higher level of customization, a new dApp control will need to be written. See the creating a module guide for a detailed breakdown of the steps that need to be taken.

In any case, the FastLane team can assist the dApp in selecting/designing and deploying a module.

2. Update the dApp Frontend

This step applies for dApps with a frontend. The actions generated by the dApp's users will need to be packed into Atlas user operations and go through the Atlas auctioneer for auctioning. This is achieved by using the Atlas typescript SDK, and requires minimal changes.

3. What about Solvers?

Typically, the Atlas solver network is large enough that a new dApp integrating with Atlas does not have to worry about onboarding its own solvers. That being said, dApps are always welcome to do so. Solving on Atlas is permissionless, and anyone can get started at any time.