Jupiter Perpetual Exchange

Jupiter Perpetual Exchange is Jupiter’s Solana-native perpetuals product, accessible via jup.ag/perps and documented in Jupiter’s docs as a perpetual futures exchange built on Solana. It is a derivatives/perpetuals protocol, not a standalone L1; public docs describe trading SOL, ETH, and BTC/WBTC markets with up to 100x leverage and an LP-backed liquidity model using the JLP pool. Official site/docs: jup.ag and docs.jup.ag/user-docs/trade/perps. Category: Solana perpetual futures exchange / leveraged DEX. Launch date: Not verifiable as of 2026-08-29. The gathered web sources say it launched in late 2023, but I did not obtain an authoritative primary-source launch announcement in this run. Chains: Solana only in the gathered sources. Native token: Jupiter’s ecosystem token is JUP, but no source gathered here establishes a separate native token specifically for the perps venue; the product instead uses the JLP pool for liquidity/counterparty exposure. Main contract addresses: Not verifiable as of 2026-08-29. The available sources confirm the product and chain, but no contract-address evidence was gathered with the required cross-check standard, and Dune/on-chain verification is unavailable in this run. Explorer verification status: Not verifiable as of 2026-08-29. Fork lineage: The gathered sources do not show Jupiter Perps as a simple public fork of a named upstream perps protocol. Its public description emphasizes a LP-backed/request-fulfillment design on Solana with JLP as counterparty, not an orderbook clone. Audited changes vs. any upstream fork are therefore Not verifiable as of 2026-08-29. Malicious-modification history in similar forks: In general, similar DeFi forks have had hidden admin backdoors, fee changes, or upgrade-key abuses, but I did not gather a protocol-specific, source-backed comparison set for Jupiter Perps in this run, so this remains Not verifiable as of 2026-08-29.

Jupiter Perpetual Exchange appears to be a real, live product portal rather than a static landing page: official Jupiter developer docs describe a perpetuals product with leveraged trading, and the developer platform documents a dedicated Perps API and multiple product docs pages. The evidence also points to active app functionality for trading and programmatic integration, including market data, open/close transaction building, and wallet-signing flows via Jupiter’s API stack. I could not verify live deposit/withdrawal behavior directly from raw on-chain data in this run, so the exact state of deposits/withdrawals is Not verifiable as of 2026-08-29. The web evidence suggests the product supports collateral deposits and position management, but that is still an interface-level claim rather than an on-chain confirmation. Docs/UX look mature: Jupiter maintains current documentation hubs for user docs and developer docs, including perps-specific pages and API references, which is a strong sign of an operational product surface rather than a template site. I did not find strong evidence of broken links or obvious template/fake-metric behavior in the sources reviewed; however, that is also Not verifiable as of 2026-08-29. Open API: yes, Jupiter Perps exposes a documented API surface, but access appears tiered/credentialed for parts of the broader API ecosystem rather than fully public and unauthenticated.

Jupiter Perpetual Exchange on Solana has at least one dedicated smart‑contract audit by Offside Labs. The audit report is hosted in Jupiter’s developer docs under the audits section, which lists Jupiter Perpetuals alongside other Jupiter products. Date & duration

• Engagement ran February 20, 2024 – March 11, 2024. Scope
• Jupiter Perpetuals Solana on‑chain program: programs/perpetuals/src/**/*.rs, with test files and inline tests explicitly excluded.
• Jupiter Perpetuals Keeper: Keeper/src/**/*.ts.
• Branch: main; commit hash: 1647dfa818b4560614acdde1b7be6a9931d5671a. This scope indicates the audit covered the core perpetuals protocol logic and the off‑chain keeper service, but did not include any later commits or un-audited auxiliary components. Findings (severity counts)
• 1 critical issue.
• 1 high issue.
• 6 medium issues.
• 2 low issues.
• 6 informational issues. The PDF snippet does not enumerate each issue’s title or remediation status line‑by‑line, but the report is presented as a completed security audit rather than a preliminary review. Fix status per finding is therefore Not verifiable as of 2026‑08‑30 without reading the full PDF. Bytecode / deployed‑code coverage
• The report states it was performed against a specific Git commit on the main branch and lists the exact file paths audited. This is typical source‑level coverage, not an explicit bytecode‑match guarantee.
• There is no explicit statement in the accessible snippet that deployed Solana program IDs were matched to the audited commit (e.g., via build reproducibility or on‑chain verification). That mapping is therefore Not verifiable as of 2026‑08‑30. Cross‑checks / other firms
• Jupiter’s audits page lists Offside Labs, OtterSec, and Sec3 under “Jupiter Perpetuals”, implying multiple reviews. However, only the Offside Labs perpetuals PDF is clearly identified in the search results; the OtterSec and Sec3 entries for perpetuals are listed but their detailed reports were not surfaced in the snippets.
• For OtterSec and Sec3 perpetuals audits, all details (date, exact scope, severity breakdown, fix status, and deployed‑code coverage) are Not verifiable as of 2026‑08‑30 from the retrieved excerpts alone. Independent datasets
• At least one independent review site (Crypto Almanac Daily) currently records 0 audits linked for Jupiter Perpetual Exchange and notes no public audit report found in its dataset. This contradicts Jupiter’s own audits page and the Offside Labs report. > Contradiction box: Jupiter’s official docs show multiple perpetuals audits (Offside Labs, OtterSec, Sec3) with a published Offside Labs report, while an external dataset reports zero publicly linked audits for Jupiter Perps. The existence of the Offside Labs PDF on Jupiter’s developer site is direct evidence of at least one completed audit, so the external “0 audits” figure reflects an incomplete dataset rather than reality.

Yes. Jupiter states it runs a public bug bounty program covering both onchain programs/protocol infrastructure and web2 assets; the security docs point researchers to security.jup.ag for the live scope, reward tiers, and rules of engagement. Jupiter also announced the program publicly on 2025-08-09, saying it had opened a bug bounty in collaboration with Meteora. For Jupiter Perpetuals specifically, the best verified public evidence is the dedicated audit trail: Jupiter’s docs list audits for Jupiter Perpetuals by Offside Labs, OtterSec, and Sec3, and the Offside Labs report shows the audit started on 2024-02-20 and concluded on 2024-03-11, with 1 critical, 1 high, 6 medium, 2 low, and 6 informational findings. The public docs also indicate the perpetuals security page routes reporters to the bug bounty program, but the exact bounty scope, tiered payouts, and current eligibility rules are only published on the live program page, which was not directly accessible here. Results: a third-party bounty tracker reports 10 resolved reports and $36,100 total paid for Jupiter’s program, with a maximum bounty of $20,000 for critical issues; however, this is an aggregator summary, not a primary program record, so it should be treated as indicative rather than definitive. Not verifiable as of 2026-08-29: the precise current payout table, whether all Jupiter Perpetuals assets remain in scope today, and whether any bounty rewards were paid specifically for the perpetuals product.

Jupiter Perpetual Exchange on Solana is structurally exposed to several categories of dependency and counterparty risk, mostly via oracles, stablecoins, and ecosystem infrastructure. All on‑chain verification is Not verifiable as of 2026-08-29. 1. External protocol & oracle dependencies

• Jupiter Perps runs on Solana and integrates with Jupiter’s broader liquidity/infra stack; it relies on Solana’s consensus, runtime and scheduling – outage or liveness failures directly halt trading and liquidations.
• Price data: public docs and community material indicate reliance on Pyth and/or Switchboard oracles for perp mark prices and liquidation triggers; oracle manipulation (low-liquidity symbols, governance attacks, or publisher failures) can cause wrongful liquidations or under‑collateralization.
• If spot routes use external AMMs (e.g., Orca, Raydium) via Jupiter, extreme slippage or pool imbalance can distort index prices and funding, although the perpetual engine itself is separate. 2. Bridges, custodians, CEX/MM exposure
• Core trading and margining are on Solana; the protocol does not appear to custody user assets off‑chain, but users typically bridge capital from Ethereum or other L1s via Wormhole or similar bridges.
• Bridge failure or exploit affects users’ portfolio value and ability to fund margin, but not the solvency of positions already held on Solana.
• Market maker flow: Jupiter’s ecosystem routes institutional and MM volume, but perps risk is primarily smart‑contract/oracle; there is no evidence of centralized custodian control over user margin.
• CEX dependency is indirect (MM hedging on CEXs; listing of collateral tokens). Extreme CEX outages can widen spreads and increase funding volatility. 3. Stablecoin & LST/restaking exposure
• Collateral is primarily USDC on Solana, plus possibly SOL and other majors; USDC is an off‑chain fiat‑backed stablecoin issued by Circle, subject to bank/custody and regulatory risk.
• USDC depeg or issuer insolvency would impair collateral quality, cause forced deleveraging and possible bad debt if risk parameters are not updated quickly.
• No clear evidence of direct LST or restaking collateral use in current public materials; if enabled in future, this adds staking-slashed or rehypothecation risk. 4. Failure / depeg / insolvency scenarios
• Oracle failure/manipulation: extreme price spikes or freezes can cause mass liquidations or an inability to liquidate, leading to systemic bad debt.
• Solana outage or finality issues: trading and liquidations halt; if price moves sharply during downtime, positions can become unhedgeable and restart may crystallize losses.
• USDC or major collateral depeg: haircut of collateral vs USD notional; insolvency if the protocol’s risk engine assumes par value.
• Bridge exploits (Wormhole etc.): users’ cross‑chain portfolios harmed; trust shock and liquidity drain from Solana/Jupiter perps, but contract solvency remains on-chain. Key gaps: specific oracle configuration, collateral whitelist, and MM arrangements are Not verifiable as of 2026-08-29 and must be confirmed with direct technical docs/audits before institutional exposure.

Jupiter Perpetual Exchange is organized as a non-custodial system at the trader level: users connect their own wallet, and positions execute directly against the protocol rather than through a centralized intermediary. On the protocol side, assets are held in the JLP pool, which uses separate on-chain custody accounts for each supported token; the custody account’s associated token account holds the tokens under management for the pool. This means custody is effectively split by asset, with each token (for example SOL, ETH, BTC, USDC, USDT, and, in later documentation, JupUSD) tracked in its own custody account rather than in a single omnibus wallet. For trading, the pool acts as the counterparty to every perp trade, and collateral is recorded in the relevant custody account for the position’s long or short side.

Since launch, I found no verified report of a successful protocol-level exploit causing loss of user funds for Jupiter Perpetual Exchange; the most concrete public issue was a March 2024 disruption in perpetual trading caused by oracle congestion / price-feed infrastructure stress during Bitcoin volatility, with Jupiter saying funds were safe and Coindesk reporting affected trading activity. A separate 2025 incident involved Jupiter’s X account being compromised, which is an account-security incident rather than a protocol exploit.

Jupiter has a public bug bounty program; its security page says researchers should report vulnerabilities affecting onchain programs, APIs, or web infrastructure through the program, and rewards are reserved for issues that materially threaten user funds, solvency, governance integrity, or user data. The official audits page also lists independent audits for Jupiter Perpetuals by Offside Labs and OtterSec, and a Sec3 audit report exists for the perpetuals codebase.

Key management / custody details for the perpetual exchange itself were not verifiable from the gathered sources. The protocol docs confirm audits and a bug bounty, but do not provide a sufficiently specific, independently verified description of admin key custody, multisig signers, or operational key-rotation controls here.

Jupiter Perpetual Exchange appears to organize key management around a hybrid operational model rather than a fully user-custodied one. The public docs say each trade requires two onchain transactions: the trader submits a request on Solana, and a keeper—an automated offchain service run by Jupiter—detects, validates, and executes it, which means the protocol’s operational signing/automation is at least partly centralized in Jupiter-run infrastructure. For liquidity and risk, the exchange uses the JLP pool as the shared counterparty for trades, with liquidity providers and the pool handling the economic exposure rather than a traditional order book. That implies the most important control points are the program authorities, keeper keys, and pool administration, but the exact signing setup for upgrade authority, multisig thresholds, or custody roles is Not verifiable as of 2026-08-29 from the provided sources. Separately, Jupiter’s broader governance material indicates the ecosystem has used multisig-controlled wallets for token distribution and treasury-related functions, but the provided results do not confirm that the perp product itself is governed by the same key structure. So, the defensible conclusion is: trade execution is keeper-driven, liquidity is pooled in JLP, and detailed protocol key custody/upgrade governance for perps is not publicly verifiable from these sources.

Jupiter Perpetual Exchange is a Solana-based perpetuals product built within the broader Jupiter ecosystem; contracts are Solana programs, not EVM proxies, so many EVM-style admin/proxy patterns do not apply directly. Because Dune MCP and direct on‑chain tools are unavailable, all on-chain verification is: Not verifiable as of 2026‑08‑29. ### 1. Contract / program identification

• Public docs and Jupiter ecosystem pages describe “Jupiter Perpetuals” as a product integrated in the main Jupiter app, but do not clearly expose program IDs or a full contract map for Perpetual Exchange.
• No independent explorer pages or audits specifically listing Jupiter Perpetual Exchange program addresses were found. Result: Exact program addresses, their deployment status, and verification on Solana explorers are Not verifiable as of 2026‑08‑29. ### 2. Upgradeability & admin roles
• Solana programs are typically either upgradeable via a program upgrade authority or made immutable by setting the authority to None. This is a general Solana pattern, not protocol‑specific.
• For Jupiter Perpetual Exchange, there is no publicly documented breakdown of:
• who controls the program upgrade authority
• existence of any multisig or timelock for upgrades
• specific admin/owner/emergency roles for the perps engine (pause, fee changes, oracle config, risk parameters). Result:
• Upgradeability, proxy architecture, and concrete admin role assignments are Not verifiable as of 2026‑08‑29.
• Whether any roles have been *renounced* on-chain or are gated by timelocks is Not verifiable as of 2026‑08‑29. ### 3. Controls: pause, withdrawal, oracle, fees
• No independent audit report or technical documentation was found detailing:
• pause or circuit‑breaker mechanisms,
• withdrawal controls or kill‑switches,
• oracle configuration rights,
• fee/taker/maker parameter controls,
• strategy/hedging contract hooks. Result: Presence and scope of these functions and who can invoke them remain Not verifiable as of 2026‑08‑29. ### 4. User exit & key‑compromise scenarios Given the missing on-chain visibility:
• Whether users can always close positions and withdraw without cooperation from an admin (e.g., even if admin keys are lost) is Not verifiable as of 2026‑08‑29.
• Worst‑case if upgrade or admin keys are compromised cannot be quantified, but in generic Solana perps architectures, compromise of upgrade authority or risk‑parameter admin can imply:
• forced parameter changes (fees, funding, margins),
• oracle manipulation or position liquidations,
• potential freezing or draining of collateral, depending on implementation. ### 5. Architecture map / diagram
• No independent, protocol‑level architecture diagram for Jupiter Perpetual Exchange (separate from the broader Jupiter swap/DEX stack) was found. Result: A reliable architecture map and diagram are Not verifiable as of 2026‑08‑29. From a risk perspective, the main finding is opacity of smart‑contract and admin architecture for this specific perps product in public, independent sources.

Jupiter Perpetual Exchange (“Jupiter Perps”) is not a separate project but part of the broader Jupiter Exchange / jup.ag “DeFi superapp” on Solana, so founder/team analysis is at the protocol level, with Perps as a product line. Founders & key individuals

• Public information consistently identifies “Meow” (pseudonymous) as the primary founder of Jupiter.
• Multiple profiles and reviews describe co‑founders Meow and Siong Ong (sometimes Meow and Ben Chow; naming is inconsistent across sources).
• A detailed overview notes Jupiter was founded in 2021 as a Solana DEX liquidity aggregator, later expanded to perps, lending, and other products.
• Meow’s prior work includes Mercurial Finance and involvement in other crypto projects; Mercurial rebranded to Meteora after earlier design issues and community controversy (restructurings, not a catastrophic exploit). Team: public vs. anonymous, size, credibility
• The founder is pseudonymous, but the broader team is partly doxxed through professional profiles and M&A disclosures (e.g., acquisition of SolanaFM, whose founders and executives are fully public).
• An independent audit-style report notes Jupiter maintains a verified corporate profile on a major professional network with roughly 50–200 employees, indicating a real organizational footprint beyond a hobby project.
• A subsequent strategy update cites ~80 team members spanning Jupiter Research Center, jup.ag, and mobile products, implying continued scaling of a multi‑discipline team.
• Jupiter runs large public channels (X/Twitter, Discord, support hub) with high activity and external partners integrating Jupiter Perps (e.g., mobile front ends), which is consistent with a live, staffed organization. Jurisdiction, office, onshore/offshore
• Public materials emphasize the protocol and DAO, not a specific registered corporate entity or jurisdiction; no clearly verifiable HQ address or legal domicile for “Jupiter Exchange” was identified in independent sources. Not verifiable as of 2026‑08‑30.
• Some leadership and acquired teams (e.g., SolanaFM) have been based in Singapore, but this does not equal a confirmed Jupiter legal domicile. Reality check vs. “just a web front”
• Indicators of a real operating business:
• Multi‑year history (since 2021) with major share of Solana trading volume and expansion into perps and other products.
• Acquisition of SolanaFM, including staff absorption and product integration.
• Large user base and integrations with external apps using Jupiter Perps infra.
• Risks from a governance/credibility perspective:
• Founder pseudonymity and incomplete public corporate footprint.
• High insider allocation (~40% of JUP) relative to conservative norms, with vesting extending several years, concentrated governance and economic power. Overall, Jupiter Perpetual Exchange sits within a relatively mature, heavily‑used Solana protocol with a sizable partially-doxxed team and real M&A/integration activity, but with pseudonymous top leadership and unclear formal jurisdiction, which are material risk flags for institutional capital.

Jupiter Perpetual Exchange (Jupiter Perps) currently has a mixed but generally positive technical/market reputation, with some serious governance and token-distribution controversies around the broader Jupiter ecosystem that institutional risk teams should treat as non‑trivial. ### Protocol & team/investors

• Jupiter Perps is the perpetuals product inside Jupiter, Solana’s leading DEX aggregator, operated by the same team that launched Jupiter in 2021.
• Multiple independent guides and exchange reviews describe Jupiter as a major "DeFi superapp" on Solana with high perps volume and large user adoption, indicating strong market traction rather than a fringe project.
• A detailed investor research note from Decentral Park Capital covers the perps launch and early volume, suggesting meaningful institutional interest and diligence.
• Specific founder identities (e.g., “Meow”) and internal funding arrangements are covered in DeFi media, including DLNews, which reports community pushback on a DAO plan to allocate ~$140m in JUP tokens to the team. ### Audits, security track record, insolvency/rug/fraud claims
• Public web sources do not prominently surface a dedicated, named smart‑contract audit for Jupiter Perps from major firms (e.g., OtterSec, Halborn, Trail of Bits). Not verifiable as of 2026‑08‑29.
• No credible reports of protocol insolvency, loss of LP funds, or confirmed smart‑contract exploits specific to Jupiter Perps appear in major analytics or media coverage. Not verifiable as of 2026‑08‑29.
• There are strong public accusations around the JUP token launch and allocation: crypto commentator Adam Cochran alleged that the Jupiter team "rug‑pulled" JUP via a large team allocation, liquidity withdrawal, and day‑one cash‑out of around $30m while retaining ~50% ownership. These are allegations, not adjudicated findings, but they materially affect reputational risk. ### Governance, sentiment, and criticisms
• Coverage of Jupiter’s DAO and tokenomics shows community and investor unease over large token allocations and compensation for the team (e.g., the $140m plan for salaries/bonuses), indicating governance‑process and alignment concerns rather than protocol‑level fraud.
• Educational and review pieces from independent publishers (CoinGecko Learn, CoinBureau, Eco, exchange reviews) generally present Jupiter Perps as a legitimate, high‑volume Solana perps venue, emphasizing functionality and risk management mechanics rather than warning of scams. ### Legal/regulatory & sanctions
• No records of regulatory actions, formal investigations, or sanctions against Jupiter Perpetual Exchange or its team were identified in accessible public sources. Not verifiable as of 2026‑08‑29. ### Unresolved concerns for institutional risk
• Audit visibility: lack of clearly cited third‑party audits for perps contracts.
• Token‑launch controversies & large insider allocations (JUP) and DAO compensation disputes.
• Model risk of an LP‑to‑trader perps design with high leverage, which can create extreme stress scenarios for the JLP pool (referenced across guides and reviews). Taken together, Jupiter Perps looks technically mature and widely used, but the ecosystem’s governance and token‑distribution controversies should be treated as ongoing reputational and alignment risks for institutional capital.

Jupiter Perpetual Exchange on Solana is a perps DEX whose economics are built around trader PnL vs. a liquidity provider (LP) pool, funding payments, and protocol fees; it does not behave like a traditional yield farm. Core strategy & assets in/out

• Users deposit collateral (e.g., USDC) to trade perpetual futures with leverage; LPs supply liquidity to a shared pool that acts as counterparty/AMM for perps.
• Traders’ profits are paid from the pool; traders’ losses and funding payments accrue to LPs as yield. Yield source & nature
• Yield to LPs comes from:
• Trading fees (maker/taker fees on perps).
• Funding rate differentials between longs and shorts.
• Net trader PnL (if traders are net losers, LPs gain; if traders win, LP yield falls or turns negative).
• This is organic, risk-based PnL, not emissions; no evidence of large token subsidies as a primary yield component. Risk profile: market-neutral vs directional
• LPs are directionally exposed to aggregated trader positions and volatility; the pool is not fully market-neutral.
• Traders can use leverage; LPs thus face amplified PnL swings and potential drawdowns.
• No restaking or external DeFi looping evident; exposure is primarily to perps positions on Solana. Lock-ups, withdrawals, mechanics
• LPs deposit/withdraw from the pool; withdrawals may be subject to cooldown/queue and slippage depending on open interest and pool utilization.
• Specific lockup or queue rules vary by pool and are configured at the product level. Fees, gates, and limits
• Fees include:
• Trading fees (per trade, tiered by role/volume).
• Funding payments continuously exchanged between longs and shorts.
• Protocol fee cut from trading fees that goes to Jupiter’s treasury/DAO rather than LPs.
• Risk controls: per-market open interest caps, max leverage limits, and maintenance margin requirements to protect the pool. Protocol revenue
• Protocol revenue = share of trading fees + possibly part of funding spread, routed to the protocol treasury/DAO; LPs receive the remainder. Collateral, TVL, APY
• Primary collateral appears to be stablecoins (USDC); some markets may support other assets as margin.
• TVL, by product/chain, and APY history are Not verifiable as of 2026-08-29 due to lack of on-chain querying and incomplete third-party coverage. APY sustainability
• LP returns are highly volatile, driven by trader flow and market regimes; in risk-off or highly profitable-trader periods, yields can compress or turn negative.

Jupiter Perpetual Exchange’s reserve picture is not fully verifiable from the gathered non-on-chain sources. The protocol’s perp liquidity is provided by the JLP pool, which holds SOL, ETH, BTC, USDC, and USDT, but the size of that pool’s reserves, the controlling addresses, and any custody breakdown are not verifiable as of 2026-08-29 from the available evidence. The main treasury-related claim in the search results is that Jupiter’s DAO treasury was reported to hold 10M USDC and 100M JUP, but this comes from a secondary ecosystem page rather than a primary governance or audited reserve report, so it should be treated as unverified until independently confirmed. Another source says Jupiter’s community treasury was to remain untouched until governance resumes and that the Litterbox Trust would remain inaccessible until 2027, with jupSOL revenues continuing to accrue to the DAO treasury; however, this is still off-chain reporting and does not establish on-chain balances or custody control. For reserve policy, the clearest documented mechanism is that 50% of Jupiter’s onchain revenue is routed to the Litterbox Trust to buy JUP and lock it for three years, while the remaining revenue funds operations and treasury reserves. The trust wallet is publicly trackable in principle, but its actual balance, composition, and control structure were not verifiable in this run. In short: on-chain balances, reserve composition by address, and custody attestations for Jupiter Perps are Not verifiable as of 2026-08-29. The only reasonably supported conclusion is that the protocol’s operating reserves are tied to the JLP pool and to the DAO/Litterbox treasury framework, but exact amounts and control cannot be confirmed from the collected sources.

Not verifiable as of 2026-08-29. I could not independently verify Jupiter Perpetual Exchange’s native tokenomics, supply, allocations, unlocks, holder concentration, admin controls, or DEX liquidity for this run because on-chain verification is unavailable and I was instructed not to infer missing values. Based on the protocol slug/site alone, the protocol appears to be associated with the Jupiter ecosystem on Solana, but whether Jupiter Perpetual Exchange has a distinct native token versus using JUP/SOL as ecosystem assets is not verifiable here. Because web-only evidence was not sufficient under the required source hierarchy, I cannot responsibly state:

• native token name/ticker or mint address
• total vs circulating supply
• market cap or FDV
• utility, governance, revenue share, buybacks, burns, or staking rewards
• emissions or unlock schedule, or whether announced unlocks occurred on-chain
• allocations to team/investors/treasury/community
• top-holder concentration, insider wallets, or admin-controlled mint/blacklist/fee-switch powers
• main DEX listings or liquidity depth If you want, I can do a web-only follow-up pass and return a stricter “verified vs unverified” memo limited to explorer, governance, audit, and media sources, but the on-chain items above would still remain Not verifiable as of 2026-08-29 in this run.

A Bitcoin drop below $10,000 would be a severe stress event for Jupiter Perpetual Exchange because BTC is one of its supported perp markets and large BTC moves can disrupt pricing and trading flow on the platform. However, the exact impact on Jupiter’s collateral pools, liquidation cascade, revenue, or solvency is Not verifiable as of 2026-08-29 from the available sources. What can be said with confidence is limited to mechanism, not quantified outcomes: Jupiter Perps lets users trade SOL, ETH, and BTC with leverage up to 100x against a shared liquidity pool, and positions settle against that pool rather than an order book. That structure means an extreme BTC crash would likely increase liquidation pressure, widen spreads/slippage risk, and raise the chance of trading interruptions or oracle-related stress, especially if market volatility overwhelms infrastructure. A relevant historical precedent is that Jupiter previously experienced trading issues during violent Bitcoin price action, with reports that disruptions were tied to infrastructure/oracle problems and that some users reported losses before operations resumed. That does not prove the same failure mode would recur at $10,000, but it shows the protocol has been stressed by sharp BTC moves before. For a true protocol-risk assessment, the missing pieces are: current BTC open interest, JLP asset composition, insurance/backstop size, liquidation thresholds, and Solana-chain exposure. Those are Not verifiable as of 2026-08-29 from the available sources.

For Jupiter Perps, a 20% depeg in the largest collateral asset is a severe stress event because trader collateral can be deposited in USDC, USDT, SOL, ETH, or wBTC, and liquidation is triggered when collateral is no longer sufficient to cover losses and fees. The protocol docs do not provide a chain-level breakdown of collateral composition or reserve buffers, so the effect of a 20% depeg on the pool and user liquidations is Not verifiable as of 2026-08-29. What can be stated from the docs is operational: liquidations happen automatically at the oracle liquidation price, and all remaining collateral is forfeited to JLP as a liquidation fee. That means a sharp collateral depeg would most likely first hit traders holding the depegged asset as collateral, while also changing liquidation thresholds across open positions that use that asset. The main risk question is the protocol’s exposure to that asset versus its ability to absorb liquidations and settlement losses, but the provided sources do not quantify either exposure or the current JLP asset mix.

For Jupiter Perpetual Exchange on Solana, a “top counterparty insolvent” scenario primarily manifests as trader default / position collapse, not a CeFi-style bilateral counterparty failure. On-chain specifics are Not verifiable as of 2026-08-30. ### 1. Stress trigger & loss path

• Trigger: Largest trader or side of open interest becomes economically insolvent (extreme adverse move, funding costs, oracles gap), such that their margin cannot cover losses.
• Immediate loss path:
• Position value < maintenance margin → position enters liquidation state.
• Liquidators (keepers / bots) use Jupiter’s perp contracts to close the position against the AMM/orderbook, using oracle prices.
• If price gaps or oracle failure cause underwater liquidation (closing worse than collateral), the protocol has bad debt. ### 2. Who absorbs the loss?
• First layer – trader’s own margin: Losses are applied to the insolvent trader’s collateral; they lose full margin and open PnL.
• Second layer – LPs / liquidity providers: If closing the position leaves a hole, it is typically borne by the liquidity pool that was the counterparty (AMM LPs providing base/quote or vAMM liquidity).
• Third layer – insurance / risk funds (if any): If Jupiter Perps has an insurance or risk fund, protocol-level bad debt is socialized there until exhausted.
• Residual socialization: In the absence of sufficient insurance, remaining shortfall is implicitly socialized to all LPs (lower pool value, worse future pricing) and possibly to traders via spread/funding adjustments. ### 3. Compensation mechanisms
• Incentives to liquidators: Liquidation fees or discounts compensate liquidators for resolving insolvent positions and help reduce bad debt.
• LP revenue vs. risk: LPs receive trading fees and funding income as compensation for bearing tail risk of counterparty insolvency.
• No guaranteed user compensation: There is typically no make‑whole for traders whose counterparties fail; instead, solvency is enforced via margin and liquidation. ### 4. Smart contract impact path
• Margin & position accounting contracts: Update balances, mark positions as liquidated, transfer collateral to the protocol / liquidators.
• AMM / liquidity pool contracts: Execute the closing trades; pool balances shift, NAV of LP tokens drops if bad debt occurs.
• Oracle integration contracts: Feed prices; if they fail or are manipulated, insolvency and bad debt can be magnified.
• Governance / admin contracts: May pause markets, adjust risk parameters, or recapitalize insurance funds after the event. Because Dune MCP is unavailable, precise on-chain mechanics, parameterization and existence/size of insurance funds for Jupiter Perpetual Exchange are Not verifiable as of 2026-08-30.

For a stress scenario involving committed fraud by the DAO or owners, I found no verifiable evidence that Jupiter Perpetual Exchange’s DAO, owners, or core team were formally accused, charged, or found guilty of fraud in the provided sources. The strongest available evidence is instead about governance centralization and trust concerns: Jupiter paused DAO voting after backlash over the team’s voting power and a “breakdown in trust,” but that is not the same as fraud. What can be said with confidence is that there are user-reported scam and phishing incidents associated with Jupiter’s brand, including fake apps and a Reddit complaint, but these are third-party frauds, not proof of fraud by Jupiter DAO or its owners. One source also alleges past team “fraud history” and cancellation of promised airdrop-related behavior, but it is an X post and not independently corroborated enough to treat as verified fraud. So, the risk assessment for this stress scenario is:

• Fraud by DAO/owners: Not verifiable as of 2026-08-29.
• Governance abuse / centralization: Verifiable concern, based on multiple reports of team voting power and paused governance.
• User scam/phishing exposure under the brand: Verifiable, but attributable to external attackers rather than the protocol itself. If you need, I can also convert this into a terse institutional risk rating with severity, likelihood, and monitoring flags.

Jupiter Perpetual Exchange’s primary yield source is JLP fee participation: Jupiter’s docs say the JLP pool earns 75% of all trading fees from the perp exchange, and support material describes this as real yield that auto-compounds into the JLP token price. Under a negative 30-day stress scenario, that primary yield source can be negative only if fee income over the period is overwhelmed by pool losses from trader PnL / directional bleed; the support material explicitly notes that JLP is exposed to price risk and can fall in a sharp SOL drawdown, even though fee accrual can offset part of that damage. The protocol docs do not provide a 30-day negative-yield metric, so the stress outcome is Not verifiable as of 2026-08-29 from the available sources.

Jupiter Perpetual Exchange governance is only partially transparent from public sources; key aspects (exact contract admins, multisig configs, and on‑chain voting data) are Not verifiable as of 2026-08-29 due to lack of direct on‑chain tooling in this run. Jupiter is a broader Solana DeFi project (mainly a DEX/aggregator) that has launched a perpetual futures product as part of its ecosystem. Governance is centered around the JUP token and the “J.U.P.” governance framework, but this framework is still maturing. Who controls what (high level)

• Protocol/dev direction: Jupiter Labs (the core team) plus JUP governance.
• Contracts (likely): Perp contracts on Solana are deployed and upgradable by the core team / designated authorities; exact upgrade authority and any program‑upgrade multisig are Not verifiable as of 2026-08-29.
• Frontend: The jup.ag domain and UI are operated by Jupiter’s core entity; there is no indication of a community‑controlled frontend.
• Funds/treasury: A JUP ecosystem fund/treasury is described in token launch and governance posts, but the precise legal entity and accounts are not fully disclosed in independent sources. Governance structure (JUP / J.U.P.)
• Jupiter introduced the J.U.P. governance model (Jupiter United Planet) in early 2024, describing a staged, community‑driven governance process for JUP.
• JUP holders can participate in proposals and votes on Jupiter‑related matters; however, the extent to which these currently control the perpetual exchange parameters or upgrades is not clearly documented in independent sources.
• Several governance proposals (e.g., emissions, ecosystem allocations) have been run via off‑chain or hybrid voting (Snapshot‑like systems), but precise details of perp‑specific proposals are Not verifiable as of 2026-08-29. DAO vs company control
• Governance appears hybrid: community JUP voting plus strong continuing control by the core team.
• Independent sources do not clearly identify a specific registered company (jurisdiction, registration number, directors) operating Jupiter or the perp exchange; likely an offshore development entity, but this is Not verifiable as of 2026-08-29. Timelocks, multisigs, voting concentration
• No independent, detailed disclosure of:
• Program upgrade timelocks.
• Multisig addresses, signers, thresholds, or their independence.
• On‑chain voting concentration / top JUP holders. All of the above are therefore Not verifiable as of 2026-08-29 from independent analytics, explorers, or governance records.

Jupiter Perpetual Exchange appears to be operated through Jupiter’s Interface terms rather than a clearly identified separate regulated exchange entity, and the Interface terms state it is deemed based solely in Panama with Panama law and Panama City ICC arbitration for disputes. The terms also say Jupiter may perform KYC/AML checks at its sole discretion and may refuse access if money laundering, terrorism financing, sanctions, or other illegal activity is suspected. Restrictions / sanctions: the terms state the Interface does not interact with wallets located in, established in, or resident in the United States, China, Singapore, Myanmar, Côte d’Ivoire, Cuba, Crimea/Sevastopol, DRC, Iran, Iraq, Libya, Mali, Nicaragua, North Korea, Somalia, Sudan, Syria, Yemen, Zimbabwe, or other sanctioned jurisdictions. That is a strong contractual geo-sanctions restriction, but it is not the same as a government licence or regulatory authorization. KYC/AML: the interface reserves the right to request information and documents for KYC/AML and to deny access if those checks are not satisfied. However, the materials available here do not show mandatory universal onboarding KYC for all users; that remains Not verifiable as of 2026-08-29 beyond the discretionary-check language. Consumer-risk warnings: Jupiter’s perps docs explicitly warn that perpetual trading involves significant risk of loss and that leveraged positions can be liquidated if collateral falls below maintenance margin. Privacy / data protection: Jupiter’s privacy policy says it applies to Interface activities, gives a contact email for privacy requests, and describes collection/use of user-provided data for support and interface interactions. A third-party review page claims no personal data is sold and that anonymized/aggregated data may be shared, but that source is weaker than Jupiter’s own policy and should be treated cautiously. Enforcement / court cases / sanctions: no specific court case, regulator action, or sanctions designation for Jupiter Perpetual Exchange was identified in the gathered sources, so those items are Not verifiable as of 2026-08-29.

Not verifiable as of 2026-08-29. The search results confirm that Jupiter Perps used a basket including USDC and USDT in its liquidity pool, and later introduced JupUSD as a native stablecoin, but they do not provide a reliable incident history showing whether a stablecoin used by the protocol ever depegged, how many times it happened, the last occurrence, or the depeg percentage. Those specifics require on-chain verification or a dedicated incident record, which is unavailable here.

Top 5 protocol risks for Jupiter Perpetual Exchange are: 1) JLP counterparty risk — JLP liquidity providers are the counterparty to all perp traders, so trending markets can produce significant directional losses for the pool. 2) High leverage / liquidation risk — leverage up to 250x can trigger rapid liquidations and, in extreme volatility, bad debt for the JLP pool. 3) Oracle dependency risk — the protocol relies heavily on Pyth price feeds, so oracle failures or staleness could lead to unfair liquidations or exploitation. 4) Solana liveness/congestion risk — if Solana is congested or degraded, trades and liquidations can fail or delay, worsening losses. 5) Scale / complexity risk — Jupiter’s expanding product surface increases attack and operational complexity, raising the chance that one issue propagates across the broader app. The first four are directly identified in the Jupiter Perpetual Exchange risk report; the fifth is a broader Jupiter ecosystem risk that also affects the perp product through shared platform complexity.

Jupiter Perpetual Exchange’s top strengths are: high leverage and broad perps functionality — it supports up to 100x leverage and includes trading controls like limit orders and take-profit/stop-loss; liquidity-backed execution — the LP-based JLP model is designed to provide deep liquidity and stable execution rather than a traditional order-book market; oracle-based pricing — it uses Dove Oracle with Pyth as fallback, which helps anchor pricing and execution reliability; simple, low-friction trading — its perps product is presented as low-fee compared with many alternatives, with a 0.06% open/close fee on position size; and ecosystem strength — Jupiter is widely described as Solana’s leading DeFi trading interface, which can improve user flow, liquidity access, and network effects.