# Introduction to Perennial

### Derivatives Redesigned for DeFi

<figure><img src="https://2608572446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FesXIGSYvKcOjqMTCdsjo%2Fuploads%2FdQQZruj9gVtXbLk9Elgd%2Fdocs%20(1).png?alt=media&#x26;token=add6c8fb-5fb6-4be5-88c3-95a4a2bb7679" alt=""><figcaption></figcaption></figure>

**A Full-Stack Perps Ecosystem**

Perennial is a **layered ecosystem**, enabling the most capital-efficient and seamless perps trading experience.

1️⃣ **The Protocol Layer** → A perps primitive designed for seamless leveraged exposure. Traders take positions, while makers & LPs manage risk with full flexibility. Powered by a hybrid intent-AMM model, it facilitates three-sided markets, settling trades against an oracle price feed.

2️⃣ **The Rollup Layer** → A dedicated perps rollup on Base, optimizing for near-zero fees, scalable throughput, and fast execution—ensuring the smoothest trading experience.

3️⃣ **The Product Layer** → Multiple frontends leverage Perennial’s protocol, including app.perennial.finance for pro traders, perp.fun for retail, and third-party integrations such as Slingshot (soon).

### **How does it work?**

The Perennial protocol is a **settlement layer** for market-isolated derivatives trades. **Takers (traders)** can submit offchain (Intent) or onchain (AMM) orders to gain exposure to a market's underlying oracle price. Regardless of order type, positions are settled into the market’s **peer-to-pool** derivatives AMM, with funding & interest rates adjusting dynamically based on market skew & utilization.

**Takers (Traders)** deposit collateral & open a position to gain leveraged exposure to price feeds—long, short, or exotic payoffs. With **Intent orders**, a **Taker’s** position is matched with an opposing order from a **Maker** before being settled into the AMM. For AMM orders, **Takers** are directly netted against each other within the market.

Where a shortfall exists between **Takers**, **Liquidity Providers (LPs)** step in to fill the gap—earning fees while managing exposure. LPs take on risk proportional to the imbalance between longs and shorts. **On an ongoing basis, takers & LPs settle up; the losing side pays the winning side.**

### Why Perennial?

At its core, Perennial is a **minimalist, DeFi-native primitive**, providing the foundational infrastructure for derivative markets while allowing **developers, traders, and liquidity providers** to interact at any level.

Some things that make the Perennial protocol stand out:

* **Hybrid Intent-AMM** — A next-gen model combining offchain intent matching with onchain AMM settlement for deep liquidity & optimized execution.
* **Cash-settled** — Trades are settled in $USD, aligning with the most popular crypto derivatives.
* **Low fees** — A hyper-efficient design minimizes costs for both takers & makers.
* **Native LP Leverage** — LPs can provide capital at significant leverage (up to 50x) and can fully customize their risk exposure & hedging strategy (or lack thereof).
* **Built for the needs of Developers** — A composable, fully on-chain primitive designed for easy integration and expansion.
* **Permissionless** — Open market creation, integration, and composability.

To dive deeper, see the [Mechanism](https://www.notion.so/o/L4EUNHdWsBUAEDZqMBNt/s/esXIGSYvKcOjqMTCdsjo/~/changes/53/protocol/~/overview) section, or explore the layers of Perennial below.

### Dive in

<table data-view="cards" data-full-width="false"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center">Markets</td><td><a href="protocol/markets">markets</a></td></tr><tr><td align="center">Intents</td><td><a href="protocol/intents">intents</a></td></tr><tr><td align="center">Vaults</td><td><a href="protocol/vaults">vaults</a></td></tr><tr><td align="center">Integrating Perennial</td><td><a href="building-on-perennial/why-perennial">why-perennial</a></td></tr><tr><td align="center">Live Contracts</td><td><a href="broken-reference">Broken link</a></td></tr><tr><td align="center">Audits &#x26; Bug Bounty</td><td><a href="security/audits-and-bug-bounty">audits-and-bug-bounty</a></td></tr></tbody></table>

### Get in touch

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center">Website</td><td><a href="https://perennial.finance/">https://perennial.finance/</a></td></tr><tr><td align="center">Github</td><td><a href="https://github.com/equilibria-xyz/perennial-mono">https://github.com/equilibria-xyz/perennial-mono</a></td></tr><tr><td align="center">Twitter</td><td><a href="https://twitter.com/perenniallabs">https://twitter.com/perenniallabs</a></td></tr><tr><td align="center">Discord</td><td><a href="https://discord.gg/n6ejatX5Rw">https://discord.gg/n6ejatX5Rw</a></td></tr><tr><td align="center">Medium</td><td><a href="https://medium.com/perennial-protocol">https://medium.com/perennial-protocol</a></td></tr></tbody></table>


---

# 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://docs.perennial.finance/introduction-to-perennial.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.
