Midas mHyperBTC
Midas mHyperBTC
Earn yield on your Bitcoin through secure, native staking
~2.44%
-3.54% (30d)$12.17M
Uncapped CapacityBTC
Denominated ReturnsOverview
Midas’s Hyperithm BTC (mHYPERBTC) is a BTC-denominated tokenized certificate issued by Midas. Investors hold an ERC-20 on Ethereum, Monad, or Rootstock rather than native BTC. Hyperithm manages the referenced strategy, and gains or losses accrue through the token’s NAV.
The strategy aims to be market-neutral. Those labels show where capital sits, but they do not fully disclose the positions, leverage, counterparties, or gross-to-net return bridge inside the strategy.
The key read: this is a managed investment product with an onchain wrapper. The contracts, estimated portfolio exposure, wallets, and attestations are publicly viewable. Hyperithm still controls the economic strategy, Midas controls issuance and redemption, and a quarter of the reported exposure sits at an unidentified centralized venue.
Returns calculator
Calculate your potential returns from BTC staking*
Your Estimated Earnings
*Rates are estimates and subject to change. Past performance does not guarantee future results.
Start Staking5-Step Risk Assessment Framework
Learn how we evaluate this product
Who controls access to the underlying BTC, and can user principal be withheld, seized, or frozen by a single party?
If the code fails or admins intervene, how much user principal can actually be impaired?
Does the yield come from durable economic activity, or from subsidies, reflexivity, and fragile strategy dependence?
How quickly and reliably can a user redeem back to base BTC during stress?
Can I independently verify the assets, liabilities, and yield path with minimal trust and minimal delay?
Yield breakdown
Quick Hits
Date of Report: 2026-08-19
Current APY: 2.05%
Current TVL: $22.77M
Reward Asset: BTC-denominated return through NAV appreciation
Where Does The Yield Come From: Hyperithm’s managed market-neutral book across lending protocols and centralized-market exposure. The exact contribution from lending, basis, funding, and other relative-value trades is not public.
Who Do You Trust: Midas as issuer and redemption operator; Hyperithm as strategy manager; Midas token, oracle, issuance, and redemption contracts; Morpho, Euler, and Aave; the unidentified centralized venue; and the attestation providers.
Fees: 0% management fee, 20% performance fee, and 0.5% redemption fee.
Minimum: 1 BTC
Redemption Terms: Midas supports instant redemption when product-level liquidity is available. Standard settlement depends on the strategy manager making funds available, and timing is not guaranteed.
Official Website: Midas mHyperBTC
Source-of-Yield Audit
Who is paying this yield?
The dashboard shows most estimated exposure across Morpho, Euler, and Aave, with another 25.05% at an unnamed centralized venue. Lending exposure can earn interest paid by borrowers. Centralized-market exposure may support basis, funding, or other relative-value trades. The public dashboard does not provide enough position-level detail to assign an exact share of return to each payer.
Returns accrue through mHyperBTC’s NAV rather than a separate reward distribution. RWA.xyz reported 2.05% trailing 7-day APY and 2.75% trailing 30-day APY on August 19. Those figures are short-window annualizations and should not be treated as realized annual returns or a new baseline.
Mechanism
- An eligible investor deposits BTC and receives mHyperBTC at the current NAV value.
- Midas maintains the token, oracle, issuance, and redemption infrastructure.
- Hyperithm allocates strategy capital across approved onchain and centralized venues, including Morpho, CEX, Maple Finance, and others.
- Lending interest, basis, funding, and other market-neutral returns increase or decrease the reference portfolio value.
- Midas applies the updated reference value to mHyperBTC’s NAV; the product charges a 20% performance fee.
- The investor redeems through Midas. Instant settlement is available only when dedicated liquidity capacity exists; otherwise settlement depends on the manager making funds available.
Trust Assumptions
Dependency Stack
Asset wrapper / backing model: BTC-denominated certificate issued as mHyperBTC
Issuer: Midas
Strategy manager: Hyperithm; exact legal entity still needs confirmation.
Token and oracle layer: Midas contracts on Ethereum, Monad, and Rootstock. Chainlink Oracles.
Onchain venues: Morpho, Euler, and Aave.
Verification layer: Midas Attestation Engine, Chainlink, vlayer, Canary, and related verifiers.
What has to go right?
Hyperithm must keep the strategy within its mandate, manage leverage and liquidity, and avoid losses that exceed earned spreads. The lending markets must remain solvent and liquid, their oracles and smart contracts must perform correctly, and the unnamed centralized venue must return assets when required.
Midas must calculate NAV accurately, propagate the correct reference value through the oracle, preserve the integrity of the mHyperBTC contracts, and process redemptions. The estimated dashboard exposures and periodic attestations must remain sufficiently current to detect a material divergence between token supply, reported NAV, and strategy assets.
Finally, instant-redemption liquidity must be available when investors need it, or the manager must liquidate positions without materially delaying settlement or changing the expected redemption value.
Framework Scoring Inputs
1. Custody & Asset Control 🔴
Control model: Issuer- and manager-controlled.
Single-party freeze risk: Yes. Midas applies platform, wallet, and jurisdictional controls.
Native BTC control: No. The user holds an mHyperBTC receipt token without programmatic exit,
A tokenholder cannot unilaterally exit to Bitcoin L1. Recovery depends on Midas honoring the certificate, the strategy remaining solvent and liquid, and the redemption path remaining available.
2. Smart Contract & Execution Risk 🟡
Contracts directly custody principal: Partial. Midas contracts govern the token, oracle, issuance, and redemption path; strategy capital also sits in external protocols and a centralized venue.
Admin pause rights: Not fully mapped.
Upgradeability: Not fully mapped.
Public audits: Multiple Midas audit reports are public
The wrapper is verifiable on-chain, but the return is not enforced by one autonomous vault contract. Execution depends on Hyperithm’s offchain and onchain portfolio management, Midas’s operational controls, the oracle process, and the downstream venues.
3. Yield Source & Economic Sustainability 🟡
Core yield source: Managed market-neutral trading and lending exposure.
Token Incentive dependence: No token-emission dependence identified.
Leverage in strategy path: Possible
Counterparty / credit exposure: Material across lending venues
The return is economically sourced rather than paid in a promotional token. Sustainability still depends on market spreads, borrower demand, execution quality, counterparty performance, and any leverage used inside the book. The 20% performance fee reduces the return passed through to NAV.
4. Liquidity & Exit Dynamics 🟡
Redemption path to base BTC: Through Midas redemption contracts and operational settlement back to wrapped Bitcoin, then through the wrapper custodian which is either Coinbase or Bitgo
Notice / cooldown / unbonding: Instant only when dedicated capacity is available; standard timing is not guaranteed
Operator discretion over exits: Yes.
Redemption fee: 0.5%.
Midas’s Staked Liquidity system can fund atomic redemption without forcing the strategy to hold idle cash. That facility is capacity-limited. If instant liquidity is unavailable, redemption depends on the manager setting aside funds, and the processing price can differ from the price shown when the request is made.
5. Transparency & Verifiability 🟡
Asset visibility: Partial
Strategy exposure visibility: Partial
Verification cadence: Exposure dashboard updated near real time; attestation checkpoints are periodic
Resources
- Midas mHyperBTC: Official product page and investor interface.
- RWA.xyz mHYPERBTC: Analytics Dashboard
- Midas Docs: Midas’s description of protocol, asset, and wallet visibility.
- Smart Contracts Registry: Official mHyperBTC addresses.
- Midas Audits: Audit reports covering token, oracle, issuance, redemption, bridge, and upgrade infrastructure. The exact deployed-code scope still needs to be mapped.
- Investment Risks: Current issuer-credit, liquidity, counterparty, and qualified-subordination framework.
Frequently Asked Questions
Everything you need to know about Bitcoin yieldLearn more about Bitcoin yield, staking, and how to maximize your BTC returns.
Bitcoin Yield Risk Framework
Version 1.2
This framework evaluates Bitcoin yield products across five pillars: Custody & Asset Control, Smart Contract & Execution Risk, Yield Source & Economic Sustainability, Liquidity & Exit Dynamics, and Transparency & Verifiability.
Scoring principle
We prioritize the risk of capital impairment. A product is judged by how easily user principal can be impaired, not by how decentralized or elegant it looks on paper.
1. Custody & Asset Control
Who controls access to the underlying BTC, and can user principal be withheld, seized, or frozen by a single party?
Green · Trust-Minimized / User-Enforced — users retain unilateral or protocol-enforced claim to BTC without relying on a single entity’s discretion. Recovery is governed by Bitcoin-native or credibly decentralized rules.
Yellow · Quorum / Qualified Custodian — recovery depends on an honest quorum, bridge signer set, federation, or regulated custodian rather than direct user control.
Red · Single-Entity Dependency — recovery depends on one company or legal structure that can freeze access, fail operationally, or leave users structurally exposed in insolvency.
2. Smart Contract & Execution Risk
If the code fails or admins intervene, how much user principal can actually be impaired?
Green · Limited Blast Radius — contracts are immutable or tightly scoped, and a contract failure would not directly allow unilateral loss of core user principal. Operational disruption may still be possible.
Yellow · Admin Guardrails / Contained Control — the protocol is upgradable, pauseable, or still maturing, but admin powers are primarily defensive and do not create clean unilateral control over principal.
Red · Direct Fund Control / Unbounded Blast Radius — a contract exploit or admin action can directly move collateral, rewrite withdrawal rules instantly, or materially impair principal.
3. Yield Source & Economic Sustainability
Does the yield come from durable economic activity, or from subsidies, reflexivity, and fragile strategy dependence?
Green · Economically Real / Non-Reflexive — yield comes from identifiable economic activity and would still exist if token incentives disappeared. The payout may vary with market conditions but is not sustained by emissions.
Yellow · Real Yield, Material Dependencies — yield is economically real, but a meaningful share depends on active management, basis spreads, counterparties, credit underwriting, market structure, or temporary incentive support.
Red · Reflexive / Fragile — yield depends primarily on token emissions, undercollateralized credit, aggressive leverage, or structures that weaken when new capital slows or incentives fade.
4. Liquidity & Exit Dynamics
How quickly and reliably can a user redeem back to base BTC during stress?
Green · Immediate & Rules-Based — users can redeem on demand with no protocol-enforced queue, lock, or discretionary gate.
Yellow · Queued / Market-Dependent — exits are allowed, but require notice, unbonding, cool-down periods, batch processing, or reliance on secondary-market liquidity.
Red · Locked / Discretionary — exits can be blocked by fixed lockups, manual intervention, legal restrictions, or terms that allow the operator to pause redemptions during stress.
5. Transparency & Verifiability
Can I independently verify the assets, liabilities, and yield path with minimal trust and minimal delay?
Green · Continuously Verifiable — a third party can independently verify solvency, backing, and strategy exposure on a continuous or near-real-time basis, either on-chain or via public cryptographic attestations.
Yellow · Delayed / Partial Attestation — transparency is present but delayed, incomplete, or dependent on a single authorized verifier (e.g., periodic proof-of-reserves, monthly auditor reports, proof of assets without liabilities).
Red · Opaque / Black Box — no cryptographic proof of reserves, hidden wallet addresses or counterparties, omitted liabilities, or a proprietary non-auditable yield engine.
How we score
Every pillar has an objective Pass/Fail check. A product cannot score Green on any pillar unless the supporting evidence is explicit in the research report.