# Pool-to-Peer engine

Liquidity Provision (LP) is the foundation of the Nexadex Pool-to-Peer engine, with LPs collectively acting as the perpetual exchange’s counterparty. The architecture is designed to offer sustainable yield and capital efficiency while introducing sophisticated, tiered risk management to appeal to a wider spectrum of capital providers, from retail users to institutional funds.  &#x20;

#### Liquidity Pool/Vault Architecture

The core of the LP model is the Liquidity Pool Contract, initially configured as the Single-Asset Liquidity Vault (SLV) holding USDC.  &#x20;

* Counterparty Role: LPs accept the counterparty risk of the protocol. They earn yield from the 0.1% trading fees collected and from realized losses of leveraged traders. They absorb losses when traders are profitable. This model ensures that LP yield is derived from real economic activity, prioritizing  &#x20;

  real yield over purely inflationary token incentives.  &#x20;
* Evolution to Hybrid Capital: The current SLV model is simple and secure , but its reliance on a single asset makes it less capital efficient than multi-asset pools or hybrid CLOB/AMM systems. Therefore, the roadmap mandates a transition to  &#x20;

  Multi-Asset Liquidity Pools (Phase 2). This move will diversify the collateral base, significantly increasing the overall capital efficiency of the protocol and allowing it to scale the volume necessary for institutional adoption. This evolution is necessary to compete with platforms that utilize advanced liquidity structures, such as Hyperliquid’s HLP Vaults or Kubo’s Stablecoin Vaults.  &#x20;

#### Risk Management for LPs

During the MVP phase, LPs face uniform risk exposure across the SLV. While the deployment of the Insurance Fund (Phase 1) acts as a collective backstop, a truly sophisticated perpetual DEX requires stratified risk management.  &#x20;

* Risk Management Tranches: Nexadex will implement segregated Risk Management Tranches in Phase 2, which is critical for attracting institutional capital.  &#x20;
  1. Senior Tranche: Lower risk, protected by the capital in the Junior Tranche, offering lower but steadier yield. This is ideal for risk-averse institutional investors seeking predictable returns.
  2. Junior Tranche (First Loss Capital): Higher risk, absorbs the initial losses from trader profits or liquidation shortfalls, and consequently offers the potential for higher APY. This appeals to retail and high-risk capital.  &#x20;
* Loss Cascade Rules: The documentation for this system will meticulously detail the Loss Cascade Rules, ensuring LPs have full transparency regarding exactly how losses are distributed across the tranches. This layered approach manages counterparty risk more effectively than a generalized pool, positioning Nexadex as a financially sophisticated venue.  &#x20;

#### Collateral Innovations and Capital Efficiency

Future innovations are designed to maximize the utility and safety of locked capital.  &#x20;

* Time Management: Liquidity Locking: The protocol will utilize liquidity locking mechanisms to ensure pool stability. Longer lock-up commitments will be incentivized through increased APY boosts and eligibility for greater governance rewards, a strategy successfully employed by protocols like AvantiFi. This mechanism ensures stable, deep liquidity, which is crucial for supporting the planned increase in maximum leverage beyond 10x.  &#x20;
* Yield Strategies: Phase 2 introduces mechanisms such as Impermanent Loss Protection (ILP) and Auto-Compounding Yield strategies. While ILP is traditionally associated with non-leveraged AMMs, the equivalent mechanism in a perpetual DEX minimizes the delta between the pool’s exposure and market price, ensuring that the realized yield remains attractive and sustainable, further strengthening the platform’s competitive standing in the DeFi market.  &#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://nexadex.gitbook.io/nexadex-docs/trading-mechanics/pool-to-peer-engine.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
