Active source-verified ordinary-wallet Ethereum exitWithdraw frozen dYdX v3 StarkEx positions
Check an Ethereum wallet for a positive dYdX v3 Escape Hatch position and review the exact four-transaction ordinary MetaMask or Rabby journey, 90/10 settlement and verified immutable Router before signing.
- Protocol
- dYdX v3
- Networks
- Ethereum
- Settlement
- 90% user / 10% service fee
- Last reviewed
- August 30, 2026
What DeFiReclaim supports
Contract-level exit
The owning EOA signs four ordinary eth_sendTransaction requests on Ethereum: verify the exact Merkle escape proof, finalize the escape into pending USDC, approve only the exact 10% service fee, and call the immutable Router. The Router withdraws the complete pending USDC directly to the user, transfers exactly 10% to DeFiReclaim, clears the allowance and retains no custody.
Support scope
Support is wallet-scoped and limited to a positive perpetual Escape Hatch position whose StarkKey is already registered to the queried EOA. The public registry contains only canonical route contracts and constants; it never publishes StarkKeys, proofs, position values, wallet inventories or route-to-wallet mappings.
Liquidity boundary
Every lookup obtains the current dYdX Explorer action and proof for the queried address, verifies the frozen StarkEx and registered owner on a fresh Ethereum block, and requires the full positive escape amount. The four transactions run sequentially on one network with no protocol wait or external-site step.
Exit contracts and deployments
These public explorer links let users and automated systems inspect deployed bytecode, transaction history and deployment receipts.
dYdX v3 Ordinary-Wallet Router
0x2910e855b4f58cef4c45836fe4bf278da833598ddYdX v3 StarkEx Perpetual
0xd54f502e184b6b739d7d27a6410a67dc462d69c8dYdX v3 Escape Verifier
0x626211c1e9bc633f4d342af99f4e8bc93f11f3ddUSDC Output Token
0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48DeFiReclaim Treasury
0x793eca600e3216e39f438abd657eb514b2072e7fdYdX v3 exit FAQ
Does dYdX v3 exit require a Smart Account or wallet_sendCalls?
No. The verified production route uses four sequential ordinary eth_sendTransaction requests from a normal MetaMask or Rabby EOA. It does not use Smart Account mode, EIP-7702, EIP-5792 or wallet_sendCalls.
Why are four transactions required?
The original frozen StarkEx requires the Merkle proof to be verified before the escape is finalized. Once the complete USDC amount is pending, an exact fee approval and one Router exit complete the atomic 90/10 settlement.
Does DeFiReclaim publish dYdX wallet or proof data?
No. The public registry is route-only. Wallet addresses are checked only on request, and StarkKeys, Merkle proofs, balances and candidate inventories are never included in public site assets.