> For the complete documentation index, see [llms.txt](https://polydash.gitbook.io/polydash-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polydash.gitbook.io/polydash-docs/polypad/bonding-curve-and-trading.md).

# Bonding curve and trading

Once a launch is open, anyone can buy and sell against the launch contract. There is always a quote because the contract itself is the counterparty.

## How the curve works

The curve is a constant-product formula on virtual reserves, priced in ETH.

```
ethReserve   = virtualEth + realEthRaised      (default virtualEth = 1.5 ETH)
tokenReserve = curveSupply - tokensSold        (curveSupply = 80% of totalSupply)
spotPrice    = ethReserve * 1e18 / tokenReserve
```

* **80%** of supply is on the curve. **20%** is held back as the liquidity reserve.
* Each buy moves the quoted price up. Each sell moves it down. The price you receive depends on your trade size and on trades just before yours.
* New reserves round in favor of the pool, so the product of the two reserves never decreases. This is covered by fuzz and invariant tests in the repository.

## Buy and sell

{% stepper %}
{% step %}

### Open the token page

Check the token address, the creator fee, and the progress toward graduation.
{% endstep %}

{% step %}

### Request a quote

The site shows the expected output and the minimum output after slippage.
{% endstep %}

{% step %}

### Sign

Buying sends ETH with the transaction. Selling needs an approval for the exact token amount, then the sell.
{% endstep %}
{% endstepper %}

## Anti-sniper settings

Each launch copies anti-sniper settings from the factory at creation: a higher buy fee that decays, and a per-wallet cap for the opening blocks. The factory owner can change these only for future launches, within fixed bounds.

| Setting                  | Bound                                    |
| ------------------------ | ---------------------------------------- |
| Starting anti-sniper fee | Up to 20%                                |
| Fee decay duration       | Up to 1 hour                             |
| Wallet-cap window        | Up to 100 blocks                         |
| Wallet cap               | Greater than 0% and up to 100% of supply |

The anti-sniper surplus is not paid to the creator or to Polydash. It is added to the liquidity that is locked at graduation.

## Where the numbers come from

Formulas and bounds are from the `polypad/contracts/docs/ARCHITECTURE.md` and `OWNER_CAPABILITIES.md` files in the repository. Live values for a given launch are on its token page.

## Risks

Curve prices can move quickly. Most newly launched tokens lose value. A token may never graduate. See the [Risk disclosure](https://polydash.gitbook.io/polydash-docs/security-and-risk/risk-disclosure.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://polydash.gitbook.io/polydash-docs/polypad/bonding-curve-and-trading.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
