Skip to main content

Common Mistakes

Solver operation arrives too late​

If the solver operation arrives after the auction duration has elapsed, it will not be included in the auction. The query API will communicate error "solver operation not found".

Not enough bonded atlEth​

Read the bonding guide to learn how to bond atlETH. This error will be communicated in the query API call.

Solver operation signer is different from the owner of Solver Contract.​

SolverBase (https://github.com/FastLane-Labs/atlas/blob/main/src/contracts/solver/SolverBase.sol) has an owner and the solver operation will revert if the signer is different from the owner. Query API will communicate error SolverOpReverted if this is the case.

Incorrect solver signature​

The solver signature is an EIP 712 signature. The following domain should be used.

{
    name: "AtlasVerification",
    version: "<version>", // Version of the Atlas Verification contract
    chainId: 1, // chain id
    verifyingContract: "<atlas_verification_address>", // Atlas Verification contract address
}

An incorrect signature will be communicated by the query API.

Incorrect Bid Token​

The bid token is described in the dapp control contract (userOperation.control). If marked to address(0), the bid token is ETH (chain's native token). Paying the execution environment with the wrong token will result in a SolverOpReverted error which will be communicated by the query API.

A reverting solver operation​

If the solver operation reverts for any reason, the query API will communicate error SolverOpReverted.