Current deployment - Nullark

The SDK currently pins one real MegaETH testnet deployment. Mainnet lookup stops until a real deployment is added; the package never substitutes testnet addresses for mainnet.

This is the MegaETH testnet deployment pinned by the current SDK. Mainnet deployment and an approved relayer endpoint are still pending.

Field	Current value
Network	MegaETH testnet
Chain ID	`6343`
RPC	`https://carrot.megaeth.com/rpc`
Pool	`0x9647AD5413ea670658C130CA4A30ee880F3F7874`
Pool deployment block	`0x000000000000000000000000000000000000000000000000000000000187c258`
Merkle tree depth	`20`
Withdrawal fee	`33` bps (0.33%)
Maximum withdrawal fee	`100` bps (1.00%)
Deposit selector	`0xca8f0370`
Withdrawal selector	`0xb942ca5e`

Contracts

Role	Address
Pool	`0x9647AD5413ea670658C130CA4A30ee880F3F7874`
Deposit verifier	`0x98b6850b11940410625d87bf7d5c6397d12b0db9`
Withdrawal verifier	`0x70DC1e79Ed9d17d6C21A73263b78e7e61d9C0daB`
Deposit verifier adapter	`0x43163cCd97Dacab3a5dd935e869775F5b80DA544`
Withdrawal verifier adapter	`0x9652aF4CB9170E19d2A8A1E5685AD858B2Cc4a30`
Poseidon2	`0xe272B7bf648D5780f3f435335a7f0f507a26c4C4`
Poseidon6	`0x6C9630223B06124Dd02C5B7b5ce8a7C197f97410`
Fee controller	`0x538aE9B8488DADea96b9C19181ff6F919d640Df6`

Read it as one object

Chain ID, pool, verifiers, adapters, fee policy, selectors, and proving files belong to the same deployment. Copying one address into another runtime can make a proof or transaction target the wrong system.

Published fact	What it confirms	What still needs checking
Address	Expected contract location	Deployed bytecode and initialization
Bytecode hash	Expected code identity	Roles, current state, and operations
Artifact hash	Exact proving-file bytes	Circuit soundness and setup provenance
Fee	Package default	Fresh onchain value before proving

The current SDK pins the published MegaETH testnet runtime. Mainnet deployment and an approved relayer endpoint remain pending; Published status tracks them.