Skip to main content
The default path is agentic. Open primev.xyz/ai, install the mev-commit-opt-in skill, and ask Claude, ChatGPT, or Grok to register your keys into the mev-commit validator coalition. Hub-true keys are one signal across many validators. Opt-in is membership, not extra block revenue from a live commitment market. The old dashboard is deprecated. Any mev-boost relay set is fine. Why this exists: why opt in. Full method detail lives on the agentic opt-in page.
1

Install the skill

2

Give the agent your keys

Upload a .txt or .csv of BLS pubkeys (0x + 96 hex, comma or newline separated). Batch 40 to 60 keys per transaction. Confirm the first and last key and the count before anything is sent.
3

Ask it to opt in

Pick the method you already use:
  • Vanilla: Opt these validator pubkeys into mev-commit with simple staking
  • EigenLayer: Register these BLS keys on the mev-commit AVS as this pod owner
  • Symbiotic: Register these keys on the mev-commit Symbiotic middleware
The agent uses your Ethereum RPC and wallet. It simulates, sends, waits for the receipt, then checks ValidatorOptInHub.Then finish the steps in Complete the registry. Do not stop after the send.
4

Confirm the registry

After the receipt, the agent must call Hub areValidatorsOptedIn on the full set.Success is every key true, plus a report of method, key count, tx hash, and an Etherscan or Hoodi link. If any key is false, treat the job as unfinished.Then ask: Are these pubkeys opted in, and what is my total on-chain ETH stake?
Hub true on each key means registration succeeded. Keep your existing relay set.
Path pages if you want cast instead of an agent: vanilla, EigenLayer, Symbiotic.

​
Bidder or provider node

Running a p2p bidder or provider node is a different path. Create a keystore, bridge ETH to the mev-commit chain, then start the binary from releases.
Then see bidder best practices or provider registration. System notes: system requirements.