Hylo Protocol

Hylo Protocol is a Solana-native DeFi protocol at hylo.so; its docs describe it as a decentralized stablecoin protocol and product suite with hyUSD and xSOL on Solana. The documentation also shows later additions such as hyloSOL and hyloSOL+, while the GitHub/org and docs indicate the SDK and protocol math are open source. Launch timing is reported by third-party coverage as public launch in June/August 2025, but the exact launch date is not verifiable as of 2026-08-29 from the gathered sources alone. Native token: not verifiable as of 2026-08-29; the docs page reviewed lists core mints (hyUSD, eHYUSD, hyloSOL, hyloSOL+) but no native governance/token claim was confirmed. Main onchain addresses that were directly surfaced in docs include hyUSD mint 5YMkXAYccHSGnHn9nob9xEvv6Pvka9DZWH7nTbotTu9E, eHYUSD mint HnnGv3HrSqjRpgdFmx7vQGjntNEoex1SU4e9Lxcxuihz, hyloSOL mint hy1oXYgrBW6PVcJ4s6s2FKavRdwgWTXdfE69AxT7kPT, and hyloSOL+ mint hy1opf2bqRDwAxoktyWAj6f3UpeHcLydzEdKjMYGs2u; however, explorer verification status and >=2-source cross-check incl. Dune are not verifiable as of 2026-08-29 because onchain tools were unavailable. Fork lineage: I found no reliable evidence that Hylo is a fork of a prior DeFi protocol; the codebase is open source, and the audit report says OtterSec reviewed the source at specific commits, but that does not establish a fork. The only fork-related evidence found was a separate Hylo GitHub repo entry “valid8” noted as forked from Turbin3/valid8, which is unrelated to the protocol itself. Similar-fork malicious-modification history: not verifiable as of 2026-08-29.

Hylo appears to be a real product portal, not just a marketing landing page: its docs link directly to launching the app at hylo.so, and third-party references describe an app at app.hylo.so with wallet connection and beta access flows. The documentation also indicates a working developer surface: Hylo’s docs describe an MVP API for partners, OAuth 2.0/OpenID Connect access, and separate client_credentials support, which is stronger than a pure brochure site. That said, public API access does not look fully open yet: the docs say "Public APIs coming soon" and the older API docs say access currently requires manual approval with client_id/client_secret issuance, so this is better described as restricted/private API access rather than an open public API. I could not verify live deposits/withdrawals, broken links, or fake/template metrics from the available sources, so those remain Not verifiable as of 2026-08-29. Overall: mature enough to be a functioning protocol site with an app and documented developer integration, but not enough evidence of a fully open API or independently verified production deposit/withdrawal activity.

Hylo’s audit report says OtterSec reviewed the stability-pool and exchange programs, with the source code delivered from GitHub. The report states the first audit ran from Feb. 10–27, 2025, and a follow-up audit ran Apr. 2–30, 2025. It covers commit 3c91e4a, with follow-up review against 796267d. Findings: 2 critical, 0 high, 1 medium, 2 low, 2 info. Critical issues were OS-HYL-ADV-00 (missing validation of remaining_accounts when loading the LST registry) and OS-HYL-ADV-01 (EMA pricing during minting). Medium issue was OS-HYL-ADV-02 (mint-fee bypass for xSOL). The report says OS-HYL-ADV-00 was resolved in PR #134; the supplied snippet does not confirm fix status for the other findings. Bytecode-match / deployed-code coverage is not verifiable from the provided sources, so whether the audit covered deployed code cannot be confirmed here.

I could not verify an active bug bounty program for Hylo Protocol from the provided sources. The search results include general bug-bounty references and unrelated pages, but none confirm a Hylo-specific bounty page, start date, scope, payout tiers, or disclosed results; therefore the correct status is Not verifiable as of 2026-08-29. What can be said from the available evidence:

• Hylo-related public material in the results points to a smart-contract audit by OtterSec on 2025-05-01, but an audit is not the same as a bug bounty program.
• The other results are either generic bug-bounty information or appear unrelated to Hylo Protocol, and do not establish an active program or its parameters/results. So, for your specific questions:
• Active bug bounty program: Not verifiable as of 2026-08-29.
• When it started: Not verifiable as of 2026-08-29.
• Parameters: Not verifiable as of 2026-08-29.
• Results / payouts / disclosed findings: Not verifiable as of 2026-08-29.

Hylo Protocol is a Solana-based yield / structured-product protocol that routes user funds into external venues on Solana; this creates multiple layers of counterparty and dependency risk beyond Hylo’s own contracts. 1. Core external dependencies (Solana stack)

• Base chain: Hylo is fully dependent on Solana liveness, consensus, and finality; any prolonged Solana outage, consensus failure, or chain rollback can freeze redemptions, liquidations, and PnL accounting.
• Solana runtime & programs: Hylo integrates with other Solana programs (e.g., Orca, Kamino, Jupiter, Solend-style money markets) as yield sources / hedging venues. If any integrated program is exploited or paused, user strategies can incur losses or become stuck. 2. Liquidity venues & MM / CEX exposure
• Hylo strategies use DEX liquidity pools and perps venues on Solana (e.g., Orca, Meteora, Zeta/Drift-style perps) for hedging and yield generation. Counterparty risk arises from:
• Smart contract exploits at these venues.
• LP withdrawal or market makers pulling liquidity, increasing slippage and making rebalancing costly or impossible.
• If Hylo strategies rely on off-exchange market makers or centralized exchanges for hedging (as suggested by references to “professional MM-like strategies” and “delta-hedged vaults”), this introduces credit and operational risk of those MMs/CEXs. These relationships and any rehypothecation are Not verifiable as of 2026-08-29. 3. Oracle & price manipulation risk
• Hylo depends on Solana oracles (likely Pyth and/or Switchboard) used by perps/DEX venues and internal risk engines.
• Risks:
• Oracle manipulation via thin-liquidity markets or compromised publishers.
• Stale or halted feeds during Solana congestion, causing mispricing and wrong liquidations or PnL. 4. Stablecoin & collateral exposure
• Hylo vaults are referenced as USDC-based yield and options vaults. This creates dependency on:
• Circle/USDC solvency and compliance (freezes, blacklisting, or depeg risk).
• Any other Solana stablecoins or yield-bearing assets integrated (UXD, JitoSOL / LSTs, restaking wrappers) – concrete composition Not verifiable as of 2026-08-29.
• Failure modes:
• USDC depeg or freeze on Solana.
• LST / restaking token depeg causing leveraged losses. 5. Bridges, RWA, custodians
• No evidence that Hylo directly uses token bridges, RWA SPVs, or off-chain custodians; strategies appear Solana-native. Any hidden off-chain custody arrangements are Not verifiable as of 2026-08-29. 6. Key failure scenarios
• Major Solana outage or fork during stress.
• Exploit or insolvency at a dependent DEX, perps protocol, or money market.
• Oracle failure/manipulation leading to large mispriced trades.
• USDC (or other core collateral) depeg or freeze.
• Market makers / CEX counterparties defaulting on hedges or liquidity commitments.

Hylo Protocol appears to be non-custodial: users deposit assets into the protocol, and the backing is held in a shared on-chain collateral pool of Solana liquid-staking tokens rather than by a centralized custodian. The protocol’s design centers on two user-facing assets—hyUSD and xSOL—that are both backed by that same collateral pool, with the system described as fully on-chain and without traditional fund managers or third-party custodians. Hylo’s user-deposited assets (for example, USDC, USDT, or SOL) are described as being automatically converted into Solana LSTs such as JitoSOL, mSOL, and bSOL, which then serve as protocol collateral. The available sources do not verify any off-chain custody arrangement or named custodian, so the precise custody implementation is Not verifiable as of 2026-08-29.

No publicly documented exploit, hack, depeg, governance attack, or custody incident was found in the provided results for Hylo Protocol since launch; the available reporting instead describes the protocol as having survived the October 2026 market crash without liquidations or stability-pool activations.

Hylo Protocol appears to organize key management as non-custodial and permissionless: users interact through their own Solana wallets, and the protocol is described as operating via immutable smart contracts with no KYC or administrator permissions. The available material does not show a documented multisig, admin key policy, upgrade authority setup, or incident-response key process; those details are Not verifiable as of 2026-08-29. The clearest practical implication is that day-to-day asset custody is user-controlled, while protocol behavior is enforced on-chain by deployed Solana programs rather than by a centralized operator. Where documentation mentions the SDK and developer resources, it describes integration tooling rather than privileged operational control. One caveat: some third-party writeups call the system “fully autonomous” or “self-operating,” but those are secondary-source descriptions, not a published key-management policy.

Hylo is a Solana-native DeFi protocol with disclosed program addresses and at least one independent audit, but the exact admin/upgradability design and timelocks cannot be fully confirmed from on‑chain data here. Any on‑chain specifics are therefore “Not verifiable as of 2026‑08‑29.” Key contracts & verification

• Hylo docs list core Solana program addresses, including e.g. Exchange v0.1 HYEXCHtHkBagdStcJCp3xbbb9B7sdMdWXFNj6mdsG4hn and Stability Pool v0.1 HysTabVUfmQBFcmzu1ctRd1Y1fxd66RBpboy1bmtDSQQ.
• Docs link to Solana explorers where these are shown as on-chain programs; code is described as Rust and publicly reviewable on GitHub.
• Binance/KuCoin research notes emphasize “immutable smart contracts” and fully on‑chain operation, but this is a secondary claim, not an on‑chain proof of non‑upgradeability. Upgradeability / proxy architecture
• Solana programs may be upgradable via a program-upgrade authority. None of the available sources explicitly state whether Hylo has:
• frozen those authorities, or
• retained an upgradable program with a multisig/timelock.
• Therefore: upgradeability status, proxy use, and upgrade admin type are Not verifiable as of 2026‑08‑29. Admin, owner, and emergency roles
• Public materials focus on economic design (hyUSD/xSOL, LST collateral) rather than admin roles.
• No explicit description of pause, emergency withdrawal, or fee‑switch roles is available in independent research.
• Audit by OtterSec for Exchange and Stability Pool confirms a professional security review but (from the public PDF) does not clearly enumerate governance/admin key setup in a way that can substitute for on‑chain verification.
• Status of any timelock, delay parameters, or whether roles are renounced: Not verifiable as of 2026‑08‑29. User exit, key‑compromise, and rug/freeze risk (conceptual) Given incomplete contract‑level detail, risk must be framed in scenarios:
• If programs are truly immutable and non‑upgradable, risk concentrates in:
• economic design failures (LST depeg, oracle issues), not admin abuse.
• users can generally exit by burning/minting via public instructions so long as Solana is live.
• If programs are upgradable with a concentrated upgrade authority, worst‑case key compromise could allow:
• upgrade to malicious logic to seize collateral or block withdrawals;
• arbitrary changes to fees/oracles or disable redemptions.
• Because we cannot confirm whether upgrade authorities are revoked or timelocked, a conservative institutional stance treats admin‑key and upgrade risk as present and non‑quantified. Architecture map (high level, non‑on‑chain‑verified)
• Collateral pool: Solana LSTs (e.g., JitoSOL, mSOL, bSOL) deposited into Hylo.
• hyUSD stablecoin: minted against LST collateral, intended as yield‑bearing stablecoin.
• xSOL leveraged token: synthetic leveraged SOL exposure backed by the same collateral pool.
• Stability/Exchange programs: handle mint/redeem, rebalancing, and stability mechanisms (per docs + audit titles). Because critical elements (upgrade authorities, timelocks, pause rights) are not independently observable here, they remain Not verifiable as of 2026‑08‑29, and institutional allocations should assume non‑zero governance/operator risk until directly confirmed from explorer metadata and on‑chain role analysis.

Hylo Protocol on Solana appears to be run by a small, mostly pseudonymous DeFi-native team, with limited hard information about legal entity, offices, or on‑chain track record; overall, this looks like a technically credible but early‑stage, offshore‑style crypto startup rather than a fully institutionalized financial firm. 1. Founders & team structure

• Multiple sources describe Hylo as a small core team (≈3 core members, expanding) with prior Solana/Rust experience.
• Publicly visible leadership is primarily via handles:
• “Plish” / “0xPlish” – repeatedly described as co‑founder/CEO of Hylo and gives technical and risk‑design interviews and podcasts.
• Other pseudonymous founders mentioned: “Sape” (Head of Growth) and “Shoom”, per independent airdrop/education coverage.
• Some coverage notes that the team emerged from Solana‑native communities/DAOs and Colosseum/accelerator ecosystems, suggesting prior ecosystem participation but not clearly named legacy projects. 2. Public vs. anonymous; prior track record
• Core founders appear pseudonymous (handles only, no clear legal names, LinkedIn, or doxxed profiles in major writeups).
• No independently documented prior protocol hacks or blow‑ups tied to these pseudonyms were found in secondary research; however, identity linkage is weak, so this is not strong exoneration. Not verifiable as of 2026‑08‑29. 3. Funding, signaling & institutional touchpoints
• Independent reports state Hylo won Colosseum’s Radar hackathon and subsequently raised a seed round led by Robot Ventures with Solana Ventures and Colosseum participating.
• A listed U.S. public company, DeFi Development Corp (Nasdaq: DFDV), publicly announced a treasury partnership with Hylo to use the protocol for SOL yield and points participation, and references Hylo’s rapid TVL growth and fee generation. This is a meaningful external validation of technical and operational seriousness, though not a guarantee of risk controls. 4. Jurisdiction, offices, and legal wrapper
• A stablecoin analytics profile explicitly lists “Jurisdiction: Not disclosed” for Hylo/hyUSD.
• No reliable evidence of a registered company name, physical office, or onshore regulatory licensing was identified in independent sources. Not verifiable as of 2026‑08‑29.
• Given pseudonymous founders, lack of disclosed jurisdiction, and typical Solana‑DeFi patterns, it is reasonable to assume an offshore or not‑formally‑disclosed structure, but this remains inference, not fact. 5. Reality check from an institutional lens
• Positives: credible ecosystem backers (Robot Ventures, Solana Ventures, Colosseum), technical depth, and a partnership with a U.S. public company.
• Negatives / unknowns: pseudonymous founders, no clear legal entity or regulatory posture, and no independently confirmed physical office or onshore presence. For an institutional profile, the *key gap* is formal KYC on founders, legal-entity documentation, and any regulatory filings; without these, Hylo sits squarely in the higher‑governance‑risk bucket despite strong technical and ecosystem signals.

Hylo Protocol currently has a constructive but relatively young reputation in Solana DeFi: it is seen as an innovative yield and leverage primitive with growing institutional interest, backed by at least one reputable auditor, and with no public fraud/rug/insolvency or sanctions allegations identified as of 2026‑08‑29. Founders, team, investors Public materials and research reports focus on the protocol’s design and products; they do not clearly disclose individual founders or major equity investors. Not verifiable as of 2026‑08‑29. Hylo has a partnership with DeFi Development Corp (Nasdaq: DFDV), a listed U.S. company that uses Hylo in its treasury strategy, which indicates some institutional comfort with the protocol. Audits and security posture Hylo has undergone an audit by OtterSec, a well-known Solana-focused security firm. The audit document is a follow‑up engagement in April 2025, which suggests ongoing rather than one‑off review. This supports a perception of moderate positive security reputation, but full coverage of all contracts and chains cannot be confirmed from the single report. Not verifiable as of 2026‑08‑29 for scope completeness. Sentiment and narrative Research reports and ecosystem write‑ups (Binance Square, KuCoin, IQ.wiki, CryptoBriefing, Alchemy, Solana community articles) generally describe Hylo as a “breakout” Solana DeFi protocol with a novel dual‑token stablecoin/leverage design and strong yield characteristics. These are largely positive and sometimes promotional in tone, emphasizing capital efficiency and “DeFi native money.” Criticisms, risk discussions, unresolved concerns Available materials do discuss risk factors—e.g., dependence on Solana LSTs and leveraged exposure, but mainly in analytical or educational terms rather than as accusations. No dedicated, critical investigative pieces or widely cited exploits are found. Not verifiable as of 2026‑08‑29 whether smaller incidents or near‑misses occurred. Fraud/rug/insolvency, legal/regulatory, sanctions No sources identified alleging rug pulls, fraud, insolvency, or formal regulatory enforcement actions against Hylo or its team. No listings in sanctions‑related coverage or regulator‑driven press materials specific to Hylo were found. Not verifiable as of 2026‑08‑29 for full global regulatory checks. Overall reputation assessment Hylo is perceived as a high‑growth, innovative Solana DeFi protocol with recognized audit work and at least one public‑company partner, but with limited transparency on founders/investors and no long multi‑year track record. For an institutional profile, this is promising but still emerging, with standard DeFi smart‑contract and design‑risk concerns remaining untested through major stress events.

Hylo is a Solana-only protocol that uses a single LST collateral pool to issue hyUSD (stablecoin), xSOL (leveraged SOL) and sHYUSD (yield-bearing hyUSD); all economics are driven by Solana staking yield and protocol fees, with no external incentives. Strategy & assets in/out

• In: Solana liquid staking tokens (LSTs) and SOL, which are staked with validators and MEV strategies.
• Out:
• hyUSD – overcollateralized USD-pegged stablecoin.
• xSOL – leveraged long SOL exposure with no funding rates and no liquidation in the traditional sense.
• sHYUSD – staked hyUSD deposited in the Earn/Stability Pool, tokenizing a claim on pooled yield. Yield source: organic vs subsidized, market-neutral vs directional
• Yield is endogenous/organic, sourced from:
• Native LST staking rewards (~6–8% base).
• Protocol fees and potential MEV/validator contributions on staked SOL.
• Rebalancing/risk premia when xSOL/hyUSD are adjusted.
• sHYUSD captures all staking rewards from the entire collateral pool, while hyUSD and xSOL themselves do not accrue yield.
• Economic exposure is directional to SOL at system level; sHYUSD holders are somewhat insulated from SOL price by overcollateralization, but not market-neutral.
• There is no evidence of token-emission subsidies; claims of “real yield” are consistent across independent analyses. Amplification, leverage, and internal flows
• Yield is amplified by redirecting all LST yield away from non-yield products (hyUSD, xSOL) into sHYUSD, so sHYUSD APY is a multiple of base LST yield (often 15–19% real yield reported).
• xSOL effective leverage is dynamic: \(\text{Collateral TVL} / \text{xSOL market cap}\).
• No evidence of external leverage/looping or restaking beyond Solana staking; external exposures are Not verifiable as of 2026-08-30. Lock-ups, withdrawals, mechanics
• sHYUSD / Earn Pool are epoch-based but non-locking; users can deposit/withdraw hyUSD and receive/return sHYUSD with auto-compounding per Solana epoch.
• hyUSD maintains its peg via overcollateralization (>160–210% CR cited) and redemption arbitrage; sHYUSD can be converted to xSOL in stress to defend the peg. Fees, protocol revenue, gates/limits
• Documentation references a “pool allocation” parameter splitting harvested yield between Earn Pool depositors and the treasury; this is the core revenue stream.
• Additional revenue from mint/redemption or rebalancing fees is discussed in research reports, but exact schedules are Not verifiable as of 2026-08-30. Collateral, TVL, APY history
• Collateral is a basket of Solana LSTs and staked SOL; detailed composition per validator/LST is Not verifiable as of 2026-08-30.
• DeFiLlama tracks Hylo as a single-pool Solana protocol with average APY ≈6% for underlying LSTs, contrasting with 15–20% APY on sHYUSD from concentrated yield.
• Specific TVL amounts and per-product breakdown on-chain are Not verifiable as of 2026-08-30; public articles mention growth toward $100M+ TVL and ~165k SOL in a major pool, which are unverified marketing/aggregator claims.
• APY exhibits high short-term volatility (e.g., 17–20% quoted, 7d/30d trailing yields 17.6%/15.8%), driven by validator performance and MEV; sustainability rests on continued Solana staking economics rather than emissions.

Hylo Protocol’s reserves/treasury are best described as a single Solana collateral pool backing hyUSD and xSOL, not a discretionary treasury: the docs state that collateral TVL equals the combined market value of hyUSD and xSOL, and xSOL price is derived from the pool’s variable reserve after hyUSD backing is set aside. The protocol docs do not disclose a fixed reserve address set, a treasury multisig, or a formal custody stack in the materials available here, so those items are Not verifiable as of 2026-08-29. For size, third-party analytics disagree materially: DeFiLlama shows $30.75M TVL on Solana, while RWA.xyz’s Hylo page shows $18.09M for Solana. Because no on-chain query is available in this run, the on-chain balance and current reserve size are Not verifiable as of 2026-08-29. For composition, available web sources indicate the collateral is SOL liquid-staking-token (LST) based; one independent report described the mix as predominantly JitoSOL, mSOL, and bSOL, but that specific split is not verifiable from the available primary sources here and should be treated as unverified. The documentation only confirms that the protocol uses a collateral pool of SOL LSTs. For control and policy, the docs describe an algorithmic invariant rather than active treasury management: total collateral value must equal hyUSD supply value plus xSOL market value, with reserve dynamics governing xSOL pricing and protocol balance. A normal collateralization threshold of 150% is described in secondary coverage, but the exact reserve policy wording is not independently verifiable here. For attestations, I found no reserve attestation, proof-of-reserves, or third-party custody attestation in the provided sources; this is Not verifiable as of 2026-08-29.

Hylo Protocol on Solana does not appear to have a separate native governance token; the protocol’s documented assets are hyUSD (stablecoin) and xSOL (leveraged SOL exposure), plus eHYUSD/hyloSOL variants, rather than a distinct protocol token. The documentation provides contract/mint addresses for these assets, including hyUSD at 5YMkXAYccHSGnHn9nob9xEvv6Pvka9DZWH7nTbotTu9E and xSOL at 4sWNB8zGWHkh6UnmwiEtzNxL4XrN7uK9tosbESbJFfVs. I could not verify total supply vs circulating supply, market cap, FDV, holder concentration, insider wallets, allocations to team/investors/treasury/community, mint/blacklist/fee-switch control, or any emissions/unlock schedule from the sources gathered here. I also could not verify any announced unlocks or whether they occurred on-chain. Per your requested standard: Not verifiable as of 2026-08-29. What is verifiable from the available sources is the protocol’s utility design: hyUSD is the flagship stablecoin, xSOL is a tokenized leveraged long position on SOL, and the protocol states that the sum of their market capitalizations equals the dollar value locked in the pool. Hylo also describes a yield-bearing variant, eHYUSD, and additional asset wrappers in its address registry. I could not verify revenue share, buybacks, burns, or staking rewards as explicit tokenomics mechanisms beyond the protocol’s described yield-bearing structure; Not verifiable as of 2026-08-29. Main external references found were documentation and third-party writeups, but they do not provide a reliable on-chain token distribution or governance picture. The protocol appears to be a Solana-native DeFi system rather than a conventional token project with a single governance asset, so the most accurate current classification is: no separately verifiable native token with public tokenomics based on the gathered sources.

Hylo’s documented stress mechanism is driven by SOL collateral ratio, not Bitcoin directly, so a BTC move below $10,000 is only relevant if it coincides with a broader crypto drawdown that also hits SOL. Hylo says it aims to keep system collateral ratio above 150% in normal conditions, enters Stability Mode 1 below 150%, and activates the stability pool below 130%; if collateral ratio falls to 100%, xSOL NAV goes to zero and hyUSD loses its hedge to SOL volatility. For a BTC < $10,000 scenario, the protocol-specific outcome cannot be mapped to a precise loss number from available sources, because Hylo does not publish a BTC-linked stress table and no on-chain verification is available in this run. Not verifiable as of 2026-08-29 for protocol-level loss magnitudes or insolvency thresholds under a BTC-specific crash. The practical risk interpretation is this: if a Bitcoin crash below $10,000 is part of a market-wide liquidation event, Hylo’s risk would likely manifest through falling SOL prices, shrinking collateral ratio, higher redemption pressure on hyUSD, and possible drawdown or conversion of staked hyUSD in the stability pool into xSOL. Third-party commentary on Hylo describes the same general failure mode: rapid SOL declines can exhaust the stability pool, push hyUSD below peg, and create severe losses for xSOL and possibly hyUSD holders. So, the concise institutional view is: BTC below $10,000 is not itself the trigger; SOL price decline and stability-pool depth are the key determinants of whether Hylo remains solvent and whether the peg holds.

Hylo’s stress response to a 20% depeg in the largest collateral is not fully verifiable from the available sources. The protocol’s documented mechanics indicate that hyUSD is designed to stay overcollateralized, with 150% as the healthy threshold and 130% as the point where Stability Mode 2 activates; if collateral ratio falls below 130%, the stability pool is drawn down and hyUSD is converted to xSOL to help restore coverage. What can be said with confidence is that a 20% collateral depeg would reduce the system’s collateral ratio in proportion to the size of that collateral’s weight in the backing set, but the exact impact depends on the current composition and live collateral ratio, which are not verifiable here. If the depegged asset is the largest collateral and the protocol starts above 150%, Hylo would first move toward Stability Mode 1 and then potentially Stability Mode 2 if the ratio breached 130%. The most relevant public claim about recent stress suggests Hylo remained operational during a market crash and reported no forced closures and no stability pool activation, but that statement is from the protocol itself and should be treated as an unverified marketing claim rather than independent evidence. Independent reporting also says Hylo’s TVL and risk metrics are sensitive to SOL price moves and collateral withdrawals, reinforcing that a large collateral shock is material to solvency and peg defense. Not verifiable as of 2026-08-29: the exact largest-collateral share, current collateral ratio, and whether a 20% depeg would trigger Stability Mode 2 or stability pool drawdown in the present state.

Hylo’s main “counterparties” are the Solana LST issuers (JitoSOL, mSOL, bSOL, etc.) and protocol users minting hyUSD, xSOL, and staking into the stability pool (sHYUSD). Because I cannot access on-chain data directly in this turn, detailed balance-sheet impacts are Not verifiable as of 2026-08-30 and are based on public documentation and independent analyses. Below is the top-stress case: largest LST counterparty becomes economically insolvent (massive loss or depegs vs SOL). ### 1. LST issuer / major LST depeg or haircut Event: One core LST backing Hylo (e.g., JitoSOL, mSOL, bSOL) suffers a permanent value impairment (slashed validator set, protocol exploit, or depeg vs SOL). Loss path:

• Hylo’s collateral pool holds LSTs; a depeg reduces the pool’s asset value versus hyUSD liabilities.
• The protocol’s “endogenous yield engine” (staking rewards of LSTs) drops or turns negative, shrinking the yield available to hyUSD+, sHYUSD, and leverage spreads on xSOL.
• If impairment is large enough, the collateral may be insufficient for full hyUSD redemption at $1, creating an undercollateralized stablecoin. Who absorbs loss:
• xSOL holders are first-loss capital because they implicitly hold leveraged long SOL exposure backed by the same LST pool; a drop in collateral value reduces xSOL intrinsic value and effective leverage.
• sHYUSD (stability pool) depositors are designed to backstop volatility and peg stability; their capital is used to absorb bad debt and undercollateralization, in exchange for protocol fees and yield in normal times.
• Ultimately, hyUSD holders bear residual risk if losses exceed xSOL and stability pool capacity; peg deviation or redemption haircuts are possible. Compensation / protections:
• Hylo advertises that yield paid to sHYUSD depositors is funded by *all* staking rewards and protocol fees to compensate them for being the safety buffer.
• There is no public indication of external insurance, RWA reserves, or bailout guarantees; protection is purely protocol-internal (xSOL equity + stability pool).
• Any governance-driven remediation (e.g., changing collateral mix, socialized losses, or migration incentives) would depend on Hylo governance decisions, which are Not verifiable as of 2026-08-30 from on-chain records. Smart-contract impact path (Solana):
• LST price/oracle feeds update; collateral valuation drops.
• hyUSD / xSOL mint–redeem math adjusts, likely worsening mint terms for new hyUSD and decreasing redeem value for xSOL.
• Stability pool contracts are triggered to cover shortfalls: sHYUSD may be converted/burned against bad debt, and associated rewards rebalanced.
• Yield distribution contracts (hyUSD+ vault, sHYUSD accrual) see lower or zero incoming staking yield, reducing APY and possibly halting new rewards. Given the lack of direct chain access this turn, detailed numeric loss splits per counterparty and per LST are Not verifiable as of 2026-08-30.

For the specific stress scenario of committed fraud by the DAO or owners, there is no verified public evidence in the provided sources that Hylo Protocol’s DAO or owners have committed fraud. The only directly relevant materials are an independent audit showing exploitable protocol vulnerabilities, not intentional fraud by insiders, and the protocol documentation describing risk mechanics rather than misconduct. What can be said is that Hylo had at least two audited critical issues that could have enabled economic exploitation if left unpatched: missing validation in LST registry loading, which could let an attacker manipulate the collateral ratio, and outdated EMA pricing during minting, which could allow minting at unfair rates. Those findings indicate security and solvency risk, but they do not establish DAO- or owner-led fraud. So, for this scenario, the status is: Not verifiable as of 2026-08-29. There is no source here showing an owner exit scam, treasury misappropriation, governance theft, or other intentional fraudulent conduct by Hylo insiders.

Hylo’s primary yield source for staked hyUSD is the protocol’s LST staking yield routed into the Stability/Earn Pool, so in a stress case where that source is negative over 30 days, the key implication is that the pool’s yield-bearing leg is no longer additive and the user outcome depends on whether other protocol revenue offsets the loss. For Hylo, the documentation says the Earn Pool aggregates yield from collateral pools and mints/distributes hyUSD to depositors, while protocol revenue also includes mint/redeem fees; however, the docs do not show a mechanism that guarantees positive net yield if the underlying LST leg is negative for a full month. The public docs instead describe yield as coming “exclusively” from LSTs for sHYUSD and note that the stability pool can be converted into xSOL during stress events, which means stress can shift value protection away from yield optimization and toward recapitalization mechanics. So, under a -30d primary yield scenario, the risk conclusion is:

• Yield compression or negative carry for sHYUSD holders if fee revenue is insufficient to offset the negative LST contribution.
• Higher balance-sheet stress because the same pool also functions as a backstop/insurance layer in adverse markets.
• Potential state change in the product if the protocol enters stress mode and converts part of the stability pool to xSOL, which can impair the expectation of a steady yield stream. What cannot be verified from the provided sources is the exact 30-day net APY under stress, the frequency of negative-yield months, or whether fee income has historically offset such periods. Not verifiable as of 2026-08-29.

Hylo Protocol’s governance on Solana is effectively company‑controlled, with only an early‑stage, mostly symbolic DAO footprint. Almost all concrete control over development, contracts and funds appears to sit with the founding team and affiliated entities. Because Dune MCP is unavailable, all on‑chain governance metrics (voting concentration, top holders, exact multisig structure, timelocks) are Not verifiable as of 2026‑08‑30. ### 1. Who controls dev, contracts, frontend, funds

• Development & product decisions: Controlled by the Hylo core team; there is no evidence of a formal, on‑chain governance framework making protocol upgrades subject to tokenholder votes.
• Smart contracts: Public sources (explorers, analytics) indicate deployer/upgrade authority is held by team‑controlled addresses or program upgrade authorities, but exact keys, upgrade policies and any timelocks are Not verifiable as of 2026‑08‑30.
• Frontend (hylo.so): Hosted and operated by the company; no evidence of front‑end routing controlled by a DAO.
• Treasury/funds: Treasury management appears team‑run; there is no independently documented, binding on‑chain treasury mandate (e.g., DAO‑controlled multisig with transparent charter). All claims about decentralized control in marketing materials should be treated as unverified marketing claims unless backed by independent audits or governance records. ### 2. Governance / DAO structure
• There is no clear, detailed public description of a functioning DAO with formal proposal and voting processes comparable to mature DeFi protocols.
• Proposal mechanics (who can propose, quorum, thresholds, veto rights) are Not verifiable as of 2026‑08‑30.
• No independent record (Snapshot, Realms, etc.) shows recurring tokenholder votes with binding impact on upgrades or treasury allocation. Given this, the DAO is best characterized as symbolic/aspirational at this stage. ### 3. Voting concentration, top holders, delegations
• Without Dune or confirmed token addresses, holder concentration, top 20 wallets, and delegation patterns are Not verifiable as of 2026‑08‑30. ### 4. Multisig / timelocks / powers
• Any upgrade authority multisig (if present), its signers, threshold, and whether signers are independent of the company are Not verifiable as of 2026‑08‑30.
• Presence or absence of timelocks on critical actions (upgrades, treasury moves) is likewise Not verifiable as of 2026‑08‑30. ### 5. Legal entity, jurisdiction, ToS
• Public materials indicate a corporate operator behind Hylo (implied by hosted frontend, branding, and typical Solana DeFi practice), but the exact legal entity name, jurisdiction, registration number, and directors are Not verifiable as of 2026‑08‑30.
• Terms of Service for hylo.so, including dispute jurisdiction and user rights, are Not verifiable as of 2026‑08‑30 (access restricted in this run). From an institutional risk lens, Hylo should be treated as founder‑controlled infrastructure with opaque governance, pending verifiable disclosures (audits, governance framework, legal entity details, and on‑chain controls).

Hylo Protocol appears to be an on‑chain yield/strategy protocol built on Solana, operated via a foundation structure, with relatively standard crypto‑native terms but some notable regulatory‑risk points. All on‑chain verification is Not verifiable as of 2026‑08‑30. ### 1. Legal entity & jurisdiction

• Hylo is associated with Hylo Foundation, described as a non‑profit working on “infrastructure for dynamic reward systems,” but its incorporation jurisdiction is not clearly disclosed on the public site.
• No explicit registration as a VASP, broker‑dealer, or investment adviser is visible in public materials. ### 2. Terms of Service / User restrictions
• Hylo’s docs and site emphasize that it is non‑custodial and that users retain control of assets via their own wallets (e.g., Phantom, Solflare).
• Access appears permissionless: there is no visible geo‑blocking or explicit exclusion of US or other high‑risk jurisdictions on the public app interface.
• Because the site does not prominently surface a detailed ToS, standard contractual protections, dispute resolution clause, and governing law remain unclear. Not verifiable as of 2026‑08‑30. ### 3. KYC / AML
• The protocol runs on Solana and connects to self‑custody wallets with no KYC onboarding or identity checks mentioned.
• There is no description of AML procedures, sanctions screening, or transaction monitoring consistent with regulated financial institutions. Not verifiable as of 2026‑08‑30. ### 4. Product classification risk
• Hylo designs “dynamic rewards” and yield strategies that could be viewed by regulators as investment products or collective investment schemes, depending on jurisdiction.
• There is no public legal analysis or classification (e.g., utility vs. security token, fund vs. pure protocol) available. ### 5. Warnings, enforcement, court cases, sanctions
• No records of regulatory warnings, enforcement actions, sanctions listings, or court cases specific to Hylo or Hylo Foundation were found in major news, regulator sites, or sanctions databases. Not verifiable as of 2026‑08‑30. ### 6. Data protection & privacy
• As a non‑custodial dApp relying on Solana wallets, most data is on‑chain, but the site’s specific privacy policy, data retention practices, and cross‑border data transfer rules are not clearly disclosed. ### 7. Legal structure vs actual risk (institutional view)
• Non‑custodial design reduces direct custody risk but does not remove regulatory risk around offering unregistered investment products or operating an unlicensed investment service.
• Lack of clear jurisdiction, ToS, and compliance framework is a material risk for institutional use; any regulated institution would likely need:
• Confirmation of the foundation’s domicile and governance
• Written legal opinions on classification
• Clarity on sanctions/KYC controls or a wrapper solution providing those.

Hylo’s stablecoin hyUSD has depegged at least once in the sources I found, but the exact full count is Not verifiable as of 2026-08-29 from independently confirmed on-chain data. The clearest independently reported datapoint is an all-time low of $0.9862 on 2025-10-10, which implies a maximum observed depeg of about 1.38% below peg versus $1.00. I found one analytics source claiming hyUSD had “only three depeg events on record,” but that figure is not independently corroborated here and should be treated as unverified marketing/analytics output rather than a confirmed fact. So, based on the available sources: yes, a depeg happened; the last verifiable one was on 2025-10-10; and the observed depth was about 1.38% below peg at the low.

Hylo Protocol’s top risks are: 1) SOL/LST price correlation risk — hyUSD depends on SOL-based liquid staking collateral, so a sharp SOL drawdown can compress collateral ratios and stress the peg. 2) Mechanism/reflexivity risk — xSOL absorbs volatility, so in a downturn leverage can increase and feed a reflexive loop that forces harsher stabilization actions. 3) Stability-pool insufficiency risk — if the buffer pool is too small during a fast selloff, the protocol may not absorb losses or rebalance quickly enough, increasing the chance of hyUSD instability. 4) Smart contract risk — like any DeFi system, bugs in mint/redeem, accounting, or edge-case logic could cause loss of funds or protocol insolvency; external reviews reduce but do not eliminate this risk. 5) Solana infrastructure / operational risk — Hylo is Solana-native, so network congestion or outages during volatile markets could prevent timely rebalancing and worsen losses.

Hylo Protocol’s top strengths are: Solana-native design, which lets it benefit from low fees and fast execution on the Solana network; an innovative token model, where a shared LST-backed system separates stablecoin utility (hyUSD/sHYUSD) from leveraged SOL exposure (xSOL); no-liquidation leverage, which gives users SOL upside without margin calls or liquidation risk; yield generation from on-chain LST collateral, which supports a real-yield stablecoin rather than relying on fiat reserves; and security/composability advantages, including an oracle-free, permissionless design that is meant to integrate cleanly with the broader Solana DeFi stack.