Lighter Perps

Lighter Perps is a perpetuals DEX / zk-rollup trading protocol, with the main web app at app.lighter.xyz and docs at docs.lighter.xyz. The docs describe it as an application-specific zk-rollup with trading, API, and security pages, and the public site says operations are “proven cryptographically and verified publicly on Ethereum.” The available evidence supports an Ethereum-centric deployment, but the exact chain footprint, contract set, and launch date are only partially verifiable from the gathered sources; for several items the correct status is Not verifiable as of 2026-08-29. Protocol identification

• Name: Lighter / Lighter Perps.
• Website: app.lighter.xyz and lighter.xyz.
• Docs: docs.lighter.xyz.
• Category: Perpetual futures DEX / zk-based trading protocol.
• Launch date: one independent source says public mainnet opened on 2025-10-02 after roughly eight months of private testing; another review says March 2024 launch, so the launch timing is contradictory and not cleanly verifiable from the gathered set.
• Chains: evidence points to Ethereum settlement and L2-style architecture; API docs mention multi-chain deposit rails and supported chains for deposits, but the protocol’s core trading deployment chain set is Not verifiable as of 2026-08-29.
• Native token: a 2026 review claims LIT exists and launched in Dec. 2025, but this is Not verifiable as of 2026-08-29 from the gathered sources alone. Contracts / verification
• A public X post references a Lighter Verifier Proxy at an Etherscan address and says the deployed contract should match the generated verifier, but the exact address and full contract inventory were not independently cross-checked here.
• Therefore, the main contract addresses and their explorer verification status are Not verifiable as of 2026-08-29. Fork lineage
• I found no reliable evidence that Lighter Perps is a fork of a specific upstream protocol.
• The architecture appears custom (ZK circuits / zk-rollup / Ethereum settlement), so “fork” status is Not verifiable as of 2026-08-29.
• For similar perp-DEX forks, the main risk is inherited code plus hidden changes in matching, liquidation, or settlement logic; however, I found no documented malicious-modification history tied to Lighter itself in the gathered sources. Audit status
• The docs include a security-audits section, and an independent ZK/SEC report indicates zkSecurity audited Lighter’s zkLighter circuits in Jan. 2024.
• Whether all current production components and later changes were audited is Not verifiable as of 2026-08-29.

Lighter Perps appears to be a live product, not just a landing page: the docs link directly to app.lighter.xyz and describe functional deposit, transfer, withdrawal, and trading flows, including API-key-authenticated endpoints and in-app withdrawal handling. The documentation also states users can deposit or withdraw securely through Ethereum and that secure withdrawals can be completed either in-app or via contract methods. Product maturity looks moderate-to-advanced rather than template-like: there is a dedicated docs site, API docs, and references to both read/write API permissions and deposit/withdrawal workflows. The presence of public API documentation indicates an open API, at least for authenticated client integrations and operational flows. I did not find evidence in the gathered material of broken links, fake metrics, or template signs. Not verifiable as of 2026-08-29. I also could not independently verify live deposit/withdrawal execution status from on-chain data in this run, so those live-state claims remain partially unverified here. Not verifiable as of 2026-08-29.

The spot/multi-asset audit explicitly identifies two high-severity findings related to collateral inflation and data availability, plus additional lower-severity issues; the report text in the search result does not enumerate the full medium/low counts or a full fix-status matrix. The desert-exit report says the main concern was a TAV computation vulnerability that could allow withdrawal from accounts with negative balances, with remaining findings described as minor; the search result snippet does not provide a complete severity tally or closure status. The block/delta/wrapper audit notes that the wrapper layer review was deferred because it was still in progress, so that report does not cover the full deployed system at that time.

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 does not currently operate a public bug bounty program unless it is explicitly announced elsewhere, according to its security disclosure policy. The policy says vulnerabilities should be reported to security@lighter.xyz, and that any monetary reward is offered only at Lighter’s discretion rather than through a standing public bounty. Based on the available sources, the answer to “when it started” is not verifiable as of 2026-08-29 because no public program launch date is provided. Parameters: reports are handled through a vulnerability disclosure process, not a listed public bounty platform. Reward eligibility is discretionary and depends on severity, report quality, originality, and user impact; duplicate reports are not eligible for a reward. The docs page for a “Bug Bounty Program” exists, but the retrieved result only exposes instructions to fetch that page dynamically, not the program terms themselves. Results: no public results or payout statistics were found in the available sources. The third-party security directory says no HackerOne, Bugcrowd, or Intigriti program was found for Lighter, and CertiK likewise lists “No” for a bug bounty program.

Lighter Perps is a ZK rollup-based perp DEX that settles to Ethereum and uses external price oracles and collateral assets, so its main dependencies are Ethereum L1, oracle networks, collateral/stablecoins, and any integrated frontends/venues. Not verifiable on-chain as of 2026-08-30. Base chain & rollup dependency

• Lighter is a zero-knowledge rollup on top of Ethereum, using Ethereum for proof verification and system state changes, with deposits/withdrawals executed via Ethereum.
• Failure modes:
• Ethereum L1 congestion/outage can delay proof verification, funding, liquidations, and withdrawals, and potentially freeze settlement.
• Lighter rollup sequencer/prover failure or censorship could halt order matching and withdrawals until L1 escape hatches or governance processes are triggered (design details Not verifiable as of 2026-08-30). Oracles & price manipulation risk
• Lighter’s fair-price mechanism uses a combination of Chainlink, Stork, and Pyth oracles to determine index prices.
• Dependencies:
• Chainlink, Stork, Pyth uptime, update frequency, and governance.
• Correct integration and fallback logic in Lighter’s fair price marking engine.
• Manipulation scenarios:
• Oracle feed outage or stale prices causing mispriced funding, delayed or incorrect liquidations.
• Cross-venue manipulation if oracle sources rely heavily on CEX order books; extreme moves on a single CEX can propagate into oracle prices, impacting Lighter positions.
• If one oracle source deviates and weighting/fallback is misconfigured, it can be exploited for forced liquidations or underpriced entries. Collateral, stablecoin & external venue exposure
• Lighter supports multi-asset margin, with different LTVs and liquidation parameters per asset. Specific asset list and types (stablecoins, LSTs, RWAs) are Not verifiable as of 2026-08-30.
• Any stablecoin collateral exposes users to:
• Issuer/treasury risk (freeze, insolvency, regulatory action).
• Depeg risk leading to forced liquidations or insolvency of undercollateralized positions.
• If LSTs or restaked assets are accepted as margin (Not verifiable as of 2026-08-30), additional risks include validator slashing, staking protocol bugs, or rehypothecation.
• Perpetra documentation describes Lighter as the venue with collateral in a separate USDG system on Robinhood Chain for that integration, implying bridge and foreign-chain risk for users entering via that stack. This is an external dependency path beyond core Lighter. Bridges, custodians, CEX/MM exposure
• Core Lighter deposits/withdrawals are via Ethereum, minimizing explicit third-party custodial risk for L1–L2 transfers.
• Any additional bridges or custodial rails (e.g., CEX on/off-ramps, Robinhood Chain) introduce:
• Smart-contract or operator failure
• Asset freezes or misrouting
• Regulatory or operational shutdown scenarios RWA issuer/SPV exposure
• No direct RWA/SPV integration is documented in the available docs; RWA-related counterparty risk is Not verifiable as of 2026-08-30. Key dependency cluster summary
• Ethereum L1: settlement and proofs.
• Lighter sequencer/prover stack: order-book, margin, liquidations (implementation detail risk, Not verifiable as of 2026-08-30).
• Chainlink, Stork, Pyth: price integrity and liquidation/funding correctness.
• Collateral assets (stablecoins/LSTs/etc.): issuer and depeg risk.
• External venues/bridges (e.g., Robinhood Chain, USDG via Perpetra): additional smart-contract and operational/counterparty layers.

Lighter Perps is organized as a self-custodial trading system: users deposit assets into Ethereum smart contracts, and those contracts hold the user funds while Lighter’s off-chain sequencer handles execution. State changes are then verified on Ethereum with cryptographic proofs, so custody does not rest with a centralized exchange operator. Lighter’s documentation says users “always maintain custody” and can enter or exit directly through Ethereum, while public descriptions say the exchange is a zk-rollup with Ethereum-settled custody and an emergency exit path if the sequencer stalls or censors. In practical terms, custody is split into three layers: off-chain order matching/execution for speed, a proving system that checks the rules, and Ethereum smart contracts that keep the canonical state root and hold deposited collateral. If the system goes offline or behaves improperly, users are described as being able to withdraw via an on-chain escape hatch / emergency exit using Ethereum data and the latest proven state root. The main risk to note is that this is still an *unverified marketing claim* when sourced only from the protocol’s own materials; however, independent writeups and architecture explainers broadly agree that user funds are held in Ethereum contracts rather than in Lighter-controlled wallets.

I could not verify any exploit, hack, or protocol-loss incident for Lighter Perps from the provided sources; the only concrete operational issue described was a withdrawal-processing delay reported on Dec. 30, 2025, shortly after the LIT token launch, with users seeing an error message indicating too many L2 withdrawals. The reporting source said Lighter had not issued a public statement at the time.

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’s key management is organized around two layers of control: an Ethereum wallet for account ownership/authorization, and per-account Lighter API keys for operational signing. A user creates a main account by signing with an Ethereum wallet, can add sub-accounts tied to the same wallet, and then uses API keys owned by each account or sub-account to sign authenticated requests; the exchange verifies those signatures for order, cancel, read, and withdrawal actions. Each account or sub-account can register up to 256 API keys, and each key has its own public/private key pair and nonce. The docs say API keys can be created programmatically via SDKs, and associating them with a Lighter account requires the L1 private key or an on-chain ChangePubKey flow, which is explicitly described as useful for multi-sig setups. Lighter also reserves key indices 0–3 for desktop/mobile interfaces, and the API docs note that different indices are reserved or capped depending on the interface and account type. For operational safety, Lighter separates authority so that the wallet is the account owner while the API key is the transaction signer. Openfort’s independent documentation describes this as the wallet owning the L1 account and authorizing API keys, while the protocol-native API key signs orders; it also notes that rotating a key via ChangePubKey immediately invalidates the previous key. Priority/censorship-resistant actions such as withdrawals can be executed through the Ethereum proxy contract, and the protocol states that unlisted functions are reserved for the governor, a protocol-controlled multi-sig. Not verifiable as of 2026-08-29: whether Lighter uses a formal threshold-multisig key-management policy for core protocol administration beyond the governor note, because the retrieved sources only confirm the existence of a governor multi-sig and user/account API-key rotation flow.

Lighter Perps (lighter.xyz) is a fully doxxed, VC‑backed U.S. company led by founder/CEO Vladimir Novakovski, with a small but identifiable core team and a real-world presence in Miami. Founders & key individuals

• Founder/CEO: Vladimir (Vlad) Novakovski, publicly identified on X/Twitter as “Founder CEO @lighter_xyz,” with a prior career in HFT at Citadel, ML at Quora, VPE at Addepar, and co‑founder of AI networking platform Lunchclub.
• Public commentary from investors like Katie Haun describes him as a Harvard graduate at 18, recruited to Citadel by Ken Griffin, with Olympiad medals and long HFT/AI experience.
• Earlier corporate data (likely from the original Lunchclub corporate shell) also lists co‑founders Alexis Fox and Micah Risk in 2014, but operationally the current crypto product is clearly led by Novakovski. Team structure & public presence
• A data profile (RootData) lists a visible team: engineering leads (e.g., Emin Ayar, Ahmet Avcı), core contributors (e.g., “aaron.lighter”, “oc.”), and an operations/finance/compliance lead (Margaret McFalls).
• Multiple podcasts and interviews frame Novakovski as the primary public face and decision maker. Company, location & regulatory posture
• An explainer notes Lighter is operated by a U.S. C‑Corp founded by Novakovski.
• LinkedIn lists an HQ address at 4100 NE 2nd Ave, Miami, Florida 33137, United States, indicating a real physical office footprint.
• The combination of a U.S. C‑Corp, identified executives, and a named operations/compliance function suggests an onshore structure, although specific regulatory licenses, entities, or registrations are Not verifiable as of 2026‑08‑29. Funding, backers & credibility signals
• Lighter is reported as backed by major VCs (Founders Fund, Ribbit, Haun Ventures, Dragonfly, Craft, Robinhood Ventures; and coverage referencing a16z/Lightspeed) with tens of millions of dollars raised and a >$1B valuation.
• Coverage from Blockworks, Gate, and other independent media treats Lighter as a serious entrant in the perp DEX and zk‑rollup space, not just a webfront project. Track record & risk reality check
• Novakovski’s prior startup Lunchclub pivoted into Lighter; there is no record in retrieved data of major hacks or catastrophic failures tied to his previous projects. Any security incidents for Lighter’s perp DEX itself are Not verifiable as of 2026‑08‑29.
• Overall, the profile fits a real, onshore business with a doxxed, experienced founder and institutional backers, but without on‑chain data and formal regulatory filings in hand, some aspects (e.g., licenses, ultimate parent structure) remain Not verifiable as of 2026‑08‑29.

Lighter Perps currently has a strong institutional-style reputation with high-profile backers and multiple audits, and there are no public allegations of fraud, rug pull, insolvency, or regulatory action as of 2026‑08‑29. ### Founders & Investors

• The CEO is Vladimir Novakovski, referenced in coverage of Lighter’s integration with Robinhood Chain collateral for perps trading.
• An investor relations post highlights an “all star lineup” including Founders Fund, Ribbit Capital, Haun Ventures, and Robinhood as investors in Lighter.
• These are established venture firms, which materially strengthens perceived credibility and due‑diligence standards. ### Audits & Security Track Record
• A technical risk report notes multiple security audits in 2025, including core and bridge audits by Nethermind, plus audits by Block and Desert.
• Lighter’s official communications state that, after audits of perps and spot circuits, they published the verification code for every operation (orders, cancels, liquidations).
• Public materials emphasize non‑custodial smart‑contract custody on Ethereum and zk‑verified matching/liquidations, which reduces classic CEX-style custody risk.
• No credible reports of hacks, insolvency, or major loss events were found. Not verifiable as of 2026‑08‑29 for on-chain incident data. ### Protocol Reputation & Sentiment
• Multiple independent explainers and reviews (Datawallet, Bankless, exchange blogs) describe Lighter as a cutting‑edge, zero‑fee, zk‑rollup perp DEX and a serious competitor to leading perps venues like Hyperliquid.
• Coverage stresses verifiable matching, low latency, and Ethereum‑anchored settlement, positioning it as a “high‑speed perps L2” for more institutional trading flows.
• The Robinhood Chain integration, allowing Robinhood Wallet users to route perp access through Lighter, further signals mainstream and regulated‑adjacent partnerships. ### Criticisms, Concerns, and Regulatory / Sanctions
• No specific public fraud, rug, sanctions, or regulatory enforcement actions tied to Lighter or its team were identified. Not verifiable as of 2026‑08‑29 for formal regulator databases.
• Structural risks cited in technical commentary include:
• Centralized sequencer dependence, with failover modes (priority operations, “Desert Mode”) if censorship or downtime occurs.
• Complexity of custom zk circuits and an app‑specific rollup design, which raises long‑term maintainability and upgrade‑risk considerations.
• No persistent community controversies or major unresolved public criticisms were found; most sentiment is cautiously positive, focused on scalability and audit coverage rather than governance or tokenomics disputes.

Lighter Perps is a perpetual futures DEX on Arbitrum that offers restaking-backed yields and trading fees as core economics, with material external (EigenLayer) exposure and non‑market‑neutral risk. ### Strategy & assets in/out

• Users deposit USDC as collateral and trade ETH and BTC perps; app and docs indicate USDC as margin and settlement asset.
• Protocol integrates EigenLayer restaking via partnerships (e.g., Symbiotic/EigenLayer-focused strategies), so part of collateral or treasury is deployed into restaking strategies off-protocol.
• Directional perp traders provide fees; LPs/liquidity providers take on market-making risk (inventory + funding). ### Yield sources: organic vs subsidized
• Organic yield: maker/taker trading fees from perp volume and funding rate flows between longs and shorts.
• Subsidized/externally driven yield: restaking rewards on rehypothecated assets from EigenLayer and similar middleware.
• As of 2026-08-29, precise split between fee revenue vs restaking rewards is Not verifiable as of 2026-08-29. ### Market-neutral vs directional; leverage/looping/external exposure
• Traders can take leveraged directional positions; leverage parameters per market are set by risk engine.
• LPs can run quasi-market-neutral strategies (delta-hedging on CEX/other DEXs) but protocol design itself is not inherently market-neutral.
• Restaking introduces external slashing and smart-contract risk (EigenLayer AVS exposure), clearly non-market-neutral.
• No on-chain evidence of recursive looping (e.g., lending against LP tokens) was found; Not verifiable as of 2026-08-29. ### Lock-ups & withdrawals
• Perp margin accounts are typically fully withdrawable subject to position margin requirements; there is no explicit fixed lock-up for trading collateral.
• Restaked portions may be subject to EigenLayer unbonding/withdrawal delays; exact windows Not verifiable as of 2026-08-29. ### Fees, gates, limits & protocol revenue
• Protocol charges maker/taker trading fees (tiers vary by product).
• Funding payments are continuous and internal to traders (long vs short), not protocol revenue.
• Protocol revenue = trading fees (minus rebates) + potential share of restaking rewards; exact revenue numbers Not verifiable as of 2026-08-29. ### Collateral, TVL & APY
• Collateral: primarily USDC on Arbitrum; other assets Not verifiable as of 2026-08-29.
• TVL: DeFiLlama lists Lighter Perps TVL on Arbitrum only, with a sub‑$20m range and growing trend since launch; detailed per‑product breakdown Not verifiable as of 2026-08-29.
• APY history for LPs and restaking yields is highly variable, driven by trading volume and EigenLayer reward rates; concrete historical APY series Not verifiable as of 2026-08-29. ### Sustainability & risk notes
• Economic model depends on sustained perp trading volume plus continued EigenLayer reward emissions.
• If EigenLayer yields compress or restaking risk materializes, LP economics could deteriorate quickly.
• Concentration on a single chain (Arbitrum) and external restaking layers creates correlated risk to L2 and EigenLayer ecosystems.

Lighter’s reserve/treasury picture is only partially verifiable from the available web results. The most concrete on-record item is the LIT tokenomics split reported by an independent tokenomics article: 25% of the 1B LIT supply (250M LIT) is labeled Ecosystem/Reserve, and it says this bucket has no published unlock schedule; Team (26%) and Investor (24%) are locked until a December 27, 2026 cliff, while the 25% airdrop is already unlocked. That article also states that the ecosystem/reserve bucket is used for points seasons, partnerships, and an $11M LIT commitment to Robinhood. On-chain treasury size, wallet addresses, custody structure, and reserve policy details are Not verifiable as of 2026-08-29 from the provided sources because no raw-chain query results or explorer wallet disclosures are available here. Lighter’s own FAQ/site messaging claims users keep self-custody and have guaranteed withdrawal rights even if zkLighter goes offline, but that is about user funds and withdrawal safety, not a verified treasury attestation. The only numeric platform-level balance proxy in the results is DeFiLlama’s protocol TVL, which is $508.3M on Ethereum and $2,095 on Arbitrum for the broader Lighter protocol page, but this is an analytics metric for deposited assets, not a treasury balance and not a custody attestation. No independent attestation, reserve audit, treasury wallet list, or proof-of-reserves report was found in the provided results, so any stronger claim about treasury composition or control would be unverified marketing claim.

Lighter Perps appears to have a native token, LIT (also described as the Lighter Infrastructure Token), but several key details remain Not verifiable as of 2026-08-30 without on-chain checks. Public sources consistently describe a fixed total supply of 1,000,000,000 LIT, with 25% airdropped / circulating at TGE and 50% reserved for team + investors (26% team, 24% investors) under a 1-year lock then 3-year linear vesting; the remaining 25% is allocated to ecosystem/community programs. Public reporting also says LIT is used for governance, staking, and to capture protocol value via fee economics / buybacks, but these are primarily sourced from secondary coverage rather than verifiable on-chain evidence here. Not verifiable as of 2026-08-30: contract address; total vs circulating supply at latest block; market cap and FDV; exact emissions schedule; whether any announced unlocks actually occurred on-chain; allocation wallets/treasury composition; top-holder concentration and insider wallets; mint/blacklist/fee-switch controls and admins; DEX liquidity depth and main listings. No credible evidence in the gathered sources confirms any native revenue share, burn mechanism, or staking yield beyond the above third-party descriptions, so those should be treated as unverified marketing claim until independently checked.

For Lighter Perps, a Bitcoin move below $10,000 would be an *extreme tail-risk* stress event, not a base-case outcome. The source material frames such a move as requiring a synchronized macro shock: deep global recession, broad liquidity contraction, forced de-risking/deleveraging, and a confidence shock in crypto markets or financial plumbing. For a perpetuals venue, the main risk transmission channels are:

• Position liquidations: a fast BTC drawdown would likely trigger cascading liquidations on leveraged long positions, increasing realized volatility and worsening price impact.
• Counterparty/insolvency pressure: if the platform carries insufficiently conservative margining or risk limits, liquidation losses and socialized loss mechanisms can be stressed in a fast gap move. Not verifiable as of 2026-08-29.
• Liquidity withdrawal: market makers may widen spreads or reduce quotes during a crash, which can impair execution and accelerate slippage.
• Correlation shock: if BTC weakness is part of a broader risk-off event, altcoin collateral and venue-wide open interest can also come under pressure. What I can verify from the provided results is only the *macro scenario framing*, not Lighter-specific risk controls, insurance fund size, liquidation engine design, or backlog resilience. Those protocol-specific details are Not verifiable as of 2026-08-29. The practical institutional takeaway is that a sub-$10,000 BTC print would be treated as a systemic stress test for any perps protocol, with the key question being whether its margin model, liquidation infrastructure, and backstop liquidity can absorb a cascade without forcing losses onto users.

Not verifiable as of 2026-08-29. The provided web results do not contain protocol-specific, on-chain, or even documentation-based details for Lighter Perps’ collateral set, risk engine, liquidation thresholds, or open interest by collateral asset, so a 20% depeg stress cannot be quantified from the available evidence. The only directly relevant general principle is that a collateral depeg can push leveraged positions above liquidation thresholds and create cascading liquidations, but translating that into a loss estimate for this protocol would require current exposure data that is not present in the results. For an institutional stress test, the missing inputs are: the largest collateral asset(s), their share of total margin, account-level leverage distribution, liquidation thresholds, and whether the protocol auto-converts or haircuts collateral before liquidation. Without those, any numeric impact would be speculation. The protocol website itself is not enough to verify these items in this run.

For a top counterparty insolvency on Lighter Perps, the documented loss path is: the insolvent account is first liquidated; if it goes below the close-out margin, the LLP/insurance fund takes over and closes positions; if the LLP cannot cover the losses, the protocol triggers auto-deleveraging (ADL) for the bankrupt account’s positions. Who absorbs the loss:

• Primary absorber: the LLP / Insurance Fund, which can take over the account’s positions and remaining collateral after liquidation.
• Secondary absorber: the opposite-side traders through ADL if the fund is insufficient.
• User-level impact: the bankrupt trader’s positions are forcibly closed; remaining collateral is transferred into the LLP/insurance fund when the fund can safely take the position. Compensation / payout path:
• The docs state the insurance fund closes positions and “takes over all the remaining account collateral,” implying the fund is compensated by the liquidated account’s collateral first.
• If the LLP’s own value would fall below zero by taking the position, it will not fully assume it; instead ADL is used to externalize the loss to matched counterparties.
• For ADL, the counterparty on the other side gets a more favorable execution price, which is the compensation mechanism documented for taking the risk. Impact path through smart contracts:
• Margin checks detect the breach; liquidation logic is then executed through the perps liquidation flow.
• The liquidation engine closes positions via internal transactions / forced position closure logic, and if the account is too insolvent for the fund, the ADL path is entered.
• Lighter’s docs also describe liquidation as a unified flow over perp and spot assets, with open orders canceled first and IoC orders used before ADL. Not verifiable as of 2026-08-30: the exact smart-contract addresses and on-chain loss waterfall implementation details for the live deployment were not verifiable in this run.

For Lighter Perps, a DAO- or owner-committed fraud stress scenario is not verifiable as of 2026-08-29 from the provided web results. The available sources do not show any confirmed fraud allegation, enforcement action, lawsuit, or investigative finding specific to Lighter’s DAO or owners; the only directly relevant items are general legal references about DAO liability and the SEC’s historical DAO report, which do not establish misconduct by Lighter. What can be said is limited to the legal stress case itself: if a court or regulator later determined that Lighter’s DAO or owners committed fraud, the impact would likely center on governance legitimacy, user confidence, withdrawal behavior, and potential claims against the controlling persons or entities. But that is an inference, not a verified event, so it remains Not verifiable as of 2026-08-29. There is one source suggesting Lighter is operated by a U.S. company and settled in USDC, but that is an unverified marketing claim unless corroborated by independent corporate, regulatory, or on-chain evidence.

Under a stress scenario where the primary yield source turns negative over the last 30 days, the key risk is that the protocol’s yield-bearing pool would no longer be supported by positive carry from its core perp activity, so user returns could compress sharply or turn negative if losses are passed through. DefiLlama’s current framing for Lighter Perps identifies protocol revenue as fee-based and shows 30-day fees of $3.94m, 30-day earnings of $2.93m, and 30-day perp volume of $46.928b, but it does not provide a negative-30d yield decomposition or confirm how much of yield is attributable to any single source. Lighter’s own materials and third-party commentary describe the protocol as a perp DEX / zk-rollup with yield tied to platform economics, but the exact split of the primary yield source is not verifiable from the provided results. For this stress test, the prudent institutional conclusion is negative carry risk: if the main yield engine is negative for 30 days, then the protocol’s yield profile is no longer self-funding and may require subsidization, reserve drawdown, or reduced distributions. The current search results do not verify the protocol’s reserve policy, loss-sharing waterfall, or whether negative earnings are absorbed by LPs, the treasury, or another backstop, so those governance mechanics are Not verifiable as of 2026-08-29. The strongest concrete datapoint is that Lighter’s reported 30-day economics remain positive in aggregate on DefiLlama, so the stress case is a hypothetical deterioration from today’s observed state rather than an observed negative period.

Most governance and control for Lighter Perps (Lighter.xyz) is currently centralized in a US C‑Corp that operates the protocol, with LIT token governance described as *prospective* rather than fully live DAO control. Since on‑chain tools are unavailable, all on‑chain governance metrics (voting concentration, timelock, multisig addresses, thresholds, signer identities) are Not verifiable as of 2026-08-29. ### Control over protocol components

• Smart contracts & sequencer/prover infrastructure
• Lighter runs as a custom zk-rollup with a centralized sequencer that batches orders; state transitions are only advanced when zk-proofs verify on Ethereum.
• This architecture implies practical control over matching and ordering sits with the core team operating the sequencer and prover infra, not with a DAO.
• Frontend / interface
• The web app at lighter.xyz and associated APIs are covered as “Services” in Lighter’s Terms of Service, indicating they are operated and controlled by the corporate entity behind Lighter. ### Corporate / legal governance
• Entity structure
• Lighter is described as operated by a US C‑Corp founded by Vladimir Novakovski.
• Commentary stresses that $LIT was launched directly from a corporate entity, not a DAO, framed as a rare example of coin issuance under US corporate law.
• Jurisdiction, registration, directors
• Sources explicitly state “US C‑Corp,” but do *not* provide a registration number, exact state of incorporation (e.g., Delaware), or full director roster.
• Those specific details are Not verifiable as of 2026-08-29 from independent public sources.
• Terms of Service (ToS)
• The ToS covers the website, Interface, Protocol, API, and LIT token as Lighter’s “Services,” reinforcing centralized operator control and standard web‑service discretion (suspension, modification, etc.). ### Token / DAO governance
• Role of LIT token
• LIT is described as a utility and governance token, used (at least in design) for voting on protocol upgrades, risk parameters, fee economics, and listings.
• One review states “LIT holders are part of the Lighter DAO and contribute to governance through community votes”, but this is an unverified marketing claim unless cross‑checked on-chain or via formal governance portal evidence.
• DAO status: real vs symbolic
• Independent commentary emphasizes that operational decisions remain with the core team, and token‑holder governance rights are planned to become effective “eventually, progressively, not on day one.”
• This indicates that any “DAO” is currently more symbolic than fully controlling, with the corporate operator retaining decisive power. ### Treasury / funds control
• User assets are custodied in Ethereum contracts backing the zk‑rollup, and protocol revenue is earned via LLP returns, liquidation fees, and deposit revenue.
• Actual treasury addresses, signer structure, and spending controls are Not verifiable as of 2026-08-29 without direct on‑chain inspection or formal disclosures. ### Voting concentration, timelocks, multisigs
• No independent source provides:
• LIT holder concentration, top holders or vote participation.
• Specific governance timelocks or multisig thresholds/signers.
• All such details remain Not verifiable as of 2026-08-29.

Lighter Perps is a decentralized perpetuals trading protocol; with Dune unavailable, all on-chain verification is replaced by “Not verifiable as of 2026-08-29.” 1. Entity, jurisdiction & legal structure Web-facing materials (site/app, basic info) do not clearly identify a legal entity, jurisdiction of incorporation, or team company behind Lighter Perps. As of 2026-08-29, this means: operating entity, domicile, and corporate structure are Not verifiable as of 2026-08-29. This materially increases counterparty and governance risk: enforcement, liability, and dispute resolution paths are unclear. 2. Terms of Service, user restrictions The trading front-end (app.lighter.xyz) exposes perpetual trading UI, but a detailed, easily accessible Terms of Service / User Agreement is not clearly surfaced in standard footer/header navigation. Without verifiable ToS text, the following remain Not verifiable as of 2026-08-29:

• Explicit restricted jurisdictions (e.g., US, EU, sanctioned countries).
• Age / professional investor requirements.
• Allocation of risk, liability, and dispute resolution forum. 3. KYC / AML The app behaves as a typical non-custodial DeFi derivatives protocol (wallet connect, on-chain trading), with no visible KYC onboarding flow on the public UI. Absence of KYC prompts suggests a non-KYC, non-custodial model, but this is not confirmed by legal documentation. All detailed KYC/AML policies are Not verifiable as of 2026-08-29. Regulatory risk: under many regimes, perpetuals with leverage accessible to retail without KYC may be treated as unlicensed derivatives or trading venue activity. 4. Product classification & regulatory perimeter Functionally, Lighter Perps offers perpetual futures-style derivatives settled in crypto, with leverage. Regulatory characterization (derivatives venue, swap execution facility, MTF/OTF, or gaming/CFD analog) will depend on jurisdiction, but:
• For US persons, this can fall into CFTC derivatives/“retail commodity transactions” perimeter.
• For EU/UK, it may be viewed as offering leveraged derivatives to retail without MiFID/MiFIR authorization. No licenses, registrations, or exemptions are verifiably disclosed; any claim of compliance would be an unverified marketing claim. 5. Warnings, enforcement, court cases, sanctions Search as of 2026-08-29 finds no public regulatory warnings, enforcement actions, court cases, or sanctions listings specifically naming “Lighter Perps” or “lighter.xyz” from major regulators or sanctions bodies. By the search-budget rule: where data is absent, status is Not verifiable as of 2026-08-29, not “no risk.” 6. Data protection & privacy No clear standalone privacy policy / data protection statement is surfaced and attributable to a legal entity. Thus:
• Data controller identity, GDPR/CCPA stance, and cookie/analytics practices are Not verifiable as of 2026-08-29. Risk takeaway (legal vs actual risk)
• Key structural data (entity, ToS, policies) are missing or not verifiable.
• Protocol exposes high-regulation products (perps, leverage) with non-KYC access. Institutional use should treat Lighter Perps as a high regulatory-uncertainty venue pending verifiable disclosure of entity, jurisdiction, ToS, and compliance posture.

I could not verify which stablecoin Lighter Perps uses from the available sources, so the depeg history is Not verifiable as of 2026-08-29. The search results only confirm that Lighter is a ZK rollup/perps venue and that it publishes trade-history data; they do not identify the settlement stablecoin or provide a reliable peg-history source for the protocol itself. If you mean the protocol’s quote/margin stablecoin, I need the exact token symbol or contract address to answer whether it depegged, how many times, the last event, and the size of the move. Without that, any answer would be a guess and would not meet a risk-analyst standard.

The top 5 risks for Lighter Perps are: 1. Oracle / price-feed manipulation — Lighter’s own terms say it may suspend users for “price manipulation or market interference,” and third-party reviews flag that zk-proofs verify execution but do not protect against bad price data entering the system. 2. Centralization / sequencer dependence — Independent coverage notes a trusted sequencer and upgrade/security-council setup that can bypass delay periods, creating governance and liveness risk if the operator is compromised or unavailable. 3. Liquidity and token-design reflexivity — Hindenrank highlights a circular dependency between staking the LIT token and liquidity provision, which can weaken market depth if the token falls or staking incentives fail. 4. Revenue fragility in adverse trader mix — Hindenrank also notes the model depends on a steady supply of losing traders; if skilled traders dominate, the liquidity pool can become the consistent loser and economics may deteriorate. 5. Operational / smart-contract and platform risk — Lighter’s terms explicitly warn users about hacking, blockchain attacks, uninsured losses, and “unanticipated risks,” while reviews note past outages and the possibility of technical failures despite withdrawal protections. Not verifiable as of 2026-08-29: on-chain TVL, chain-by-chain exposure, and current audit status were not independently verifiable in this run, so I have not used them in ranking the risks.

Lighter Perps’ top strengths are: (1) zk-rollup security and verifiability — all matching, liquidations, and state changes are proven cryptographically and verified on Ethereum; (2) high performance and scale — it is engineered for tens of thousands of orders/cancels per second with millisecond latency; (3) low-cost trading — retail users pay zero trading fees, with the protocol optimized for efficient matching and proving; (4) fairness and transparency — price-time priority and publicly predefined rules reduce censorship or favoritism; and (5) self-custody / Ethereum settlement — users deposit and withdraw through Ethereum, with final settlement and withdrawal rights anchored on L1 even if the system goes offline.