Follow the next asset, the next permission and the first deadline. Staking withdrawal, issuer redemption and a market sale are not interchangeable exits.
Research examined 17 October 2026 · Historical conversion occurred 7 October, 05:44:35 UTC · Last account endpoint: 16 October, 02:58:59 UTC · Other cases retain their dates · Complete funded recovery remains partial
Start with the asset that can actually leave your position. A transferable USDe token, an earning sUSDe share, a fixed staking claim and a lender’s receipt are different claims. None should silently become “one bank dollar tomorrow.” The route determines who must pay, which permissions apply and who bears a delay. Claim definitions and published terms.
A borrower’s funding has to arrive before the queue can help
Time-ordered mechanism, not a real account. One day was the observed staking duration at Ethereum block 26,005,156 (18 September 2026, 15:02:59 UTC); it is not a complete cash-delivery time. A free-share sale is an alternative, not completion of the cooldown. Claim mechanics and ordered example.
Which claim do you have?
A position’s next transition—not a promise that the transition will execute.
Position
Next transition
First consequence
Plain USDe
Sell to a funded buyer, or redeem through the issuer only with the required eligibility and service access.
The holder bears market discount, unavailable access and the underlying backing risk.
Free sUSDe
Sell the unpledged shares, or begin cooldown and later claim USDe.
The staker bears share-sale discount, lower rewards and withdrawal constraints.
USDe in cooldown
Meet the recorded release condition and submit the unstake transaction.
The queued amount is fixed USDe. The burned shares no longer exist to earn or sell.
Collateral with debt
Obtain the debt asset or sufficient other collateral before releasing the pledged asset.
A borrower can face liquidation before staking or issuer redemption can fund repayment.
Lending or vault receipt
Withdraw available loan assets or wait for repayment / liquidation through the relevant market and allocation.
The supplier can face illiquidity or residual bad debt without holding USDe directly.
PT, YT or venue account
Follow the exact wrapper, maturity, account and output rules.
A principal label or account credit does not remove the underlying or operational exit risk.
The foundation’s deeper cases were direct sUSDe on Aave and USDe/USDC on Base. The 27 September comparison identified the active November PT and its payout units; 28 September added sized native sUSDe-output quotes. The 2 October comparison joins exact quantities through a cross-block indicative final USDC leg. The 4 October continuation adds matching fixed-block alternatives, while actual financing and waiting remain unresolved. The prior dated chapters are unchanged.
Who received the payment—and who supplied it?
Evidence examined 17 October; transaction occurred 7 October 2026 at 05:44:35 UTC. The historical conversion now connects DAI delivery, DAI-to-USDS substitution and USDT settlement to the borrower’s already recorded cash receipt. Actual delivery is stronger evidence than a quote, but it is not a complete account of every upstream payer.
Recipient, payer and cost bearer need different evidence
Interpretation of the 7 October event, examined 17 October. The published SellGem field identifies the DAI recipient. It does not complete the initial USDC transfers or identify who provided the small additional DAI amount. Own debt service and outside execution expenses are separate. PSM field meaning · Recorded quantities.
The published PSM event’s owner field identifies the DAI recipient, not the beneficial owner of every USDC unit used upstream. The acquired next DAI input is 0.000000180475496719 DAI larger than the preceding delivery. That economically tiny difference remains unattributed; it is not called a fee or sponsor contribution.
10,001.640594 USDT received plus 4.688632 USDT of own cash equals 10,006.329226 USDT of debt service. The own contribution is not a fee; principal-versus-interest allocation is unestablished. Zero DAI fee in one conversion and a six-parts-per-million swap rate do not establish the complete gas, reimbursement or borrower expense.
The temporary 10,000-USDC principal returned using new persistent USDC borrowing. That borrower receipt and provider repayment do not settle the last creditor. The inherited October 16 endpoint still carries USDT and USDC obligations with positive accepted-value headroom; no new current state or final payoff is asserted.
Settling debt and delivering cash are different transitions
16 October, 02:58:59 UTC · Ethereum block 26,202,255. The selected Aave account still owes USDT and USDC. Its directly owned corresponding aUSDT and aUSDC balances are both zero. That is a specific matching-claim ownership screen, not an assessment of all beneficial-owner resources. Exact owned-resource comparison.
The same debt reduction can have a different cash effect
Symbolic comparison, not a transaction or a new reserve balance sheet. Ignore contemporaneous accrual, rounding and external charges only to isolate the two mechanisms. Both satisfy Δ(cash + receivables − supplier claims) = 0. A public source branch is not deployed-route assurance. Mechanisms, source scope and entitlement.
The new history adds a qualified ordinary-payment result. Two successful Pool filters cover blocks 26,196,048–26,202,255, returning no matches. The beneficiary/owner field includes documented repayment in either cash or aToken mode, so it is not merely a search for payments initiated by the debtor. Liquidation-user and token histories were not obtained. Neither the older gap nor these other categories becomes empty by inference. Coverage and provider limits.
The conditional ledger uses p in one owed denomination. Cash service adds p to the reserve and removes p of receivables. Eligible same-reserve claim cancellation removes p of receivables and p of supplier claims without adding cash. Both may discharge debt; the required resource, admission and final records still matter. No full cancellation, sufficient claim acquisition or funded recovery is observed here.
A funded purchase of a matching claim could change the path. If the purchase itself is financed, the new creditor still needs repayment. The historical temporary-principal return and 4.688632-USDT own debt service are not that future obligation’s settlement or an all-in expense result. The principal-versus-interest split of the own service remains unestablished. Historical cash, replacement debt and expenses.
A paid temporary lender does not mean the remaining debt was paid
The historical 7 October, 05:44:35 UTC sequence serviced 10,006.329226 USDT and returned a temporary 10,000 USDC. It left persistent USDC borrowing and most USDT debt. Later account states therefore need to be read in both owed tokens, not as a single dollar number. Historical creditor sequence.
Two surviving debts; an incomplete payment history
Observed states, not a continuous payment ledger. The October 7 event is earlier evidence. The later comparison preserves both owed denominations; it does not establish an absence of offsetting flows or a completed recovery. Dates, fields and coverage.
At 15 October, 06:13:35 UTC, both debts remain positive: 5,871,988.139231 USDT and 10,011.072984 USDC. The current health factor is above one, and the collateral claim remains. This is an open measured position, not a missed-maturity or default finding. Matching scaled endpoints do not prove zero gross borrowing or repayment; the history after the later 7 October cutoff was not successfully covered. What endpoint equality can establish.
Under repay-both-first, direct same-token cash only, the supplied October 15 calculation needs 5,871,983.138477 USDT and 10,011.072984 USDC before later interest and expenses. These are sequence-specific requirements, not a minimum loan for every unwind or an admitted facility. Free USDe is not valued at zero, but no new conversion is credited. The zero request fields and 86,400-second setting do not establish a funded wait. Funding assumptions and remaining expenses.
Own cash is debt service: the historical 4.688632-USDT contribution is not a fee. Its allocation between principal and accrued interest is unestablished. The earlier dated chapters remain the original evidence record; this qualification applies to the current interpretation.
A funded repayment can leave a different reserve waiting
Observed on 7 October, 05:44:35 UTC, Ethereum block 26,138,499. The already identified sUSDe/USDT borrower actually received 10,000 USDC from Morpho, spent it, received 10,001.640594 USDT and repaid 10,006.329226 USDT to Aave. The additional 4.688632 USDT was its own cash contribution—not a fee. Aave then lent 10,000 USDC, which returned the temporary principal. Cash movements and protocol records.
An actual payment sequence—and the loan that survives
Observed partial refinancing, 7 October 2026, 05:44:35 UTC. One matched transaction at Ethereum block 26,138,499; steps follow log order, not proportional elapsed time. Protocol records corroborate transfers and are not extra cash arrivals. The 4.688632-USDT contribution is own cash used for repayment, not a fee. The complete internal conversion and all-in costs remain unestablished. Transaction, counterparties and cash ledger.
At the later 14:04:11 UTC state, Ethereum block 26,140,985, the account still owes 5,866,650.101604 USDT and 10,000.460197 USDC. Its recorded sUSDe collateral is unchanged at the sampled pre-event, post-event and later endpoints. The current account description therefore has two debt denominations; October 2 and 4 USDT-only observations stay intact as historical evidence. Exact debt states.
The original USDT reserve received a real replenishing payment and the temporary provider got principal back. That is a positive, account-specific funding result, not merely an illustrative facility. The persistent USDC reserve has not been shown finally repaid. The transaction neither recovers the full collateral position nor establishes that the same funding can scale to its whole debt, another borrower or the PT case.
The three sampled cooldown records remain zero/zero. The 86,400-second duration setting is not an already-running request or a funded one-day interval. Pre/post debt changes also differ slightly from the actual transfer because they are end-of-block values: the 0.281595-USDT accrual/rounding residual is not another fee. No separate complete receipt or all-in expense statement was obtained. Cash contribution and accounting residuals.
Additional borrowing and an admitted refinance answer different questions
5 October analysis; October 4 financial inputs. A large lending-market balance is not cash the borrower owns. Most of the selected Base position’s collateral-based capacity is already consumed by its debt. Under frozen price, collateral and stored-share debt, the extra gross slack is 76,416.480707 USDC, not the entire 2,783,150.575859-USDC capacity. The record retains its 32-second accrual lag; neither amount is an executable borrowing allowance. Exact inputs and credit boundary.
More market cash does not erase an existing loan
5 October analysis; 4 October inputs. Base block 52,154,691, 07:25:29 UTC. Amounts rounded for display; the exact values are in the table. The positive slack is a fixed-input financial calculation, not an executable borrowing limit. A financed fee is an algebraic variable, not a sampled fee. Neither same-position slack nor this diagram rules out a separately admitted refinance. Credit, fee and resource evidence.
A same-position loan with gross debt g and fee f delivers only g − f. Paying that cash back to the existing position leaves D + f, not a debt-free account. The fee is an algebraic variable, not an observed selected charge. A different creditor can instead advance enough for a full refinance and take collateral under its own agreement. That can protect the original supplier; it does not extinguish the new creditor’s claim.
The actual Aave USDT account also separates borrowing and liquidation headroom. On its 4 October accepted values, reported available borrowing translates to 162,397.724770 USDT, while slack to the liquidation threshold is 296,524.575842 USDT. The 90% borrowing LTV and 92% liquidation threshold are not interchangeable. Neither amount is owned cash, a current executable loan or a universal refinancing cap. Account, values and assumptions.
The favorable possibilities remain: independent cash, admitted collateral migration, delegated credit or a creditor agreeing to accept a claim can change the sequence. No selected commitment or funded waiting interval is established. The complete conditional creditor sequence names the new obligation after the old loan is paid; the older account-level observations below retain their dates.
The whole recorded account still needs the token it owes
4 October 2026 · Ethereum block 26,117,487 · 07:26:23 UTC. The established Aave borrower now records 5,359,416.826189 sUSDe collateral against 5,873,310.573496 USDT debt. Its health factor 1.0504867863 and the 116,658,584.104160 sUSDe at the aToken are favorable accepted-value and native-inventory observations, not USDT payment resources. Whole account and actual denomination.
Accepted collateral, one sale budget, actual owed-token cash
4 October 2026, 07:26:23 UTC. The full recorded collateral conversion and free USDe are quoted together—not as two sales against the same untouched pool. The idle USDT is credited once. This is a conditional terminal comparison, not an actual collateral release, an advance commitment or observed bad debt. Other resources and routes are not excluded. Account, amounts and source trail.
The combined conditional sale uses the whole collateral’s 6,706,342.569439 USDe-equivalent plus 23,908.467042 free USDe in one enquiry. Its 329,886.694793-USDT output plus 9.689386 idle USDT leaves a 5,543,414.189317-USDT terminal gap under the named frozen-route assumptions, before later interest and costs. It does not count two independent sales against the same untouched pool. This is not a bad-debt observation, a collateral write-off or a minimum advance for every unwind sequence. Exact quantity join.
The collateral-only native alternative reaches 309,274.179330 USDT through crvUSD and USDC. It leaves the free USDe unconverted and is not added to the other path. The account’s cooldown end and underlying amount both return zero: the 86,400-second normal setting is not an already-running, funded cash-arrival schedule. Request, wait and financing boundary.
The October 2 principal-funded partial example and October 3 repay-all-first calculation below retain their original quantities, assumptions and dates. The new whole-account comparison strengthens the final-token question; it does not retroactively make either earlier illustration an executed recovery.
Paying the original lender is not always the last payment
3 October analysis / October 2 inputs. The actual account below owes USDT and has measured free-USDe inventory outside Aave. That inventory supports a useful partial-principal comparison; it does not finance every full-repayment sequence. In the repay-all-first case, the saved debt less idle USDT and one quoted free-USDe disposition leaves 5,134,402.561856 USDT of additional prior funding, before costs and later accrual. This is not every possible staged unwind’s minimum loan. Exact sequence and denominator.
A first repayment can leave a second creditor unpaid
3 October analysis; October 2 inputs, Ethereum block 26,103,809, 09:41:11 UTC. The account is 0xea1776…60add4 and the selected pool is 0x5b03cc…38e96. Repay-all-first; non-replenished single pool; before costs. The prior advance is not observed funding. Schematic boxes are not value-scaled. Exact cash ledger and limits.
The selected pool’s initial 838,081.997038 USDT includes the 123,910.406881 USDT that the opening free-USDe quote would spend. Under a non-replenished single-pool assumption, only 714,171.590157 USDT remains in that stock for a later payment, leaving 4,420,230.971699 USDT of other terminal cash required in this case. These are calculations over the 2 October, 09:41:11 UTC Ethereum batch—not a new quote, account default or global liquidity estimate. Same-pool accounting and residual collateral.
Independent equity cash can end the original loan while the holder keeps collateral. Credit-funded repayment instead leaves a replacement lender waiting for realization. Likewise, an in-kind vault exit can end one wrapper claim while returning direct lending claims rather than spendable USDC. The obligation that ends must be named; an exit label alone does not establish the final payment.
An actual USDT borrower has a first-payment resource outside Aave
2 October 2026, Ethereum block 26,103,809, 09:41:11 UTC. The activity-selected account 0xea1776733cc969df4ff004a9e1a2d87f5b60add4 has 4,788,971.74886648 sUSDe collateral and 5,258,323.140055 USDT debt, with eMode 31 and health factor 1.0481943841. This is the newly established direct-sUSDe cross-token comparison—not a relabelling of the older USDe-debt accounts or hypothetical USDC example. Exact account, reserve IDs and values.
The same address holds 123,908.467042095491407286 USDe outside Aave and 10.171318 USDT. A quote for that exact USDe amount returns 123,910.406881 USDT, with compatible same-batch pool inventory. Unlike pledged sUSDe, this USDe does not first need release from the Aave position. Its availability for this purpose still assumes no outside assignment or other restriction on its use.
Outside-Aave inventory can fund a partial payment
Ethereum block 26,103,809, 2 October 2026, 09:41:11 UTC. Inventory and the sized quote are observed; repayment and release are Research’s explicit assumptions. Dashed arrows are financial dependencies, not executed transfers. The calculation excludes costs and later changes; a USDT residual is not native-ETH funding. Account evidence · conditions and remaining debt.
The supplied partial illustration devotes 100,000 USDT to repayment and releases 250,000 sUSDe. Those amounts are assumptions, not observed actions or recommendations. Research’s fixed-input calculation requires about 34,309.47 USDT of prior paydown for that release, so the assumed repayment is sufficient at the sampled marks. It leaves 5,158,323.140055 USDT owed, with a post-release health factor of 1.0127348608. The lower remaining health factor shows why a repayment combined with collateral withdrawal need not improve headroom.
Before external costs, quoted proceeds plus initial USDT leave 23,920.578199 USDT after the assumed repayment. That residual is not native-ETH gas funding. Control of the account, necessary authorization, inclusion, future prices and the whole-position cash exit remain unestablished. The borrower retains the released shares’ sale and waiting risk; an outside party funding principal or costs would acquire a separate claim. Complete conditional ledger and remaining debt.
The original debt can be paid before the exit is complete
Analysis dated 1 October; no new account reading. Temporary funding can put the debt token in the right place before collateral release. It does not establish the final cash that repays the replacement creditor. Morpho’s published same-transaction mechanism is a relevant alternative to private term funding, but requires repayment within that transaction; it is not finance for an otherwise unfunded positive cooldown interval.
The first lender can be paid while the last creditor still waits
Financial dependency diagram, not an executed refinancing or a current credit offer. Public same-transaction funding has a same-transaction repayment condition; a positive waiting period needs separately supported finance. Funding evidence and cash conservation.
The recorded Base full-debt amount is a prior payment for a one-shot full release, not the minimum seed for every staged exit. The earlier small-slice case remains a conditional counterexample. Neither route is completed simply by identifying a funding mechanism: its amount, admission, costs, final sale and repayment time must fit.
Likewise, a PT quote pays sUSDe, while its creditor may require USDC. There can be one financing interval before PT release and another before the final cash conversion. A waiting USDe claim does not keep earning as the burned sUSDe shares. The September 28 Aave cases below still owe USDe. The separate 2 October account establishes actual direct-sUSDe collateral and USDT debt; it does not make the older hypothetical USDC account real.
The separately dated 28 September UTC evidence makes the denomination of an earlier payment decisive. The measured Aave accounts both owe USDe, not the USDC debt assumed in the earlier dated illustration. At Ethereum block 26,077,313, AV1 held 385.354213 sUSDe against 311.501509 USDe debt; AV2 held 362.949171 sUSDe against 413.341234 USDe debt. Both used eMode 32. Exact accounts and boundaries.
The repayment asset is USDe for these two accounts
Activity-selected accounts at Ethereum block 26,077,313, 28 September 2026 UTC. The prior-payment comparisons are necessary financial bounds, not executed withdrawal limits; category, idle balances and cooldown were observed separately. Full account evidence and owed-token distinction.
AV2 needs approximately 45.518185 USDe first to release 50 sUSDe at the algebraic boundary, while AV1 needs no prior paydown in that comparison. The later accounting equivalent of 50 shares—about 62.518318 USDe at the sampled ratio—is not already available for the earlier payment. Any funder waits for actual release and conversion, subject to its own maturity and costs. The exact health-factor boundary is not an operational safety margin.
The Base comparison is different again: the owed token is Base USDC. A local 50,000-USDe budget fits within the fixed-input release bound and quotes 49,987.498985 USDC, but larger releases need earlier paydown. At Base block 51,912,543, the million-unit enquiry reaches its price boundary without returning consumed input. Local quote, prior payment and residual creditor.
The 28 September PT comparison established a sized pre-maturity sale to sUSDe, not USDC. Its USDe accounting equivalent was not a second quote. The 2 October cross-block indicative path adds a quantity-matched USDC enquiry; it does not establish quote persistence through a cooldown or a funded final payment. Exchanging free PT can remove one position while leaving its separate creditor unpaid.
A healthy position can still need repayment cash first
The 27 September evidence distinguishes the amount pledged, the amount that may become free and the asset needed to repay the loan. The activity-selected Base borrower held about 3.039 million USDe, but the fixed-input no-repayment release bound was only 83,022.46 USDe at health factor one. Releasing one million USDe required at least 839,034.45 USDC of repayment in that financial model. These amounts belong to Base block 51,851,358, 06:54:23 UTC, not a live account assessment.
Gross collateral is not all available to sell
Base block 51,851,358, 27 September 2026, 06:54:23 UTC. Same-unit bars compare gross collateral with a necessary algebraic bound, not an observed withdrawal. Fixed price 1 USDC/USDe, LLTV 91.5%, no subsequent interest or costs. Equality at health factor one is not a recommendation or an assured executable endpoint. Position, calculation and limits.
This is a necessary accounting bound, not an executable withdrawal limit or a recommended endpoint. Interest before inclusion, permissions, contract rounding and actual release conditions still matter. Zero idle USDC and USDe in the two sampled balances does not establish the address’s beneficial owner, other wealth or credit access. Exact inputs and formula.
Outside funding changes the order of events, not the need for cash. The separate Aave illustration assumes a new lender supplies 90,000 Ethereum USDC before repayment. Aave is then paid while the new lender waits for collateral release, staking withdrawal and the later sale. That is funded by assumption, not an observed account, facility or completed unwind. Who remains exposed after repayment?
The active PT-sUSDE-26NOV2026 comparison adds a distinct claim: USDe is its accounting unit, while its SY wrapper lists sUSDe as the redemption output. Maturity changes the available claim path; it does not cancel a USDC debt or itself produce USDC. No sized pre-maturity sale was established in that September 27 evidence. The September 28 quotes now price its sUSDe-output leg, not a completed USDC repayment. Accounting unit, payout token and remaining loan.
Holding USDe does not grant the issuer’s route
The published terms distinguish ordinary Holding Users from eligible Mint Users. The issuer, Ethena BVI Limited, applies onboarding, jurisdiction, compliance, fee and service conditions. Its published redemption commitment is reserve-based and capped at one-dollar notional per USDe; that ceiling is not an unconditional dollar floor for every holder. The agreement places legal reserve title with the company rather than describing a personal segregated deposit for each token holder. Published terms and agreement.
For an admitted customer, obtaining a quote, signing an order, authorised submission and receiving the settlement asset are distinct stages. A signature alone does not create an operator, reserve remaining block capacity or replenish payout inventory. The observed Mint V2 ceilings constrain a route; they are not cash waiting for that customer. Issuer workflow and limits.
A USDC or USDT payment still leaves a separate asset-issuer, market or banking transition. Finishing one step should be described precisely: USDe returned from staking, a supported token delivered on redemption, and bank dollars credited are different outcomes. Private customer rights and stressed processing performance were not established.
The August 2025 terms, reread on 20 September 2026, do not pass Maple borrower rights or fund-holder redemption permissions through to every USDe holder. They distinguish the eligible Mint User from a secondary-market holder; US users are not eligible to become Mint Users under those published terms. A specific person’s enforceable rights and any private agreement still require separate legal assessment. Issuer title and claim boundaries · Published eligibility terms.
Acceptance and suspension are different from token possession
The documentary order-validity process places last-look acceptance and other checks after user signing and before issuer submission. Refusing an order is not the same as changing its signed terms. Valid consent does not commit an operator, reserve capacity or guarantee a payment time. Those controls can protect common backing while leaving a redeemer reliant on another exit. Documented acceptance and holder consequences.
Read the suspension clauses together. The Mint User Agreement contains broad interruption, cancellation, setoff and forfeiture language, but its conflict provision gives the USDe Terms priority for USDe transactions. Section 14 of the Terms preserves rights and obligations during suspension and subjects discretion to applicable law and licenses. Suspension is not established as automatic extinction of every claim. No executed customer-specific agreement or enforceability opinion is supplied. Terms, precedence and the legal reading limit.
A contractual service restriction is not proof of a function able to reverse arbitrary USDe transfers. A market maker or liquidator using another institution’s issuer route depends on that institution’s continued admission and willingness. Fund approval and fund-holder eligibility do not pass through as universal issuer-redemption access. Which right belongs to which holder.
What an observed payout does—and does not—prove
A payment is a flow; a later balance is a stock
Matched standard Transfer logs share the transaction/block hashes and are marked nonremoved. The nominal difference of 1.079 is not attributed to a fee: commercial quote terms were not obtained. Inventory can be replenished or spent and is not future accepted capacity. Transaction and recorded log evidence · Three separate payout-asset inventories.
The three sampled Mint assets were active and subject to one global 10 million-USDe redemption limit per block, alongside the sampled per-asset limits, at Ethereum block 26,019,040. Adding three asset caps does not produce thirty million of independent capacity. Nor does a balance promise that an order will be accepted, submitted or paid before this holder’s deadline. Configuration and inventory in the same 20 September snapshot.
To fund later payments from Maple, the authorized pool withdrawal and onward transfer must actually return the needed asset. To fund them from JAAA, the investor instruction, portfolio settlement, claimability and network route must all work. A current market sale may provide another exit, but it has its own size and price; a published recovery interval cannot stand in for it. Lending route · Fund route.
Cooldown changes the claim—not only the clock
On the inspected positive-duration route, requested sUSDe shares burn when cooldown begins. The amount of USDe is fixed and moved into the Silo arrangement. It no longer participates in later reward-driven growth of the burned shares. A rising USDe-per-share accounting value is also not proof that those USDe units can be sold for a dollar. Staking source and design.
The sampled cooldown was 86,400 seconds at Ethereum block 26,005,156, on 18 September 2026 at 15:02:59 UTC. The endpoint is a staking-release condition, not a complete payment deadline. A further request can aggregate the amount and reset the account’s common endpoint; a change in positive global duration does not simply rewrite every stored timestamp. No generic transferable or cancellable queue receipt is assumed. Dated setting and identity.
A separate observation reconfirmed 86,400 seconds at Ethereum block 26,019,040 on 20 September 2026, 13:31:35 UTC. It did not execute a user withdrawal or establish a bank-cash deadline. The diagram above retains its original 18 September reference. New cooldown read and its limited scope.
For a borrower, the necessary funds may be needed before any of that begins. Pledged collateral cannot all be withdrawn while debt remains inadequately secured. External debt-asset liquidity can make an orderly release possible; a hoped-for future cooldown payout cannot be spent before the collateral has been released. This is why an eventual sound claim can still produce a forced loss.
The 22 September documentary reading distinguishes the March 1/3/5/7-day policy framework, the described 90-day ceiling and the earlier one-day observations. Reported policy adoption is not verified autonomous operation, and a timer change cannot supply outside debt-repayment cash or accelerate a fund’s banking route. Staking and liquidity-policy evidence.
The notice window must cover the whole remaining exit
The source-based continuation distinguishes earliest governance readiness from a holder’s cash deadline. Ordinary scheduling does not promise how soon a ready instruction will execute, and it does not guarantee that the holder notices it when scheduled. A route that needs collateral release, a new cooldown and a final sale or issuer payout must complete all of those steps—not only the timer. Source and timing analysis.
One day of notice is not one day to complete every exit
Conceptual sequence, not a timeline to scale. The two 86,400-second values are inherited from 18 September 2026; no September 26 parameter read or actual exit was performed. The comparison concerns a new cooldown within a minimum-length window; free USDe, an existing queue or a longer delay changes it. Timing assumptions and source basis.
Under the inherited 18 September settings, a minimum-length governance wait and the staking cooldown were each 86,400 seconds. A newly starting cooldown therefore consumes the whole nominal window before allowing for detection, repayment funding, claiming and conversion. The comparison does not assume current settings are unchanged or that every operation executes at first readiness.
Already-free USDe, a partly elapsed queue, a longer scheduled delay or an accessible sale of free shares can shorten or change the route. Independent repayment cash can release pledged collateral before the staking exit. Each remains conditional on actual funding, price and eligibility. Restoring a revoked permission is also not automatically as fast as revoking it, and restored access does not itself replenish inventory. Restoration is a separate dependency.
The size of the exit changes the question
A later investigation adds a different Ethereum USDe/USDC route: at block 26,067,144 on 27 September, its 100,000-USDe price view returned 99,923.537191 USDC, whereas one million USDe returned 243,084.492699 USDC. These are independent indications, not filled trades, future prices or Base exit capacity. New size-dependent USDC comparison. The USDT example below keeps its separate 18 September date and pool.
A quote for 100 tokens does not describe an exit for 100,000
18 September 2026, Ethereum USDe/USDT Uniswap V3 pool 0x435664008f38b0650fbc1c9fc971d0a3bc2f1e47, fee 0.01%, no protective sqrt-price limit. The small quote is block 26,005,291 (15:29:59 UTC); the three larger quotes are block 26,005,285 (15:28:47 UTC). Independent simulations, not trades, cumulative fills, a market-wide depeg, Base liquidation capacity or USD cash. Thin bar widths are rounded to at least one display pixel; labels give the rates. Full quote evidence.
The small near-par observation is a genuine countercase to treating every route as distressed. The larger outputs nevertheless show that this particular pool, in its sampled state and without a protective price limit, did not support a near-par large sale. They do not establish an issuer reserve shortfall or the capacity of other pools, venues, multihop routes or primary redemption. Quote arguments, balances and limitations.
A remote-chain holder also needs local conversion or a working bridge path. An exchange customer must satisfy that account’s margin and transfer rules. Neither Ethereum liquidity nor a documentary conversion facility establishes funded cash where a Base borrower or venue customer needs it. Remote-chain boundary · Venue gates.