Active source-verified ordinary-wallet Arbitrum exitWithdraw legacy Shell Ocean positions on Arbitrum
Check an Arbitrum wallet for reviewed legacy Shell Ocean ERC-1155 positions and inspect the complete three-transaction ordinary-wallet exit before signing.
- Protocol
- Shell Protocol Legacy
- Networks
- Arbitrum
- Settlement
- 90% user / 10% service fee
- Last reviewed
- August 30, 2026
What DeFiReclaim supports
Contract-level exit
The owning normal EOA first signs Ocean setApprovalForAll(Router, true), then one immutable Router exit transaction, and finally Ocean setApprovalForAll(Router, false), all through ordinary eth_sendTransaction requests. The exit consumes the complete selected Ocean token ID, executes the bound Shell pool path, unwraps the terminal asset and atomically transfers exactly 90% of the actual output to the user and 10% to DeFiReclaim. The final transaction removes the temporary global ERC-1155 operator approval.
Support scope
Only the retired legacy Ocean at 0xC32eB36f886F638fffD836DF44C124074cFe3584 on Arbitrum is in scope. Ethereum Shell v1 is deliberately excluded because its stablecoin route can only withdraw part of the position and its BTC route remains blocked.
Liquidity boundary
Every lookup pins one current Arbitrum block, reads the exact ERC-1155 balance and quotes the complete configured Shell path. A changed pool binding, failed quote, partial balance, output outside the signed bounds, non-EOA account or missing revoke step fails closed. No wallet inventory or per-position value is placed in the public registry.
Exit contracts and deployments
These public explorer links let users and automated systems inspect deployed bytecode, transaction history and deployment receipts.
Shell Legacy Ocean Ordinary-Wallet Router
0x57ab39d05ee7809dd08421f70eca29b8683c9694Shell Legacy Ocean
0xC32eB36f886F638fffD836DF44C124074cFe3584DeFiReclaim Treasury
0x793eca600e3216e39f438abd657eb514b2072e7fShell Protocol Legacy exit FAQ
Can I use a normal MetaMask or Rabby account?
Yes. The source-verified production route uses three ordinary eth_sendTransaction requests in a normal MetaMask or Rabby EOA: global Ocean operator approval, the exit, then the mandatory global operator revoke. Smart Account mode, EIP-7702 and wallet_sendCalls are not used.
Why are there three wallet transactions?
Shell Ocean uses one global ERC-1155 operator approval instead of a per-token allowance. The first transaction enables the reviewed immutable Router, The exit performs the full exit and atomic 90/10 settlement, and the third transaction immediately disables that operator again.
Does this include Ethereum Shell v1?
No. This integration is Arbitrum-only. The reviewed Ethereum v1 stablecoin path leaves part of the SHL position behind, while the BTC path cannot currently complete, so neither is included.