{"id":"perpx","title":"PerpX","content":"## Introduction\n\nPerpX is a decentralized derivatives exchange that aims to provide perpetual futures trading through a hybrid model that pairs off-chain order execution with on-chain settlement. The project emphasizes self-custody, auditable settlement, and AI-assisted risk insights, with [Arbitrum](https://iq.wiki/wiki/arbitrum) identified as its primary settlement layer and the PRPX token used for incentives and governance functions [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Overview\n\nPerpX positions itself as a non-custodial perpetuals venue designed to combine centralized-exchange-like performance with deterministic, auditable on-chain state. The system routes high-frequency tasks such as matching and validation to an off-chain engine, while submitting final state transitions (settlement, position accounting, liquidations) to smart contracts. This approach aims to reduce latency and enable advanced order handling without relinquishing the security and transparency of on-chain settlement [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\nThe project’s documentation specifies [Arbitrum](https://iq.wiki/wiki/arbitrum) as the primary settlement chain. Order intents are signed and processed off-chain, with completed executions batched for on-chain settlement to provide a verifiable record of positions and events. PerpX further describes a risk and analytics layer intended to supply users with real-time signals, such as liquidation proximity and volatility shifts, in order to aid risk management and strategy selection [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\nPerpX’s public materials claim audited smart contracts, MEV-aware execution design, and compatibility with self-custodial wallets, including cold-storage practices. At the same time, several disclosures commonly expected for a derivatives protocol—such as founder identities, token supply and allocations, and downloadable audit reports—were not available in the reviewed public pages and documentation and therefore remain unverified in these sources [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Products\n\n### Perpetual DEX (Trading Platform)\n\nThe core product is a perpetual futures trading platform that connects directly to users’ [Web3](https://iq.wiki/wiki/web3) wallets. Order creation and matching occur off-chain to target low latency, while settlement and position updates occur on-chain to preserve self-custody and transparency. The trading interface presents standard derivatives controls and asset markets, with a stated focus on delivering CEX-like execution characteristics within a non-custodial framework [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Staking Module\n\nPerpX describes a performance-based staking system that accepts [USDC](https://iq.wiki/wiki/usdc) stakes and LP tokens under distinct rules. Rewards are determined using net PnL accounting with high-water mark logic, and the module offers lockup options that adjust performance fee tiers. The platform frames staking as a component of the wider incentives layer, interacting with liquidity and trading activity across the exchange [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Multi-Chain Swap and Messaging\n\nThe documentation outlines cross-chain capital mobility through a swap and messaging integration, with [deBridge](https://iq.wiki/wiki/debridge) identified as the primary partner. This module is intended to enable near-instant movement of collateral from multiple L1s/L2s into PerpX’s settlement environment on [Arbitrum](https://iq.wiki/wiki/arbitrum). The design is presented as extensible to other messaging layers, while [deBridge](https://iq.wiki/wiki/debridge) is cited as supporting transfers across a broad set of networks [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Risk and AI Intelligence Layer\n\nPerpX materials describe an intelligence layer that provides real-time telemetry and AI-driven insights to traders and liquidity providers. Indicative signals include liquidation risk probabilities, funding and skew indicators, and alerts about volatility or liquidity regime changes. The aim is to supplement execution with analytical tools that help participants monitor exposures and adjust strategies as market conditions evolve [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Liquidity Management\n\nThe protocol references a MUX V3-style liquidity model for utilization-driven funding and borrowing costs, with borrowing fees accruing continuously and settling hourly within defined bounds. The roadmap includes a progression toward native LP pools designed to capture trading fees, funding revenue, and incentive distributions, coupled with risk controls such as position caps and adaptive spreads for skew management [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Features\n\nPerpX’s stated features center on a hybrid execution architecture, non-custodial access, and risk-aware design. The platform asserts that orders are signed and matched off-chain to minimize latency and MEV exposure, and that only final settlement updates are posted on-chain to ensure state verifiability. [Arbitrum](https://iq.wiki/wiki/arbitrum) is identified as the settlement layer where deterministic rules govern margin updates, funding payments, and liquidations. The exchange interface supports common derivatives order types, including market, limit, stop/trigger, and close-only orders, and is paired with a real-time analytics layer that aims to highlight funding pressure, liquidation proximity, and volatility regime shifts [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\nThe documentation describes a multi-asset collateral framework and both cross-margin and isolated-margin modes to reduce rebalancing friction and accommodate diverse risk preferences. A multi-source oracle design with deviation checks, fallbacks, and time-weighting is presented to support price integrity for settlement and risk calculations. The project also cites encryption and private routing approaches for data and orderflow, and lists a fee schedule that includes a flat 0.30% trading fee applied to both maker and taker orders in the materials reviewed [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Ecosystem\n\nPerpX’s ecosystem is organized around its trading infrastructure, the PRPX token, staking and reward mechanisms, liquidity provisioning strategies, and cross-chain interoperability. Execution and validation functions reside off-chain, while settlement and final state changes occur on [Arbitrum](https://iq.wiki/wiki/arbitrum). On the interoperability side, [deBridge](https://iq.wiki/wiki/debridge) is presented as the primary integration for moving assets across multiple chains into the settlement environment. Liquidity and funding follow a utilization-based model, with a stated pathway toward native LP pools and governance involvement in configuring listings, fees, and risk parameters over time [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\nThe documentation frames PRPX as the token connecting incentives, governance, and participation in staking and LP programs. It emphasizes plans for progressive decentralization and delegated voting while noting that critical system behaviors—such as custody, core matching engine behavior, and settlement sequencing—are intended to remain outside governance scope. Additional community and operator roles (for example, liquidators and oracle providers) are implied by the architecture, although the public sources reviewed do not list named counterparties or detailed role specifications beyond the general model [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Use Cases\n\n* Non-custodial perpetual futures trading with on-chain settlement\n* Hedging of spot or portfolio exposures using perpetual contracts\n* Liquidity provisioning strategies earning fees, funding, and potential incentives\n* Cross-chain movement of collateral into [Arbitrum](https://iq.wiki/wiki/arbitrum) via integrated bridging\n* AI-driven risk monitoring for traders and LPs\n\nThese use cases reflect the protocol’s focus on hybrid execution, composable liquidity, and risk-aware tooling for derivatives market participants [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Architecture\n\n### Hybrid Execution Engine\n\nPerpX describes a system in which order intents are signed locally and submitted to an off-chain engine responsible for matching, risk evaluation, and validation. This design aims to minimize exposure to MEV by avoiding public mempool broadcasts and to deliver lower latency through private routing and off-chain computation. After execution, the engine emits settlement updates that are pushed on-chain, providing an auditable record under deterministic rules [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Settlement Layer on Arbitrum\n\n[Arbitrum](https://iq.wiki/wiki/arbitrum) is specified as the primary on-chain settlement environment. Smart contracts on this chain govern position updates, margining, funding payments, and liquidations. The protocol’s stated objective is to preserve CEX-like execution characteristics while ensuring “deterministic, auditable settlement and liquidations” through on-chain enforcement of risk parameters and final state transitions [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Cross-Chain and Bridging Layer\n\nThe documentation indicates that PerpX integrates with [deBridge](https://iq.wiki/wiki/debridge) as its primary cross-chain swap and messaging infrastructure. This enables movement of collateral from various L1s and L2s into the [Arbitrum](https://iq.wiki/wiki/arbitrum) settlement domain, with [deBridge](https://iq.wiki/wiki/debridge) support described as spanning more than 24 networks. The architecture is presented as modular and compatible with additional messaging layers such as [LayerZero](https://iq.wiki/wiki/layerzero) and [Wormhole](https://iq.wiki/wiki/wormhole) if incorporated in the future [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Liquidity, Funding, and Margin Mechanics\n\nPerpX references a MUX V3-style funding model with utilization-based borrowing costs. Borrowing fees accrue continuously and settle on an hourly cadence, and the platform outlines a roadmap for native LP pools to capture trading fees, funding revenue, and incentives. Margining is described as supporting both cross- and isolated-margin modes, and the protocol’s risk controls include LP protections like adaptive spreads and dynamic funding adjustments to manage skew and inventory risk over time [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Oracles and Price Integrity\n\nThe protocol states that price feeds are derived from multiple sources with deviation checks, fallback providers, and time-weighted mechanisms to mitigate manipulation risks. These oracles feed into the settlement layer and the risk engine to determine margin requirements, funding payments, and liquidation triggers according to auditable parameters [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Staking and Rewards Mechanics\n\nThe staking system uses on-chain contracts that support [USDC](https://iq.wiki/wiki/usdc) and LP token staking with configurable lockups. Rewards are calculated based on net PnL and high-water mark logic, with performance fee tiers that vary with lockup duration. Early exits are described as subject to penalties designed to align incentives among participants and the protocol treasury [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Order Lifecycle\n\nIn the high-level flow presented by the documentation, a user signs an order intent off-chain and submits it to the matching engine. The engine executes the trade, generates settlement updates, and submits those updates to the on-chain contracts. Once included on-chain, the transaction becomes part of the public, auditable record, enabling independent verification of position states and events [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Tokenomics\n\nPerpX identifies PRPX as its governance and incentive token. Public materials describe several utilities and a governance scope but do not disclose total supply, allocation percentages, vesting, or contract addresses in the sources reviewed. The platform associates PRPX with staking and liquidity incentives and indicates that token holders will participate in governance over parameters such as listings, fee schedules, and risk settings, subject to a stated boundary that keeps core custody, matching engine behavior, and settlement sequencing outside governance control [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Utilities\n\n* Governance participation over listings, fees, risk parameters, incentives, and treasury\n* [Staking](https://iq.wiki/wiki/staking) participation via [USDC](https://iq.wiki/wiki/usdc) and LP [staking](https://iq.wiki/wiki/staking) modules with performance-based rewards\n* Incentives for liquidity providers and alignment with fee and funding revenue channels\n* Delegated governance to enable representation of voting power\n\nThese utilities are described across the project’s public materials as central to the protocol’s incentive and governance design [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n### Governance Details\n\nThe documentation outlines a governance flow in which participants deliberate proposals and cast votes to determine parameters such as asset listings, fee schedules, funding bounds, margining thresholds, and incentive distributions. Delegated voting is supported, and the project frames governance as progressively decentralized over time. The docs also state that governance will not control user custody, the fundamental behavior of the off-chain matching engine, or settlement sequencing, positioning these areas as outside governance to maintain technical determinism and safety assumptions [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Confirmed Partnerships\n\n* [deBridge](https://iq.wiki/wiki/debridge) (primary cross-chain swap and messaging integration)\n* MUX V3 (liquidity and funding model reference for utilization-driven mechanics)\n* Partner logos displayed on the PerpX homepage; names not textually specified in reviewed snapshot\n\nPerpX’s documentation explicitly cites [deBridge](https://iq.wiki/wiki/debridge) and a MUX V3-style model. The homepage displays partner imagery without textual identification in the reviewed content; individual partners should be corroborated through official announcements or partner pages [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5) [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx).\n\n## Blockchains and Infrastructure\n\nPerpX specifies [Arbitrum](https://iq.wiki/wiki/arbitrum) as the primary on-chain settlement environment. Cross-chain capital mobility is facilitated through [deBridge](https://iq.wiki/wiki/debridge), which supports transfers across a broad set of L1s/L2s, enabling users to bring collateral into the PerpX settlement domain. The architecture is presented as modular to accommodate additional messaging layers, although the reviewed sources do not list active deployments beyond [Arbitrum](https://iq.wiki/wiki/arbitrum) or provide contract addresses for verification [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5) [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx).\n\n## Technical and Security Considerations\n\nPerpX states that it employs audited smart contracts, multi-source oracles with deviation checks and fallbacks, and private or MEV-aware routing for orderflow. The docs also reference treasury allocations to audits, bug bounties, and incident response. However, third-party audit reports, auditor identities, final audit results, and on-chain contract addresses were not linked in the reviewed materials. Users and researchers are advised to seek primary audit documents and verified contract records to validate these claims before engaging with protocol contracts or assuming risk exposure [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Challenges, Limitations, and Information Gaps\n\nSeveral key disclosures commonly expected for a derivatives protocol remain absent or unverified in the public materials reviewed. Founder names and team biographies are not disclosed, limiting insight into the project’s leadership and development history. [Tokenomics](https://iq.wiki/wiki/tokenomics) specifics—including total supply, allocation percentages and recipients, vesting schedules, emission timelines, and contract addresses—are not published in the reviewed sources. While the platform references audits and partner integrations, downloadable audit reports and named partners (beyond [deBridge](https://iq.wiki/wiki/debridge) and the MUX V3 model reference) are not provided in text form on the homepage snapshot. The settlement chain is identified as [Arbitrum](https://iq.wiki/wiki/arbitrum), yet comprehensive on-chain contract listings and addresses are not included for verification in the reviewed materials [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\nThese gaps do not necessarily indicate that the information does not exist; rather, they highlight areas where additional primary sources are needed. Prospective users, researchers, and token holders may wish to consult official audit documents, verified contract repositories, governance forums, and press releases to confirm the platform’s security posture, contract deployments, and token economics [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Selected Statements from Documentation\n\nPerpX’s documentation includes statements that summarize core design intents. Examples include: “Orders are signed off-chain and not posted to mempools,” presented as part of a MEV-aware orderflow model; “Arbitrum is the primary on-chain settlement layer,” identifying the chain where final state transitions occur; and a design goal to provide “deterministic, auditable settlement and liquidations” through on-chain enforcement of risk parameters and event recording. These statements encapsulate the protocol’s emphasis on hybrid execution with on-chain finality and transparency [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Comparative Context\n\nPerpX’s design aligns with a broader group of hybrid derivatives protocols that separate low-latency execution from on-chain finality. The documentation’s emphasis on MEV-aware order handling, multi-asset collateral, and multi-source oracles reflects common concerns in decentralized derivatives, such as minimizing front-running risk and ensuring price integrity while providing features traditionally associated with centralized venues. The integration of a MUX V3-style funding model places the platform within a lineage of utilization-driven funding mechanisms aimed at balancing trader demand with inventory and skew management for liquidity providers [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).\n\n## Legal and Access Considerations\n\nPublic materials indicate self-custodial wallet access without traditional account registration, and list legal documents such as terms of use and a privacy policy. The site positions the platform as non-custodial, with settlement on-chain and support for cold storage, but it does not provide jurisdictional availability, KYC/AML policies, or regulatory posture details in the reviewed snapshot. Prospective participants should refer to the platform’s legal documentation and any region-specific access restrictions before attempting to use derivatives products [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx).\n\n## Research Notes and Areas for Verification\n\nFor a fully comprehensive entry, additional primary materials would help substantiate several claims and fill remaining gaps. These include a tokenomics paper with supply and allocation details, verified contract addresses and repositories for on-chain components, downloadable audit reports and auditor attestations, and named partner announcements with scope and integration descriptions. Documentation of founder and team identities, along with any funding disclosures, would improve the protocol’s biographical and organizational transparency [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5) [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx).\n\n## References\n\nPrimary references for this entry are the project website and documentation. The website provides high-level positioning, product descriptions, and legal resources, while the GitBook serves as the principal source for architecture, features, governance scope, and technical parameters cited above. Where claims lacked linked artifacts (such as audit PDFs or contract addresses), this entry notes the limitation and recommends consulting official releases or repositories for verification [\\[1\\]](#cite-id-eqIAi0HRsyOJFgNx) [\\[2\\]](#cite-id-qG3tLMWmtxwxsXX5).","summary":"PerpX is a decentralized perpetuals exchange using off-chain matching with on-chain settlement on Arbitrum. It emphasizes self-custody and AI-driven risk insights and uses the PRPX token for incentives and governance.","images":[{"id":"Qmf967vze32PDZFDgJLZZi2PKHjijAfRmdonqqRoCjw3k5","type":"image/jpeg, image/png"}],"categories":[{"id":"exchanges","title":"exchanges"}],"tags":[{"id":"DEXes"},{"id":"Protocols"},{"id":"Ethereum"}],"media":[{"id":"Qmf967vze32PDZFDgJLZZi2PKHjijAfRmdonqqRoCjw3k5","name":"1000626252.png","caption":"","thumbnail":"Qmf967vze32PDZFDgJLZZi2PKHjijAfRmdonqqRoCjw3k5","source":"IPFS_IMG"}],"metadata":[{"id":"website","value":"https://perpx.ai/"},{"id":"references","value":"[{\"id\":\"eqIAi0HRsyOJFgNx\",\"url\":\"https://perpx.ai/\",\"description\":\"PerpX website\",\"timestamp\":1776954247071},{\"id\":\"qG3tLMWmtxwxsXX5\",\"url\":\"https://perpx-3.gitbook.io/perpx.ai/\",\"description\":\"PerpX docs\",\"timestamp\":1776954247071}]"},{"id":"commit-message","value":"\"Added PerpX introduction and overview content\""}],"events":[{"date":"2026-04-23","title":"PerpX Founded","type":"CREATED","description":"PerpX was founded and officially launched.","id":"ee393a8c-784e-4094-a3c7-0577a981634f"}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"operator":{"id":"0x07f51b61cf92afB2AB1D9d27FCc6343f16742868"},"language":"en","version":1,"linkedWikis":{"blockchains":["arbitrum","ethereum"],"founders":["anon"],"speakers":[]}}