Lighter Perps

Lighter Perps appears to be the perp-trading product of Lighter, whose official site is app.lighter.xyz and whose docs are at docs.lighter.xyz. The protocol is described in its docs and official materials as a zero-knowledge rollup / application-specific Ethereum L2 for perpetuals, and its public mainnet was reported to open on 2025-10-02 after private testing. The docs list chain IDs 304 (mainnet) and 300 (testnet), so it is not a multi-chain deployment in the usual sense.

The native token is LIT, launched on 2025-12-30 per independent coverage and project-linked materials. For main contract addresses, I cannot verify them to the standard you requested because on-chain checks are unavailable in this run; therefore they are Not verifiable as of 2026-09-04. The only address-like item surfaced in the gathered material is a Lighter Verifier Proxy address referenced in an official post, but I cannot cross-check it against a second independent source here, so it should be treated as unconfirmed.

On fork lineage, the evidence gathered supports that Lighter is not presented as a simple fork of another perp DEX; rather, it is described as a custom app-specific zk-rollup with verifiable matching and liquidations. I found no reliable source in this run establishing an upstream fork, audited delta from an upstream codebase, or a malicious-modification history tied specifically to this protocol. That means the fork-status question is Not verifiable as of 2026-09-04.

Regarding audits, Lighter’s docs say security audits exist for smart contracts and circuits, and the official X post says audits of perps and spot circuits had completed before code publication; however, the underlying audit reports themselves were not directly verified in this run.

Lighter Perps appears to be a real, functioning product portal rather than a pure landing page. The documentation site exposes a full trading API, deposit/withdrawal flows, partner integration, API keys, and order-book/account endpoints, which is consistent with an operational exchange backend rather than a template shell. Live deposits/withdrawals are documented as supported, including Ethereum mainnet deposits, universal deposit addresses, and withdrawal-related flows; however, the presence of docs alone does not prove successful user execution today, so live operability is Not verifiable as of 2026-09-04.

The site also has mature docs/UX signals: a dedicated docs portal with a complete index, API get-started pages, and multiple topical pages rather than a sparse marketing site. I did not find evidence in the gathered sources of broken links, fake metrics, or obvious template signs, but that absence is not a proof of quality; it is simply Not verifiable as of 2026-09-04. Yes, it has an open API: the official docs explicitly point to a public API documentation site and expose endpoint references for account, transaction, order, and deposit/withdrawal functionality.

Lighter’s documentation says it does not currently operate a public bug bounty program unless explicitly announced otherwise, though it may offer monetary rewards at its sole discretion for vulnerability reports. The security policy is a vulnerability disclosure process rather than a formal public bounty program. No start date or payout schedule for a public program is stated, and no public results ledger was found in the gathered sources.

The best-supported reading is that there is no active public bug bounty program as of 2026-09-04.

Assessment (as of September 6, 2026):

• External protocols / bridge / custody: Funding is not purely wallet-to-contract. Lighter exposes a Universal Deposit Address through bridge.lighter.xyz, routing assets from multiple chains and converting perps collateral to USDC. The perps account accepts USDC only; supported inbound assets include USDT, ETH, DAI, USDe, BTC-related assets and native-chain assets. This creates bridge, routing, swap/slippage and operational-dependency risk. Circle CCTP is documented for some legacy USDC routes. A permissionless Ethereum escape path exists in the design, but L2BEAT identifies current upgrade/proof-verifier control as a residual trust assumption.
• Oracle / manipulation risk: Lighter’s ZK proofs verify computation using supplied oracle inputs, not the economic accuracy of those inputs. Independent analysis reports Stork as the primary oracle and a mark-price median of orderbook impact prices, EMA-capped premiums and CEX median marks. Manipulating two inputs, or sequencer-supplied data, could affect liquidations, funding and settlement. High-severity dependency.
• Sequencer / counterparty / CEX-MM exposure: The sequencer controls transaction ordering, inclusion timing, liquidation timing, mark-price application and ADL counterparty selection. This permits MEV, soft censorship and potentially adverse liquidation sequencing even though included state transitions are proven. No independently verified named market-maker, CEX custodian, RWA issuer/SPV, LST or restaking dependency was identified.
• Stablecoin / failure scenarios: USDC is the core perps collateral dependency. USDC depeg, bridge/router failure, oracle corruption, sequencer censorship, contract-upgrade compromise, or insurance-fund insufficiency could cause delayed exits, bad liquidations, socialized losses or collateral impairment. Not verifiable as of September 6, 2026: current USDC concentration, insurance-fund coverage, bridge balances, CEX/MM exposure, or any active insolvency/depeg event. Contradiction / qualification: Lighter markets “self-custody” and guaranteed withdrawals as protocol features, but independent review still identifies sequencer discretion and Stage 0 upgrade risk; these claims should not be treated as equivalent to trustless operation today. No Dune MCP was available; on-chain exposure percentages were not computed.

Lighter Perps is structured as non-custodial: users connect a self-custody wallet, and user collateral is held in Ethereum smart contracts rather than in an operator-controlled wallet. Custody is therefore split between the user’s wallet for signing and the protocol contracts for holding collateral and enforcing withdrawals; the documented exit/forced-withdrawal paths indicate users can withdraw directly from the contract even if offchain components fail. I did not find verifiable evidence that withdrawals are currently paused, so withdrawal_paused is Not verifiable as of 2026-09-06.

I also did not find verifiable evidence of segregated assets at the custody level, so segregated_assets is Not verifiable as of 2026-09-06.

October 10–11, 2025: 4.5-hour sequencer/database outage during extreme volatility. A delayed database upgrade and database failure prevented users from entering, exiting, or managing positions. Reported user losses were approximately $25M during platform degradation plus $7M during the post-crash outage; LLP contributors reportedly lost about $21.5M (approximately $50M aggregate user/LP impact, though estimates are secondary and partly include market losses).

Lighter restored service, upgraded infrastructure/database systems, refunded liquidation fees, and distributed 250,000 compensation points across affected traders and LLP users. Compensation was not equivalent to full cash reimbursement. Current status: resolved operationally; remediation completed, but full reimbursement is not verifiable as of September 6, 2026.

December 30, 2025: Users reported delayed withdrawals after the LIT token launch, with a “Too many L2 Withdrawals” error. No protocol loss, user loss, reimbursement, cause confirmation, or incident-specific closure was disclosed. Current status: Not verifiable as of September 6, 2026.

February 25–26, 2026: ARC perpetuals liquidation/stress event, not a confirmed exploit. A whale accumulated a highly leveraged ARC long; approximately $2M was liquidated on the order book and the remainder moved into the LLP. Auto-deleveraging and an isolated ARC risk bucket contained losses.

Lighter reported approximately $75,000 of LLP loss; the trader reportedly lost approximately $8.2M, a user trading loss rather than attacker proceeds. About 600 counterparties/market participants were exposed. Lighter imposed a $40M ARC open-interest cap, capped liquidity allocation, and automatic ADL fallback.

Current status: resolved; no reimbursement reported.

A separate report described a BTC perpetual-contract flash crash around Feb. 25–26, 2026, which Lighter reportedly attributed in Discord to a whale market-selling about 1,000 BTC into limited liquidity rather than a hack or platform vulnerability. The source did not report any reimbursement or protocol loss tied to the event.

Lighter Perps uses a per-account API key model rather than signing trades with the wallet’s EVM key. Each internal account—master or sub-account—has its own key space, and each key is tied to a specific account index and API-key index with its own nonce. The docs say API keys provide both read and write access, can submit transactions and withdrawals, and can be created through the SDKs or by interacting with the smart contract via ChangePubKey.

Key organization is index-based. Indices 0–1 are reserved for the web/mobile interfaces, while 2–254 are available for user or third-party use; Lighter also notes that a premium account can mark up to 251 keys per account index as maker-only. A key pair is therefore managed as (accountIndex, apiKeyIndex), and each pair has its own nonce and authentication state.

Rotation is used instead of a separate revoke flow. Registering a new key at an occupied index immediately replaces the prior key, and the old key stops verifying; this is the documented way to revoke a compromised key. The docs also note that API-key generation itself does not require the L1 private key, but binding the key to the Lighter account does, which can be done directly or via SDKs, including in multi-sig setups.

In practice, this means key management is delegated, indexed, and rotatable, with the L1 owner authorizing keys once and then API keys handling ongoing trading and withdrawal operations.

As of September 6, 2026, Dune MCP is unavailable; no on-chain Dune query ID/execution snapshot can be provided. Findings below use explorer, auditor, GitHub, and protocol technical materials only. Verified deployment: Ethereum Lighter/ZkLighter collateral and priority-transaction contract: 0x3B4D794a66304F130a4Db8F2551B0070dfCf5ca7. Etherscan identifies it as a verified custom Proxy; the explorer reports implementation 0x831EF69B…b124E7008 but the fetched evidence does not expose the complete implementation address.

Exact deployment registry across other chains: Not verifiable as of 2026-09-06. Architecture: users deposit collateral into the Ethereum proxy; Lighter’s sequencer submits state commitments; a prover verifies batches; verified withdrawal messages release assets. Priority transactions include withdraw, withdrawPendingBalance, order cancellation, and reduce-only orders. If priority requests expire, the documented Escape Hatch/Desert Mode freezes further commitments and permits proof-based user exits.

This materially reduces sequencer-censorship risk, but does not eliminate proxy-admin or implementation risk. Upgrade/admin risk: the proxy exposes getMaster, transferMastership, getTarget, and upgradeTarget(newTarget,...). This is a custom mastership-controlled upgrade pattern, not a standard TimelockController/ProxyAdmin architecture. Master address, multisig status, role renunciation, emergency-role holders, and timelock delay: Not verifiable as of 2026-09-06.

No evidence of a timelock was found. Privileged capabilities: the upgrade authority can potentially replace the implementation, alter withdrawal, fee, oracle/state-validation, or emergency logic, and freeze or redirect operations. A compromised master could therefore create a catastrophic loss scenario, including unauthorized collateral withdrawal, although the current implementation’s exact drain path was not independently simulated. Direct user exit without admin is documented through priority withdrawals and Escape Hatch proofs, subject to valid state data and gas availability. Audit evidence: Nethermind reviewed LighterCore and the EVM deposit bridge.

Reports show zero unresolved findings, including zero unresolved critical/high findings; however, audit commit-to-deployment matching is Not verifiable as of 2026-09-06. Main residual risk is centralized upgrade authority with no verified timelock/multisig evidence.

New published report identified: zkSecurity’s Audit of Lighter’s zkLighter Circuits, dated January 22, 2024. The review covered the main ZK circuit, exit-hatch circuit, and MIMC/GKR hash implementation. The report lists two High findings involving forged Merkle proofs, one Medium matching-engine issue, and five Informational findings; no Critical or Low findings are listed.

Corrected publication date for Nethermind’s Lighter EVM Deposit Bridge review: September 22, 2025, not merely “2025.” The report covers the CCTP bridge contracts and records five Informational findings, all marked Fixed.

Nethermind Security — Security Review, final report September 21, 2025. Scope: 1,655 LoC Solidity across Lighter core rollup, governance, upgradeability, deposit/withdrawal, and Desert Mode contracts; final commit 0ddf2bf. Covers deployed code: Not verifiable as of September 5, 2026; audited repository commit and deployed bytecode match were not established.

Findings: 1 Critical (inconsistent hash padding bricks emergency withdrawals), 0 High, 1 Medium (malicious deposits can DoS critical address setters), plus 3 informational and 3 best-practice items. Fix status: 4 fixed, 1 mitigated, 3 acknowledged, 0 unresolved.

Nethermind Security — EVM Deposit Bridge review, published 2025. Scope: deterministic per-user contracts, Circle CCTP integration, FastCCTPV2, LighterProxy, governance, fees, and approvals. Covers deployed code: Not verifiable as of September 5, 2026; bytecode match not established.

Findings: 0 Critical/High/Medium; 5 informational. Fix status: all five resolved before deployment, according to Nethermind.

Lighter’s published security audit page points to multiple zkSecurity reports covering its ZK circuits and related components; independent search results identify at least one report for the Block circuits (Aug. 4, 2025), one for Block and Delta layers (Sep. 8, 2025), and one for spot market circuits and multi-asset support (Nov.

24, 2025). The zkSecurity spot-market report states this was the 6th audit in a series for Lighter.

zkSecurity — Audit of Lighter’s Block and Delta Layers, September 8, 2025. Scope: delta, recursion, bigint, hints, comparison, and related changes between commits 4876a50 and b119f03. Covers deployed code: Not verifiable as of September 5, 2026.

Findings: 2 High, 2 Medium, 4 Low, 2 Informational. Fix status: client responses mark findings fixed in later commits, including Phase 2 fixes; deployment match not established.

zkSecurity — Audit of Lighter’s Wrapper Circuits, October 10, 2025. Scope: WrapperInner/Outer circuits, blob evaluation, bitstream gate, and blob polynomial targets at commit 0028b73b1e38de7e7c7e4ad33c7680a39e2c6c90; BLS12-381 and Gnark outer circuit excluded. Covers deployed code: Not verifiable as of September 5, 2026.

Findings: 2 High, 1 Low, 1 Informational. Fix status: developers applied suggested fixes for the two High findings; remaining remediation status not fully stated.

zkSecurity — Audit of Lighter’s Exit Hatch, November 5, 2025. Scope: Desert/escape-hatch circuits, TAV computation, withdrawal validation, blob deserialization, and related transaction changes at commit b99c425b8c0868501e65e78fd16aaf16bbe0ea2b. Covers deployed code: Not verifiable as of September 5, 2026.

Findings: 1 High, 1 Medium, 1 Low, 1 Informational. Fix status: High finding fixed in commit f6818da; other remediation and deployment match not fully verifiable.

zkSecurity — Audit of Lighter’s Spot Market Circuits and Multi-Asset Support, November 24, 2025. Scope: multi-asset delta, asset registration, deposits/withdrawals, transfers, matching, orders, markets, liquidation, and transaction state; two commits reviewed. Covers deployed code: Not verifiable as of September 5, 2026.

Findings: 0 Critical/High, 3 Medium, 1 Low, 1 Informational. Fix status: findings marked fixed in Phase 2 or spot-branch commits; deployment match not established.

Lighter’s X post says the audits of its perps and spot circuits were completed and that the code verifying every operation was published; it also says the deployed verifier contract at a specific Etherscan address should match the build output. That is a strong indicator that the audits covered code intended for deployment, but the snippet does not itself provide a formal bytecode-match verification result from an independent reviewer. Therefore, the bytecode-match status is Not verifiable as of 2026-08-29 from the provided sources alone.

Lighter Perps is a founder-led, non-anonymous, VC-backed US-based business, not a purely anonymous web-front protocol. Founders & key background

• The protocol is founded and led by Vladimir (Vlad) Novakovski, publicly identified as founder & CEO of Lighter across media, podcasts and social channels.
• Background: Russian-born, immigrated to the US, elite STEM Olympiad participant, entered Harvard in his mid-teens and graduated very early, then recruited directly into Citadel as an engineer/trader.
• Prior projects: co‑founded Lunchclub, an AI social network, and worked at Addepar before moving back from AI into crypto trading infrastructure.
• He has advised Robinhood early on and shares origins with Robinhood founder Vlad Tenev (same high school, long-standing ties). Team, corporate form, and investors
• Lighter is operated via a US C‑Corp, with Novakovski as CEO, indicating an onshore corporate structure rather than an offshore foundation.
• The team has reportedly raised ≈$89m across rounds (including a $68m round at a ~$1.5bn valuation in late 2025) from major VCs: Founders Fund, Ribbit Capital, Haun Ventures, Dragonfly, Craft Ventures, Robinhood Ventures and others.
• Investor commentary explicitly states the founder and team quality as central to the investment thesis (Founders Fund quote that “Vlad and his team are 85 to 90 percent of why we invested”). Public vs. anon, office reality, jurisdiction
• The founder is fully public with multiple interviews (Fortune, The Block, podcasts, X Spaces) under his real name and face.
• Given the US C‑Corp structure and US-centric investor base, operations and legal domicile are onshore in the US; specific physical office addresses are Not verifiable as of 2026‑09‑04. Credibility, track record, and risk-relevant history
• Track record includes high-frequency trading, AI startups, and a prior social networking platform; no prior protocol hacks or rug pulls associated with Novakovski or Lighter are reported in the retrieved sources.
• Lighter has quickly become a top perp DEX by volume, which is covered extensively in independent media (Fortune, Blockworks, Defiant) rather than only protocol marketing.
• Some critical research pieces frame Lighter as potentially a “points pump” vs. “revolutionary perp DEX,” indicating mixed but serious scrutiny, not pure hype. Reality check
• Overall, this is a visible, KYC’d founder with a conventional VC-backed US corporate structure, substantial prior professional pedigree and no public record of protocol-related fraud or hacks in the available data.
• However, absence of evidence is not evidence of safety: detailed on‑chain behavior, internal controls, and formal regulatory posture are Not verifiable as of 2026‑09‑04 from the current dataset.

Lighter Perps (Lighter.xyz / LIT) currently has a strongly positive technical and investor reputation, with multiple audits and institutional partnerships, and no public fraud, rug-pull, insolvency, sanctions, or enforcement actions reported as of 2026‑09‑04. However, it remains a relatively new, complex zk-rollup perps venue, so operational and regulatory risks are not fully battle‑tested. Team, investors, positioning

• Media coverage ties Lighter to Robinhood Chain’s perp access, with CEO Vladimir Novakovski quoted as confirming Robinhood Chain collateral support, signaling at least some institutional‑grade integration and scrutiny.
• An analysis of LIT by crypto media notes that DeFi investor Will Price is a Lighter advisor and frames Lighter as aligned with “where Wall Street and U.S. regulation are heading,” suggesting a deliberate focus on regulatory‑compatible design rather than pure degen positioning.
• Coverage and exchange research pieces consistently describe Lighter as an application‑specific zk‑rollup perps DEX competing with leaders like Hyperliquid, implying it is viewed as a serious, technically sophisticated venue rather than a meme project. Audits, security posture, and unresolved concerns
• A third‑party research report states Lighter underwent multiple security audits in 2025, including core and bridge audits by Nethermind, plus additional audits by Block and Desert. These are industry‑recognized auditors, which materially improves perceived security.
• Lighter’s own communications highlight that perps and spot circuits were audited before publishing the verification code that checks every order, cancel, and liquidation, emphasizing formal verification of core logic.
• The protocol uses a centralized sequencer with zk proofs and an emergency “Desert Mode” exit path if the sequencer stalls or censors, which media frame as a mitigation but still an area of centralization and liveness risk.
• On‑chain robustness, incident history, and exact TVL / solvency metrics are Not verifiable as of 2026‑09‑04 under current constraints. Sentiment, criticisms, and risk themes
• Reviews and guides from perps‑focused outlets and exchanges are broadly positive, emphasizing zero trading fees, high speed, and verifiable matching and liquidations.
• No major public exploits, user fund losses, or rug allegations are reported in available media as of this date; sentiment is more about tech trade‑offs (centralized sequencer, complexity of custom zk circuits) than misconduct.
• Lighter’s tight integration with Robinhood Chain and tokenized stocks may attract future regulatory scrutiny, but there are no current sanctions or enforcement actions publicly documented. Given the young age of the protocol and its bespoke rollup stack, residual concerns center on smart‑contract and zk‑circuit risk, sequencer centralization, and regulatory overhang, rather than reputational red flags about fraud or governance today.

Economic model (as of September 6, 2026). Lighter Perps is a derivatives venue, not a conventional yield vault. Traders deposit collateral and take directional long/short perpetual positions; liquidity is supplied by the Lighter Liquidity Provider (LLP), which also absorbs liquidation/ADL risk. Yield is therefore variable trading PnL, funding transfers, and—where applicable—LP/public-pool performance, not a fixed lending yield.

Funding is peer-to-peer: longs pay shorts when funding is positive, with no exchange fee on funding. Assets and exposure. Supported collateral includes USDC and other listed assets; the product supports crypto perps and has expanded to RWA markets. Exposure is directional unless the user separately hedges; no evidence supports a market-neutral default strategy. Leverage is market-specific, up to 50x for BTC/ETH, with lower limits for other markets. Organic vs subsidized. Standard accounts currently pay 0 maker/taker fees; opt-in Premium accounts pay fees, with LIT-staking discounts.

DeFiLlama reports Lighter Perps 30-day fees of $3.81m, revenue of $2.84m, and incentives of $0, but these are analytics-platform figures rather than raw on-chain verification. Revenue includes maker/taker, transfer, and withdrawal fees; liquidation fees go to LLP. LIT buybacks are classified as holders’ revenue. Lock-ups and withdrawals. Public Pools issue redeemable shares and reportedly have no lock-up; withdrawals can occur at any time, subject to liquidity/operator mechanics.

Secure withdrawals/transfers have a 1-USDC minimum; fast USDC withdrawals have a 4-USDC minimum. TVL, trend, APY. Product-level DeFiLlama TVL is not displayed in the retrieved record; parent Lighter TVL is approximately $660–670m, but it includes bridge, spot, and other products and must not be attributed to Lighter Perps. Lighter Perps’ 30-day perp volume is $40.49bn and open interest $1.089bn. APY history/volatility/sustainability is not applicable as a standardized metric; returns depend on trading, funding, liquidation, and pool performance.

Dune comparison, chain-level raw balances, and historical APY are Not verifiable as of September 6, 2026. Contradiction callout: Earlier notes identified Arbitrum; current DeFiLlama identifies Lighter Perps as operating on zkLighter. The current product-level source supersedes the older note; Arbitrum attribution is Not verifiable as of September 6, 2026.

As of September 6, 2026:

• Protocol treasury / reserve size: Not verifiable as of 2026-09-06. No independent reserve report, proof-of-reserves, attestation, or treasury balance disclosure was located.
• On-chain balances via Dune: Not verifiable as of 2026-09-06. Dune MCP was unavailable for this run; no on-chain balance figure or Dune query/execution ID is available.
• Custody address: Lighter documentation identifies the Ethereum proxy contract holding platform collateral as 0x3B4D794a66304F130a4Db8F2551B0070dfCf5ca7. This is a user-collateral custody contract, not evidence of a separately disclosed protocol treasury.
• Custody model: Independent coverage reports that Ethereum smart contracts custody user funds, with state changes accepted only after proof verification on Ethereum. Lighter’s own materials additionally claim user-controlled funds and withdrawal rights if the rollup goes offline; the latter is an unverified marketing claim.
• Control: Lighter documentation states that unlisted contract functions are reserved for a protocol-controlled governor multisig. The multisig address, signers, threshold, and ability to move or encumber collateral were not independently verified here.
• Composition / reserve policy: The system supports deposited collateral and public pools; no independently verifiable breakdown of assets, insurance-fund balances, liquidity-provider capital, operating treasury, or reserve-policy parameters was found. The reported 25% “Ecosystem/Reserve” LIT allocation is a token-allocation category, not evidence of liquid treasury reserves.
• Attestations: Not verifiable as of 2026-09-06. Risk conclusion: User-collateral custody architecture is partially documented, but protocol-owned reserves, liabilities, treasury control, and solvency cannot be quantified. Do not treat the disclosed custody contract balance as protocol liquidity without a reproducible on-chain reconciliation.

Lighter Perps currently appears to have no native token live or announced, so most standard tokenomics dimensions are *Not applicable*. Below is what can and cannot be verified as of 2026-09-04. ### 1. Existence of a native token Public sources describing Lighter Perps/Lighter.xyz present it as a perpetuals DEX/product without mentioning any live or upcoming protocol token, ticker, or token sale.

The app front-end and docs-style materials focus on trading, margins, and liquidation mechanics, not on a token. No Lighter token listing is visible on major aggregators (DefiLlama, CoinGecko, CoinMarketCap) under “lighter-perps” or obvious variants. → On this basis, the appropriate statement is: Lighter Perps does not have a native token, or none is publicly disclosed/active. Not verifiable as of 2026-09-04. ### 2. Token identifiers (name, ticker, contract)

• Native token name: Not verifiable as of 2026-09-04.
• Ticker: Not verifiable as of 2026-09-04.
• Contract address(es) on any chain: Not verifiable as of 2026-09-04. No explorer pages or analytics dashboards clearly labeled as a “Lighter” governance or utility token contract are findable for this protocol. ### 3. Supply, market cap, FDV Because no token contract is identified:
• Total and circulating supply: Not verifiable as of 2026-09-04.
• Market cap and FDV on major trackers: not present for a Lighter Perps token. ### 4. Utility, governance, and value accrual There is no documented token utility (governance voting, fee discounts, staking, revenue share, buybacks, burns) tied to a native Lighter token in accessible materials. ### 5. Emissions, unlocks, allocations Without a token or published tokenomics sheet:
• Emissions schedule / unlock calendar: Not verifiable as of 2026-09-04.
• Allocations (team, investors, treasury, community): Not verifiable as of 2026-09-04.
• Whether announced unlocks occurred on-chain: Not verifiable as of 2026-09-04. ### 6. Holder concentration, mint/blacklist/fee-switch
• Top-holder concentration / insider wallets: Not verifiable as of 2026-09-04.
• Mint, blacklist, fee-switch, or admin functions for a token: Not verifiable as of 2026-09-04, since no token contract is identified. ### 7. DEX liquidity and listings No Lighter Perps-native token pool or listing is visible on mainstream DEX/cross-chain analytics under the protocol slug. Any assets traded on Lighter Perps (e.g., collateral or underlying pairs) are standard crypto assets, not a protocol-native token. For risk analysis purposes, treat Lighter Perps as a non-tokenized protocol until a verifiable token contract and tokenomics are published.

A BTC move below $10,000 would be a severe stress event for a perpetuals venue like Lighter because perps allow substantial leverage, so a sharp market gap can trigger rapid liquidations and losses for over-levered traders. Lighter’s own funding docs confirm hourly funding on positions, which means stressed market moves can quickly feed into position economics and liquidation pressure. For Lighter Perps, the main risk transmission channels would be:

• Liquidation cascade: falling BTC prices would likely force leveraged long positions to unwind, amplifying short-term volatility.
• Funding stress: sustained one-sided positioning can make funding more extreme and increase carry costs for trapped longs.
• Liquidity strain: lower market depth during the drawdown can worsen slippage and reduce orderly execution. What I can verify from the available sources is limited: the web results describe Lighter as a perp venue and explain perps/leverage mechanics, but they do not provide verifiable protocol-specific stress-test data, insurance fund size, liquidation engine parameters, or reserve backstop details. Those items are Not verifiable as of 2026-09-04. So the practical stress view is: if BTC falls below $10,000, Lighter would likely face a high liquidation-volume regime and potentially severe temporary market dislocation, but the magnitude of protocol losses, user deficits, or socialized loss risk is Not verifiable as of 2026-09-04 from the sources provided.

For Lighter Perps, a 20% depeg in the largest collateral is a severe collateral shock, but the resulting damage cannot be quantified from the provided sources alone. The only directly relevant evidence here is general: a 20% collateral loss can make a loan unwhole when leverage is already high, because liquidation may not recover the full debt after the collateral falls. For this protocol specifically, the key impact channels to assess would be: reduced margin value, faster liquidation of leveraged positions, and any resulting bad debt if liquidation buffers are insufficient.

However, the protocol’s collateral composition, margin parameters, liquidation rules, and concentration by asset are Not verifiable as of 2026-09-04 from the available sources. If you want a practical risk statement for an internal memo, the safest wording is: a 20% depeg of the dominant collateral would likely trigger broad margin compression and liquidations, with loss severity depending on the collateral’s share of total margin and the protocol’s liquidation haircuts; the size of any insolvency gap is Not verifiable as of 2026-09-04.

For Lighter Perps, the relevant stress case is a liquidation shortfall / bankruptcy event: if a user falls below close-out margin, the protocol’s LLP (insurance fund) takes over the position and remaining collateral; liquidation fees can be routed into LLP, and LLP is explicitly described as the backstop for ADL events. If LLP is insufficient, I cannot verify a documented further loss-sharing layer for Lighter from the gathered sources, so the terminal fallback is Not verifiable as of 2026-09-04. Expected loss path

• A bankrupt trader’s account is force-closed; the close-out mechanics attempt to execute the position and capture collateral/liquidation fees into LLP.
• LLP absorbs the deficit and backstops ADL risk for liquidity providers.
• If LLP cannot fully cover the deficit, the remaining downstream handling is Not verifiable as of 2026-09-04. Who absorbs it
• First: the LLP / insurance fund.
• In ADL-type stress, liquidity providers are the risk-bearing counterparty class referenced as being backstopped by LLP. Compensation / recovery
• The protocol documents liquidation fees flowing to LLP, including a fee of up to 1% when liquidation fills better than zero price.
• I could not verify any explicit socialized-loss compensation mechanism, recapitalization rule, or user clawback rule from the gathered sources, so that part is Not verifiable as of 2026-09-04. Smart-contract impact path
• Margin breach triggers liquidation logic.
• Liquidation engine transfers seized collateral and liquidation proceeds to LLP.
• LLP then assumes the risk / position exposure.
• ADL risk is explicitly stated to be fully backstopped by LLP. Contradiction callout: one Lighter docs page describes LLP as closing positions and taking remaining collateral, while another more recent page frames LLP as the backstop for ADL and liquidity-provider risk; these are consistent at a high level, but the exact end-of-loss waterfall beyond LLP is not exposed in the gathered sources.

For Lighter Perps, I found no verifiable evidence that the DAO or owners committed fraud. As of 2026-09-04, that specific stress scenario is not verifiable from the provided results. The only directly relevant authoritative material in the search set concerns The DAO and broader DAO liability/fraud cases, not Lighter Perps.

The SEC’s DAO report shows that a DAO can face securities-law issues and that misconduct can arise in DAO structures, but it does not say anything about Lighter Perps specifically. The other results are unrelated legal commentary or cases about other DAOs and DeFi protocols, so they do not establish fraud by Lighter Perps’ DAO or owners. Assessment:

• Fraud by DAO/owners: Not verifiable as of 2026-09-04.
• Known incident evidence in provided sources: None specific to Lighter Perps.
• Confidence: Low, because the search results do not include protocol-specific investigative, regulatory, audit, or on-chain evidence for Lighter Perps. If you want, I can next assess related risks such as admin-key abuse, insider control, or custodial/bridge fraud exposure for Lighter Perps using only protocol-specific evidence.

Lighter Perps has a negative 30-day primary yield source only if the protocol’s primary yield is interpreted as the LLP/APR or LP yield and that yield has turned below zero; however, none of the provided sources verify a negative 30-day value. The available evidence only shows that Lighter’s yield and revenue streams come from maker/premium fees, liquidation-related flows, and USDC interest sharing, while retail trading fees are zero. For a stress scenario, the key risk is that Lighter’s yield is structurally variable, not guaranteed, and can fall sharply if trading activity, premium payments, or interest income weaken.

A third-party research PDF explicitly says LLP APRs were “in excess of 200%” at the time of writing but “very volatile and far from guaranteed,” which supports the conclusion that a negative 30-day outcome is plausible in stress, even though it is not directly verified here. Because the web results do not provide an auditable 30-day yield time series for the selected protocol, the exact negative 30-day figure is Not verifiable as of 2026-09-04.

As of September 13, 2026 — Governance assessment Control surface. Elliot Technologies, Inc. (“Lighter”) operates the hosted frontend, API, token programs and related services. Its Terms allow unilateral modification or suspension of the Interface/API.

The protocol’s Ethereum contracts hold collateral and canonical state; users have an on-chain escape hatch if the Sequencer fails. Contracts and funds. L2BEAT identifies upgradeable rollup/escrow, Governance and verifier contracts. The contract admin routes through an UpgradeGatekeeper to a 3-of-5 “Lighter Multisig 2”. That governor can manage validators, the network governor, markets/assets, insurance-fund and treasury addresses.

A separate 4-of-7 “Lighter Multisig” security council can reduce the nominal upgrade delay to zero. Therefore, a malicious authorized upgrade could potentially redirect or drain funds; this is an upgrade-admin risk, not evidence of a routine direct withdrawal function. Timelock/emergency powers. Nominal upgrade delay: 21 days (504 hours). Effective delay can be zero because the security council can bypass it.

L2BEAT flags this as critical and notes that funds could be stolen through a malicious code upgrade. DAO and proposals. LIT documentation describes staking, LLP access, rewards and buybacks, but not token-holder voting. The documented “Governance” contract is an administrative contract controlled by the network-governor multisig, not a DAO voting system. Proposal process, quorum, delegation, and execution by LIT holders: Not verifiable as of September 13, 2026.

DAO governance is therefore assessed as false / symbolic or absent. Voting concentration/top holders. Dune MCP was unavailable in this run. Voting concentration and top LIT holders: Not verifiable as of September 13, 2026. Company/legal wrapper. The service entity is Elliot Technologies, Inc.; a 2020 SEC Form D identifies Delaware incorporation and EIN 82-1211884. Current registration status, registration number, directors, board control and multisig-signer independence: Not verifiable as of September 13, 2026.

Terms select Florida law and Miami-Dade County forums. Bottom line: real contract administration is concentrated in multisigs, not token holders. The 21-day timelock is not a reliable exit protection because the 4-of-7 security council can eliminate it.

As of September 4, 2026: Entity / jurisdiction. The identified operator is Elliot Technologies, Inc., doing business as Lighter. A SEC Form D identifies it as a Delaware corporation, incorporated in 2016, with a principal business address in Mountain View, California. The protocol is described as autonomous software, but the company supplies the web interface, API, token-related services and related products.

Terms / restrictions. The Terms prohibit access by persons located, resident, incorporated or principally operating in the United States, Canada, United Kingdom, China, North Korea, Russia, Ukraine, Cuba, Iran, Venezuela or Syria, and by sanctioned/restricted persons. They include mandatory arbitration, class-action waiver, broad suspension rights and user indemnities. KYC/AML. No standalone public KYC/AML policy or licensing disclosure was located.

The Terms contain sanctions/geographic representations and unlawful-conduct prohibitions, but that does not verify a full AML program, identity verification, transaction monitoring or Travel Rule compliance. Not verifiable as of September 4, 2026. Classification / actual risk. Lighter offers perpetual-futures trading and markets itself as a decentralized, non-custodial exchange. That architecture does not eliminate operator or jurisdictional exposure: a U.S. corporation operates the interface, API and commercial ecosystem while offering derivatives-like products and excluding U.S. users contractually. The token’s legal classification and any applicable derivatives, securities, commodities or money-transmission registrations are Not verifiable as of September 4, 2026. Warnings, enforcement, litigation, sanctions. No regulator warning, court case, enforcement action or sanctions designation naming Lighter or Elliot Technologies, Inc. was located in the reviewed sources.

This is not a clearance determination: Not verifiable as of September 4, 2026. Data protection. The mobile privacy policy states collection of IP address, approximate location, device/usage data and potentially email; it references Google Play Services, Expo, Sentry and Mixpanel, permits legally compelled disclosures, and provides deletion requests by email. A comprehensive web-interface privacy policy, governing law, GDPR/CCPA representations and breach obligations were Not verifiable as of September 4, 2026.

No exact GLEIF LEI record for 'Elliot Technologies Inc', 'Lighter Perps'. OFAC SDN screening of 'Elliot Technologies Inc', 'Lighter Perps': no match. SEC litigation and administrative release feeds: no mention.

Lighter Perps does not appear to issue its own stablecoin; the available web evidence describes the protocol as using external stablecoins such as USDC and USDG as collateral/quote assets, with USDC described as the preferred/default stablecoin in later coverage and USDG described as collateral and quote asset in Robinhood-related integrations. No verifiable web evidence in this run shows a depeg event for the stablecoin(s) used by Lighter, so depeg_count, last_depeg_date, and max_depeg_pct remain not verifiable as of 2026-09-06. The structured fill is: own_stablecoin=false, stable=null, depeg_count=null, max_depeg_pct=null, last_depeg_date=null, stablecoin_ids=["USDC","USDG"].

Lighter Perps combines high-leverage derivatives, oracle-dependent marking, automated liquidation, and a custom ZK-rollup stack; failures can therefore propagate across trading, collateral, and withdrawals. On-chain balances, LLP/insurance coverage, utilization, concentration, and chain exposure are Not verifiable as of September 5, 2026 because Dune verification was unavailable; residual assessments below are consequently conservative.

Lighter’s top strengths are its verifiable trading integrity, CEX-like speed, zero-fee retail access, Ethereum-anchored settlement/security, and purpose-built execution architecture. In practice, it combines zk-verified matching and liquidations with a custom perps-specific rollup, so traders get deterministic price-time-priority execution and cryptographic proof that the venue followed its own rules.

• Verifiable matching and liquidations: Lighter’s main differentiator is that order matching, risk checks, and liquidations are provably correct via custom zero-knowledge circuits.
• High performance / low latency: Sources describe it as delivering centralized-exchange-like execution speed, with millisecond-level matching and sub-10ms latency claims.
• Zero fees for retail: Standard retail users pay zero maker and taker fees, which is one of the clearest user-facing advantages.
• Ethereum security and non-custodial settlement: User funds are kept in Ethereum smart contracts, and state advances only after proofs verify on L1, improving security and transparency.
• Specialized architecture for perpetuals: Lighter is built as an app-specific zk-rollup for perpetuals, which gives it an efficiency advantage over general-purpose rollups for order books and liquidation logic.