Liminal Basis

Protocol identification

• Name: Liminal Basis (product line of the Liminal protocol).
• Website: liminal.money.
• Docs: docs.liminal.money.
• Category: Automated delta‑neutral yield / basis & funding‑rate strategies built on Hyperliquid’s perp and spot markets, packaged as DeFi vaults/strategies.
• Launch date: Not verifiable as of 2026‑09‑04 (docs and media describe architecture and products but do not clearly state mainnet launch date).
• Chains (user touchpoints):
• Hyperliquid L1 / HyperEVM: execution layer for all strategies; Liminal is described as “Hyperliquid’s Native Yield Layer” and runs natively on Hyperliquid.
• Arbitrum: used for USDC deposits/withdrawals and cross‑chain access to Hyperliquid via Liminal; docs explicitly mention Arbitrum for deposits and withdrawals.
• Ethereum, Base, BNB, HyperEVM: supported for deposits/withdrawals via deBridge, but strategies still execute on Hyperliquid.
• Native / protocol tokens:
• limUSD: described in docs as a portfolio‑optimized USD yield token in the “Tokenized” product line.
• xTokens: fungible leveraged delta‑neutral basis/funding strategies (long spot/LSTs, short perps) whose NAV accrues funding and spot yield.
• A distinct governance token for Liminal Basis is not documented; not verifiable as of 2026‑09‑04.
• Main contract addresses & explorer verification:
• Liminal operates primarily on Hyperliquid L1 / HyperEVM and interacts with Hyperliquid’s trading and bridge infrastructure.
• Specific Liminal Basis vault/strategy contract addresses on HyperEVM, Arbitrum, or Ethereum are not listed in public docs, media, or independent research sources consulted; therefore not verifiable as of 2026‑09‑04.
• Explorer verification status for any Liminal contracts is likewise not verifiable as of 2026‑09‑04. Fork lineage & modifications
• Public docs and independent analyses describe Liminal Basis as an original structured‑yield protocol built on Hyperliquid, not as a fork of a known upstream AMM or vault (e.g., Perpetual Protocol, GMX, Gamma). No credible source identifies it as a fork; thus any fork status is not verifiable as of 2026‑09‑04.
• Design changes (custom delta‑neutral strategies, tokenized xTokens/limUSD, self‑custody vs regular modes) are documented as bespoke architecture on top of Hyperliquid’s trading infrastructure.
• Audits: Docs and media consulted do not provide a clearly referenced smart‑contract audit report for Liminal Basis strategies; existence, scope, and auditor are not verifiable as of 2026‑09‑04.
• Malicious‑modification history in similar forks: No independent report or incident database entry was found describing malicious modifications or exploits in Liminal Basis or direct forks thereof; therefore, presence or absence of such history is not verifiable as of 2026‑09‑04.

Liminal Basis looks like a real operating product rather than a pure landing page: the public site, docs, and app-facing guidance describe deposit, withdrawal, strategy selection, and portfolio flows, and the docs explicitly say deposits trigger immediate spot/perp execution and withdrawals can be initiated instantly. The product also appears to have an API layer for wallet and transaction operations, with documentation for creating hot wallets, sending transactions, and retrieving balances/pending transactions. I could not verify live app health, broken links, or whether the website currently has template/fake-metric signs from the available web evidence alone.

Not verifiable as of 2026-09-04. The chain routing in the docs suggests the product supports Hyperliquid, Arbitrum, and cross-chain deposit/withdrawal paths from Ethereum and other EVM chains, but I could not independently confirm current live deposits/withdrawals on-chain here. Not verifiable as of 2026-09-04. ## Assessment

• Real portal vs landing: real portal / productized app, not just a brochure site.
• App functionality: deposit, withdrawal, wallet ops, and strategy execution are documented.
• Live deposits/withdrawals: claimed in docs, but not independently verifiable here.
• Docs/UX: appears relatively mature, with user guides, fee pages, and API references.
• Open API: yes, documentation explicitly references RESTful APIs and wallet/transaction endpoints.
• Broken links / fake metrics / template signs: Not verifiable as of 2026-09-04.

Not verifiable as of 2026-09-04. The only web evidence found points to a bug bounty page for Liminal Custody, not clearly the DeFi protocol Liminal Basis; that page lists rewards of HoF to $100, $100 to $300, $300 to $500, and $500 to $1000, but it does not establish that this is the selected protocol’s active bounty program or confirm a start date/results for Liminal Basis specifically. Because of the name-collision risk, the program cannot be safely attributed to Liminal Basis from the available evidence.

Assessment as of September 6, 2026. Dune MCP is unavailable; therefore balances, collateral composition, permissions, venue positions, and percentage exposures are Not verifiable as of September 6, 2026. Core counterparty — Hyperliquid. Liminal’s principal strategy is long spot/HYPE (sometimes LST-based) against short Hyperliquid perpetuals. This creates material dependence on Hyperliquid execution, order-book liquidity, uptime, funding conditions, liquidation mechanics, HLP backstop capacity, and ADL. A prolonged outage, market dislocation, bad-debt event, negative funding regime, or forced hedge closure could impair NAV, yield, or redemptions.

Liminal itself identifies downtime, negative funding, liquidity constraints, and ADL as risks. Oracle risk. xHYPE uses Pyth price feeds plus Liminal NAV/price-oracle contracts. Oracle staleness, manipulation, incorrect NAV publication, or compromised updater/guardian controls could cause incorrect minting, redemptions, liquidations, or secondary-market pricing. Liminal’s “institutional-grade” custody/multisig safeguards are protocol claims, not independently verified here. Bridge and chain risk. xTokens use a LayerZero V2 hub-and-spoke/OFT design, with HyperEVM as hub and Ethereum/Arbitrum as spokes.

LayerZero messaging, endpoint, token-accounting, or chain-finality failures could strand or misrepresent shares; redemption may require routing through the hub. Asset and issuer dependencies. xHYPE may hold kHYPE, creating Kinetiq/LST staking, redemption, validator, and depeg exposure. Strategies settle in USDC, adding Circle issuer/depeg risk. Liminal documents integrations with HyperLend, Pendle, and Project X; these are additional composability/liquidity risks if users deploy xTokens there, but core protocol exposure is not quantified. Custodian/CEX/MM/RWA. No independently verified CEX, market-maker, RWA issuer/SPV, or named third-party custodian exposure was found. Not verifiable as of September 6, 2026. > Contradiction / data gap: DeFiLlama currently reports $24.17m TVL, 100% on Hyperliquid L1, while the supplied metadata lists Arbitrum, Ethereum, and Hyperliquid L1.

This is aggregator data, not on-chain verification; the chain split is Not verifiable as of September 6, 2026. Stress scenarios: Hyperliquid outage or ADL; kHYPE/USDC depeg; oracle failure; LayerZero bridge failure; negative funding; insufficient exit liquidity; smart-contract/admin-key compromise. No active failure was confirmed in the reviewed sources.

Liminal Basis appears to offer two custody modes: regular users use a Liminal-managed EOA and the docs say those funds are held in a dedicated, segregated EOA with withdrawals initiated by the user, while self-custody users keep assets in their own Hyperliquid sub-account and authorize Liminal only as a trade-only agent. The docs also say self-custody users give no transfer or withdrawal rights to Liminal, and withdrawals are available from Hyperliquid Spot and Arbitrum for regular users, while self-custody withdrawals are Hyperliquid-only. There is no verified evidence here that withdrawals are currently paused, and the source set does not support a chain-level determination that all assets are segregated across every deployment, so that remains only partially verifiable from the available material.

No incident since launch was verifiable from the available web results for Liminal Basis. The only clearly related security event in the results concerns WazirX’s July 2024 multisig-wallet breach while using Liminal’s custody/interface stack, but the results do not verify that this was an exploit of Liminal Basis itself.

Liminal Basis appears to organize key management around institutional wallet infrastructure that supports MPC or multisig setups, with policy- and threshold-based controls for transfers. Its documentation also says the system is API-driven and designed to safeguard private keys, while a separate limited-use API key mechanism adds scoped, time-bounded access for integrations. For the protocol-facing angle, Liminal’s public materials say users can run strategies from their own Hyperliquid account via a native agent system while keeping full custody of assets, which implies the user’s signing authority remains central rather than being handed to the protocol.

What is not verifiable as of 2026-09-04 from the available sources is the exact operational model for key custody across Arbitrum, Ethereum, and Hyperliquid L1: for example, whether keys are generated in an HSM, how shards or signer roles are distributed, whether there is social recovery, and what the precise rotation/backup/revocation workflow is. So, the best-supported characterization is: Liminal Basis uses programmable, policy-controlled wallet infrastructure (MPC/multisig) plus scoped API credentials, with custody intended to remain with the user or institution rather than being openly delegated to the protocol.

As of September 6, 2026. On-chain verification was unavailable; no Dune query/ execution IDs are available. Addresses / verification. The current public documentation identifies xHYPE contracts on HyperEVM (chain 999), Arbitrum, and Ethereum, including ShareManager 0xac962f...51e03, DepositPipe 0xE7E0...0efc9F9, RedemptionPipe 0x19f4...6C03e8, NAVOracle 0xbF97...7bfF042, PriceOracle 0xC415...71d5D, and TimelockController 0x7540...B7491. Arbitrum and Ethereum list ShareOFT contracts.

These are protocol-published addresses; verified source status, exact implementation addresses, and whether they match current production deployments: Not verifiable as of 2026-09-06. Architecture. Hub-and-spoke design: user deposits → chain-specific DepositPipe → LayerZero messaging → HyperEVM ShareManager/vault and strategy/oracle layer → RedemptionPipe; spoke ShareOFTs represent cross-chain positions. Underlying trading/strategy execution occurs on Hyperliquid infrastructure, creating an additional execution and custody dependency. ``text Ethereum / Arbitrum ShareOFT + DepositPipe │ LayerZero ▼ HyperEVM hub (chain 999) ShareManager ─ NAV/Price Oracles │ Strategy / Hyperliquid execution │ RedemptionPipe → USDC ▲ TimelockController (published) `` Upgradeability and privileged functions. Proxy standard, implementation slots, proxy-admin type, owner/admin addresses, role membership, pause/unpause, emergency withdrawal, fee changes, oracle updates, strategy migration, and upgrade calldata: Not verifiable as of 2026-09-06. Timelock existence is documented, but its effective delay and whether it controls every privileged path are Not verifiable as of 2026-09-06. User exit / key compromise. Documentation states withdrawals are intended to be available without fixed lockups, while self-custody mode gives Liminal trade-only—not withdrawal—permissions. This is a protocol claim, not an on-chain verification.

If privileged keys control upgrades, oracle/NAV, pause, or redemption logic, worst case is fund theft, NAV manipulation, frozen redemptions, or permanent loss; exact drainability is Not verifiable as of 2026-09-06. > Contradiction / data-quality finding: DeFiLlama currently attributes 100% of tracked TVL to Hyperliquid L1, while its yield-server issue reports duplicated global NAV across Hyperliquid, Ethereum, and Arbitrum. Aggregated multi-chain TVL should not be treated as independent exposure. Audit status. The project claims Spearbit and Pashov audits for xTokens, but audited-deployment correspondence and unresolved findings are Not verifiable as of 2026-09-06.

Auditor: Cantina Managed review (Denis Miličević, Slowfi); report publication date: October 29, 2025; scope: liminal-contracts at commit 55346a53, including ShareManager, NAVOracle, FeeManager, DepositPipe, RedemptionPipe, DepositForwarder, PythPriceOracle, VaultTimelockController, and omnichain vault-composer contracts. Findings: 0 critical, 0 high, 6 medium, 8 low, 8 gas-optimization, and 12 informational findings. Medium findings concerned privileged redemption fees, refund-recipient conversion, oracle parameter timelocks, timelock administration, NAV-setting/drain safeguards, and oracle manipulation.

Fix status: 25/34 fixed and 9 acknowledged; all 6 medium findings fixed and verified by Cantina Managed; 7/8 low findings fixed, 1 acknowledged. Covers deployed code: Not verifiable as of 2026-09-05. The report is tied to commit 55346a53 and provides no verified deployed-address/bytecode match; therefore it should not be treated as confirming all deployed contracts.

Corrected and rechecked. Cantina Managed review of Liminal’s liminal-contracts codebase; official Cantina listing identifies the Liminal review as running October 12–21, 2025, and the report identifies commit 55346a53. The report covers ShareManager, NAVOracle, FeeManager, DepositPipe, RedemptionPipe, PythPriceOracle, VaultTimelockController, VaultComposer and omnichain/LayerZero contracts.

Bytecode match to currently deployed contracts on Arbitrum, Ethereum and Hyperliquid L1: Not verifiable as of 2026-09-06.

Previously recorded report rechecked. Liminal’s current site confirms that xTokens were audited by Spearbit and Pashov, but the exact report text, issue table and remediation evidence were not retrievable in this run. Bytecode match to currently deployed Arbitrum, Ethereum and Hyperliquid L1 contracts: Not verifiable as of 2026-09-06.

This remains an unverified marketing claim for deployed-code coverage.

Liminal’s audits page says Pashov conducted a security audit and that the reports are publicly verifiable and available for download. The available search result does not include the report contents, so the audit date, scope, critical/high/medium findings, remediation status, and coverage of deployed code are not verifiable from the provided evidence.

Security audit of Liminal’s xTokens smart contracts, per Liminal’s audits page.

Liminal’s audits page says Spearbit conducted a security audit and that the reports are publicly verifiable and available for download. The page does not expose the report text in the search result, so the exact audit date, scope, finding counts, fix status, and whether the report explicitly covers deployed code are not verifiable from the provided evidence.

Not verifiable as of 2026-09-04. The web results I found are mostly for other companies named Liminal or unrelated projects, not clearly the DeFi protocol Liminal Basis, so I cannot reliably identify founders, team members, office, or incorporation details without a namesake risk. The one relevant clue is a LinkedIn post mentioning a demo of “Liminal” to Coinbase Base Batches and naming a founder/CEO, but it does not establish that this is the same protocol or provide enough evidence to assess prior projects, hacks, public vs anon status, or whether there is a real operating business.

Because the protocol identity itself is not confirmed from the retrieved sources, the founder/team/credibility review remains unverified.

Available information portrays Liminal Basis (Liminal) as a relatively new, specialized basis‑trading / delta‑neutral yield protocol closely tied to Hyperliquid, with no public record of fraud, rug, insolvency or regulatory actions as of 2026‑09‑04. ### General reputation & sentiment

• Independent write‑ups (Oak Research comparisons, DefiLlama listing, Alchemy dApp directory) describe Liminal Basis as an automated, market‑neutral basis/funding‑rate strategy protocol for Hyperliquid, focusing on stable, delta‑neutral yield.
• A French crypto media article presents Liminal as a “protocole DeFi… qui automatise les stratégies delta‑neutral” and explains its mechanics in generally positive, informational terms.
• Coverage in The Defiant on TVL >$90m frames Liminal as Hyperliquid’s “native yield layer” and emphasizes institutional sub‑account automation and xTokens, again with non‑alarmist, neutral‑to‑positive tone. Overall, current public sentiment appears constructively positive but still early‑stage, with most discussion focused on yield mechanics and integrations rather than risk incidents. ### Founders, investors, auditors
• I could not locate independently verified information on founder identities, team backgrounds, major investors, or completed smart‑contract audits from auditor websites.
• Not verifiable as of 2026‑09‑04.
• Docs state architectural choices (integration with Hyperliquid’s HyperCore, no reliance on HyperEVM for some products) and fee structures, but these are unverified marketing claims pending third‑party confirmation. ### Criticisms, risk discussions, concerns
• Independent pieces focus on strategy description and comparisons, not on documented incidents or sharp criticism.
• Key *implicit* concerns raised by analysts/media:
• Strategy risk: dependence on funding/basis spreads and execution quality on Hyperliquid (market‑neutral but not risk‑free).
• Platform concentration: Liminal is “Hyperliquid’s Native Yield Layer,” operating “exclusively” or primarily on Hyperliquid, so users inherit exchange‑level risk.
• Custody/execution model: docs emphasize user custody via sub‑accounts, but this remains a design claim; operational and governance controls are not independently mapped. ### Fraud/rug/insolvency & legal/regulatory status
• I found no reports of:
• Hacks, insolvency, or user fund losses.
• Fraud, rug pulls, or serious misconduct.
• Formal regulatory enforcement actions, sanctions lists, or court cases mentioning Liminal Basis/Liminal.
• Not verifiable as of 2026‑09‑04 beyond public web sources. ### Unresolved information gaps
• On‑chain verification (per‑chain), formal audits, founder KYC, investor base, and regulatory posture cannot be verified under current data and tooling constraints.
• For an institutional profile, these gaps should be treated as open due‑diligence items, not as evidence of cleanliness or risk.

Economic model (as of September 6, 2026)

• Strategy/assets: Delta-neutral basis/carry: deposits of USDC, USDT or USDT0 fund a matched long spot and short perpetual position on Hyperliquid. Yield primarily comes from perpetual funding; staking or money-market lending may apply to some tokenized strategies. Price direction is intended to be neutral.
• External exposure/leverage: Current documentation describes execution on Hyperliquid infrastructure, not centralized-exchange execution. Customized users can select assets, allocations and leverage; leverage increases notional exposure and therefore liquidation, funding-reversal and execution risk. Exact maximum/current leverage is Not verifiable as of 2026-09-06. No restaking or recursive DeFi looping was identified.
• Organic vs subsidized: The stated yield source is market funding and related carry, not token emissions. However, the percentage that is organic versus incentives is Not verifiable as of 2026-09-06; organic_yield_pct: null.
• Products/collateral: Customized is user-specific/segregated; Tokenized products mint xTokens representing pooled strategy shares, usable as DeFi collateral. Exact collateral composition by product is Not verifiable as of 2026-09-06.
• Withdrawals/limits: Customized has no lockup; users can partially or fully withdraw, with the engine unwinding the hedge. Minimum deposit is 500 USDC. Tokenized standard redemption can take up to three days; instant redemption is immediate only if the liquidity buffer is sufficient and charges 0.3%.
• Fees/revenue: Customized charges a 10% performance fee on profitable gross funding after execution costs and a 1-bp builder fee. Cross-chain routes add 0.04% deBridge plus 0.02% Liminal fees; Hyperliquid trading fees are external execution costs. These fees are the identifiable protocol-revenue sources.
• TVL/APY: DeFiLlama reports $24.16m TVL, all on Hyperliquid L1, down 4.1% over 30 days; it tracks seven pools with 7.8% average supply APY. limUSD is shown at 7.26% APY, with “volatile” 30-day stability. APY is not a final net return because spreads, slippage and trading fees may be excluded. Contradiction / data gap: User-provided chain scope includes Arbitrum and Ethereum, but current DeFiLlama TVL attributes 100% to Hyperliquid L1; Arbitrum/Ethereum appear to be deposit/bridge access routes rather than strategy TVL. Dune comparison, TVL by product, historical APY volatility series, and trend reconciliation are Not verifiable as of 2026-09-06. leverage_ratio: null. The 2026-09-04 evidence URLs were example.com placeholders and were not usable evidence.

As of September 6, 2026, reserves/treasury are not independently verifiable. Dune/on-chain verification was unavailable in this run; therefore no Dune query ID, execution ID, block-height snapshot, reserve address, or chain-level balance can be provided.

• Size/composition: Not verifiable as of September 6, 2026. DeFiLlama reports approximately $24.16 million TVL on Hyperliquid L1, but TVL is an analytics-platform estimate, not proof of liquid reserves or treasury assets.
• Multi-chain exposure: The supplied Arbitrum/Ethereum/Hyperliquid deployment scope should not be interpreted as three separate reserve pools. A DefiLlama adapter issue reported that one global Hyperliquid NAV had previously been duplicated across deployments, with estimated real NAV materially below the aggregate displayed pool figures. This is an analytics-data-quality finding, not an independent reserve attestation.
• Addresses and on-chain balances: Not verifiable as of September 6, 2026. No independently confirmed reserve, treasury, custodian, or strategy-wallet address was established.
• Custody/control: The documentation describes automated delta-neutral strategies and notes that Hyperliquid’s ADL mechanism is outside Liminal’s control; it does not establish legal custody, segregation, multisig signers, withdrawal controls, or treasury ownership.
• Reserve policy: Not verifiable as of September 6, 2026. No independently sourced minimum-reserve, insurance-fund, liquidity-buffer, or redemption-policy documentation was located.
• Attestations/audits: Not verifiable as of September 6, 2026. DeFiLlama labels the product as having audits, but no auditor report or reserve attestation was independently confirmed in this check. Contradiction / data-quality callout: Any aggregate multi-chain TVL figure that sums the same global NAV across Arbitrum, Ethereum, and Hyperliquid would be overstated; the on-chain reserve amount remains unverified here.

Liminal Basis does not appear to have a live native token on Arbitrum, Ethereum, or Hyperliquid L1 as of the latest available data. All specific tokenomics items requested are therefore Not verifiable as of 2026-09-04. I’ll walk through what can and cannot be established. 1. Existence of a native token

• Web search returns references to Liminal Basis as a DeFi/yield strategy concept and research content, but no credible, chain‑linked token contract, ticker, or listings on major DEXes/CEXes on Arbitrum, Ethereum, or Hyperliquid L1.
• No independent analytics (DefiLlama, Token Terminal, etc.) list a "Liminal Basis" token or protocol entry with token metrics.
• No explorer pages (Etherscan, Arbiscan) can be confidently linked to a canonical "Liminal Basis" token contract; matches either do not exist or cannot be resolved to this protocol with high confidence. Given the research rules and missing on‑chain/Dune access, any assumption of a token would be speculative. Under the Missing data rule, the correct statement is that a native token cannot be verified. 2. Token details (ticker, address, supply, cap/FDV, utility)
• Ticker, contract address, total vs circulating supply, market cap, FDV, and token utility/governance role: Not verifiable as of 2026-09-04.
• No credible audit reports, governance forums, or investor materials describing a Liminal Basis token distribution or role. 3. Economics: revenue share, buybacks, burns, staking rewards, emissions
• Any revenue share, buyback/burn mechanisms, staking rewards, or emissions schedule tied to a token: Not verifiable as of 2026-09-04. 4. Unlocks, allocations, insider concentration
• Unlock schedule, whether unlocks occurred on‑chain, allocations (team/investors/treasury/community), and top‑holder/insider concentration: Not verifiable as of 2026-09-04. 5. Contract controls (mint, blacklist, fee‑switch)
• Presence of mint/blacklist/fee‑switch functions and who controls them cannot be linked to a specific verified token contract for Liminal Basis: Not verifiable as of 2026-09-04. 6. DEX liquidity and listings
• No verifiable DEX pools or CEX listings for a Liminal Basis token on Arbitrum, Ethereum, or Hyperliquid L1: Not verifiable as of 2026-09-04. For institutional risk purposes, treat Liminal Basis as having no confirmed native token until a contract and ticker can be independently verified via explorers and analytics, with clear linkage to the protocol.

Liminal Basis is not verifiable as of 2026-09-04 from the provided sources, so I cannot state protocol-specific solvency, TVL, vault, or liquidation impacts with confidence. For the stress case you specified, the only defensible conclusion is that a Bitcoin move below $10,000 would be a severe tail-risk macro shock and could materially impair any BTC-linked or BTC-collateralized DeFi strategy, especially if it coincides with liquidity contraction, ETF outflows, forced deleveraging, or a broader risk-asset selloff. For Liminal Basis on Arbitrum, Ethereum, and Hyperliquid L1, the protocol’s chain-by-chain exposure, collateral composition, debt structure, liquidation thresholds, and hedging design are Not verifiable as of 2026-09-04.

Because I cannot confirm the protocol’s actual positions from on-chain data in this run, I also cannot quantify which chain bears the largest share of the stress or whether the protocol uses segregated risk per chain. What can be said generally is:

• If the protocol is long BTC delta, a sub-$10,000 BTC print would likely compress NAV and may trigger margin/liquidation pressure.
• If the protocol is basis/hedged, the main risks shift to funding dislocation, exchange/venue basis blowouts, collateral haircut changes, and execution slippage during stress.
• If the protocol relies on cross-chain liquidity, contagion can propagate unevenly across Arbitrum, Ethereum, and Hyperliquid depending on where collateral and debt are actually parked; that allocation is Not verifiable as of 2026-09-04. If you want a usable risk memo, I need protocol-specific on-chain positions or a validated dashboard; otherwise the correct output remains: Not verifiable as of 2026-09-04 for exposure and loss estimates.

Not verifiable as of 2026-09-04. I could not confirm the protocol’s collateral set, chain-specific positions, or liquidation parameters from the provided results, so I cannot quantify the impact of a 20% depeg on the largest collateral. In general, a 20% collateral price drop can push an already high-LTV loan above liquidation thresholds and, in stressed conditions, can leave the liquidation process unable to fully repay the debt if the initial collateralization was thin.

That means the key risk outputs to check for Liminal Basis would be: which asset is the largest collateral by value, whether it is isolated to one chain or spread across Arbitrum, Ethereum, and Hyperliquid L1, and whether a 20% haircut would breach health-factor or LTV limits. None of those protocol-specific inputs are verifiable from the supplied sources. The most defensible conclusion is that the scenario is potentially material, but the actual loss or bad-debt estimate is Not verifiable as of 2026-09-04.

Stress scenario — insolvency of the principal execution/settlement counterparty (Hyperliquid/HLP). Liminal’s basis trade pairs spot exposure with an equal short perpetual position on Hyperliquid; Tokenized products pool users into one line, while xTokens represent proportional claims on that pool.

• Expected loss path: Hyperliquid’s clearing/liquidity layer cannot honor profitable perp settlement, collateral withdrawals, or liquidation proceeds. The spot leg may remain valuable, but the short-leg receivable and/or margin becomes impaired. A gap, liquidation loss, or venue failure therefore converts a nominally delta-neutral position into a direct NAV loss.
• Who absorbs it: First, the affected strategy’s pooled holders absorb losses through a lower NAV/share price. Hyperliquid’s own liquidity/insurance and ADL mechanisms may socialize losses before that point; Liminal documentation describes ADL as the backstop when HLP becomes undercollateralized. No Liminal principal guarantee or dedicated user-loss insurance was identified — Not verifiable as of September 5, 2026.
• Compensation/recovery: Recovery would depend on Hyperliquid’s venue-level remediation, insurance assets, or legal recovery. Liminal’s “instant redemption” buffer is a liquidity facility, not loss compensation; standard redemption can take up to three days. No contractual compensation waterfall was identified — Not verifiable as of September 5, 2026.
• Smart-contract impact path: HyperEVM NAVOracle reports impaired NAV → ShareManager’s share value falls → new mints receive fewer shares and redemptions return fewer USDC. RedemptionPipe burns xTokens and pays available USDC; if liquidity is insufficient, withdrawals are delayed or suspended operationally. LayerZero spoke tokens on Ethereum and Arbitrum remain claims on the impaired hub pool, not separately collateralized assets. Contract addresses and this hub-and-spoke design are documented for xTokens. Secondary counterparty stresses: Kinetiq/kHYPE failure would impair the xHYPE spot leg and NAV; custodian/agent failure could trap assets off-contract. In both cases, holders—not Liminal’s contracts—bear the residual loss unless an external recovery source exists. Exact exposure by chain and counterparty: Not verifiable as of September 5, 2026 (Dune unavailable). Note that DeFiLlama has previously duplicated one hub NAV across three chains; its displayed chain TVL should not be treated as separate exposure.

For a committed-fraud-by-DAO-or-owners stress scenario, the practical answer is: yes, loss is possible on Hyperliquid’s bridge layer, but the mechanism is different from a classic DAO treasury rug. Hyperliquid’s official bridge design says withdrawals require signatures from 2/3 of the stake-weighted validator set, and the bridge can be locked during a dispute period if a malicious withdrawal does not match Hyperliquid state. Independent coverage likewise states that compromising a majority of validators could, in principle, authorize fraudulent withdrawals from the Arbitrum bridge contract.

For Arbitrum, the relevant risk is not a simple owner-drain but a governance/security-council intervention. Arbitrum’s docs describe the chain’s fraud-proof system and note that Ethereum acts as the arbiter for disputes. Separate reporting shows the Arbitrum Security Council has used upgrade authority to freeze and move assets in an emergency, and that the resulting funds were placed under further Arbitrum DAO governance control.

That means a malicious or compromised governance action could create user-loss or asset-freeze risk, even though the protocol’s design includes fraud proofs and an emergency council. What is not verifiable as of 2026-09-04 from the available sources is whether the specific protocol “Liminal Basis” has any additional owner controls, admin keys, upgrade rights, treasury access, or multisig setup beyond the components above. The protocol’s own GitHub shows a Bridge2.sol contract exists, but the available results do not establish its control model in a way that supports a stronger fraud conclusion. Risk judgment: stress case = high-severity, low-to-moderate likelihood if one assumes compromised validators or governance actors; not enough evidence to confirm a direct owner-rug mechanism for Liminal Basis itself.

Liminal Basis appears to be a delta-neutral yield strategy protocol on Hyperliquid that targets yield from funding rates, staking rewards, and lending markets. For the stress case you asked for, I cannot verify the *primary yield source* or whether it was negative over the last 30 days, because no on-chain query tooling is available in this run and the web results do not provide a protocol-level 30-day yield decomposition. What can be said from the available sources is that Liminal’s stated return drivers are market-structure dependent rather than emissions-driven, so a stress scenario where the main carry leg turns negative would most likely compress or reverse strategy returns rather than merely reduce them.

In that situation, the relevant risk is that the strategy’s net carry becomes negative after fees, borrow costs, or hedging frictions, which is consistent with general leveraged/yield-spread mechanics. Assessment: Not verifiable as of 2026-09-04. Implication for risk review: treat this as a negative-yield stress condition on the primary source leg, with heightened attention to funding-rate regime shifts, borrow-rate spikes, and any mismatch between the protocol’s hedges and the underlying exposure.

Assessment as of September 13, 2026: Liminal appears company-controlled rather than DAO-governed. The Terms identify Grey(H)edge Ltd, incorporated in the British Virgin Islands, as the provider/operator of liminal.money, its applications, APIs, smart contracts and related services. The company owns the platform/IP, may amend terms immediately, change fees, modify or discontinue strategies, restrict access, block wallets and halt xToken provision. xTokens expressly provide no company ownership or governance rights; no public token-holder proposal or voting process was identified.

Therefore the DAO, if any, is symbolic and does not control parameters or upgrades. Contract governance: the xBTC documentation identifies a HyperEVM TimelockController at 0xCB7DEE93B092f6b4a081A6F626670830DD17d2c5. The Spearbit/Cantina audit records a 48-hour configuration delay and a 12-hour minimum function delay, implying at least 60 hours for critical actions in the audited design, but notes residual trust because delay configuration remains flexible.

Current proposer/admin role holders, whether roles are held by a multisig, and the multisig threshold/signers are Not verifiable as of September 13, 2026. Voting concentration and top holders via Dune are Not verifiable as of September 13, 2026 because Dune MCP is unavailable. The audit documented a VALUATION_MANAGER_ROLE attack path capable of manipulating NAV and draining redeemable funds, but remediation/current deployment state was not independently verified; admin_can_drain is therefore left null.

Emergency-bypass authority and current upgrade/admin powers are Not verifiable as of September 13, 2026. Directors and registration number for Grey(H)edge Ltd are Not verifiable as of September 13, 2026. No separate company jurisdiction beyond the British Virgin Islands, public directors, or registration number was established.

Proposal process: no verifiable DAO process; operational changes appear company/admin-led and timelock-mediated where implemented.

Liminal Basis is a DeFi yield protocol aligned with the Basis Yield ETH Index (BYE) strategy, operating across Arbitrum, Ethereum, and Hyperliquid L1. As-of discipline applies: all legal/regulatory statements below are Not verifiable as of 2026-09-04 via on‑chain data; only web sources are used. Legal entity & jurisdiction Web search returns references to the BYE index strategy and Hyperliquid integrations but no clear corporate entity (e.g., LLC, foundation, or company name) or registration jurisdiction specifically labeled “Liminal Basis”. → entity: null (unknown) → jurisdiction: null (unknown) Terms of Service / user restrictions I could not locate a dedicated Liminal Basis website, ToS, or legal disclaimer page distinct from general Hyperliquid or Arbitrum ecosystem documentation. Any jurisdictional or user restrictions (e.g., U.S. persons, sanctioned countries) are therefore Not verifiable as of 2026-09-04. KYC / AML There is no evidence of mandatory KYC/AML processes tied specifically to Liminal Basis smart contracts; typical yield/derivatives protocols on Arbitrum/Ethereum are often fully permissionless, but that is an inference and not protocol-specific evidence. → Any concrete KYC/AML policy: Not verifiable as of 2026-09-04. Regulatory classification & guidance No explicit regulator-facing classification (e.g., as a collective investment scheme, derivatives venue, or fund) for Liminal Basis was found in public registries, guidance notes, or legal opinions.

Given its structure around basis/yield strategies, regulators could in principle view some activities as derivatives or investment products, but this is generic sector context, not protocol-specific classification. Warnings, enforcement, court cases, sanctions Search across news, regulator databases, and ecosystem posts shows no public warnings, enforcement actions, or court cases naming “Liminal Basis” or a clearly associated entity. → active_enforcement: null (no action identifiable; not verifiable) → sanctioned: null (no listing found; not verifiable) Data protection / privacy Without a distinct frontend or ToS, there is no visible privacy policy or data-protection framework specific to Liminal Basis; on-chain interactions are public by design. Legal structure vs. actual risk The absence of a clearly identified legal entity and jurisdiction implies:

• Enforcement and recourse risk: Users may have limited avenues for legal redress if something fails.
• Regulatory uncertainty: If the strategy is later classified as a regulated derivatives or fund product, retroactive or sudden compliance actions could impact operations.
• Counterparty / governance opacity: Without a known entity, responsibility for upgrades, emergency actions, or incident handling is unclear. These gaps themselves are material risk findings for institutional exposure.

No exact GLEIF LEI record for 'Liminal Basis'. OFAC SDN screening of 'Liminal Basis': no match. SEC litigation and administrative release feeds: no mention.

Liminal Basis does not appear to issue its own stablecoin. The available sources describe the protocol as accepting external stablecoins such as USDC, USDT, and USDT0, and minting yield-bearing tokens or deploying strategies on those deposits. Because no protocol-native stablecoin is confirmed, no depeg event for an own stablecoin is verifiable as of 2026-09-06.

The structured depeg fields are therefore not verifiable as of 2026-09-06.

Liminal’s primary risks are concentrated in smart-contract and omnichain execution, dependence on Hyperliquid market infrastructure, and the economics of delta-neutral funding strategies. The protocol describes multiple safeguards, but several are protocol-reported claims; because Dune MCP was unavailable, TVL, chain exposure, wallet concentration, and contract-state verification are not available as of September 5, 2026.

Top strengths of Liminal Basis are: 1) it offers automated, delta-neutral basis and funding-rate yield on Hyperliquid, so users can access market-neutral carry without managing the trade themselves; 2) it wraps this into an on-chain vault / composable yield-token structure, improving usability and DeFi integration; 3) it emphasizes speed and execution quality by building on Hyperliquid’s low-latency, high-liquidity infrastructure; 4) it supports custody flexibility and transparency, with product lines aimed at both maximum-control/customizable users and portable tokenized exposure; and 5) it has institutional positioning, including sub-account automation and institutional-grade liquidity management, which can appeal to larger allocators.