Polygon FastLane
  • What is Polygon FastLane?
    • Overview
    • Design Principles
    • Components
    • Component Diagram
  • Getting Started as a Validator
    • Getting Started as a Validator
    • Connecting to a FastLane Sentry Node
      • Finding Your Enode Address & Peer ID
      • Adding FastLane as a Static Peer
    • Patching Your Sentry Nodes With The FastLane Patch
      • Installing from source
        • Patch Download
        • Patch Installation
      • Installing from packages
  • Withdrawing Validator Revenue
    • Validator Vault
      • Connect an Eligible Wallet
      • Revenue Redemption (withdrawal)
  • Searcher Guides
    • Getting Started as a Searcher
      • Solver Call Data
      • Submission Methods
      • Migration Guide for Searchers
    • Bundles (Backruns)
      • Bundle Format
      • Bid Submission
      • Bundle Requirements
      • Full Example
      • Subscribe Events
    • 4337 Bundles Integration Guide
      • Overview
      • How it works
      • RPC Reference
      • Examples
    • Searcher Contract Integration
      • Safety Considerations
      • atlasSolverCall
      • Direct Implementation
      • Proxy Implementation
      • Solver Concepts
      • Altas Bonding Concept
      • Bond atlETH
      • Estimating Solver Gas Charges
    • Addresses & Endpoints
    • Helpers
    • Common Mistakes
    • Atlas SDK's
  • Tools and Analytics
    • FastLane Bundle Explorer
      • Features Overview
      • Key Components
      • Usage Example
      • Error Codes & Troubleshooting
  • Key Concepts
    • Transaction Encoding
  • INFRASTRUCTURE
    • Health Status Endpoint
  • Reference
    • Relay JSON-RPC API
    • Relay REST API
    • Glossary of Terms
Powered by GitBook
On this page
  • Overview
  • Key Processes
  • Atlas
  • Execution Process for Atlas Solver
  • Example Solver Contract
  1. Searcher Guides

Searcher Contract Integration

PreviousExamplesNextSafety Considerations

Last updated 6 months ago

Solver deploys their Solver Contract that implements ISolverContract

Overview

  • The interactions between the Atlas Contract and the Solver Contract in the execution of MEV strategies are vital for successful transactions in the FastLane network. The process involves several key steps to ensure efficient and timely execution.

Key Processes

  1. Payout Mechanism: The Solver Contract reimburses the Atlas Contract by returning the BidAmount after the successful completion of a task.

  2. Execution of MEV Strategies: Utilizing the solverOpData, the Solver Contract deploys specific MEV strategies. This involves the internal execution of the solver() function.

  3. Initiation by Atlas: The Atlas Contract triggers the execution by calling the atlasSolverCall function on the Solver Contract.

  4. Bundle Submission:

    • The FastLane Auctioneer submits the victorious bundle directly to the validator via the Atlas Contract.

    • The FastLane Relay ensures the bundle is efficiently propagated to the FastLane Auctioneer.

  5. Network Integration: The Solver submits its bundle to the FastLane Relay Network to facilitate the overall process.

  6. Deployment of Contracts: To partake in this ecosystem, Solvers must deploy their own Solver Contracts, incorporating the ISolverContract interface, to implement the necessary operations effectively.

Atlas

Atlas is a specialized Execution Abstraction protocol created by FastLane Labs to streamline the deployment of application-specific backrun auction processes. It enhances transaction efficiency and optimizes value retention in blockchain systems.

Execution Process for Atlas Solver

Atlas Solver Execution - Core Flow:

  1. Security First

  • Validates solver is bonded

  • Validate signature for solverOperation

  1. Execution

  • Atlas calls solver through atlasSolverCall

  • Solver executes MEV strategy using calldata

  • Must implement atlasSolverCall function

  1. Payment

  • Solver must pay specified bidAmount back to Atlas

  • Atlas will try each solver until bid is paid

Example Solver Contract

For our sample solver contract, we suggest keeping the logic minimal. Implement an additional function to manage the MeV (Miner Extractable Value) strategy. Atlas will loop through each solver's solution, ordered by their bidAmount.

Searcher can choose how they want to implement their solver contract.

Two examples:

1) Direct Method

2) Proxy Method

Implement MEV strategy inside the contract which implements the ISolverContract interface
Implement MEV strategy external to the contract which implement the ISolverContract interface