Lot impairment and recovery

Backing, component transfers and market liquidity are separate conditions. A fully backed Lot can lack an executable sale route; a transfer restriction or reserve shortfall affects different actions. Identify the affected condition before choosing an exit or recovery path.

Recovery is not insurance: it provides no guaranteed amount or payment date. No public recovery interface is available. See product availability.

This page covers fixed-Lot recovery. Upcoming Dynamic Lots represent current managed holdings.

Redeem a Lot on chain

Each Lot is its own contract on chain, and any holder can redeem it there directly, for the Lot's components, without the application.

The contract. Each Lot is one Basket contract. It is both the Lot token (an ERC-20 with 18 decimals) and the vault that holds the components, so the address of your Lot token is the address you call.

The function. redeem(uint256,address) (selector 0x7bde82f2), declared in the source as redeem(uint256 amount, address to):

• it burns amount of the caller's own Lot tokens, so no approval is needed;
• it sends each component to to, in the amount units × amount / 10^18, rounded down, where units is that component's figure from constituents();
• anyone holding the Lot token can call it. It has no owner check and does not consult the recovery ledger, so no incident state, operator or Safe can block it;
• it reverts if amount is zero, if the caller holds less than amount, or if any single component transfer fails. It never pays a partial recipe.

If one component cannot be transferred. redeemSkipping(uint256,address,uint256) takes a third argument, skipMask. Setting bit i leaves component i in the vault and sends the rest. The Lot tokens are burned in full, so the skipped share is given up: it is not paid later and not credited to you. Use it only when a component transfer is failing, and only for that component.

Walkthrough on the block explorer

Use rh-scan on Robinhood Chain (chain ID 4663) with the wallet that holds the Lot tokens. Contract read and write forms are available when the explorer has the contract interface.

1. Open the Lot. Search the explorer for your Lot token's address, or open it from your wallet's token list. Check the chain and the full address, not only the name or ticker.
2. Confirm it is a Lot. Open the Contract tab, then Read, and call factory(). A Lot created on Lots returns 0xe78b036BD6dA158CD61a3DAC3f67e18f62EcDDFd (BasketFactoryV15).
3. See what you will receive. Call constituents(): it returns the component token addresses and, for each, its units per 10^18 of Lot token. Call balanceOf(address) with your wallet address to read your balance in raw units (18 decimals: 1 Lot token is 1000000000000000000).
4. Redeem. On the Contract tab, open Write, connect your wallet and open redeem. The transaction is sent and signed from your own wallet, not by the explorer. Enter amount in raw units (18 decimals) and to as the address to receive the components, usually your own wallet. Submit and confirm in your wallet. The call needs a small amount of ETH for gas.
5. Check the result. The transaction logs show a transfer of each component from the vault and a Redeemed(by, to, amount, skipMask) event. Your Lot-token balance falls by amount.

If the Contract tab says no interface is available for the Lot, its source has not been matched on the explorer, so there is no form to fill in. The contract still accepts the call: send it from any wallet or tool that can call a contract function, using the function redeem(uint256,address), selector 0x7bde82f2, with the same two arguments.

A launch token is a separate contract. It is not a Lot token, and it cannot be redeemed for the Lot or its components.

Identify the failure

Situation	What it means for the holder
Healthy backing and transfers	Complete in-kind minting and redemption can proceed; trading also requires liquidity
Illiquid component market	An ETH route may fail while in-kind redemption remains executable
Stale or missing dollar reference	The valuation is unavailable; this alone does not prove lost backing or a transfer freeze
Component transfer restriction or shortfall	Normal operations that cannot deliver the complete recipe fail; affected issuance and new launches can be restricted
Temporary impairment resolves	Operations can resume after backing and transfers are verified, before recovery claims or distributions begin
Permanent recovery	Holders retain component-specific rights to available assets and later recoveries

An issuer API outage is not proof of an onchain freeze. A restriction affecting one recipient does not by itself establish that the entire Lot is impaired.

Recovery requires authorization

Only the 2-of-3 operations wallet can authorize incident transitions, recording reasons, scope and evidence; a timer cannot activate recovery.

Verified restart is possible before claims or distributions begin. Once either starts, the Lot stays in recovery and normal issuance cannot resume through that state. Direct redemption remains callable, succeeding only if every required transfer completes.

What a Lot holder keeps

Conversion burns the selected Lot tokens, pays transferable healthy components and records claims for affected assets. Healthy payments preserve those impaired-component claims.

Converted claims are wallet-bound and non-transferable. There is no claim market, automatic replacement or compulsory dollar payout. Unconverted Lot tokens retain their entitlements and transfer rules.

If Z becomes restricted in an X/Y/Z Lot, receiving X and Y preserves the holder's claim to later Z recoveries, without guaranteeing them. Track original tokens, converted claims and payments separately; the healthy-redemption formula does not determine every recovery payout.

Lot tokens inside locked launch liquidity

Pool-held Lots retain component entitlements under the principal lock. Recovery permits neither principal withdrawal nor direct distribution to launch-token holders. Those holders must obtain Lot tokens through an executable sale to have Lot redemption or recovery rights.

When an action fails

Check the error, component and receipt. Failed ETH routing does not prove lost backing; normal redemption returns every component or reverts.

Verify incident information through official links, preserve receipts and retain control of the entitled wallet.