Hyperbeat Earn

Hyperbeat Earn is a yield optimization / vault protocol built on the Hyperliquid L1 / HyperEVM stack, operating as Hyperliquid’s native yield layer with automated smart‑contract vaults. ### Protocol identification

• Name: Hyperbeat Earn (part of the Hyperbeat ecosystem).
• Website / dApp: app.hyperbeat.org (Earn interface at /earn and /vaults).
• Docs: docs.hyperbeat.org, section “Hyperbeat Earn” and related vault pages (e.g. HyperUSD vault).
• Category: Yield aggregator / automated vaults, including meta‑vaults, delta‑neutral strategies, and liquid staking.
• Chains: Primarily described as running on HyperEVM / Hyperliquid L1; DefiLlama lists chain “Hyperliquid L1” for Hyperbeat Earn TVL.
• Native / ecosystem token: The broader Hyperbeat product suite includes HYPE liquid staking and beHYPE staking vaults; Earn vaults use assets such as USDT, USDE, USDR, and UBTC, but HYPE appears as the core staking asset of the protocol rather than a vault‑native token. ### Main contracts & verification status Specific contract addresses for Hyperbeat Earn vaults are visible via the app for individual vaults (e.g. Gauntlet USDT0 vault, Gauntlet uETH vault), but these pages do not themselves show explorer metadata.
• Contract addresses and on‑chain verification on Hyperliquid’s explorer are Not verifiable as of 2026‑08‑29 given current tool constraints and lack of direct explorer access.
• Consequently, a ≥2‑source cross‑check (explorer + analytics + on‑chain) for those addresses is Not verifiable as of 2026‑08‑29. ### Launch date Docs and analytics describe Hyperbeat Earn as a live product but do not clearly state an official launch date.
• No authoritative launch date (block height or calendar) could be confirmed from independent analytics or explorer sources.
• Therefore, Launch date is Not verifiable as of 2026‑08‑29. ### Fork lineage / upstream relationships Available sources describe Hyperbeat Earn as Hyperliquid’s native yield layer with proprietary meta‑vault and delta‑neutral architectures, not as a fork of an existing Ethereum yield protocol.
• No evidence that Hyperbeat Earn is a direct fork of Yearn, Beefy, or other major vault protocols; language emphasizes custom strategies integrated with Hypercore funding markets and Unit Protocol.
• No public record of malicious‑modification incidents in Hyperbeat Earn forks or in other protocols explicitly identified as forks of Hyperbeat.
• A third‑party listing labels Hyperbeat Earn as “audited”, but does not link a specific audit report; without the report from the auditor’s own site, this is an unverified marketing claim. Accordingly, fork lineage, exact upstream codebase, and audit coverage for code changes remain Not verifiable as of 2026‑08‑29 beyond general claims in docs and listings.

Hyperbeat Earn appears to be a live product portal, not just a marketing landing page: the app has dedicated Earn, vault, and borrow pages, and the docs point users to the app for vault access. The portal also exposes individual vault pages with deposit-oriented UI language, including references to vault TVL, APY, rewards, and wallet connection flows, which is consistent with an active DeFi frontend rather than a static brochure. There is evidence of product documentation beyond the app itself: the docs site has a Hyperbeat Earn page and separate vault docs such as the USDT Vault, which suggests some UX maturity and public-facing support material. I did not find verifiable evidence in the retrieved material of broken links, fake metrics, or template-only behavior; those points are not verifiable as of 2026-08-29. For deposits and withdrawals, the search results support live deposit functionality through vault pages and user instructions to connect a wallet and deposit into vaults, but withdrawal support was not explicitly confirmed in the retrieved sources; not verifiable as of 2026-08-29. Likewise, an open public API was not found in the retrieved material; not verifiable as of 2026-08-29. Overall: Hyperbeat Earn looks like a functioning, fairly developed DeFi app with a real portal and docs, but open-API availability and withdrawal UX are not confirmed from the available sources.

Nethermind performed two full audits of Hyperbeat’s liquid staking (beHYPE) and multi‑asset yield vault infrastructure on Hyperliquid L1, which underpins Hyperbeat Earn. These covered withdrawal queue logic, vault accounting/valuation, cross‑chain and OFT-based share-token mechanics, and general vault safety properties. First audit findings: 1 Critical, 4 Low, 1 Informational, 1 Best Practice. Second audit findings: 2 Medium, 5 Low, 2 Informational, 1 Best Practice. Nethermind states that all vulnerabilities were resolved before deployment. As of this check there is no public statement confirming that the exact deployed Hyperbeat Earn bytecode on Hyperliquid L1 matches the audited artifacts → Bytecode match: Not verifiable as of 2026‑08‑29.

Not verifiable as of 2026-08-29. I could not confirm an active bug bounty program for Hyperbeat Earn from the available non-protocol sources. The only directly relevant source is Hyperliquid’s separate bug bounty documentation, which shows that Hyperliquid L1 itself has a bounty program with severity-based rewards and payout ranges, but it does not establish that Hyperbeat Earn runs its own program. The Hyperbeat docs entries provided in search results are just documentation entry points and do not state any bounty start date, parameters, or results. What can be said with confidence is limited to this: if Hyperbeat Earn has a bounty, its parameters and results are not publicly verifiable from the available sources, so the program details are Not verifiable as of 2026-08-29. The Hyperliquid bounty framework uses severity-based classification and variable payouts, but that is a protocol-level program and should not be attributed to Hyperbeat Earn without explicit evidence.

Hyperbeat Earn is a non-custodial vault interface on Hyperliquid/HyperEVM that deploys user assets into other DeFi protocols and partner vaults, so its main dependencies are *external protocols*, *bridge rails*, and *liquidity/oracle conditions* rather than an internal balance-sheet business. The platform’s terms say vaults may be co-operated with third parties and assets may be deployed across HyperEVM protocols or partner protocols; it also says Hyperbeat is not a custodian or counterparty to user transactions. The Earn docs say deposits are bridged to HyperEVM and deployed into HL-ecosystem protocols via Royco markets, and that partners include protocols such as Hyperlend, Harmonix, Hypurrfi, Timeswap, Silhouette, and Hyperswap. The clearest counterparty risks are therefore: 1) *partner protocol failure* (smart-contract bugs, insolvency, adverse governance changes, or reward-incentive changes in any downstream venue); 2) *bridge risk* because the system explicitly moves assets cross-chain before deploying them; and 3) *strategy risk* from automated vault reallocation across multiple venues. Hyperbeat’s own docs also note that some vaults use external infrastructure such as Morpho-powered credit and ether.fi-based LST flows, which adds dependency on those counterparties and on the underlying LST/staking economics. For *stablecoin / LST / restaking exposure*, the product materials show exposure to stable assets, LSTs, and yield-bearing strategies, including vaults such as HyperETH and other ecosystem vaults that rely on external staking/liquid-staking infrastructure. That means a depeg, validator slashing, restaking loss, or issuer-side failure in any underlying asset would transmit through to vault NAV. The docs also reference partner protocols distributing incentives, which creates reward-risk concentration and possible APY discontinuity if those programs end. For *oracle / manipulation risk*, no independent, protocol-specific audit or oracle design detail was verifiable from the gathered sources, so the exact oracle stack is *Not verifiable as of 2026-08-29*. The general risk remains material because automated allocation and leveraged/LP-like strategies can be sensitive to stale or manipulated prices, especially on thin-liquidity assets. One important contradiction: Hyperbeat’s marketing emphasizes “no CEX, no wrapped IOUs” on its main site, but the Earn flow still relies on bridge mechanics and downstream protocol exposure; the economic reality is therefore *not zero counterparty risk*, only reduced direct custody risk.

Hyperbeat Earn appears to be organized as non-custodial, self-custody smart contracts rather than a centralized custodian holding user deposits. Hyperbeat’s docs say users hold the keys, are the Owner of a smart contract wallet, and that assets sit either in the user’s contract or in the DeFi positions that the contract deploys into; Hyperbeat’s backend Operator is only allowed to settle transactions within user-defined limits and cannot arbitrarily seize or redirect funds. The public site also states that users retain full self-custody and that assets sit in a smart wallet controlled by the user. For the Earn product specifically, Hyperbeat describes it as smart-contract vaults on HyperEVM, including Meta Vaults that route capital across HyperEVM and HyperCore strategies and liquidity-provider vaults that earn trading fees. A Morpho page adds that Hyperbeat-curated Morpho vaults route deposits into selected onchain lending markets. There are still a few elements that make the custody model more operationally complex than a plain wallet. Hyperbeat says it uses Turnkey for non-custodial key management, where Turnkey generates and protects the user signing key and enforces policy-based signing rules, but “never has custody of funds.” The docs also mention a TokenWhitelistRegistry to restrict which assets can be used, and settlement actions are permissioned through the Operator role. So, in practical terms, custody is organized as: user-controlled smart wallet + smart-contract vaults + restricted operator permissions + non-custodial key management. Based on the sources, Hyperbeat is presenting Earn as a self-custodial DeFi structure, not a custodial account model.

Hyperbeat Earn’s key management is described as non-custodial and centered on a Turnkey-powered wallet flow rather than Hyperbeat holding user keys. The docs say Turnkey generates and protects each user’s on-chain signing key, that this key becomes the owner of the user’s ManagementAccount smart wallet, and that Turnkey never has custody of funds. The architecture doc also says users are the Owner of their smart contract, while the Operator is only a service provider and cannot arbitrarily seize funds or withdraw assets to unauthorized addresses. For convenience, Turnkey provides session keys with limited permissions for actions like trading or viewing balances; these session keys cannot move assets or change account permissions. Recovery is also handled without Hyperbeat acting as custodian: Turnkey supports recovery through passkeys, hardware keys, and social recovery. Hyperbeat’s terms reinforce this model by stating that users are solely responsible for their private keys or other security credentials, and that the staking feature is independent and non-custodial. One conflicting page claims HyperBeat uses MPC across 12+ nodes and says HyperBeat never touches user keys. Because that appears to describe a different product layer or a marketing-level description that is not matched by the Earn architecture docs, the more specific Earn documentation is the better source for Hyperbeat Earn’s key management model.

Hyperbeat Earn is deployed on Hyperliquid L1, a non-EVM custom chain, so standard EVM-based contract/address, proxy, and on-chain role analysis is Not verifiable as of 2026-08-29. From available public information, Hyperbeat Earn functions as a yield product built on Hyperliquid’s perpetuals/points ecosystem, not as a standalone EVM DeFi protocol with transparently documented contract architecture. ### Smart contract / address transparency

• No canonical list of Hyperbeat Earn contract addresses on Hyperliquid L1 is published in independent sources (explorers, analytics, audits). Not verifiable as of 2026-08-29.
• Hyperliquid uses its own L1 and explorer; there is no broadly used decoded-contract ecosystem comparable to Etherscan/Dune for this chain. ### Verification, upgradeability, roles
• There is no publicly available audit report specific to Hyperbeat Earn from major auditors (e.g., OpenZeppelin, Trail of Bits, Quantstamp). Not verifiable as of 2026-08-29.
• Proxy architecture (if any), upgradeability pattern, and proxy admin type cannot be determined from independent tooling, as Hyperliquid L1 is non-EVM and Dune MCP is unavailable. Not verifiable as of 2026-08-29.
• Admin/owner/emergency roles, pause/withdrawal/upgrade/fee/oracle/strategy controls, and whether any roles are renounced are not documented in independent technical sources. ### User exit characteristics
• Without on-chain visibility, it is not possible to confirm whether users can always exit (withdraw principal plus yield) without admin cooperation or whether any form of pause/freeze can block withdrawals.
• Given the typical pattern of yield products on bespoke L1s, a centralized or semi-centralized admin controlling strategy allocation and potentially emergency controls is plausible, but this is inference, not a verified fact. ### Worst case if keys compromised / rug risk
• If Hyperbeat Earn relies on admin keys with authority over:
• strategy allocation,
• fee parameters,
• emergency pause or withdrawal routing, then compromise could enable:
• forced migration of user funds into loss-making or malicious strategies,
• indefinite withdrawal freeze,
• confiscatory or exploitative fee changes. These are generic risk modes for yield products with opaque governance and no publicly audited contracts, not specific proven behaviors. ### Architecture map (high-level, inferred)
• Frontend: app.hyperbeat.org interfaces with Hyperliquid L1 accounts/positions.
• Backend/contracts: proprietary logic on Hyperliquid L1 managing pooled user positions and strategy routing. Exact modules, upgrade paths, and timelocks: Not verifiable as of 2026-08-29. Given these gaps, Hyperbeat Earn currently presents high unquantified smart-contract and admin risk from an institutional perspective, primarily due to missing independent contract, role, and upgradeability disclosures.

Hyperbeat Earn appears to be a real, funded Hyperliquid-native DeFi team, but several identity details remain only partially verifiable from public sources. The strongest independent evidence is a Morpho feature stating that Kilian Boshoff is the founder of HyperBeat and that HyperBeat already runs a curation business behind its earn side; LinkedIn also shows Hyperbeat as a small, privately held team of 1–10 employees, and Boshoff’s profile lists him as Founder at Hyperbeat since December 2024 with location in the Cayman Islands. Public-team visibility is mixed: Boshoff is public, while at least one other co-founder is described elsewhere as pseudonymous/low-key (for example, 800.HL appears in third-party coverage), so this is not a fully doxxed team. A Binance Square article says the team began as early Hyperliquid testnet validators, self-funded about $200k, and says the company is registered in the Cayman Islands; however, that is a secondary-source claim and should be treated as *unverified marketing-adjacent reporting* rather than hard corporate proof. Credibility signals are materially positive but still not equivalent to on-chain proof: Hyperbeat announced a $5.2M seed round backed by ether.fi Ventures and Electric Capital, with additional venture participation reported by mainstream finance coverage, and Morpho’s profile indicates the protocol is now operating live products on Hyperliquid. I found no independently verified office address or onshore operating footprint, so a real office is Not verifiable as of 2026-08-29. Likewise, prior-founder project history beyond Hyperbeat itself is limited in the public record I could verify; no major hacks or prior failures were confirmed in the sources reviewed. Reality check: Hyperbeat is clearly more than a pure web-front, because there are multiple independent references to live products, funding, and an operating team; but its exact legal structure, office presence, and full founder roster remain only partially transparent, so the protocol should be categorized as *real but selectively opaque*, not fully transparent.

Available information portrays Hyperbeat Earn as a growing, ecosystem-native yield layer for Hyperliquid, with no public record of fraud, rug, or insolvency events, but with typical smart‑contract and strategy risk and limited independent, institutional‑grade scrutiny. Founders, investors, team

• Public web sources and analytics profiles describe the protocol’s design and products but do *not* clearly identify doxxed founders, executive team, or named institutional investors.
• Not verifiable as of 2026-08-30 whether the team is fully anonymous, partially doxxed, or backed by specific funds. Audits and security posture
• A Hyperliquid ecosystem directory (HypeWatch) tags Hyperbeat Earn as “audited”, without specifying which auditor or providing a direct report.
• Hyperbeat marketing and docs emphasize “onchain solvency proofs” and use of standard ERC‑4626 patterns for vault shares, but this is an *unverified marketing claim* absent direct audit links from independent auditor sites.
• No publicly listed major exploits, hacks, or emergency shutdowns are found in the surfaced sources. Not verifiable as of 2026-08-30 via on-chain data. Protocol reputation & sentiment
• Analytics platforms (DefiLlama, OakResearch, DefiCare) present Hyperbeat Earn as Hyperliquid’s native yield layer with large TVL ("hundreds of millions" to over $1B on Hyperliquid L1) and central role in the ecosystem.
• Third‑party educational content in Chinese positions it as a DeFi “high‑yield bank” for arbitrage, aimed at retail users, with generally positive tone and no red‑flag warnings.
• Ecosystem listings highlight expected airdrops and integration with Hyperliquid protocols, again positive but promotional. Criticisms, allegations, regulatory issues
• No credible reports found of:
• Fraud, rug pulls, or intentional misappropriation.
• Insolvency or failure to honor withdrawals.
• Regulatory actions, sanctions, or formal investigations.
• Major public controversies around governance or tokenomics. Not verifiable as of 2026-08-30 via independent regulatory or sanctions databases. Unresolved concerns for an institutional profile
• Lack of clearly documented founders, governance structure, and investor base is a material KYC/operational‑risk gap for institutional allocators.
• “Audited” status is not backed by named firms or accessible reports in independent sources; this should be treated as unverified until confirmed from auditor websites.
• On‑chain solvency, stress‑test history, and incident‑response process are Not verifiable as of 2026-08-30. Net: market sentiment appears positive and usage sizable, but from an institutional risk lens the absence of transparent team, governance, and verifiable audits remains a significant unresolved concern.

Hyperbeat Earn is a yield product built on the Hyperliquid L1 perpetuals/options ecosystem, offering structured, automated strategies that route user deposits into trading on Hyperliquid via vaults and bots. ### Strategy & Assets

• Assets in: Users deposit USDC or other stable/major assets supported on Hyperliquid L1; positions are then expressed as perpetual or options strategies on Hyperliquid.
• Strategy types (from app and docs):
• Market‑neutral funding‑rate / basis‑trade style strategies on Hyperliquid perps (earn funding/premium while hedged).
• Directional volatility strategies using options (short volatility / covered calls / spreads) targeting yield from option premia.
• Yield sources: Primarily
• Perpetual funding rates and basis on Hyperliquid.
• Option premia collected through structured products.
• Hyperliquid incentives (points / rewards) in some products. Given absence of on-chain access to Hyperliquid L1, all on-chain mechanics are Not verifiable as of 2026‑08‑30. ### Organic vs Subsidized, Leverage, Exposure
• Yield is mainly organic, coming from trading PnL, funding, and premia; some strategies add subsidized rewards (Hyperliquid points / potential HLP-like incentives).
• Strategies can be leveraged via perp margin and options; leverage levels, risk limits, and margining are set at vault level.
• Exposure:
• Market‑neutral vaults hedge delta across perps; still exposed to funding regime changes, liquidity, and execution risk.
• Directional/volatility vaults are directional or short vol.
• External exposure is primarily to Hyperliquid counterparty and engine risk; no restaking / external DeFi leg found. ### Lock‑ups, Withdrawals, Fees
• Products are structured as vaults with epochs or rolling positions; withdrawals typically allowed at epoch end or with a delay for position unwinding.
• Fees (from docs/app):
• Performance fee on profits.
• Possible management fee for some vaults.
• Trading fees are paid to Hyperliquid; vault returns are net of those. ### Protocol Revenue & Collateral
• Protocol revenue: performance/management fees on vault AUM plus potential share of incentives.
• Collateral: user deposits sit as margin in Hyperliquid accounts controlled by the vault logic/bots; specific segregation control Not verifiable as of 2026‑08‑30. ### TVL, APY History & Sustainability
• No DeFiLlama listing for hyperbeat-earn on Hyperliquid L1 was found; TVL figures are Not verifiable as of 2026‑08‑30.
• APYs shown in the app are unverified marketing claims; historical APY, volatility, and sustainability cannot be independently reconstructed without Hyperliquid L1 on‑chain data or public time series. Key risk: dependence on Hyperliquid’s matching engine, risk controls, and any incentive program continuity; plus leverage and strategy model risk.

Hyperbeat Earn does not have a verifiable public treasury/reserve disclosure in the gathered sources beyond marketing- and docs-level references to a treasury-backed stablecoin and a separate “Hyperstrategy” treasury fund. The only independently reachable evidence is that Hyperbeat describes “Hyperstrategy” as a strategic fund for the Hyperliquid ecosystem, while a DeFi analytics page says beatUSD reserves are backed by USDC and USDG held by a Hyperbeat reserve address on Ethereum and HyperEVM; no source in this pass provided a complete treasury address list, custody setup, reserve policy, or attestations that can be checked on-chain. The on-chain balance and reserve composition for Hyperbeat Earn specifically are Not verifiable as of 2026-08-29, and chain-by-chain exposure could not be broken out without a live chain query. If you need a strict risk memo standard, the current finding is: reserves/treasury size, addresses, custody, control, policy, and attestations are Not verifiable as of 2026-08-29.

Hyperbeat Earn currently has no publicly documented native token for the “Earn” product on Hyperliquid L1. All token-related information below is therefore “Not verifiable as of 2026-08-29” unless explicitly stated. 1. Existence of a native token

• Hyperbeat’s app (app.hyperbeat.org) and available web sources describe it as a yield/points product built on Hyperliquid that distributes “Hyperbeat Points” and interacts with existing assets on Hyperliquid, not with a separate ERC-20 style governance token.
• I found references to “points”, “vaults”, and “earn” flows, but no contract address, ticker, or token contract on Hyperliquid L1 that is clearly identified as a Hyperbeat token.
• Name-collision and phishing-angle searches ("Hyperbeat token", "HBT token", "Hyperbeat Earn Hyperliquid contract") mostly surface either the app, social media, or generic mentions, not a verified token contract. Given the research constraints and lack of verifiable contract-level data, treat Hyperbeat Earn as having _no launched native fungible token_ as of the stated date. 2. Tokenomics dimensions (all Not verifiable as of 2026-08-29) Because no native token contract can be reliably identified:
• Token name/ticker/contract address: Not verifiable as of 2026-08-29.
• Total vs circulating supply; market cap; FDV: Not verifiable as of 2026-08-29.
• Token utility & governance role: Hyperbeat materials speak about points and potential future governance, but these are unverified marketing claims without an on-chain token reference.
• Revenue share, buybacks, burns, staking rewards: Not verifiable as of 2026-08-29.
• Emissions & unlock schedules; whether unlocks occurred on-chain: Not verifiable as of 2026-08-29.
• Allocations (team/investors/treasury/community): Not verifiable as of 2026-08-29.
• Top-holder concentration / insider wallets: Not verifiable as of 2026-08-29.
• Mint / blacklist / fee-switch functions & controllers: Not verifiable as of 2026-08-29.
• DEX liquidity depth & listings: I find no evidence of a Hyperbeat-branded token listed on Hyperliquid spot/Perps or other major DEXs; all token data for a hypothetical Hyperbeat token is Not verifiable as of 2026-08-29. Risk analyst takeaway From an institutional risk perspective, treat Hyperbeat Earn as a points-based yield product without a live, tradable governance/utility token until a concrete token contract, listings, and on-chain data are disclosed and independently verifiable. Any references to future tokens or point conversion should be flagged as unverified marketing claims and not relied upon for valuation or collateral purposes.

If Bitcoin falls below $10,000, the main expected impact on Hyperbeat Earn is indirect stress: lower crypto prices would likely reduce user risk appetite, suppress DeFi activity, and can trigger withdrawals or lower deposits into yield vaults. Hyperbeat Earn’s documentation says its vaults are designed to provide yield opportunities on HyperEVM and automate DeFi strategies across a range of risk tranches, so the protocol is exposed to broader market and strategy risk even if it is not directly BTC-denominated. The most specific downside channel supported by the available sources is funding-rate compression. Independent risk analysis of Hyperbeat Earn says its delta-neutral vaults depend on funding rates, which can go to zero or negative in calm or stressed markets; that would mean lower yield or potentially losses for depositors. A severe BTC drawdown would plausibly coincide with a wider deleveraging event, which can reduce funding-rate opportunities and worsen vault performance, but that last step is an inference rather than a directly verified protocol-specific fact. What cannot be verified from the available sources is whether Hyperbeat Earn has direct BTC collateral exposure, BTC-pegged strategy components, or specific liquidation thresholds tied to BTC at $10,000. Not verifiable as of 2026-08-29. The risk picture is therefore: lower yield, possible NAV pressure, and higher withdrawal stress, with the strongest documented concern being dependence on funding rates and composability risk across HyperEVM protocols.

Hyperbeat Earn’s available public documentation in the provided results does not include enough on-chain position data, asset allocation, or collateral concentration to model a 20% depeg stress scenario quantitatively. The vault pages do state that the strategy allocates funds across whitelisted liquid collateral markets to optimize risk-adjusted yield, but the underlying exposures are not disclosed in the search results, so the impact of a largest-collateral 20% depeg is Not verifiable as of 2026-08-29. What can be stated from the sources is limited to product structure: Hyperbeat Earn includes vaults/markets such as USDC, USDT, and USDe-related borrow markets, and its documentation says the strategy has operated with no defaults, bad debt, or liquidations over four years. However, that is not sufficient to determine loss severity under a 20% collateral depeg because the key missing inputs are the size of the largest collateral, the haircut/liq threshold, and the amount of leverage or rehypothecation in each market. If you want a usable stress estimate, the minimum required inputs are: current collateral composition by market, largest-collateral share of total assets, liquidation thresholds/LTVs, and whether liabilities are matched or rehypothecated. Without those, any numeric loss estimate would be speculative and would not meet verifiability requirements.

For Hyperbeat Earn, the best-supported answer is that an insolvent top counterparty would primarily transmit losses through the vault’s deployed strategy, not through an explicit protocol-level backstop. Hyperbeat’s docs state that Earn vaults are smart-contract vaults running across HyperEVM/HyperCore strategies, and that vaults carry smart-contract, oracle, counterparty, liquidation, and liquidity risks; however, I could not verify a published, protocol-specific insolvency waterfall or rescue mechanism beyond the vault’s own solvency/proof pages. Expected loss path: the underlying position or connected venue becomes impaired, the strategy realizes a shortfall, and the vault NAV falls. If the vault has concentrated exposure, that loss is passed directly to vault share value. Hyperbeat’s public docs emphasize risk-managed strategy selection, but do not publicly specify a guaranteed compensation scheme for counterparty default. Who absorbs it: in the absence of an explicit insurance fund or sponsor guarantee, the loss is borne by vault depositors / share holders through reduced claim value. I could not verify any binding promise that Hyperbeat, a curator, or a third-party market maker contractually makes users whole in this scenario. Not verifiable as of 2026-08-30. Compensation: the only verifiable compensation path is whatever the vault’s actual recoveries generate after impairment. Public docs mention proof-of-solvency pages for some vaults, but I could not verify a documented, automatic compensation waterfall, socialized loss mutualization rule, or treasury recapitalization commitment for Hyperbeat Earn. Not verifiable as of 2026-08-30. Impact through smart contracts: user deposits sit in the vault contract; the vault allocates capital into strategy venues; if a venue becomes insolvent, the strategy’s assets become impaired; the vault’s accounting/share price updates downward; withdrawals then clear at the lower NAV and any unrecovered claim remains trapped until/if recovered. That flow is consistent with the vault architecture described in the docs, but the exact on-chain implementation details are not fully public in the sources reviewed.

For the stress scenario ‘committed fraud by the DAO or owners’, I found no verifiable evidence in the provided sources that Hyperbeat Earn’s DAO or owners have committed fraud. The most relevant primary-source material here is the project’s own site and terms, which do not substantiate fraud allegations. A third-party writeup describes Hyperbeat as high-risk and mentions phishing/scam indicators, but it does not verify DAO/owner fraud against Hyperbeat Earn specifically. Another independent review focuses on structural DeFi risks and legal disclaimers, again without proving fraud by the DAO or owners.

Hyperbeat Earn has multiple yield sources, so a negative 30-day result in the *primary* source does not by itself prove the whole protocol is loss-making. The documentation says USDC vault yield is derived from growth in the hbUSDC exchange rate and that deposited assets are deployed into HyperEVM protocols and basis trades via dnTokens, while the broader Hyperbeat product also includes meta-vaults and delta-neutral strategies across several venues. However, I could not verify which component is currently the protocol’s primary yield source or whether its 30-day yield for that source is negative, because the available search results do not provide on-chain or dated performance data for Hyperbeat Earn itself.

Hyperbeat Earn appears company-operated, not meaningfully DAO-controlled. The public materials say HBEAT holders can vote on proposals for fee structures, chain integrations, treasury allocations, protocol upgrades, and new products, with a 72-hour timelock before execution, but this is an unverified marketing claim because I could not independently verify the voting contract, proposal flow, or signer set in this run. The operating entity is disclosed in third-party legal coverage as Zoeion Ltd Corporation, with Hyperbeat terms pointing to the company contact domain; however, the exact jurisdiction, registration number, directors, and whether a separate foundation/legal wrapper controls assets are Not verifiable as of 2026-08-29 from the sources available here. I could not verify any on-chain governance concentration, top holders, or DAO voting distribution because chain-level verification was unavailable in this run; therefore the voting-concentration and top-holder analysis is Not verifiable as of 2026-08-29. I also could not verify a timelock contract, multisig threshold, or signer independence from explorer-grade evidence, so those controls are Not verifiable as of 2026-08-29. The strongest available source for the protocol’s own description says Hyperbeat Earn vaults are smart-contract vaults on HyperEVM, while a separate Hyperbeat page says beHYPE enables “validator driven governance,” which suggests some governance mechanisms exist around staking/validators rather than a fully decentralized DAO. The available evidence therefore supports a reading of centralized company operation with limited token/validator participation rights, not a clearly autonomous DAO.

Hyperbeat Earn appears to be operated under the broader Hyperbeat legal framework, with the privacy policy naming Zoeion Ltd Corporation as the controller and giving a Panama City address; the terms also point to Cayman Islands governing law, while the foundation’s terms separately state Cayman Islands law and jurisdictions. This creates a structure that is *offshore/legal-entity layered*, not a single clearly documented operating company for Earn alone. On restrictions and compliance, Hyperbeat’s terms state that the service is not available to sanctioned persons or residents of embargoed/sanctioned jurisdictions, including Cuba, Iran, North Korea, Sudan, Syria, and persons on U.S./UK sanctions lists; the foundation terms also bar U.S. persons and mention other sanctioned jurisdictions. The terms further say the platform may conduct background checks or verification checks, request identity information, and use information to detect money laundering, terrorist financing, fraud, or other financial crime, which indicates AML/KYC-style screening even if the product is marketed as self-custodial. The privacy policy says personal data may be collected, used, disclosed, and processed under applicable law, that Hyperbeat is the data controller, and that data may be transferred outside the user’s jurisdiction, including outside Panama, the EEA, the UK, and to the U.S. The card terms also reference data handling and, for Nigerian users, compliance with Nigerian data-protection law and CBN requirements, showing that some Hyperbeat services are subject to local regulated intermediaries. I did not find credible reports of court cases, regulator actions, or sanctions enforcement specifically against Hyperbeat Earn as of 2026-08-29. Not verifiable as of 2026-08-29. Risk view: the legal documents are more developed than many DeFi front ends, but the practical risk remains that access can be restricted by sanctions/geo rules, identity checks may be required for some services, and the entity/jurisdiction setup is not fully transparent for the Earn product itself. The protocol website’s “full self-custody” framing should be treated as an unverified marketing claim unless corroborated elsewhere.

Not verifiable as of 2026-08-29. The web results show Hyperbeat Earn accepts multiple stablecoins (notably USDT0/USDT and USDC in some vaults), but they do not provide a historical price series or any documented depeg incidents for the stablecoin used, so the number of depeg events, the last occurrence, and the depeg percentage cannot be confirmed from the available sources. The only stablecoin-related risk information found is product documentation describing the assets and strategy, not independent evidence of a depeg event.

The top 5 risks for Hyperbeat Earn appear to be: (1) smart contract / composability risk from deploying across multiple HyperEVM protocols, where a bug or exploit in any downstream integration can drain vault deposits; (2) yield compression risk because delta-neutral strategies depend on funding rates that can fall to zero or negative in low-volatility markets, reducing yield or causing losses; (3) nascent-chain / limited battle-testing risk since the protocol launched in 2025 on Hyperliquid’s still-maturing HyperEVM, so there is less real-world security history than older ecosystems; (4) depeg risk because Vault Tokens or beHYPE may lose their intended 1:1 peg to the reference asset, affecting redemption value; and (5) liquidation / leverage risk if users or positions use leverage, where adverse price moves can trigger liquidation and potentially total loss of capital. The protocol also discloses broader market and network risks, including volatility, validator/network failures, slashing, hacking, theft, and loss of access to assets.

Hyperbeat Earn’s main strengths are: self-custodial, non-custodial design; automated vaults that deploy capital across HyperEVM protocols; strategy diversification across lending, liquidity provision, and funding-rate/market-neutral approaches; capital efficiency and compounding through auto-rebalancing and higher base-yield positioning; and ecosystem breadth via integrated save/spend/trade/borrow/pay features on Hyperliquid infrastructure. These strengths are supported by Hyperbeat’s own terms and product pages, plus an independent review that highlights multi-protocol yield optimization and strategy novelty, while noting the protocol is young and composable risk remains.