Skip to main content

Prepare for mainnet launch

Time Sensitive - DIN AVS Mainnet Launch: November 14th, 2025

Operators must begin onboarding with their wallets immediately due to a 17-day operator allocation delay. October 27, 2025 is the latest date to create your wallets and onboard in time for mainnet launch.

Critical: Create and register TWO wallets (primary + backup) with EigenLayer. If your primary wallet encounters issues during onboarding, you won't have time to activate a new wallet before the deadline.

Immediate action items

Perform the following steps before the October 27, 2025 cut-off for mainnet launch:

  1. Create TWO new wallets (primary + backup):

    • Generate two new externally owned account wallets. Refer to the wallet setup options.
    • Each wallet must not be used with any other EigenLayer Autonomous Verifiable Service (AVS).
    • Secure your private keys for both wallets.
    • Document both wallet addresses.
    • Why two wallets? Due to the 17-day EigenLayer activation delay, having a backup wallet ensures you can still meet the mainnet launch deadline if any issues occur with your primary wallet during onboarding.
  2. Secure ETH for both wallets:

    • Minimum 1 ETH per wallet (EigenLayer recommendation).
    • Transfer to both operator wallets.

    Specific stake amounts will be calculated during Step 2.

  3. Register BOTH wallets with EigenLayer:

    • Access the DIN app.
    • Complete only Step 1 with your primary wallet.
    • Complete only Step 1 again with your backup wallet.
    • This ensures both wallets will be ready by mainnet launch in case you need to switch.
    note

    Only Step 1 (EigenLayer registration) is needed now. Steps 2-5 will be completed after the DIN contract is deployed on mainnet.

Configuration steps

Before starting Step 1 registration, configure the DIN app for mainnet:

  1. Switch MetaMask to Ethereum Mainnet:

    • Open MetaMask and switch from Sepolia to Ethereum Mainnet network.
  2. Select DIN Mainnet configuration:

    • In the DIN app, go to AVS settings.
    • Select DIN Mainnet from the AVS configuration dropdown.
  3. Verify network settings before registration:

    • When you open the TXTX page for Step 1, confirm Mainnet is displayed.
    • Ensure your wallet shows the correct mainnet address and ETH balance.

Wallet setup options

MetaMask Required for TXTX Onboarding

You must use MetaMask wallet when connecting to the DIN app for AVS onboarding. TXTX is only proven to work reliably with MetaMask, and we strongly recommend operators use MetaMask for their onboarding TXTX wallet interface. While you can store your keys in a hardware wallet, you must access them through MetaMask during the onboarding process. Onboarding will fail if you use other wallet connection methods (WalletConnect, Coinbase Wallet, etc.).

Use one of the following wallet options:

  • Option 1: Hardware wallet (recommended)

    • Use Ledger or Trezor
    • Create new derivation path
    • Document recovery phrase securely
  • Option 2: Software wallet

    • Higher risk profile
    • Use only if hardware unavailable

Prepare infrastructure

While completing onboarding, ensure your infrastructure is ready:

  • Set up RPC nodes for chosen networks (operator sets).
  • Configure high availability.
  • Implement monitoring.
Initial period guidance

During the initial period of the DIN AVS, DIN admins will recommend which operator sets you should join based on your DIN Router traffic history. This helps ensure optimal network coverage and performance using observed traffic patterns.

Mainnet and testnet differences

Testnet and mainnet have different risk, funding, and activation profiles. Use Sepolia testnet to validate your setup end to end with test funds, then move to mainnet when you are ready to stake real assets and accept slashing risk.

TestnetMainnet
WalletAny EOA wallet (MetaMask recommended)Two new EOA wallets (primary + backup), dedicated to DIN AVS
Wallet connectionMetaMask required for onboardingMetaMask required for onboarding
Wallet age requirementNoneBoth wallets must be registered on EigenLayer for 17 days before activation
FundingTestnet ETHETH
Allocation delayCustomizable (0 default)Customizable (0 default)
SlashingNo real lossReal economic risk
PerformanceRelaxed service level agreementsStrict service level agreements

Common mainnet pitfalls

Fatal mistakes

  • Using a non-MetaMask wallet connection

    Fix: Always connect through MetaMask when onboarding in the DIN app. You can use hardware wallets for key storage, but connect them through MetaMask. Other wallet providers (WalletConnect, Coinbase Wallet, etc.) will cause onboarding to fail.

  • Reusing a wallet from another AVS

    Fix: Use a fresh, DIN-dedicated EOA for mainnet. Do not reuse keys/accounts tied to any other AVS.

  • Wrong network selected during registration

    Fix: Before starting Step 1, switch MetaMask from Sepolia to Ethereum Mainnet AND select DIN Mainnet in the app's AVS configuration. Verify Mainnet is displayed in the TXTX page before proceeding. Registering on the wrong network wastes the 17-day activation period.

Costly errors

  • Not creating a backup wallet

    Fix: Create and register two wallets with EigenLayer. If your primary wallet encounters issues during onboarding (e.g., transaction failures, wrong configuration), you won't have time to create and activate a new wallet before the November 14th deadline due to the 17-day activation period.

  • Starting after October 27th, 2025

    Fix: Plan for EigenLayer's protocol activation delay (17 days). Start by October 27, 2025, to be active by November 14, 2025.

  • Insufficient ETH for gas

    Fix: Pre-fund your operator wallet with buffered ETH (gas + safety margin). Monitor fees; top up before critical steps.

  • Not using hardware wallet

    Fix: Prefer Ledger/Trezor or MPC, enforce approvals/policies, and restrict who can sign mainnet transactions.

  • Poor allocation strategy

    Fix: Set the default allocation delay to 0 (see Step 3) unless you need an operations buffer; size and place stake where you can meet SLAs, and avoid over-concentration or thin coverage.