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
  • Common Pitfalls in Solver Operation Generation
  • Solver Operation Configuration Issues
  1. Searcher Guides

Common Mistakes

Error is human

PreviousHelpersNextAtlas SDK's

Last updated 6 months ago

Common Pitfalls in Solver Operation Generation

Solver Operation Configuration Issues

1. Incorrect Solver Calldata Encoding

  • ❌ Encoding the Atlas solver call interface instead of the internal solver contract call

  • ✅ Should use: solverContract.interface.encodeFunctionData('solve')

  • Common error: Using Atlas ABI to encode the call instead of the solver contract's ABI

2. Outdated Contract Addresses

  • Dapp Control address not matching the deployed network version

  • Dapp signer address not matching the current environment

  • Atlas contract address mismatch between environments

3. Gas Configuration

  • Not accounting for gas overhead in the operation

  • Using incorrect gas price calculations for legacy vs EIP-1559 transactions

  • Not properly handling maxFeePerGas and maxPriorityFeePerGas for EIP-1559 transactions

4. Signature Related Issues

  • Using wrong signer for operation signing

  • Not handling signature recovery parameters correctly

  • Missing or incorrect chainId in signing process

5. Deadline Configuration

  • Setting too short or too long deadlines (deadline in block number)

  • Using timestamps instead of block number for deadlines

6. Bid Token Configuration

  • Using incorrect token decimals in bid amounts

  • Incorrect zero address usage for native token bids

7. Operation Hash Calculation

  • Incorrect user operation hash calculation for backrun transactions

  • Not properly handling legacy vs EIP-1559 transaction parameters in hash calculation

  • not using the opportunity transaction matching gas settings

8. Permission and Access Issues

  • Solver contract not properly authorized on Atlas

9. Value Transfer Issues

  • Incorrect handling of value field for native token transfers

  • Not accounting for bid amount in value field when required

  • Not sending the bidAmount to the executionEnvironment

10. Environment Specific Issues

  • Using production addresses in testing environment

  • Not properly handling different network configurations

  • Missing environment-specific parameter adjustments

Addresses & Endpoints