mGLO — Midas × Fasanara GDADF Strategy

The note is issued by a dedicated compartment of Aureum Securitisation Fund (RCS O136) under the Luxembourg Securitisation Act 2004. Aureum is an unregulated securitisation fund without legal personality, restricted by law to securitisation activity and operating outside the scope of AIFMD; it acts through its management company, Aureum Manco S.à r.l. (RCS B301171), whose object is limited to that role and which is unlicensed by design. Midas is the tokenisation and platform layer, handling minting, burning, on-chain NAV publication, USDC custody during subscription windows, and off-ramping to the compartment's accounts; it is the operational hub but never the legal issuer.The issuance stack is orphaned. The Midas Purpose Trust, administered by three Hawksford Jersey entities as settlor, trustee, and enforcer, holds 100% of the ManCo's shares and the units issued by the fund and its compartments, with at-any-time, without-cause dismissal power over the ManCo's board; the structure chart is certified by United International Management S.A., a CSSF-regulated Specialised PFS (per the A&O Shearman structure chart and Midas confirmations on the Aureum stack, August 2026). No Midas party owns or controls the issuer. The notes are ledger-based registered securities under Article 100-14 of the Companies Act 1915, with the blockchain constituting the legal Register.An mGLO token is a claim against the compartment, with recourse limited to compartment assets, and no direct claim on Fasanara, Sub-Fund 36, the GDADF, or any receivable. Steakhouse characterizes the instrument as a security within the meaning of MiFID II (July 2026). The compartment invests note proceeds into shares of Fasanara mGLOBAL Fund, Sub-Fund 36 of Fasanara Investments S.A. SICAV-RAIF: a dedicated open-ended sub-fund with USD as reference currency and monthly valuation, whose stated main investments are trade receivables, invoices, SME loans (including real-estate-backed) and other alternative credit originated through technology-enabled platforms. Fasanara confirms Sub-Fund 36 currently obtains that exposure through GDADF fund interests rather than holding originator SPV notes directly; the executed Investment Management Agreement binds Fasanara to the stated policy under AIFM supervision, the PPM's broader permitted-instrument language covers ancillary items (cash management, FX hedging, implementation), and Sub-Fund 36 is not contractually required to hold GDADF shares indefinitely: a direct portfolio implementing the same strategy remains possible within the mandate. The effective claim chain is therefore: noteholder → Aureum mGLO compartment → Sub-Fund 36 shares → GDADF interests → SPV senior notes → receivables. Enforcement in a severe stress scenario traverses each layer sequentially.On priority: Conditions 3 and 8.2 of the Aureum note Terms and Conditions rank the Notes subordinate to the Units in the priority of payments, with noteholders having recourse only to compartment assets remaining after Unitholder claims are satisfied in full. Luxembourg securitisation compartments must have a unitholder, so each compartment issues 2 Units of USD 1 each, held by the Purpose Trust trustee and not acquirable outside the structure; their entire entitlement is USD 2 of principal plus a symbolic USD 42 distribution, with no participation in portfolio returns, and keeping the Units economically empty is what preserves the orphan structure; Midas confirms the mGLO compartment's Units carry exactly the same mechanism as documented for mWIN (September 2026). The subordination is therefore structural rather than economic.

The securitisation fund is non-regulated: neither the CSSF nor another supervisor oversees the vehicle, and the investor protections attached to regulated fund wrappers do not apply. Primary minting and direct redemption require KYC/AML eligibility through Midas greenlisting, enforced independently by each chain's own on-chain registry rather than a single global list. As of 11 September 2026: across all deployments, 362 greenlisted accounts in total, of which 28 have ever transacted in mGLO (verified by on-chain inspection). Once minted, the token is freely transferable on each of its four live deployments (Base, Ethereum, Optimism, and Robinhood Chain) while transfers remain unpaused and the receiving address is not blacklisted, under the same role architecture on each chain. Secondary (peer-to-peer) transfer does not itself require greenlisting on any of the four chains, but minting and redemption through each chain's own Deposit/Redemption Vault do, independently confirmed on-chain (greenlistEnabled()=true, greenlistedRole()=M_GLOBAL_GREENLISTED_ROLE) for every vault on all four deployments.One sharp edge attaches to free transferability: under Condition 6.4, a holder who does not qualify as a professional client under the Luxembourg Banking Act 1993 and holds less than the USD 130,000 Minimum Investment Amount may be mandatorily redeemed on 5 Business Days' notice at the Redemption Amount less a 30% penalty. Since secondary transfers require no greenlisting on any chain, a retail wallet acquiring a small position over the counter is exposed to a documented 30% haircut power.

Protection is layered. The compartment is legally ring-fenced from other Aureum compartments, with limited-recourse and non-petition language that is both statutory and contractual and survives redemption. The orphaning does the second job: because the Purpose Trust holds both the ManCo's shares and the compartment Units, a Midas Software GmbH insolvency leaves holders with their claim against compartment assets rather than making them unsecured Midas creditors, and the trustee can replace the ManCo's managers at any time without cause. Below the fund, each originator relationship runs through a dedicated SPV owned by an orphan Dutch stichting with no legal connection to the originator; receivables transfer by true sale with Notice of Assignment giving direct creditor rights, and collections flow into Fasanara-controlled Goldman Sachs accounts from which originators are excluded. Compartment and sub-fund ring-fencing is credible under Luxembourg law but remains untested for tokenised securitisation notes in a cross-border insolvency.

Events of Default are narrow: failure to perform any obligation continuing 30 Business Days after investor notice, insolvency proceedings unstayed for 30 Business Days, or inability to pay debts (Condition 10.1). Acceleration requires holders of not less than 50% of outstanding Notes, and the accelerated Redemption Amount remains subject to the limited recourse provisions, the Priority of Payments and the underlying fund's valuation mechanics, payable no later than 60 Business Days after determination (Conditions 10.1, 10.2). Payment delays are expressly not Events of Default and accrue no late interest anywhere in the structure (Conditions 6.1(c), 6.3(c)(vii), 7.8, 10.2). Issuer calculations and determinations are binding absent wilful misconduct, bad faith or manifest error (Condition 7.5). The Issuer may amend the Conditions without investor consent for formal, minor or technical matters with no negative impact on investors (Condition 12.1) and may never be replaced as principal debtor (Condition 13.3). Transferees must provide KYC documentation promptly on the Issuer's request (Condition 13.2). Claims prescribe ten years after the payment first falls due (Condition 11). Payments are made free of Luxembourg withholding unless required by law, with no gross-up, and tax refunds on the Underlying Assets pass through to holders (Conditions 9, 7.10). Notices are validly given by publication on the Midas website alone, deemed effective at publication (Conditions 17, 19), so gate, suspension and call notices need never reach a holder directly. The Notes are governed by Luxembourg law with exclusive jurisdiction of the Luxembourg-City courts (Condition 20).

The issuer and platform hold broad powers. The Board may suspend redemptions on significant volume; redemption gating operates at the fund layers (none until Sub-Fund 36 reaches $200M AuM, then 12.5% per Redemption Day); Midas may pause the token where a reliable NAV cannot be established; both vault legs revert mechanically outside the oracle's health parameters (per the note terms and verified by on-chain inspection); the Issuer may call the Notes in whole at its sole discretion on 5 Business Days' notice at the Redemption Amount (Condition 6.2); and its calculations are binding on investors absent wilful misconduct, bad faith or manifest error (Condition 7.5).In-kind delivery is asymmetric across the two layers. At the underlying fund, redemption in kind requires the redeeming shareholder's agreement, with asset selection on a fair and reasonable basis, the valuation confirmed by a special auditor's report, and transfer costs borne by the redeemer (per the Fund PPM, section 8.9): the compartment cannot be forced to take paper. At the note layer the direction reverses: Condition 7.3 permits the Issuer, on notice to the investor or by agreement, to satisfy all or part of any Redemption Amount by Physical Delivery of Underlying Assets, with the value determined by the Issuer, all Delivery Expenses borne by the redeeming investor, and delivery fully discharging the obligation; investors hold no right to demand specific assets (Condition 7.3(i)). The noteholder can be delivered receivables-fund paper but cannot demand it.A 13 August 2026 token upgrade added burnGoverned(address,uint256), permitting the burn-operator role to burn balances without the blacklist check, an issuer power aligned with the note terms. Holder rights extend beyond economics in two respects: Investor Meetings may be convened by holders of 50% of outstanding Notes, with a 50% quorum and simple-majority resolutions binding on all holders, and investors attend and vote pro rata with Unitholders on any Unitholder resolution affecting their financial rights or the Underlying Assets (Conditions 16.1 to 16.4). There is otherwise no governance participation.

The GDADF strategy purchases short-dated, self-liquidating trade receivables and digital invoices originated by fintech lenders, typically 70 to 80% trade receivables and invoices and 20 to 30% fintech-originated loans, including SME working-capital, consumer and selected secured or real-estate-backed lending (per Fasanara, September 2026). Fasanara does not lend directly: 141 approved originators (73 active in GDADF) sell receivables to bankruptcy-remote SPVs, which issue senior and junior notes, with the fund invested at the senior level, and the fund uses no financial leverage at portfolio level. Each transaction is a true sale making the fund the outright creditor, and structural protection applies in two layers. First, portfolio-wide: advance rates run 70 to 90% of face value (85% average), so every purchased exposure carries built-in over-collateralisation against the receivable's face amount. Second, on top of that cushion, approximately 75% of GDADF exposure benefits from first-loss protection, other credit enhancement, and/or government or corporate guarantees, with a 17.1% average senior attachment point on first-loss-protected senior exposures; protections vary by transaction and include originator junior capital, overcollateralisation, excess spread, credit insurance, guarantees, repurchase obligations, eligibility criteria, delinquency triggers, stop-funding rights, and acceleration. The remaining ~25%, typically higher-grade obligors, relies on the advance-rate cushion alone.Origination and underwriting run in two layers (per Fasanara, September 2026). The originator performs the primary borrower-level underwriting under a credit policy approved at onboarding, typically covering KYB and AML checks, financial and cash-flow information, repayment capacity, payment history, external credit data, sector and geography, existing indebtedness, fraud checks and any collateral. Fasanara approves each originator only after full loan-tape and cohort analysis, review of underwriting, servicing and collections policies, management interviews, on-site and technology diligence, reconstruction of default and loss curves, sample testing of underlying transactions, an independent Risk opinion and Credit Risk Committee approval. Assets then transfer only if they satisfy the agreed eligibility criteria, including borrower type, product, jurisdiction, sector, maturity, Fasanara Debtor Rating threshold, concentration limits, advance rate and required credit enhancement, and, for receivables, invoice existence, delivery of the underlying goods or services, absence of prior assignment, disputes or offsets, and legal enforceability of the assignment. The Fasanara Debtor Rating places obligors sourced through different platforms onto one internal scale, combining originator inputs with loan-level performance, third-party financial and alternative data, and Fasanara's proprietary portfolio data, standardising rather than adopting the originator's own score. Ongoing oversight runs through monthly servicer reports, live analytics, covenant and trigger monitoring, and periodic originator reviews with sample audits tracing individual assets against the approved policy, higher-risk originators reviewed more frequently; breaches can trigger asset repurchase, suspension of new funding, acceleration or enforcement.

The strategy's disclosed loss record:

Defaults have climbed with the European SME credit cycle from 0.49% in 2022 to 1.17% in 2025, while crystallised losses have stayed below 1% every year; recovery rates on recent vintages trend lower, partly because pursuing very small receivables can favour earlier write-off. Fasanara characterizes the vintage recovery figures as recovery achieved to date rather than fixed ultimate assumptions. Two datapoints the headline record understates: first-loss buffers have been exhausted at least 20 times across individual transactions historically without producing a negative month, so breach count is a leading indicator worth tracking; and the FY2024 audited statements show write-offs of EUR 12.08M against total income of EUR 68.0M for Sub-Fund 1, with a EUR 9.55M bad-debt provision outstanding at year-end (KPMG-audited financial statements, 31 December 2024). Two single-name precedents put the sizing discipline on record: the First Brands exposure carried no first-loss protection and was written off in full, but had been capped at roughly 0.10% of NAV; and when a German finance provider became insolvent, the backup servicer restored operations within 7 days, bringing data in-house, redirecting payments, and coordinating recovery, with no material loss disclosed. Concentration sits at UK plus US 41% of NAV; the top originator, which typically also acts as servicer, was 13% of NAV in August 2026, with the top ten at roughly 65% (13, 9, 8, 7, 7, 5, 4, 4, 4, 4), making originator concentration the relevant proxy for servicing concentration. Obligor-level concentration is far more granular: per the April 2026 obligor schedule, the largest single obligor was 1.75% of NAV and the top ten combined 10.02%, with the remaining top-ten exposures between 1.30% and 0.61% and an obligor HHI of 8.25 bps (per Fasanara, September 2026), so single-name risk is negligible and the binding concentration is originator and servicer level.

The receivables reprice every 60 to 120 days, so duration is close to zero and the rate exposure is reinvestment yield. The book is not marked to market. Digital-lending assets are carried at principal plus accrued interest, less expected-credit-loss provisions, so deterioration reaches NAV through ECL before any write-off. Interest keeps accruing for up to 120 days past expected maturity, a grace period the Board sets from repayment history and reviews annually, so a delinquent loan can carry about four months of accrued interest in NAV. Write-offs go through P&L and later recoveries come back as income, which means part of any year's yield can be old defaults resolving.

The book is self-liquidating and the natural run-off is the underlying's redemption engine; there is no meaningful secondary market for the paper. Fasanara clarifies that the widely quoted "60 to 90 days" describes the typical short-duration strategy profile rather than a hard portfolio cap; actual average maturity moves with live composition and stood at 107 days in August 2026, with the ladder: 15% due within 30 days, 25% in 30 to 90 days, 10% in 90 to 120 days, 34% in 120 to 180 days, 12% beyond 180 days, and 4% past due, so 50% of the book is due within 120 days, down from 58% in July as the 120-to-180-day bucket grew. A split of the ladder between the receivables and loan sleeves is not disclosed; Fasanara provided the aggregate profile and the typical 70 to 80% / 20 to 30% asset mix only (September 2026).

JTC Luxembourg produces the official NAV off the month-end Valuation Day, calculating after receipt of valuations for the underlying illiquid assets and normally communicating it one to three weeks after calculation; Midas then reviews it, deducts accrued fees, and publishes on-chain, with primary issuance confined to a window after each publication and minting disabled for roughly 90% of the month. A contractual deadline exists at the note level but is anchored to the fund: the Issuer must publish the NAV per Note no later than 4 Business Days after the Fund administrator publishes its official NAV, with on-chain publication itself a contractual obligation (Conditions 14.2, 14.3). The fund's own publication carries no deadline in any document reviewed, and a Fund NAV Disruption at that layer defers the note-level print in full (Condition 15), so the calendar risk sits entirely with the underlying. Midas pushes the price update immediately on receiving JTC's NAV report, usually landing in the third week of the following month and up to four weeks (per Midas, September 2026); the only on-chain enforcement is the feed's 60-day healthyDiff. Standard Redemptions may only be priced off the official NAV, never an estimated or indicative value (Condition 14.4). Between prints, the on-chain value is administratively static.

One base print feeds three published prices through immutable adjustment wrappers:

All three read the same aggregator, 0x6b59...fcbc, written by a single Oracle Admin address, 0x83b5...795b, an externally owned account on-chain, controlled through ForDefi MPC under multi-approver policies per Midas (September 2026). Two write paths exist on the same admin role: setRoundDataSafe, the path used for all regular mGLO price updates, enforces a 1% deviation cap and a one-hour cooldown, while setRoundData validates only a 0.10 to 1000.00 range, under 2 and 4 ForDefi approvers respectively. There is no monotonicity floor, and no staleness enforcement at write.

Because the official NAV lags month-end by roughly three weeks, mint and redeem both execute against adjusted prices and deliver 93% of the entitlement immediately, with the balance trued up and delivered after the official print. The mechanic is contractual, and its two legs are deliberately asymmetric. On subscription, the Issuer issues 93% of the Purchase Price divided by the latest published NAV immediately, and the 7% holdback funds a deferred issuance that is positive-only: additional notes are issued if the next NAV works in the investor's favour, but the initial issuance is never clawed back if it does not (Conditions 2.1(d)(B)(ii), (v)). On redemption, the deferred distribution equals the notes redeemed multiplied by the lower of the fixed instant price and the NAV the notes would have received as a Standard Redemption, less the initial amount, the Instant Redemption Fee and attributable Costs, so the redeemer bears downside NAV drift during the window and captures no upside above the fixed price (Condition 6.3(b)(vi)). Both true-ups are due within 10 Business Days of the relevant publication, the redemption leg explicitly by on-chain distribution or airdrop where applicable (Conditions 2.1(d)(B)(vi), 6.3(b)(vii)), matching observed delivery. One implementation gap: the Conditions specify 93%, while the on-chain wrappers divide by 1.07 and deliver 93.46%. The mechanic protects existing holders from dilution during the staleness window and materially narrows adverse selection, at the cost of a roughly four-week pending entitlement that has no on-chain representation until the airdrop lands (per the Conditions, Midas documentation, and verified against on-chain delivery).

Return is realized through NAV appreciation; there are no distributions. Net return to the noteholder is what survives of the underlying portfolio's gross yield (9.46% average USD, August 2026 factsheet, down from 9.56% in July and 10.36% in June) and GDADF's 8 to 10% gross USD return target after the fee and cost chain. That chain is now largely attributable: Sub-Fund 36 Class A USD Acc charges 1.0% management and 10% performance over a 6% hurdle, the platform management fee takes 0.40%, and FX hedging is a material cost line. GDADF's base currency is EUR, non-EUR asset exposures are hedged to EUR at portfolio level, and GDADF's non-EUR share classes are separately hedged against EUR with hedge gains, losses and costs reflected in the relevant class NAV. Sub-Fund 36's USD reference currency is fully hedged against GDADF's EUR base through that share-class hedge, so the principal EUR/USD hedge sits inside the GDADF USD class NAV, with Sub-Fund 36 running no hedging program of its own and nothing hedged at the token (per Fasanara, September 2026). Worked through at a 9% gross USD strategy return: less 1.0% management leaves 8.0%; with full catch-up the performance fee is 10% of the whole return once it clears roughly 6.7%, so 0.80%, leaving 7.2%; less the 0.40% platform fee leaves ~6.8% to the noteholder before residual costs.

Subscription requires prior greenlisting and runs through the DepositVault on Base against USDC. The window opens at the earlier of the price update plus holdback distribution or 7 business days before month-end, and closes 2 business days before month-end (per Midas, September 2026); the Conditions set the Subscription Cohort cut-off ordinarily on the 19th of the month, variable by Issuer notice, with the operational window sitting inside that variance. Instant daily mint limit is $30M, and price variation tolerance is 2% (verified by on-chain inspection); the documentary Minimum Investment Amount is USD 130,000. Minted tokens follow the 93/7 delivery described above; proceeds are off-ramped by Midas and subscribed into the underlying fund at month-end NAV.

Two routes exist:

• Standard: request before the note-level monthly cut-off, targeted at 2 business days before month-end (per Midas, September 2026), valuation at month-end. Contractually, settlement falls as soon as reasonably practicable after the Issuer receives the corresponding Underlying Asset Receipt and in any event within 10 Business Days of that receipt, or of NAV publication if later (Conditions 6.3(c)(v)-(vi)); in practice proceeds are intended within ~35 calendar days of the Redemption Day, extendable to 90 days at fund level in exceptional circumstances (per Fasanara, September 2026). No fee. An alternative initiation route lets a holder whose notes are pledged register a redemption by posting a refundable 2% deposit instead of transferring the notes upfront. If the notes reach the Redemption Smart Contract within the Issuer's deadline, the deposit is returned or netted against proceeds; if not, the compartment keeps it (Conditions 6.3(c)(i), (iv)).
• Instant: 0.50% fee as configured on-chain against a documentary cap of up to 1% (Condition 6.3(b)(iv)), $200,000/day limit on the redemption vault, 93% paid immediately with the balance after the next official NAV. The Issuer may reject, defer or partially process a request to the extent liquidity is unavailable, with fallback to Standard Redemption (Condition 6.3(b)(ii)). Funded solely by the Midas Staked Liquidity facility, the designated External Liquidity Facility under the Conditions, subject to availability, and may be suspended, reduced, or become unavailable (per the Midas comparison, July 2026).

How the monthly note sits on a quarterly fund: the redemption cycles operate at different levels. GDADF's share classes remain quarterly (45 to 60 days' notice), but Sub-Fund 36 is a separate open-ended vehicle with a monthly Valuation Day and monthly redemption dealing, functioning as a liquidity-management layer: the AIFM is required to align the sub-fund's liquidity profile with its redemption policy and may hold cash and equivalents or access short-term facilities to bridge timing (per Fasanara DDQ responses, September 2026). The maturity transformation between monthly dealing and a quarterly underlying is therefore real and is managed by the AIFM's buffer discipline rather than by matching terms; the 90-day exceptional extension is the documented safety valve. The note terms contain no fixed calendar bound to conflict with it: Standard Redemption settlement is due within 10 Business Days of the Issuer receiving the corresponding Underlying Asset Receipt (or of NAV publication, if later), and Condition 6.3(c)(viii) passes any Fund Liquidity Restriction (gate, deferral, suspension, settlement in instalments) through to noteholders subject only to notice obligations, so a fund-level extension flows through mechanically as delay. Such delay is expressly not an Event of Default and accrues no late interest (Conditions 6.3(c)(vii), 7.8, 10.2).Gating: an mGLO redemption can face two liquidity tests, one at Sub-Fund 36 and one at GDADF (per Fasanara, September 2026). Sub-Fund 36 has no gate today and will introduce one when its AUM reaches $200M. The gate will cap each Redemption Day at 12.5% of sub-fund NAV. When requests exceed the cap, they are filled pro rata, and the unfilled balance carries priority into the next Redemption Day. Deferred amounts are priced at the NAV applicable when processed, so a holder queued through a declining month bears the interim NAV move.GDADF separately runs its own quarterly framework, including a 12.5% threshold. Scale and design both temper this second test. At August 2026 GDADF AUM of about $1.3bn, 12.5% equals roughly $162.5M a quarter. That is on the order of Sub-Fund 36's entire AUM, which sits below the $200M activation level. Fasanara describes the provision as discretionary: requests above 12.5% can be processed where liquidity permits. The same discretion permits tighter treatment in stress. Liquidity behind both tests comes from the short-dated, self-liquidating book. Average maturity was about 107 days in August 2026, with substantial ongoing amortisation. Fasanara's broader receivables origination and servicing platform, about $3.5bn, adds operational support but no contractual commitment (per Fasanara, September 2026).The $200M activation level and the 12.5% gate are both measured on Sub-Fund 36 as a whole, across all of its shareholders. The shareholder base is wider than mGLO: the sibling Aureum mGLOBAL compartment also invests through Sub-Fund 36. The $200M activation clock therefore runs on combined mGLO and mGLOBAL flows. Once the gate is active, the two products share one 12.5% allowance pro rata. A redemption wave in mGLOBAL, a separate compartment, could gate an mGLO exit even when no mGLO holder is redeeming. Below $200M the same dependence exists, with no gate to order the queue. The AIFM's buffer discipline manages it.Board suspension on significant volume, a Midas pause where reliable NAV cannot be established, the oracle health reverts described above, and a USDC circuit breaker triggered when Chainlink USDC/USD prints outside 0.997 to 1.003 can each independently halt deposits or redemptions.

Since effectively all mGLO demand is levered, the most relevant exit mechanic is the dedicated Repay-and-Redeem process for holders using the token as lending collateral. The investor submits a formal request to unwind a collateralised position, posts a deposit of up to 2% of the redemption request value, and Midas reserves the required redemption liquidity. The unwind then iterates through the Redemption Vault: mGLO is redeemed into USDC, the USDC repays debt in the lending venue, released collateral is redeemed in turn, repeating until the position is closed, with completion required before the next cohort cut-off. If the investor completes on time the deposit is returned; on liquidation, abandonment or timeout, Midas may release the reserved liquidity back to the portfolio and apply the deposit to compensate the cash drag. Settlement timelines match a Standard Redemption and the exit carries no fee; the 2% security deposit is returned after redemption processing (confirmed by Midas, September 2026). The legal underpinning is Condition 2.2(e): where Notes are held by a smart contract address, expressly including collateralised lending arrangements, the beneficial owner for the purpose of exercising rights under the Conditions, including redemption, is the person who deposited the Notes or holds the contractual right to withdraw them, provided that person is Greenlisted. Morpho-posted mGLO therefore retains its redemption rights in the hands of the depositor.

The mGLO compartment carries no internal liquidity sleeve: mGLO deploys 100% to the strategy, whereas mGLOBAL holds a 10% Aave V3 USDC sleeve, and Midas confirms mGLO's instant liquidity is provided solely by the Midas Staked Liquidity facility, currently $31.1M in total with $20M exclusively allocated to mGLOBAL/mGLO redemptions (per Midas, September 2026). The allocation is shared between the two sibling products, so against mGLO's $61M outstanding alone it covers roughly a third of supply at par. Separately from the contractual facility, Midas reports soft commitments of more than $100m in OTC and structural-buyer liquidity for T+0/T+1 bilateral execution (per Midas, October 2026); these sit outside the Conditions, are uncommitted, and are untested at size.

Global supply is 61,003,135.39 mGLO across 15 holders on four chains. The token functions primarily as lending collateral, its intended on-chain use case: the Base Morpho Blue singleton holds 26.36M and the Robinhood Chain Morpho Blue holds 34.52M, together 99.80% of everything outstanding, which evidences adoption of the collateral design while concentrating effective exposure in the continued operation, liquidity, and risk parameters of two markets. The largest holder outside Morpho is an idle beacon proxy named Caliber on Base at 123,618.07 mGLO (0.20% of global supply); every other address on every chain combined holds under 0.01%. Effective economic ownership concentrates in a handful of leveraged borrowers. No AMM or DEX liquidity pool was identified on any chain; DEX trading is not the product's designed liquidity mechanism, which instead runs through fee-free standard redemption, capacity-dependent instant redemption, and the Repay-and-Redeem route for collateralized positions, but the consequence stands that every on-chain exit path routes through the Issuer's own machinery and timelines, with no on-chain spot venue identified as an independent alternative; the OTC routes Midas reports are bilateral, soft-committed, and unverified.

The Base deployment remains the reference surface; Ethereum, Optimism, and Robinhood Chain each carry an architecturally identical stack of token proxy, vaults, and NAV feeds, with chain-specific divergences captured in their rows.

All privileged key addresses return zero bytecode, so on-chain they present as single externally owned accounts; the ForDefi X-of-N thresholds above are custodial policy, not observable on-chain. No mGLO role has ever been revoked, and renounceRole reverts, so a compromised key cannot self-remove (verified by on-chain inspection).

On all four chains, every proxy's admin is a ProxyAdmin owned by a 48-hour timelock. Practice matches the configuration. All 23 calls ever scheduled on the Base timelock target the ProxyAdmin. The Robinhood timelock, 0xb821...c7f3, holds its own admin role and has been used once, to execute the 13 August 2026 token implementation upgrade scheduled nine days earlier.On Base, Ethereum, and Optimism, the governance Safe is the sole proposer and sole executor of each chain's timelock. It runs at 1 of 3, across two MPC-custodied EOAs and a nested 3-of-7 Safe. On Robinhood, the separately deployed 1-of-3 Safe 0x563e...B9eD holds proposer, executor, and canceller. On every chain, the Safe that schedules an upgrade also executes it. The 48-hour delay is therefore a waiting period with no second-party check. Where the canceller role is mapped, the same Safe holds it.The Safes' authority extends beyond upgrades. The governance Safe on Base, Ethereum, and Optimism holds DEFAULT_ADMIN_ROLE on the shared access control, so it can grant itself mint authority on a token with no supply cap. It also owns the LayerZero adapters on those three chains. The adapters hold unrestricted mint and burn roles, and setPeer on them carries no delay. On Robinhood, the chain's own Safe holds DEFAULT_ADMIN_ROLE on the local access-control registry, owns the adapter, and holds the timelock roles. Role-granting, bridge, and upgrade authority on Robinhood sit with that one Safe. The platform root-admin EOA 0xd419...1227 holds DEFAULT_ADMIN_ROLE on all four access-control instances. Neither Safe has that system-wide reach alone.The Oracle Admin EOA can write any price between 0.10 and 1000.00 through the wide path, change the aggregator, or move the health parameters, each in one undelayed transaction. Per Midas (September 2026), the wide setRoundData path requires 4 ForDefi approvers and the guarded setRoundDataSafe path, used for regular updates, requires 2. These custodial controls are not observable on-chain. The root-admin key, the Oracle Admin, and the two threshold-1 Safes are the privileged surfaces of the system. On-chain, one compromised signer key on either Safe is enough to reconfigure that chain's peers, rate limits, or endpoint delegate (verified by on-chain inspection). The EOA signers are themselves ForDefi MPC wallets requiring 4 approvers each, so the practical threshold is higher than the on-chain one (per Midas, September 2026).

Two potential oracle failure modes stand out, both rooted in the feed's architecture. First, the feed is closed and single-writer: the Base NAV aggregator exposes a Chainlink-style interface but is not a decentralized feed; exactly one address, the Oracle Admin, can write to it. The official fund NAV is independently produced upstream: JTC calculates it as administrator, under AIFM and depositary oversight, with KPMG auditing the fund. That independence ends at communication of the figure: from JTC's number to the on-chain print, the path runs through Midas alone, which reviews the NAV, deducts accrued fees, computes the published figure, and writes it with no party outside Midas verifying what lands on-chain. Second, a wide write path exists alongside the guarded one: setRoundDataSafe, the path used for all regular mGLO price updates, enforces a 1% deviation cap and a one-hour cooldown, but the same admin role can call setRoundData, which validates only that the price sits between 0.10 and 1000.00, so a write can move the print by orders of magnitude in one undelayed transaction, with no monotonicity floor and no staleness check at write. The stated operational control is custodial rather than on-chain: the guarded path requires 2 ForDefi approvers, while the unguarded path requires 4 and is reserved for legitimate moves exceeding the 1% deviation threshold, the extra approvals standing in for the bypassed on-chain check (per Midas, September 2026). The guards are also asymmetric: the deposit and redemption feeds enforce a 60-day staleness limit and [0.90, 1.10] bounds, while the Morpho collateral leg carries neither, so a lapsed print halts primary rails mechanically while the lending market continues to price collateral at the stale figure.Midas publishes independent third-party audit reports for its contract suite at docs.midas.app/resources/audits (per Midas); mGLO itself has no incident history, and the Morpho market shows zero liquidations and zero realised bad debt to date. A proof-of-reserve layer exists: mGLO is registered on the Midas Attestation Engine, a single Ethereum-mainnet registry (MidasSaveRegistryWithClaim, 0x2D6e...809d, LlamaRisk's SAVE framework) publishing claims through a Chainlink CRE receiver with source emails notarized by vLayer. Exactly two reports have ever been filed, both on 21 August 2026 with identical content, and the feed has been silent since. No mGLO contract reads the attestation registry, and nothing in minting, redemption, pricing, or liquidation is conditioned on it: it is a disclosure channel, not a control.

The dependency chain has several single points of failure, each impairing a different function:

• Midas: all token lifecycle events (mint, burn, NAV publication, redemption processing) run through its operational keys; a disruption at Midas halts primary flows even if the underlying fund performs normally.
• JTC Luxembourg: the sole NAV source; the figure reaching the chain is Midas-ops-computed from JTC's communication.
• Oracle Admin: one authorized address between the administrator's number and the on-chain price; multi-approver under ForDefi MPC per Midas (2 approvers guarded path, 4 unguarded; custodial policy, not observable on-chain).
• The cross-chain operational key: 0xA13f...4F07 holds mint, burn, pause, greenlist, and blacklist authority on all four chains simultaneously, so one key compromise propagates system-wide.
• The platform root-admin key: 0xd419...1227 holds DEFAULT_ADMIN_ROLE on all four access-control registries, so it can grant or revoke every role, including mint, system-wide; the operational key above holds five roles, this key can grant them.
• Ascender Fund Partners and Banque de Patrimoines Privés: AIFM and depositary for the underlying fund.
• Circle / USDC: the only on-chain settlement rail, with the 0.997 to 1.003 circuit breaker placing peg risk directly on the exit path. The contractual regime sits wider: a Depeg Event occurs at a deviation above 2% from 1:1, upon which the Issuer may postpone payment until the rate recovers or pay fiat USD to a nominated bank account (Condition 7.4). The fiat fallback is a mitigant at Issuer discretion, not a holder right; the Issuer is not otherwise obliged to pay in USD (Condition 7.2).
• Fasanara: portfolio management, originator network, and control of the Goldman Sachs collection accounts.

Resilience features worth crediting: the compartment structure survives a Midas insolvency; the underlying book self-liquidates on a 107-day average maturity regardless of on-chain conditions; the fund's collections architecture excludes originators from cash; and the token's pause has never been used. Between JTC's number and the holder, no independent party verifies the figure; the only mechanical checks are the feeds' own bounds and staleness guards.