# What is PiperX

<figure><img src="/files/OQABYRqGpvFjvM4C9Ze4" alt=""><figcaption></figcaption></figure>

Programmable-IP-er Exchange (PiperX) is the ultimate DEX and liquidity layer on [Story L1](https://www.story.foundation), the world's first IP blockchain. While Story aims at onboarding a new RWA - IP, representing a $3T market, PiperX aims at building the best liquidity layer for those new assets. &#x20;

{% hint style="info" %}
Want to learn more about Story's vision to onboard the $3T IP assets on chain? Read [their vision](https://www.story.foundation/media/vision)&#x20;
{% endhint %}

### Who will be benefited from PiperX's success?

* **IP asset owners** (creators, IP companies, etc.): owners will be benfited from a liquid market for their assets, making them easier to monetize.
* **Investors/Users** (crypto-native and non-crypto-native): investors will get access to a new RWA asset class: IP asset. They can either diversify their existing investment, or seeking for alphas here.
* **IP Dapp builders**: builders could plug in the liquidity of PiperX to help their Dapp's. For example, for builders building IP meme coin launchpad, they could deploy to PiperX after creating the coins.

### What problem is PiperX solving?

In one word: "the liquidity problem of IP assets". As any new on-chain asset class, there is no liquid market for IP assets on Story, making users and asset owners has no motivations to participate. Additionally, IP assets are diverse, meaning there are many long-tail assets with low liquidity, making price discovery incredibly difficult.

### How is PiperX solving the liquidity problem for IP assets?

PiperX has three core products to solve liquidity problem for IP assets:

* **AMM DEX** powers seamless trading for IP assets via concentrated liquidity.
* **Proof-of-creativity Voting** identifies high quality IP asset pools, and generate yields for voters.
* **BoostPad** brings extra liquidity to high quality IP asset pools through incentives.&#x20;

&#x20;&#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://docs.piperx.xyz/archive/quickstart.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.