Active MetaMask Smart Account-only Ethereum exitWithdraw Kinto shutdown claims on Ethereum
Check an Ethereum address for a live, fully funded Kinto shutdown claim and review the MetaMask Smart Account-only atomic exit before signing.
- Protocol
- Kinto Shutdown Claims
- Networks
- Ethereum
- Settlement
- 90% user / 10% service fee
- Last reviewed
- August 30, 2026
What DeFiReclaim supports
Contract-level exit
The legacy claim can execute only from its owning address. After wallet_getCapabilities confirms MetaMask atomic support, the owning MetaMask Smart Account submits five linked calls: Collector begin, Kinto acceptAndClaim, an exact temporary USDC approval for 10%, Collector finish, and approve(0). wallet_getCallsStatus confirms the atomic result. The user keeps exactly 90%, the treasury receives exactly 10%, and the Collector finishes with zero USDC custody and zero allowance.
Support scope
Only an unclaimed Ethereum userInfos entry that is fully covered by the claim contract's current USDC balance is eligible. The public registry contains the reviewed contract route only; wallet inventories, balances and route-to-wallet mappings are never published. Rabby, ordinary MetaMask eth_sendTransaction flows, other delegation targets and contract accounts fail closed before exit RPCs.
Liquidity boundary
The Kinto claim contract is currently underfunded in aggregate, so queue order matters. Every wallet lookup pins a fresh Ethereum block and rechecks the exact claim amount, claimed flag, account code, Kinto USDC and owner bindings, direct acceptAndClaim call and enough current contract cash for that individual claim. Any changed or underfunded state fails closed.
Exit contracts and deployments
These public explorer links let users and automated systems inspect deployed bytecode, transaction history and deployment receipts.
Kinto Shutdown Claims
0x47a56a558892de88367108183df913852617e77cUSDC
0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48DeFiReclaim Kinto Collector
0x72d19cbc61441395157689de4a1c1559d6f3c256DeFiReclaim Treasury
0x793eca600e3216e39f438abd657eb514b2072e7fKinto Shutdown Claims exit FAQ
Why is this route MetaMask Smart Account-only?
Kinto binds both the claim and its complete USDC payout to msg.sender. Ordinary independent transactions would release all USDC to the user before DeFiReclaim could enforce its 10% fee. MetaMask Smart Account mode keeps the five reviewed calls atomic from the owning address. Rabby and ordinary MetaMask transactions are therefore unsupported and blocked before any exit request.
How many confirmations or return visits are required?
A wallet already using MetaMask Smart Account mode signs one atomic exit request. MetaMask may first request one additional confirmation to enable Smart Account mode. There are five linked calls, no protocol wait, no return visit, no external site and no exit-time network switch. MetaMask may show Unnecessary permission or Your assets may be at risk for the reviewed batch; stop if the network, recipient, amount or warning differs from the DeFiReclaim disclosure.
What happens if the Kinto claim contract lacks enough USDC?
DeFiReclaim does not build a transaction. The wallet-scoped check re-reads the claim and contract cash at one current Ethereum block and requires enough USDC for that complete individual claim. A partial withdrawal or voluntary later fee is never offered.