Skip to content

Storage Layout

DISCLAIMER // NFA // DYOR

This analysis is based on observations of the contract bytecode. We are not smart contract security experts. This document aims to explain what the contract appears to do based on the code. It should not be considered a comprehensive security audit or financial advice. Always verify critical information independently and consult with blockchain security professionals for important decisions.

⊙ generated by robots | curated by humans

METADATA
Contract Address 0x1f2f10d1c40777ae1da742455c65828ff36df387 (etherscan)
Network Ethereum Mainnet
Analysis Date 2026-01-05

Overview

The Jared 2.0 MEV bot employs a stateless design - it does not use any storage slots. All operational parameters are passed via calldata, and the contract maintains no persistent state between transactions.

This is verified by querying the first several storage slots:

export ETH_RPC_URL=https://eth.llamarpc.com

cast storage 0x1f2f10d1c40777ae1da742455c65828ff36df387 0
# Returns: 0x0000000000000000000000000000000000000000000000000000000000000000

cast storage 0x1f2f10d1c40777ae1da742455c65828ff36df387 1
# Returns: 0x0000000000000000000000000000000000000000000000000000000000000000

cast storage 0x1f2f10d1c40777ae1da742455c65828ff36df387 2
# Returns: 0x0000000000000000000000000000000000000000000000000000000000000000

Storage Slots

SLOT VARIABLE NAME TYPE CURRENT VALUE PURPOSE
0 (unused) - 0x0 No storage used
1 (unused) - 0x0 No storage used
2 (unused) - 0x0 No storage used
... (unused) - 0x0 No storage used

EIP-1967 Proxy Slots

The contract is not a proxy. Standard proxy storage slots are empty:

SLOT (EIP-1967) PURPOSE VALUE
0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc Implementation 0x0
0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103 Admin 0x0
0xa3f0ad74e5423aebfd80d3ef4346578335a9a72aeaee59ff6cb3582b35133d50 Beacon 0x0

Why Stateless?

The stateless design provides several advantages for an MEV bot:

Gas Efficiency

  • No SSTORE operations (20,000 gas for cold storage writes)
  • No SLOAD operations for state reads
  • All data passed in calldata (much cheaper)

Security

  • No reentrancy vulnerabilities (no state to corrupt)
  • No storage collision risks
  • Simpler attack surface

Atomicity

  • Each transaction is fully self-contained
  • Failed transactions leave no residual state
  • No cleanup required between operations

Diagram

graph TD
    subgraph Traditional["Traditional Contract"]
        S1["Storage Slot 0: owner"]
        S2["Storage Slot 1: balance"]
        S3["Storage Slot 2: mapping"]
        S4["..."]
    end

    subgraph Stateless["Jared 2.0 (Stateless)"]
        E1["All slots empty"]
        E2["Data in calldata"]
        E3["Computed at runtime"]
    end

    CD["Calldata"] -->|"Contains all params"| Stateless
    Traditional -.->|"Not used"| X["❌"]

Hardcoded Values in Bytecode

While no storage is used, the contract does contain hardcoded addresses and values in the bytecode itself:

TYPE VALUE PURPOSE
Operator 0xae2Fc483527b8ef99eb5d9b44875f005ba1FaE13 Access control
WETH 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 Token wrapping
USDC 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 Stablecoin swaps
USDT 0xdAC17F958D2ee523a2206206994597C13D831ec7 Stablecoin swaps
Balancer Vault 0xBA12222222228d8Ba445958a75a0704d566BF2C8 DEX integration
Uniswap V2 Factory 0x5C69bEe701ef814a2B6a3EDD4B1652CB9cc5aA6f Pair computation
Uniswap V3 Factory 0x1F98431c8aD98523631AE4a59f267346ea31F984 Pool computation
V2 Init Code Hash 0x96e8ac4277198ff8b6f785478aa9a39f403cb768dd02cbee326c3e7da348845f Pair address calculation
V3 Init Code Hash 0xe34f199b19b2b4f47f68442619d555527d244f78a3297ea89325f843f87b8b54 Pool address calculation

These values cannot be changed without deploying a new contract.