Liminal Basis

Liminal Basis is a basis‑trading / delta‑neutral yield protocol built around the Hyperliquid ecosystem, with an on‑chain front end on Arbitrum and Hyperliquid L1 (HyperEVM). It automates market‑neutral strategies that combine spot and perpetual positions to harvest funding and basis yields, primarily on Hyperliquid. Identification

• Protocol / product name: Liminal (product line often referred to as Liminal Basis for its basis‑trading vaults).
• Category: DeFi basis‑trading / delta‑neutral yield layer and automated strategy vaults.
• Website: liminal.money (front page describes it as Hyperliquid’s “Native Yield Layer”).
• Docs: docs.liminal.money.
• Chains:
• Hyperliquid L1 / HyperEVM: described as the primary execution environment where Liminal is “Hyperliquid’s Native Yield Layer”.
• Arbitrum: supported for deposits/withdrawals and cross‑chain access to the strategies.
• Additional bridges from Ethereum, Base, BNB, HyperEVM, etc. are mentioned for deposits, but the question scope is Arbitrum + Hyperliquid.
• Launch date: Not explicitly stated in independent sources; coverage and TVL news appear from mid‑2025, implying a 2024–2025 launch window. This is an inference, not a confirmed on‑chain date.
• Native token: No independent source confirms a governance or reward token specific to “Liminal Basis”; instead, the key products are limUSD (a yield‑bearing USD expression) and various vault shares/xTokens. As of today, “native token” in the classic governance‑token sense is Not verifiable as of 2026‑08‑29. Contract addresses & verification Independent listings (e.g., Alchemy dapp directory, DefiLlama, CoinsCapture) describe Liminal Basis as a DeFi app on Hyperliquid and Arbitrum but do not publish canonical contract addresses. Without direct access to explorers or on‑chain analytics tools in this turn, main contract addresses and their verification status are Not verifiable as of 2026‑08‑29. Fork lineage and code provenance
• None of the independent sources (OakResearch comparisons, DefiLlama, directories, media coverage) describe Liminal Basis as a fork of a specific upstream protocol (e.g., GMX, Ethena, Morpho, etc.).
• There is also no evidence in these sources of:
• A declared upstream fork lineage.
• Specific code‑level changes vs. an upstream.
• Independent audits that reference a forked codebase.
• Malicious modifications found in Liminal or in named forks of the same code. Given the lack of verifiable audit PDFs, GitHub repos, or contract source links in independent coverage, all of the following are Not verifiable as of 2026‑08‑29:
• Exact fork origin (if any) and nature of modifications.
• Whether changes vs. any upstream were audited.
• Any documented history of malicious modifications in similar forks. Accordingly, for institutional risk work, Liminal Basis should currently be treated as an original or undocumented‑provenance strategy layer around Hyperliquid, pending direct contract, repo, and audit evidence.

Liminal Basis appears to be a real, functioning web app rather than a pure landing page: the main site promotes the protocol, while the docs describe live deposit/withdraw flows, wallet connection, strategy selection, and instant execution through the Liminal dashboard. The docs explicitly mention supported deposits on Arbitrum and Hyperliquid Spot/Perps, plus withdrawals to Arbitrum or Hyperliquid Spot, which is consistent with an operational product rather than a static marketing page. That said, a few maturity points remain not fully verifiable as of 2026-08-29: the presence or quality of broken links, fake metrics, and template reuse cannot be conclusively assessed from the available evidence, and no independent site audit was found to confirm UX reliability. The site and docs do show a structured documentation set and product-specific workflows, which is a positive sign for maturity. Open API: not clearly verifiable as a public protocol API for users/integrators as of 2026-08-29. The public docs surfaced here focus on app usage, fees, deposits, withdrawals, and strategy execution, but do not clearly expose a general open API for the protocol itself.

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.

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.

I could not verify an active bug bounty program for Liminal Basis from the results provided. The only directly matching source is Liminal Custody’s bug bounty page, which appears to be for a different product/domain and therefore does not confirm this protocol’s program status. Because of that, the program’s start date, parameters, and results are not verifiable as of 2026-08-29. The search results do show a general bug bounty page for Liminal Custody with reward tiers of Low-Medium: HoF to $100, Medium: $100 to $300, Medium-High: $300 to $500, and High: $500 to $1000, but this is not confirmed to belong to the requested protocol, Liminal Basis. The result set also includes unrelated examples from other protocols and platforms, such as Lido’s Immunefi program and HackenProof listings, but none establish a Liminal Basis bounty program, its launch date, or its outcomes. So the safest answer is: Not verifiable as of 2026-08-29 for whether Liminal Basis has an active bug bounty, when it started, what the exact scope/reward parameters are, or how many reports/rewards it has processed.

Liminal Basis is a delta‑neutral yield protocol tightly coupled to Hyperliquid’s trading stack, so its main risks are dependencies on Hyperliquid itself, the funding/basis markets there, and the stablecoins/custodial rails used to reach it. 1. Core external dependencies

• Hyperliquid exchange & infra: Strategies are built “on top of Hyperliquid’s high‑performance trading infrastructure” and integrated with HyperCore, not HyperEVM. Execution, hedging, and rebalancing, as well as institutional sub‑accounts, all depend on Hyperliquid remaining solvent, liquid, and operational.
• Spot + perpetual markets: Liminal Basis packages market‑neutral positions that combine spot and perpetual exposure on Hyperliquid to capture basis and funding‑rate opportunities. If Hyperliquid liquidity thins or funding mechanics change, yields can collapse or positions can become harder to rebalance. 2. Oracles & market data / manipulation risk
• Liminal “leverages native execution layers and real‑time market data” from Hyperliquid. There is no separate blockchain oracle mentioned; pricing and funding are effectively whatever Hyperliquid’s matching engine and data feeds report.
• This creates exchange‑level manipulation risk: extreme moves, thin order books, or internal glitches on Hyperliquid could affect funding, mark prices, and liquidation thresholds for the basis trades. 3. Bridges, custodians, and CEX/MM exposure
• Users typically acquire USDC on centralized exchanges (e.g., Binance) and then bridge to Arbitrum before interfacing with Hyperliquid and Liminal. Bridges such as Jumper are suggested as one route.
• Bridge failure, depeg, or censorship could strand funds off‑chain or on the wrong network.
• Liminal docs emphasize being “designed with user custody in mind” and not relying on smart contracts or HyperEVM. However, users’ USDC and positions are still ultimately dependent on Hyperliquid accounts and any custodial/operational risks there. 4. Stablecoin / asset exposure & depeg scenarios
• Liminal uses USDC as the main deposit asset for delta‑neutral strategies.
• USDC issuer/circle risk: regulatory action, reserve shortfall, or chain blacklisting could lead to depeg or frozen balances.
• Strategies rely on long spot / short perp pairs (e.g., BTC) on Hyperliquid. Asset‑specific events (e.g., exchange delisting, oracle anomalies in the perp market) could force unwinds or losses if hedges break. 5. Arbitrum & multi‑chain routing
• Deposits can originate from Arbitrum and other networks before being deployed to Hyperliquid strategies. Exact vault and contract dependencies on Arbitrum are Not verifiable as of 2026‑08‑30 (on‑chain view not available here).
• Any smart contracts used on Arbitrum for routing or vaulting introduce typical DeFi risks (bugs, admin keys, upgradeability), but specific implementations are Not verifiable as of 2026‑08‑30. 6. RWA, LST, restaking exposure
• Liminal is described as a crypto‑native basis / funding‑rate yield protocol; there is no indication of RWA, LST, or restaking exposure in available materials. If such products exist, they are Not verifiable as of 2026‑08‑30. Key failure modes
• Hyperliquid insolvency, hack, or prolonged downtime.
• Severe funding rate regime changes or market illiquidity on Hyperliquid.
• USDC depeg/freeze or bridge failures between CEX → Arbitrum → Hyperliquid.
• Potential Arbitrum smart‑contract bugs in any vault/router components (details not currently verifiable).

Liminal Basis appears to organize custody as non-custodial for end users: the protocol says it does not take custody of user funds, and users can connect their own wallet to trade on Hyperliquid. On Hyperliquid, the trading venue is an on-chain L1, so user activity is signed by the user’s wallet rather than handed to a centralized exchange custodian. The main custody bottleneck is the bridge rail: one source says native USDC is deposited on Arbitrum One into a canonical Bridge2 contract, which escrows the USDC and then credits the corresponding balance on Hyperliquid L1. That means assets are not held by the protocol in the traditional CEX sense, but they are temporarily controlled by the bridge contract and the Hyperliquid validator-signed withdrawal process. For institutions, the same Hyperliquid ecosystem also supports qualified custodians; Hyperliquid states that users who prefer a custodian can use providers such as Anchorage, BitGo, FalconX, Fireblocks, and Komainu. A separate SEC filing about a Hyperliquid ETF describes a third-party custodian structure with segregated cold storage, but that is an ETF custody arrangement, not proof of how the protocol itself custody is organized. What is not verifiable as of 2026-08-29 from the available sources is whether Liminal Basis itself uses any bespoke custody entity, segregated omnibus wallets, or vault-level controls beyond the standard Hyperliquid/Arbitrum flow.

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 use a self-custody / native-agent model on Hyperliquid, where users run strategies from their own Hyperliquid account and keep full custody of their assets; the protocol’s page says strategies run via Hyperliquid’s native agent system rather than through a hosted vault. That means key control is organized around the user’s own Hyperliquid account credentials and authorization path, not a protocol-controlled omnibus wallet. For the broader Liminal product stack, the vendor describes MPC and multisig as the core wallet-security models, with policy-based controls, transaction thresholds, whitelisting, role-based permissions, and audit trails. Its custody/HSM offering adds a hardware-backed layer where private keys remain offline, transactions pass through multiple authentication and validation layers, and key rotation and policy updates are supported. What is not verifiable as of 2026-08-29 is the exact key architecture used specifically by Liminal Basis on Arbitrum versus Hyperliquid L1, including whether each chain uses a distinct signer set, MPC shard split, multisig threshold, or delegated session-key design. The available sources support the high-level conclusion that Liminal emphasizes self-custody on Hyperliquid and enterprise MPC/multisig/HSM tooling in its custody stack, but they do not expose the protocol’s precise operational key-management scheme for this specific yield product.

Liminal Basis relies heavily on off-chain execution and centralized control, with limited publicly verifiable information on concrete contract addresses and admin roles on Arbitrum and Hyperliquid L1. Not verifiable as of 2026-08-30. Contract footprint & deployment model

• On Hyperliquid L1, core Liminal operations are described as integrated with HyperCore, not standard smart contracts, and “does not currently use smart contracts” for core yield logic. This implies:
• No standard EVM proxy/implementation pattern today.
• Strategy logic and risk controls live in an off-chain or native HyperCore integration layer controlled by the team/Hyperliquid, not user-governed contracts.
• For Arbitrum, third‑party descriptions (DefiLlama, Alchemy, Oak Research) frame Liminal Basis as an “automated basis‑trading vault” routing deposits to Hyperliquid funding strategies, but do not provide firm contract addresses or verified explorers. Not verifiable as of 2026-08-30. Admin / owner / emergency roles
• Because the core system is not yet smart‑contract driven on Hyperliquid, admin power is effectively operational control over:
• Position sizing, hedging, and rebalancing across spot/perp markets.
• Custody and routing of user USDC deposits to Hyperliquid accounts.
• Docs and external analyses do not disclose any on-chain multisig, timelock, or role-based access control (RBAC) structure for Liminal Basis. Not verifiable as of 2026-08-30.
• No evidence of renounced roles, protocol-owned timelocks, or DAO governance controlling upgrades or parameters. Not verifiable as of 2026-08-30. Upgradeability / pause / fees / oracle & strategy control
• With off-chain integration, upgrades likely occur via backend/config changes rather than contract upgrades, meaning there is no on-chain upgrade timelock for users to monitor.
• Strategy parameters (assets, leverage, hedging rules, funding capture) and risk limits can presumably be changed by operators without on-chain delay.
• No published details on pause functions, withdrawal queues, or fee switches at the smart-contract level. Not verifiable as of 2026-08-30. User exit and key-compromise scenarios
• Liminal marketing and docs state users can withdraw balances “anytime,” but this depends on system solvency and operator cooperation—this is an unverified marketing claim.
• If operational keys or HyperCore integration credentials are compromised:
• Attackers could misroute deposits, open risky/unhedged positions, or block withdrawals.
• Users face rug/freeze risk: off-chain controllers can effectively halt redemptions or drain managed accounts without an on-chain safeguard. Architecture summary (textual map)
• Users deposit USDC (Arbitrum/Hyperliquid/other chains) → funds are bridged/credited into Hyperliquid accounts controlled by Liminal → Liminal opens spot-long + perp-short basis positions and manages hedging → yield is attributed to user balances via off-chain accounting and any thin on-chain wrapper vaults. Because no verifiable contract addresses, proxies, or role structures are disclosed by explorers or independent analytics, all on-chain admin details for Liminal Basis remain: **“Not verifiable as of 2026-08-30.”

Liminal Basis appears to be part of / built on top of the Liminal delta‑neutral yield protocol on Hyperliquid L1 and Arbitrum, but there is no publicly documented, protocol-specific team page for “Liminal Basis” itself as of 2026‑08‑29. ### 1. Identity: founders & team

• The main Liminal protocol (Hyperliquid native yield layer) has public docs but does not name founders or core contributors in those docs.
• Several unrelated companies called “Liminal” (AI security, fintech, bioinformatics, consulting) have detailed founder bios, but they operate in different industries and are not tied to Hyperliquid/Arbitrum DeFi; using them here would be a name‑collision error.
• Result: Founders, prior projects, and individual track records for Liminal Basis are Not verifiable as of 2026‑08‑29. ### 2. Public vs. anonymous; credibility
• The yield protocol’s documentation and third‑party write‑ups describe architecture, strategies, and performance but never attribute them to named individuals.
• There is also no clear “team” section, LinkedIn organization, or doxxed founder announcement linked directly to the Hyperliquid/Arbitrum protocol instance.
• Therefore, the operator(s) of Liminal Basis should be treated as effectively anonymous / pseudonymous from an institutional risk perspective. ### 3. Real-world footprint: office, jurisdiction, business status
• No evidence of:
• A registered legal entity explicitly branded as “Liminal Basis” in major English‑language corporate news or PR.
• Physical office locations, mailing address, or jurisdictional disclosures in protocol docs.
• Multi-chain deployment (Hyperliquid L1 and Arbitrum) indicates crypto‑native, cross‑jurisdictional infrastructure, but not where the team is actually based.
• Conclusion: Office location, onshore/offshore status, and legal wrapper are Not verifiable as of 2026‑08‑29. ### 4. Track record: prior hacks / outcomes
• Public materials and third‑party risk write‑ups discuss Liminal’s strategies and TVL but do not report any protocol hacks, major insolvencies, or exploit incidents for Liminal Basis.
• Absence of evidence is not proof of safety; it only means no widely reported incidents turned up. ### 5. Reality check (institutional lens)
• Key risk flags:
• Anonymous / non‑doxxed team.
• No verifiable legal entity or office.
• No on-chain transparency tooling available in this run.
• This is therefore best characterized as a web‑front, crypto‑native product with opaque organizational reality, not a clearly identified operating company.

Liminal Basis appears to be a Hyperliquid-native DeFi yield protocol with Arbitrum as a deposit/withdrawal rail, but the public web results I found do not provide verifiable founder names, investor backers, or an independent audit corpus beyond the protocol’s own claims. Because I could not confirm those details from independent sources, founder/investor/auditor reputation is Not verifiable as of 2026-08-29. I found no credible web evidence of fraud, rug-pull, insolvency, sanctions, or active regulatory action specifically tied to Liminal Basis. I also found no independent media or legal coverage raising concrete allegations against the protocol itself; most search hits were unrelated uses of “Liminal” or general DeFi commentary. The main reputation caveat is that the protocol’s own site claims its smart contracts are audited by independent firms and that xTokens were audited by Spearbit and Pashov, but that statement is unverified marketing claim until checked against the auditors’ own reports. The docs also describe the protocol as “Hyperliquid’s Native Yield Layer,” but that is likewise protocol-provided positioning rather than independent validation. Overall sentiment from the limited third-party material is mildly positive/neutral: coverage describes Liminal as an automated basis/funding-rate or delta-neutral yield strategy on Hyperliquid, with no obvious scandal signal in the sources retrieved. Unresolved concerns remain around the absence of independently confirmable founder, investor, and audit provenance in the sources available here, plus the lack of any on-chain verification in this run.

Liminal Basis is a delta-neutral, funding-rate capture protocol on Hyperliquid, exposed to users via vaults and xTokens and accessible from Arbitrum as a front-end/on-ramp. ### Strategy & Asset Flows

• Strategy type: Automated basis / funding-rate trades: buy spot, short perps on Hyperliquid to earn funding while keeping near-zero price exposure.
• Assets in: Primarily USDC and other stablecoins deposited via Hyperliquid, Arbitrum, and bridged EVM chains.
• Assets out: Yield is paid in the deposited asset (e.g. USD stablecoins) via vault balances or tokenized products like limUSD and asset-level xTokens.
• Execution venue: Strategies are executed off-chain on Hyperliquid’s core (“HyperCore”), not via HyperEVM smart contracts; Liminal operates sub-accounts and positions for users. ### Yield Source & Risk Profile
• Primary yield: Perpetual funding rates and basis (spot–perp price convergence) on Hyperliquid.
• Organic vs subsidized: Yield is described as “real, sustainable” and market-derived, not from token incentives; this is an unverified marketing claim.
• Market-neutral vs directional: Target is delta-neutral; net P&L is still exposed to funding-rate changes, basis volatility, and execution risk.
• Leverage & external exposure: Docs reference leverage on the perp leg and multi-asset allocations; exact leverage parameters per vault are Not verifiable as of 2026-08-29. ### Lock-ups, Withdrawals, and Mechanics
• Lock-ups: No explicit fixed lock-up; yields are dynamic and not fixed-rate.
• Withdrawals: Deposits/withdrawals for Customized strategies on Hyperliquid and Arbitrum are fee-free at the protocol level. Withdrawals can be initiated from Hyperliquid and Arbitrum, with self-custody limited to Hyperliquid.
• Gates/limits: No hard caps or gating rules are documented in public sources; specific per-vault limits are Not verifiable as of 2026-08-29. ### Fees & Protocol Revenue
• Performance fee: 10% performance fee on funding-rate yield for most assets; USDe and thBILL allocations are exempt. The APY displayed is net of this fee.
• Deposit/withdrawal fees: Zero protocol fees on deposits/withdrawals for Customized.
• Protocol revenue therefore comes primarily from performance fees on funding yield. ### Collateral, TVL, APY Behavior
• Collateral: User capital sits as spot and margin on Hyperliquid sub-accounts; details per asset and margin regime are Not verifiable as of 2026-08-29.
• TVL: Reports mention TVL > $90m on Hyperliquid as of August 2025, but without on-chain queries this is Not verifiable as of 2026-08-29.
• Chain split: Economic activity is structurally Hyperliquid-centric; Arbitrum functions mainly as interface/on-ramp, not core yield venue.
• APY history & volatility: 30-day APY is an annualized estimate from recent funding, highly dynamic, non-guaranteed, and sensitive to short-term funding volatility and capital inflows. Concrete historical APY time series and volatility stats are Not verifiable as of 2026-08-29.

Not verifiable as of 2026-08-29. The web results do not provide a credible, protocol-specific reserve or treasury disclosure for Liminal Basis, nor do they establish the treasury addresses, custody model, reserve policy, or attestations. The only directly relevant result is the project homepage, which describes Liminal as a native yield layer on Hyperliquid but does not disclose reserve size, composition, or control details. The remaining results are unrelated or name collisions, so they cannot be used to identify this protocol’s treasury. On-chain balances via Dune are also not verifiable in this run because Dune MCP is unavailable, so no on-chain reserve figures can be confirmed.

Liminal Basis does not appear to have a fully documented, live native governance or utility token as of the latest available web data. Most publicly visible information concerns the protocol’s perp market and ecosystem, with no reliable, independent confirmation of a deployed ERC‑20 token on Arbitrum or Hyperliquid. Because Dune MCP and direct on‑chain queries are unavailable in this run, all on‑chain verification is: Not verifiable as of 2026‑08‑30. ### 1. Native token existence

• I could not locate a credible, independent source (explorer, major analytics site, audits, or bug bounties) that confirms a Liminal Basis token contract, symbol, or address on Arbitrum or Hyperliquid L1.
• No listing on major aggregators (Coingecko, CoinMarketCap, DefiLlama, Token Terminal) under “Liminal Basis” or a clear ticker tied to the protocol could be verified.
• As a result, all token-metric questions (supply, market cap, FDV, unlocks, allocations, emissions) are Not verifiable as of 2026‑08‑30. ### 2. Tokenomics fields (requested, but currently unverifiable) Given the lack of verifiable token-level data, for each requested item:
• Token name / ticker / contract address: Not verifiable as of 2026‑08‑30.
• Total vs circulating supply; market cap & FDV: Not verifiable as of 2026‑08‑30.
• Token utility & governance role; revenue share, buybacks, burns, staking rewards: Not verifiable as of 2026‑08‑30.
• Emissions and unlock schedules; whether unlocks occurred on‑chain: Not verifiable as of 2026‑08‑30.
• Allocations (team / investors / treasury / community): Not verifiable as of 2026‑08‑30.
• Top‑holder concentration & insider wallets: Not verifiable as of 2026‑08‑30.
• Mint / blacklist / fee‑switch functions & controllers: Not verifiable as of 2026‑08‑30.
• DEX liquidity depth and main listings: No confirmed Liminal Basis token pools or listings on primary Arbitrum DEXs (Uniswap v3, Camelot, Ramses, etc.) or centralized exchanges could be independently matched to this protocol; Not verifiable as of 2026‑08‑30. ### 3. Risk‑analysis implication For institutional risk purposes, the working assumption should be: Liminal Basis currently operates without a clearly verifiable native ERC‑20 token, or, if a token exists, it is not yet covered by major independent data providers.
• Any token-related exposure, unlock trading, or governance rights would therefore be high‑uncertainty and must not be sized or risk‑managed until directly confirmed with:
• Verified contract addresses on Arbitrum / Hyperliquid explorers.
• Independent listings on at least one major analytics or pricing platform.
• Formal docs/audit references, which today remain unverified marketing claims absent cross‑checks.

Bitcoin below $10,000 is best treated as an *extreme tail-risk* input, not a base case. The web results describe it as requiring a synchronized macro and crypto stress event: global liquidity shock, forced deleveraging, persistent institutional outflows, weak spot demand, and broader risk-asset weakness or geopolitical disruption. For Liminal Basis, a BTC move under $10,000 would primarily stress any design that is economically exposed to BTC price, BTC collateral value, or BTC-denominated hedging flows. In practical risk terms, the main transmission channels would be: collateral devaluation, liquidation pressure, lower borrow capacity, and potential peg/hedge slippage if the protocol depends on liquid BTC markets. I could not verify the protocol’s chain-specific exposure, vault composition, or liquidation mechanics from the provided results, and on-chain checks are unavailable in this run. Not verifiable as of 2026-08-29. What can be said with confidence is the scenario shape: if BTC fell below $10,000, the protocol should be assumed to face *maximum volatility*, with any BTC-linked positions likely suffering the largest mark-to-market losses and any leverage layered on top of those positions facing the highest liquidation risk. If you want, I can turn this into a protocol-specific stress grid once you provide the vault addresses or a docs snapshot.

Not verifiable as of 2026-08-29. The provided web results do not identify Liminal Basis’s live collateral composition, chain-by-chain TVL, or which asset is the *largest collateral* to shock, so a 20% depeg stress cannot be quantified without on-chain or protocol-specific exposure data. The only directly relevant material in the results is generic stress-test methodology and unrelated examples, not protocol state or positions. For this protocol and scenario, the correct institutional risk treatment is:

• identify the largest collateral asset on Arbitrum and Hyperliquid L1 separately;
• apply a 20% mark-down to that asset only;
• recompute account health, bad debt, and liquidation coverage;
• aggregate results by chain and then across the protocol. Because on-chain verification is unavailable in this run, the chain split, absolute loss, and post-shock solvency impact are all Not verifiable as of 2026-08-29.

For a fraud-by-DAO/owners stress scenario, Not verifiable as of 2026-08-29 for Liminal Basis on Arbitrum and Hyperliquid L1. The web results available do not identify this protocol’s DAO, owner set, treasury controls, upgrade keys, or any committed-fraud event attributable to its governance or controllers. What *is* verifiable is that the relevant chains have strong admin-control surfaces that could matter in an owner-fraud scenario. Hyperliquid’s bridge requires 2/3 of validator staking power for deposits and withdrawals, includes a dispute period, and uses cold-wallet signatures of 2/3 of the stake-weighted validator set to unlock the bridge. Arbitrum’s Security Council has demonstrated emergency intervention capability, including an upgrade that temporarily impersonated the sender to move frozen funds during the KelpDAO incident. That shows chain-level governance can move assets in exceptional circumstances, but it is not evidence that Liminal Basis itself committed fraud. No independent source in the provided results reports a fraud allegation, prosecution, sanctions action, or governance vote involving Liminal Basis owners or DAO controllers. The only directly related materials concern unrelated incidents on Arbitrum and Hyperliquid bridge operations. If you want, I can next check for: 1) the protocol’s deployer/admin addresses, 2) governance multisig signers, 3) treasury custody, or 4) any public complaints or legal actions specifically naming Liminal Basis.

For Liminal Basis, I could not verify a published 30-day primary-yield negative-stress result from independent sources, so the correct status is Not verifiable as of 2026-08-29. Liminal’s own materials say its yield comes from delta-neutral strategies on Hyperliquid, including funding rates, staking rewards, and lending markets, but they do not provide an independently verifiable 30-day stress case showing the primary yield source turns negative. Under the stated stress scenario, the relevant risk is that the protocol’s main yield driver can be market-structure dependent and therefore can compress or flip negative if funding, staking, or lending economics deteriorate. That is an inference from the strategy description, not a verified measured outcome. No on-chain check was available in this run, so I cannot confirm chain-level exposure for Arbitrum vs. Hyperliquid L1, nor can I quantify whether the negative 30d condition is already occurring. Not verifiable as of 2026-08-29.

Liminal Basis appears to be a centrally controlled strategy protocol, not a fully on-chain DAO, and detailed governance parameters (multisig, timelocks, signers, voting) are largely not publicly specified. Not verifiable as of 2026‑08‑29. ### 1. Governance model (DAO vs. company vs. team)

• Public descriptions frame Liminal Basis as an automated basis‑trading product within the broader Liminal / Hyperliquid native yield layer, run by a core team that designs and operates strategies on Hyperliquid.
• There is no evidence of a Liminal Basis governance token, on‑chain voting, or dedicated DAO governance forum specific to Liminal Basis. Not verifiable as of 2026‑08‑29.
• On Arbitrum, only the chain itself is governed by the ARB DAO and Security Council; this is *infrastructure* governance, not protocol‑level control of Liminal Basis contracts. Assessment: Governance is team/company‑driven, with users having no visible formal voting rights over strategy parameters, upgrades, or treasury. Not verifiable as of 2026‑08‑29. ### 2. Control over dev, contracts, frontend, and funds
• Docs describe Liminal as a “native yield layer” with fully automated strategies”, implying the team controls strategy logic, rebalancing, and integrations with Hyperliquid and other ecosystems.
• Vaults on Hyperliquid L1 and Arbitrum are presented as products of the Liminal team; nothing indicates immutable contracts or community‑controlled upgraders. Not verifiable as of 2026‑08‑29.
• No transparent registry of admin keys, upgrade roles, or pauser roles is disclosed for Liminal Basis. Not verifiable as of 2026‑08‑29. ### 3. Multisig / timelock / signers
• The Liminal ecosystem docs mention multisig support for users’ own wallets on Arbitrum (e.g., ARB cold multisig), but this refers to *user custody*, not protocol governance.
• There is no public breakdown of:
• protocol treasury or vault admin multisig addresses,
• signer identities/independence,
• thresholds (e.g., 2‑of‑3, 3‑of‑5),
• whether changes are gated by timelocks. All of the above are “Not verifiable as of 2026‑08‑29.” ### 4. Voting concentration & top holders
• Without on‑chain analytics access and with no evidence of a dedicated governance token, voting concentration, top holders, and delegation patterns cannot be established. Not verifiable as of 2026‑08‑29. ### 5. Legal entity / ToS
• Public marketing sites describe Liminal/Liminal Basis as a product brand but do not disclose a corporate entity, jurisdiction, registration number, directors, or formal terms of service specific to Liminal Basis. Overall risk takeaway: governance is likely centralized in the core team, with opaque admin and upgrade rights, and no demonstrable DAO structure for Liminal Basis as of 2026‑08‑29.

Not verifiable as of 2026-08-30. I could not confirm a protocol-specific legal entity, governing jurisdiction, or formal terms for Liminal Basis from the available results. The only clearly relevant source found was the app privacy notice for a product called Liminal, which identifies Zenly Ltd (trading as Liminal), a UK company, with a London registered address, and says KYC/ID verification is required to access KYC-gated features; it also states biometric consent may be required and that some KYC data is retained for compliance periods. Because this appears to be a product-level privacy notice rather than a protocol legal wrapper, it does not establish the legal structure of Liminal Basis itself, and I could not verify whether these terms apply to the Arbitrum or Hyperliquid L1 deployment. I found no verifiable evidence in the available results of a Liminal Basis-specific court case, regulator warning, enforcement action, or sanctions designation, and therefore those items remain Not verifiable as of 2026-08-30. I also could not verify any protocol-specific data-protection disclosures beyond the unrelated/possibly adjacent Liminal privacy notice, so the actual legal structure versus operational risk is unresolved. On risk interpretation, the main issue is entity ambiguity: if the protocol is operated through an identifiable UK entity with KYC-gated features, that materially increases the chance of centralized compliance controls, data-processing obligations, and potential geofencing or user exclusion; however, that conclusion is only a structural inference from the privacy notice and remains only partially verifiable here.

The stablecoin used by Liminal Basis is Not verifiable as of 2026-08-29 from the provided sources, so I cannot confirm whether it ever depegged, how many times, or the last depeg magnitude. The search results only provide general stablecoin depeg references and do not identify the protocol’s actual stablecoin or any protocol-specific price history. If you can share the stablecoin symbol/contract, I can assess its depeg history precisely.

Top risks for Liminal Basis appear to be:

• Funding-rate / market risk: The strategy is delta-neutral, but Liminal itself says sudden volatility and funding-rate reversals can reduce or negate yield, and prolonged negative funding can hurt returns.
• Hyperliquid dependency / infrastructure risk: Liminal operates on Hyperliquid infrastructure; if Hyperliquid is down or under maintenance, execution, rebalancing, and withdrawals may be delayed or paused.
• Liquidity / redemption risk: Liminal states that withdrawals/redemptions can be delayed, staged, or temporarily optimized during high volatility or low liquidity to unwind positions safely.
• Smart-contract / oracle risk: The protocol’s docs state its contracts are audited, but also acknowledge residual smart-contract risk and oracle dependence for NAV and price feeds.
• Stablecoin / custody risk (USDC): Deposits ultimately settle in USDC, so users face issuer risk, potential depeg risk, and custody-related operational risk. A notable additional concern is track-record risk: independent commentary says the protocol is relatively new and may not yet have been tested through a full adverse market cycle.

Liminal Basis’s top strengths appear to be: native Hyperliquid focus, delta-neutral yield design, cross-chain composability, self-custodial/customizable strategies, and automation with transparency/institutional positioning. The project describes itself as “The Native Yield Layer of Hyperliquid” and says it provides access to “real yield” through a delta-neutral approach, either via composable yield tokens or self-custodial customizable strategies. It also says these strategies are made possible by Hyperliquid’s deep liquidity, high-speed native execution, and purpose-built architecture. The docs add operational strengths such as automated sweeping to cold storage, dynamic liquidity management, unified wallet control, fee optimization, and a transparent, automated user experience.