USDe Risk Audit / Backing recovery and redemption capacity
When backing becomes money the issuer can pay
A loan-pool share, a fund redemption and an eligible holder’s payout are different claims, controlled by different parties. Follow the asset across each boundary before treating it as usable cash.
The central finding is a gap between owning backing and being able to pay—not a finding of issuer insolvency. The selected Maple Institutional position is a large accounting claim supported by a pool whose direct USDC balance is much smaller. The selected JAAA holding is a fund-share balance on Base, not a measured amount of claimable USDC. At the downstream boundary, Mint V2 held sampled payout assets and a standard-token-log pairing supports one burn and payment. The investigation did not establish that either selected backing chain funded that payment.
This changes the practical question from “does a lending or fund allocation exist?” to “which entity can release how much of it, in the required asset and location, before the next obligation?” Specific pool and token observations now support that question. Private legal links, borrower-level deadlines, current fund NAV and claimable cash still prevent an issuer-wide recovery or redemption-capacity total.
Evidence: dated position assessment, Maple observations, JAAA observations and matched token logs. No universal cash guarantee, default probability or complete contract-security conclusion follows.
Select a claim—and keep its dates attached
The two deep cases were selected for materiality and different recovery mechanisms, not as a ranking of every backing asset. LlamaRisk’s assessment published on 18 September 2026, using 14 September positions, reported the following amounts. Its position-level leads were followed into the selected contracts; its internally inconsistent aggregate backing and supply denominators were not used to calculate a coverage ratio. Position selection and wallet labels.
| Candidate | Reported position | Why it matters |
|---|---|---|
| Maple Institutional | $302,941,604 | A consequential lending claim with a traceable Ethereum pool and wallet. |
| Anchorage | $1,000,000 | A smaller reported bilateral comparator—not an equal half of institutional lending. |
| Tokenized JAAA | $252,870,687 across Solana and Base | Material fund exposure with historical large-exit evidence and observable Base shares. |
| STAC | $253,013,814 on Solana | Similarly sized fund comparator. JAAA is not claimed to be the largest fund. |
The JAAA reported total combines $202,296,550 on Solana and $50,574,137 on Base. Those are reported dollar values, while the new Base observation is a token quantity. The two cannot be subtracted to infer investment growth or combined with an old NAV to create a refreshed valuation. No current Solana redemption or cash balance was read in this investigation.
| Evidence group | Block and chain | Chain time on 20 September 2026 |
|---|---|---|
| Matched burn/payment logs | Ethereum 26,018,948 | 13:13:11 UTC; mined logs, not a separately fetched receipt. |
| Mint inventory and settings | Ethereum 26,019,040 | 13:31:35 UTC; one snapshot. |
| Maple accounting, holder and queue | Ethereum 26,019,059 | 13:35:23 UTC; one snapshot. |
| JAAA Base token and balances | Base 51,561,133 | 13:40:13 UTC; the outer reader reported block 51,561,134. |
| Maple conversion getters | Ethereum 26,019,086 | 13:40:47 UTC; later than the accounting snapshot. |
A source retrieval on 20 September does not update its economic cutoff. The issuer index exposed an August 2026 attestation entry, but its linked body remained unreadable. The newest readable issuer attestation body among the alternatives retrieved had a 26 November 2025, 23:59 UTC cutoff; its linked custodian images were not readable. Neither that old body nor the recent assessment supplies a current signed custody reconciliation. Issuer attestation index · Readable historical issuer backing disclosure.
Who can demand and deliver the money?
The published Mint User Agreement names Ethena BVI Limited, places legal title to the reserves with the company, and disclaims a fiduciary or custody relationship for token holders. A USDe holder therefore must not be presented as the direct owner of a particular Maple loan, custody account or underlying CLO asset. The holder’s issuer claim and the issuer’s backing claims need separate analysis. Issuer terms and reserve title · USDe holder and Mint User terms.
The reviewed Maple framework identifies Protocol Pool Operations Alpha LLC, a Delaware entity, with onward deployment into institutional pools. Anchorage’s comparator is A1, Ltd., a Cayman entity distinct from the chartered bank. Those legal names are not guarantees from every affiliate sharing a commercial brand. The public legal reviews do not disclose the executed commercial terms or all security and enforcement provisions. Maple / Anchorage proposal and legal reviews · Protocol Pool Operations Alpha entity filing.
| Boundary | What is supported | What is not established |
|---|---|---|
| Issuer → backing claim | Published company reserve-title provisions and reviewed lending/fund frameworks. | Perfected title, agency mandate or exact executed agreement for every observed wallet position. |
| Wallet → pool or fund instrument | Selected token and pool-share balances at named addresses and blocks. | Who beneficially owns the position, which entity can demand proceeds, or legal priority against external creditors. |
| Underlying assets → proceeds | Published repayment, impairment, sale and redemption mechanisms. | Selected-loan recovery percentage, a finite enforced deadline, or current claimable fund cash. |
| Proceeds → issuer → holder | Sampled Mint inventory and one matched token-log payment pairing. | A traced Maple/JAAA replenishment, future instruction acceptance, or universal holder eligibility. |
A wallet label is a lead, not a legal opinion. The assessment labels the selected wallets and the chain records their instruments. It does not reveal their agency mandate, the person entitled to enforce each loan, or the agreement attaching to a particular pool position. No diagram in this chapter turns that missing legal link into a solid guarantee.
A claim becomes a defensible cash input only after establishing the correct creditor, the right to enforce or request release, net realizable proceeds, entitlement to those proceeds, and actual delivery to the paying entity. Review criteria help ask those questions; they do not prove that every recommended protection exists. Institutional MLA review criteria.
Maple: a share claim is not a withdrawal balance
The selected instrument is a USDC-denominated Maple Institutional secured-lending pool on Ethereum. The contract’s asset and manager getters, and the manager’s withdrawal-manager getter, bind the route more tightly than a product name alone. The selected wallet is the one labelled in the September position assessment; beneficial ownership is not independently established. Maple Ethereum contract registry · Exact observed identities.
A large pool claim still has to become payment cash
At block 26,019,059, the wallet held 233,412,770.855973 pool shares out of 263,318,334.567905. Pool accounting assets were 342,067,873.308294 USDC units. Applying the documented share formula, with integer floor rounding, gives a 303,218,574.812566-USDC accounting claim. The pool itself held 694,920.022526 USDC directly. The claim is a share of the pool assets, and the direct cash is inside those same assets; they are not additional independent reserves.
floor(233,412,770,855,973 × 342,067,873,308,294 ÷ 263,318,334,567,905) = 303,218,574,812,566 raw USDC units.
USDC has six decimals: 303,218,574.812566 USDC.
The small direct balance demonstrates a need for asset realization or other funding under a full-exit condition. It does not measure all pool liquidity, an inability to recall loans, or a waiting time. Other pool assets, strategy positions or borrower payments may supply cash; those sources were not fully enumerated. Nor was the direct balance shown to be reserved for this holder. Accounting and exit exchange rates.
The manager’s unrealizedLosses(), queue totalShares(), selected-holder lockedShares() and pool maxRedeem() each returned zero at that snapshot. These are different fields. Zero recorded unrealized losses is not a solvency certification. Zero maxRedeem is not proof of a freeze or default. Under the published request-and-processing architecture, lockedShares refers to manually available shares, not every unprocessed request. Institutional withdrawal process · Withdrawal-manager queue.
A later observation, block 26,019,086, returned 303,218,726.518832 USDC from both conversion getters for the recorded share amount. That later value is kept separate from the earlier ratio. A conversion getter expresses accounting; it is not a completed withdrawal.
Repayment, refinancing and recovery do not share one clock
Maple’s institutional guidance describes liquidity-dependent first-in, first-out processing and automatic delivery. Its technical material separates the request from manager processing. Where existing pool cash is insufficient, the next question is which asset can actually return USDC—not simply when a withdrawal request was submitted. Institutional withdrawal process · Withdrawal-manager queue.
| Stage and actor | What can produce cash | Timing limit |
|---|---|---|
| Pool manager and withdrawal machinery | Authorize and process a permitted withdrawal from available pool funds. | No holder-specific payment deadline or reservation of direct cash established. |
| Performing borrower | Make repayment under the applicable loan agreement. | Open-term notice is instance-specific. Refinancing can resolve a call without fresh payment cash. |
| Collateral enforcement / execution parties | Realize controlled collateral and settle the sale. | A price trigger or agreed sale can precede actual asset delivery; slippage, custody and settlement can intervene. |
| Correct creditor and legal process | Recover residual value after the applicable costs and priorities. | Amount and duration depend on rights, disputes, debtor assets and realization. No finite selected-claim deadline established. |
| Authorized pool holder / agent | Receive pool proceeds and deliver them onward to the issuer. | A payment to the pool-share holder is not yet Ethereum Mint V2 inventory. |
Published mechanisms and their limits: Open-term loan mechanics, Borrower MLA recovery synopsis and Loan default and impairment procedure. The ladder does not assert that any adverse branch is currently occurring.
Delay can become a permanent outcome for an exiting holder
The lender documentation allows impairment before technical default and warns that exiting an impaired position gives up later recovery participation. A separate four-page procedure describes a 12–24-hour margin cure, collateral liquidation when relevant triggers are reached, impairment of the remaining gap and potentially multi-month recovery. The public descriptions do not establish one authoritative sequence or a selected-loan service-level commitment. Their differences remain unresolved. Defaults and impairments · Loan default and impairment procedure.
Holder accounting value = q × A ÷ S.
Holder exit value = q × (A − U) ÷ S.
Difference = q × U ÷ S, where q is holder shares, A pool accounting assets, S pool shares and U unrealized losses.
An impairment that later reverses can therefore leave a holder who exited with a different outcome from one who waited. The recorded value of U was zero; the formula explains a conditional branch, not a current observed loss. A treasury needing immediate proceeds and an unleveraged investor able to wait do not necessarily bear the same timing cost. Accounting and exit exchange rates · Defaults and impairments.
Maple’s borrower-MLA synopsis describes reasonable documented recovery costs before pro-rata lender principal, then accrued interest and remaining Maple fees. For gross proceeds G, allowed first costs K and principal P, the simplified maximum principal payment is min(P, max(0, G − K)). Full net recovery arriving late is a timing problem; net proceeds below principal are an amount problem even after unlimited waiting. This is a downstream synopsis, not a determination of the confidential Ethena–PPO agreement or universal insolvency priority. Borrower MLA recovery synopsis.
Do not add pledged collateral to the loan it secures, issued pool shares to the underlying assets, or an assumed guarantee to a named cover contract. Security and collateral can help recovery, but their scope, enforceability and available funding must be established for the actual claim. Technical default and cover mechanisms.
JAAA: fund value is not yet claimable issuer cash
The selected fund is the tokenized Janus Henderson Anemoy AAA CLO Fund, JAAA, a participating interest through Anemoy Capital SPC Limited—not the exchange-traded fund with the same ticker. The June review identifies Anemoy management, Janus Henderson portfolio management and Trident administration. It also contains inconsistent custody descriptions: a JPMorgan migration alongside Pershing/StoneX material. The executed governing documents and current service-provider schedule were not independently obtained. JAAA fund assessment and legal review.
A fund share crosses several gates before the issuer can pay
At Base block 51,561,133, the selected wallet held 59,637,405.470326 JAAA tokens against 59,639,455.161466 total supply of this Base token. Its 99.996563% fraction is a Base-token denominator—not fund-wide ownership across networks. The observed name, symbol and six-decimal scale bind the measured instrument. They do not supply contemporaneous dollar NAV, investor permissions, claimable proceeds or issuer payout cash. Token, wallet and read details.
Historical execution is real counterevidence, not a future maximum
The June review reports a $318.6 million exit on 11 March 2026, executed with Bank of America at about five basis points slippage. It also reports thirty redemption observations over 29 July 2025–9 May 2026, with a 1.98-business-day 90th percentile (P90) and a 3.71-day maximum under a Monday–Friday convention. These remain attributed review findings, not this investigation’s independently replayed bank receipts or trading records. JAAA fund assessment and legal review.
That substantial reported exit is a reason not to assume every CLO-fund holding must take months to realize. But a maximum observed in this historical sample is not a stress bound. The review combines monthly-cycle language with a T+1 target/T+3 description and board suspension powers despite no formal daily capacity limit. Neither “no daily limit” nor a normal target establishes an unconditional deadline. Securities-sale completion also need not coincide with USDC arriving at the right issuer wallet.
The source’s timing ambiguity therefore stays next to the historical evidence. The operative request acceptance, calendar, portfolio realization, token funding and holder/network permission would have to be matched to the selected investor before treating a stated interval as its cash-arrival date. Centrifuge asynchronous vault mechanics · Centrifuge investor permissions · Centrifuge network liquidity management.
Changing the asset or network is a real operation
A fund NAV update is not a funded redemption vault. A processed instruction is not necessarily claimable proceeds. A Base USDC receipt is not already Ethereum USDC at Mint V2. The receiving entity needs authority to move the asset, and the onward path needs the required network, sufficient proceeds and timely settlement. No current Solana cash-out or funded Base-to-Ethereum issuer replenishment was established for the selected holding.
STAC is a useful comparison rather than a substitute assumed available to the same holder. Its June evaluation identifies Securitize AAA CLO Tokenized Fund Ltd, Securitize management and Insight submanagement; it describes a minimum holding period, roughly T+4/5-business-day settlement and broad board discretion. The stated 2% instant-liquidity fee belongs to a particular route, not every fund redemption. That comparison does not establish that JAAA is gate-free. STAC fund evaluation and addendum.
A funded advance can bridge time—but must leave a liability
Basin illustrates a possible way to advance cash against slower-settling assets. Grove describes conditional facility capacity and eligible-asset limits; Centrifuge’s concrete announcement concerns JTRSY, not a demonstrated Ethena/JAAA entitlement. No Basin amount is credited to this selected recovery chain. Grove’s Basin facility announcement · Centrifuge’s JTRSY settlement announcement.
The valid positive case is an independently funded, eligible draw that reaches the right entity in the required asset before its deadline. Borrowing then creates debt; an advance against assigned proceeds makes the underlying claim unavailable for another payment. Timely financing can solve a wait, but does not automatically increase net backing or repair a permanent asset loss.
From issuer inventory to an eligible holder
The downstream check is more specific than a statement that “redemptions operate,” but narrower than a capacity audit. The Mint snapshot reconfirmed the reciprocal USDe/minter relationship and the three sampled active payout assets. The global redemption limit and each sampled per-asset limit were 10 million USDe per block. The common global limit prevents adding three per-asset limits as parallel independent capacity. Mint and redeem contract V2 design · Recorded inventory and settings.
| Asset | Recorded token units | What the stock does not establish |
|---|---|---|
| USDC | 30,934,109.172 | Future reserved balance, accepted orders or all issuer USDC liquidity. |
| USDT | 31,023,756.754732 | Automatic timely conversion into USDC or bank dollars. |
| USDtb | 30,989,945.898569999933226432 | Automatic par conversion, network availability or customer entitlement. |
Balances can be replenished and can be spent before a later request. The inventory sample is not the complete issuer balance sheet or an exhaustive list of obligations. Active-asset status does not establish a current customer’s quote, role, beneficiary, signature, allowance or remaining block-capacity conditions. A high cap does not create payment assets, and a funded contract does not make every order eligible.
A payment is a flow; a later balance is a stock
For the sampled transaction, the standard token logs record 165,891.907 USDe burned and 165,890.828 USDC transferred from Mint V2 to the same address. Their transaction and block hashes match; they are marked nonremoved and precede the Mint-contract event in log order. A separate receipt/status was not obtained. The supported claim is this mined-log pairing, not independently verified finality or a complete end-to-end settlement audit. Inspect the recorded identities and log ordering.
The pinned official client ABI produces a candidate Redeem event topic different from the observed Mint event topic. Candidate Mint events were therefore not promoted into an ABI-verified redemption count or throughput statistic. The nominal 1.079 difference between burned USDe and transferred USDC is not called a fee without the missing quote terms. Neither the candidate event nor the matching Transfer is an extra payment to count again. Pinned official Mint client ABI.
The payment happened before the later inventory read. Subtracting it from that later balance would count the outflow twice. Its funding also was not traced to a Maple withdrawal or JAAA redemption; existence of all three endpoints does not establish the missing transactions between them.
Which holder can receive the result?
Under the August 2025 terms reread on 20 September, Holding Users and eligible Mint Users have different access. For an onboarded, whitelisted Mint User, redemption follows the token’s pro-rata reserve notional, capped at one US dollar and payable in supported digital assets, subject to the terms and applicable fees. US users are not eligible to become Mint Users. Setoff, processing and other agreement qualifications remain relevant; their legal effect in an individual dispute was not determined. USDe holder and Mint User terms · Issuer terms and reserve title.
| Position | Necessary next condition | First timing or loss consequence |
|---|---|---|
| Eligible Mint User | Accepted instruction, authorized execution and deliverable supported asset. | An owned reserve claim is insufficient if payout assets are not released in time. |
| Secondary-market USDe holder | Funded market execution or successful admission to a permitted issuer route. | The holder bears sale discount or lack of direct access; fund redemption rights do not pass through automatically. |
| sUSDe holder / borrower | Release pledged collateral when debt permits, then sell shares or complete staking withdrawal and a later USDe exit. | The observed 86,400-second cooldown ends at USDe, not bank cash. An earlier debt deadline may require outside funding. |
| Stablecoin supplier / liquidator | Obtain the actual debt asset through available repayment or liquidation routes. | Accepted collateral value is not a receipt of that asset at the required place and time. |
The one-day staking setting was reconfirmed in the 20 September Mint/staking batch. The underlying share-burning, fixed-USDe queue and debt-release explanation remains the separately dated whole-system foundation; this narrow refresh is not a new test of every staking or lending path. Independent borrower repayment can replenish lenders and break a funding feedback chain. It must arrive before collateral recovery is being relied upon.
Separate delay, permanent loss and competing payments
Every payment amount needs five labels: entity, location, asset, release condition and deadline. A resource enters the paying entity’s cash only when it crosses that boundary. A mark-to-market gain, contractual refinancing, unsigned quote or future release is not an arrival. The source loses the resource when the destination gains it; the transfer does not create another reserve.
| Resource | What could count toward a payment | What must not be added twice |
|---|---|---|
| Maple pool shares / direct pool cash | Net proceeds actually authorized and delivered to the relevant holder, then onward to the issuer. | Pool share value, underlying assets and direct pool USDC are overlapping representations. |
| JAAA on Base / reported Solana position | Accepted, funded, claimable proceeds and the permitted onward route. No verified current Solana cash amount. | Tokens, NAV, redemption proceeds and issuer cash are successive states—not four reserves. |
| Mint USDC, USDT and USDtb | Their own usable units after competing uses, or a realized net conversion into the required asset. | No assumed par interchangeability; earlier outflows are already reflected in later balances. |
| Reserve / custody balances | Only proven owned, available, non-overlapping resources. Neither was quantified as free cash here. | Do not add an old reserve figure or a custodian balance plus its venue mirror. |
| Independent bridge funding | An eligible funded draw received before the deadline. | Record matching debt or assigned proceeds; do not reuse the encumbered claim. |
Copper supplies a concrete custody comparator. Its balance guide constrains undelegation by both delegated and main-account availability; only main-account funds are releasable through that route. Its settlement documentation allows pending client settlement until inadequate exchange collateral is topped up. These are provider conditions, not measured Ethena account balances. A positive receivable may retain value without being free cash for an unrelated payment. Copper delegated and releasable balances · Copper settlement conditions.
Cash by T = opening cash + qualifying net arrivals received by T − payments made by T − amounts still reserved at T.
Initially funded bridge needed:
Largest positive shortfall at any deadline up to T—not the sum of separately measured gaps and not merely the final balance.
The maximum earlier shortfall matters because a receipt tomorrow cannot retroactively meet a payment due today. The bridge calculation describes a funding requirement under a schedule; it does not assert that credit is available or that an issuer has accepted the hypothetical orders.
The same recovery can be sufficient in amount and late in time
Hold the Mint USDC snapshot fixed and assume four separately accepted orders, each for ten million USDe at exactly one USDC per USDe, at successive permissible deadlines. With no other arrivals, conversions, pre-consumed limits or competing uses, the 40-million-USDC total exceeds the observed opening USDC by 9,065,890.828 USDC. The cap sizes this scenario; there is no claim about four actual blocks, elapsed-time throughput, a live queue or a promised quote.
| Change from the no-arrival example | Required initial funding | Meaning |
|---|---|---|
| No additional receipt before deadline 4 | 9,065,890.828 USDC | Conditional shortfall against that opening USDC stock only. |
| Same amount received just before deadline 4 | 0 additional USDC | The assumed timely independent arrival closes this particular gap. |
| Same amount received after deadline 4 | 9,065,890.828 USDC | Eventual cash does not erase the earlier deadline deficit. |
| One extra USDC reserved before deadline 4, no arrival | 9,065,891.828 USDC | A reservation reduces free cash one-for-one; it need not be a capital loss. |
Replacing the hypothetical arrival with Maple or JAAA proceeds requires the missing release and entity-specific transfer evidence. A bridge may meet the deadline under the example’s other conditions, but its debt or assignment remains. No Basin entitlement, historical reserve amount or presumed USDT/USDtb conversion is inserted to make the result look funded.
Permanent loss asks a different question
For claim principal P and net recoverable principal R after applicable costs and priorities, a positive P − R is an amount shortfall. Full recovery after the deadline may need temporary financing without principal loss. Recovery below principal cannot be repaired by waiting alone; ordinary borrowing moves the funding burden rather than adding loss-absorbing capital. The issuer resources needed to absorb that shortfall are not reconciled here, so no claim-level haircut is converted into a current USDe reserve ratio.
One reserve dollar cannot absorb a permanent loss and simultaneously remain untouched for redemption or margin. Conversely, a borrower’s payment realizes an already-counted receivable; it is not both new backing and recovery of old backing. The useful stabiliser is timely, genuinely available cash—not a second accounting label for the same asset.
What the new evidence changes—and what it cannot settle
The 18 September foundation connected claim types, governance, valuation and exit mechanics. The 20 September investigation adds position-specific recovery evidence rather than simply refreshing those explanations. It makes several previously broad uncertainties more concrete while withholding an issuer-wide cash or recovery total.
| Earlier question | New support | Remaining decision limit |
|---|---|---|
| Which lending and fund chains merit depth? | Dated position assessment followed by Maple and Base JAAA contract/wallet observations. | Reported dollar figures and wallet labels are not a current reconciled beneficial-ownership map. |
| What must turn into cash in the lending route? | Bound pool/manager/queue, selected claim, direct USDC and documented recovery branches. | Other liquidity sources, specific borrower notice/maturity and enforceable holder rights are not fully known. |
| Can fund value reach the issuer promptly? | Historical large-exit counterevidence, timing ambiguity and a measured network-specific holding. | No current NAV, claimable proceeds, Solana cash-out or proven issuer replenishment. |
| Is there an observable payout leg? | One matched standard USDe burn and USDC transfer, plus later sampled inventory. | No separate receipt/status, exact candidate Mint-event ABI match, accepted-demand total or Maple/JAAA funding attribution. |
| Can timing be distinguished from loss? | Entity/asset cash conservation and paired deadline tests using an observed inventory input. | No actual demand schedule, available bridge commitment or calibrated issuer-wide stress capacity. |
The strongest remaining limit is the complete legally usable cash picture. No synchronized issuer assets/liabilities/encumbrance ledger or readable recent assurance body was obtained. The confidential Ethena–PPO MLA, borrower agreements, perfected-security evidence, investor registration and wallet mandates remain unavailable. Neither the zero recorded-loss field nor the selected holder’s zero maxRedeem getter resolves those gaps.
Evidence that could change the assessment is specific: an executed creditor or agency mandate; selected-loan recall and repayment instructions; a current fund redemption route with permissions, funding and claimable assets; and timestamp-matched transfers into the actual issuer payout location. These could establish a timely route, expose a shortfall, or show genuine independent funding. An updated headline coverage percentage alone would not answer the same questions.
No default, unavailable-for-a-day amount, guaranteed T+ fund exit, instantaneous portfolio capacity, total DEX liquidity or universal dollar exit is inferred. A treasury, lender or holder can use the chapter to locate the missing condition in its own route; it is not an investor-suitability recommendation or a complete security certification.
Recorded observations, methods and public sources
Public documentary sources below were retrieved by Research on 20 September 2026. Source dates and economic periods are stated separately. Published descriptions and legal reviews are not executed private agreements. Provider-mediated observations are reproduced here as dated inputs, not fresh browser or chain checks. Download the selected observations and calculation inputs (CSV). The CSV is not an additive balance sheet and contains no invented cash credit for unmeasured resources. Import raw integers and addresses as text to preserve precision rather than relying on automatic spreadsheet conversion.
Maple: identity and the same-block calculation
| Identity / query | Recorded input or output |
|---|---|
| Assessment-labelled holder | 0xb8734a14fbd4aa2d44e6aa830405ffc861ba313c |
| Pool | 0xc39a5a616f0ad1ff45077fa2de3f79ab8eb8b8b9 |
Pool asset() | USDC: 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 |
Pool manager() | 0x9cef7d1d390a4811bba1bc40a53b40a506c33b19 |
Manager withdrawalManager() | 0x8a665131e796203a5232527fac441480e02fbb7f |
Pool balanceOf(holder) | 233412770855973 raw six-decimal pool shares. |
Pool totalSupply() / totalAssets() | 263318334567905 raw shares / 342067873308294 raw USDC accounting units. |
USDC balanceOf(pool) | 694920022526 raw units = 694,920.022526 USDC. |
Manager unrealizedLosses() | 0; accounting field, not a guarantee. |
Queue totalShares(); lockedShares(holder); pool maxRedeem(holder) | 0 / 0 / 0; no freeze or default inference. |
| Later conversions, Ethereum 26,019,086 | At 13:40:47 UTC, convertToAssets(233412770855973) and convertToExitAssets(233412770855973) each returned 303218726518832 raw USDC units. Not substituted into the earlier calculation. |
The selected wallet fraction is q/S; direct-cash-to-claim is cash divided by qA/S. The exact selected claim is floored to a USDC base unit before the full-exit difference. Registry identity: Maple Ethereum contract registry; method: Accounting and exit exchange rates.
JAAA: Base units, not dollars
| Query / identity | Recorded input or output |
|---|---|
| Token | 0x5a0f93d040de44e78f251b03c43be9cf317dcf64 |
| Assessment-labelled holder | 0x2d4d2a025b10c09bdbd794b4fce4f7ea8c7d7bb4 |
name(), symbol(), decimals() | Janus Henderson AAA CLO Fund; JAAA; 6. |
balanceOf(holder) | 59637405470326 raw units = 59,637,405.470326 JAAA tokens. |
totalSupply() | 59639455161466 raw units = 59,639,455.161466 Base JAAA tokens. |
| Calculated fraction | 99.996563% of this sampled Base token supply. Not fund-wide concentration, NAV or cash. |
Mint: separate asset balances and a common execution cap
Ethereum block 26,019,040, 20 September 2026, 13:31:35 UTC. Mint V2 is 0xe3490297a08d6fc8da46edb7b6142e4f461b62d3; USDe is 0x4c9edd5852cd905f086c759e8383e09bff1e68b3. The reciprocal minter() and usde() getters returned those identities. The sUSDe cooldownDuration() at 0x9d39a5de30e57443bff2a8307a4256c8797a3497 returned 86400 seconds.
| Token contract | Raw amount and scale |
|---|---|
USDC · 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 | 30934109172000 / 10⁶ = 30,934,109.172 USDC. |
USDT · 0xdac17f958d2ee523a2206206994597c13d831ec7 | 31023756754732 / 10⁶ = 31,023,756.754732 USDT. |
USDtb · 0xc139190f447e929f090edeb554d95abb8b18ac1c | 30989945898569999933226432 / 10¹⁸ = 30,989,945.898569999933226432 USDtb. |
globalConfig() returned 200,000,000 × 10¹⁸ maximum mint and 10,000,000 × 10¹⁸ maximum redeem per block. Each sampled tokenConfig(token) returned active status and those same limits. These are USDe-scale policy limits, not asset reserves or actual throughput. No arithmetic sum of the three payout inventories is treated as dollar liquidity.
The recorded burn/payment pairing
Transaction locator: 0x72e8a9d27138863379ee0d1a55a70d25495c9ef3d26db9f5c22733da3c2e3140. This link identifies the transaction; it is not a claim that an explorer receipt was obtained. The recorded block is 26,018,948, at 13:13:11 UTC on 20 September.
| Log and token | Recorded movement |
|---|---|
| 57 · USDe Transfer | 165,891.907 USDe from 0x298e013544c56aa8cd0ca7770b8680fa3bbe0d64 to the zero address. |
| 58 · USDC Transfer | 165,890.828 USDC from Mint V2 to 0x298e013544c56aa8cd0ca7770b8680fa3bbe0d64. |
| 59 · Mint-contract event | Observed event topic differs from the pinned client’s candidate Redeem signature; not used as another payment or an ABI-verified redemption count. |
The common block hash was 0x59b03c3a4e798637bb0e9d886d92f21def50aea58f34d683ac30a5d57d1e3e53. Standard Transfer topic: 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef. The event-ABI comparison and absence of separately obtained receipt/status remain material limits; no funding trace from the selected backing chains was supplied.
Why the Mint event was not treated as ABI-verified throughput
The pinned client describes Redeem(address,string,address,address,address,uint256,uint256), giving candidate topic 0xb15a422f244aaa6fee8671718d386a234dc4c169c71a290a64d49b7fb56e8817. The observed Mint topic was 0x0ea36c5b7b274f8fe58654fe884bb9307dec1899e0312f40ae10d9b3d100cc0c. The mismatch limits interpretation of that event; it does not erase the separately matched standard token transfers or establish an exploit. Pinned official Mint client ABI.
Public source trail
Position selection and wallet labels
LlamaRisk assessment published 18 September 2026; positions dated 14 September. Position-level leads and labels, not signed custody assurance. Inconsistent aggregate backing/supply denominators are not endorsed.
Issuer terms and reserve title
August 2025 revision, retrieved 20 September. Ethena BVI Limited; company reserve title, eligibility, setoff, fees and processing qualifications. No individual enforceability opinion.
USDe holder and Mint User terms
August 2025 revision, retrieved 20 September. Conditional reserve-proportionate supported-asset redemption, capped at one US dollar; not universal bank-cash convertibility.
Maple / Anchorage proposal and legal reviews
10–19 March 2026. Identifies Protocol Pool Operations Alpha LLC and A1, Ltd.; confidential commercial terms and the legal connection to the particular wallet remain unresolved.
Maple Ethereum contract registry
Registry read 20 September; retrieved Git blob 6e55ccc8f26f7a46b125aa4c25206cd19f850835. The URL follows a mutable branch. Pool, manager, asset and withdrawal-manager bindings were separately observed.
Institutional withdrawal process
Undated published operating guidance retrieved 20 September. Liquidity-dependent FIFO processing and automatic delivery; normal averages are not contractual maxima.
Withdrawal-manager queue
Undated technical documentation retrieved 20 September. Request, manager processing and manually available shares are distinct.
Accounting and exit exchange rates
Undated technical documentation retrieved 20 September. Accounting and exit values can differ through unrealized losses; conversion getters do not supply cash.
Open-term loan mechanics
Undated technical documentation retrieved 20 September. Notice periods are instance-specific; refinancing can resolve a call without fresh payment cash. No selected borrower notice or maturity was obtained.
Defaults and impairments
Undated lender guidance retrieved 20 September. Early impairment and loss of later recovery participation on exit; not an observed current impairment.
Loan default and impairment procedure
Undated four-page procedure; Research visually checked all four pages on 20 September. Its 12–24-hour cure and subsequent recovery sequence is not a selected-loan service commitment; version priority against the other public guidance was not established.
Borrower MLA recovery synopsis
Undated legal synopsis retrieved 20 September. Costs, principal, interest and residual fees; not the confidential Ethena–PPO MLA or a universal insolvency priority.
Technical default and cover mechanisms
Undated technical documentation retrieved 20 September. A cover mechanism or registry entry does not establish a funded independent guarantee.
JAAA fund assessment and legal review
June 2026 review. March 11 exit and July 2025–May 2026 timing sample are attributed findings, not independently replayed bank receipts. Timing and custody-provider descriptions conflict.
STAC fund evaluation and addendum
8 and 12 June 2026. Comparator for holding periods, settlement and discretion; a 2% instant-liquidity fee belongs to that route, not every redemption.
Centrifuge asynchronous vault mechanics
Undated documentation retrieved 20 September. Request, processing and claimability are distinct; not verification of the selected live vault or investor permissions.
Centrifuge investor permissions
Undated documentation retrieved 20 September. Investor and network eligibility need their own checks; token possession alone is insufficient.
Centrifuge network liquidity management
Undated documentation retrieved 20 September. Per-network balances and authorized ramps; no selected-holder cash-out route or amount was verified.
Grove’s Basin facility announcement
14 May 2026. Conditional capacity and eligible assets; no funded Ethena/JAAA entitlement established.
Centrifuge’s JTRSY settlement announcement
28 May 2026. Describes a JTRSY route, not a JAAA or USDe reserve.
Mint and redeem contract V2 design
Deployment description dated 8 July 2024; retrieved 20 September. Live inventory and settings are separate observations, not inferred from the design page.
Pinned official Mint client ABI
Commit 8aa953d9a4cd1db18bfad782c34c66163509b0fc; blob 408ea4b78263e205241205d1db8a9284a4ff545d. The candidate Redeem event signature does not match the observed Mint event topic.
Copper delegated and releasable balances
Undated provider documentation retrieved 20 September. Main-account availability constrains release; no Ethena account-specific balance obtained.
Copper settlement conditions
Undated provider documentation retrieved 20 September. Insufficient exchange collateral can leave settlement pending until top-up.
Issuer attestation index
August 2026 entry visible on 20 September; linked body unreadable. No signed current opinion, cutoff or reconciliation inferred from the index.
Readable historical issuer backing disclosure
Cutoff 26 November 2025, 23:59 UTC. Readable issuer body, unread linked custodian images. Not September 2026 backing or usable cash.
Institutional MLA review criteria
14 April 2026. Criteria for evaluating protection, not proof that each selected security interest was perfected.
Protocol Pool Operations Alpha entity filing
22 March 2024 filing index. Entity identification only; no regulatory approval, balance or guarantee inferred.
The 18 September foundation evidence supplies the retained staking/debt, custody, Aave, Base and whole-system findings. Its observations are not redated by this investigation. The separate research calculations use frozen inputs and cash-conservation tests, not fresh RPC calls, EVM execution, private-rights verification or a current solvency model.