Active hybrid Ethereum exit routesWithdraw legacy Ribbon Finance vault positions
Check an Ethereum wallet for a reviewed Ribbon Finance V1 vault balance or matured V2 withdrawal. V1 uses ordinary MetaMask or Rabby transactions; V2 keeps its reviewed atomic MetaMask Smart Account route.
- Protocol
- Ribbon Legacy
- Networks
- Ethereum
- Settlement
- 90% user / 10% service fee
- Last reviewed
- August 30, 2026
What DeFiReclaim supports
Contract-level exit
For V1, the wallet first grants the immutable Router an exact full-balance approval and then signs the exit as a normal transaction. The Router calls the original withdraw function and atomically distributes actual output 90/10. Matured V2 withdrawals remain bound to the owning EOA and continue through the existing reviewed EIP-7702/EIP-7821 batch.
Support scope
Support covers four direct-withdraw V1 routes and eight V2 routes with already matured withdrawal mappings. New V2 requests in the current round and four treasury vaults that lack an ordinary permissionless user exit are excluded.
Liquidity boundary
Before signing, DeFiReclaim rechecks the V1 receipt balance and withdrawal quote or the V2 withdrawal round, shares and round price per share, then statically calls the original vault action. Current-round or failed routes remain hidden and cannot build a transaction.
Exit contracts and deployments
These public explorer links let users and automated systems inspect deployed bytecode, transaction history and deployment receipts.
Ribbon V1 Standard Wallet Router
0x4ebf9d401a5b53bd01fa1a116e395373d79cbe9cRibbon EIP-7702 Fee Collector
0xe66db69e18f229f55a8bd9e5199117d490e900e6DeFiReclaim Treasury
0x793eca600e3216e39f438abd657eb514b2072e7fRibbon Legacy exit FAQ
Does Ribbon V1 require a MetaMask Smart Account?
No. Each V1 position uses an exact approval followed by the exit through ordinary eth_sendTransaction in either normal MetaMask or Rabby. The Smart Account notice and consent gate are shown only for V2.
Why does Ribbon V2 still use a MetaMask Smart Account?
A matured V2 withdrawal mapping belongs to the original EOA, so the reviewed route must call completeWithdraw from that address and settle the 90/10 split atomically. V2 therefore keeps the existing MetaMask-only EIP-7702 flow.
Can DeFiReclaim complete a new Ribbon V2 withdrawal request?
Not immediately. A V2 request must already belong to a closed earlier round. Current-round requests depend on the legacy protocol rollover and are not shown as withdrawable routes.
Do the Ribbon exit contracts take custody of withdrawn assets?
No. The V1 Router atomically forwards 90% to the user and 10% to DeFiReclaim, then returns to its pre-call balances. For V2, the original vault sends output to the wallet and the immutable collector transfers only the disclosed fee inside the same atomic batch.