> For the complete documentation index, see [llms.txt](https://docs.collection.xyz/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collection.xyz/guides/technical-reference/bonding-curves/parameters-of-the-bonding-curves.md).

# Parameters of the bonding curves

We maintain four parameters for the bonding curve.

<details>

<summary>Delta</summary>

Delta is a static variable until changed used to determine the speed of price increase\
\
Delta can be **functionally flat** as well, if you don’t want prices to change from trade to trade.

* The number indicating **functionally flat** delta differs from each curve. For `Linear` curves, input a delta of `0`. For `Exponential` curves, input a delta of `1e18` (representing 100% i.e. no multiplicative change). You can also do that with `Sigmoid` curves by setting `P_min` = `P_max`. However, since these are all functionally equivalent, we recommend just sticking with the simple `Linear` representation if you wish to create a **functionally flat** pricing curve.

</details>

<details>

<summary>SpotPrice</summary>

SpotPrice is a stateful variable that is used to store a rough price level to help calculate bid/asks

</details>

<details>

<summary>Props</summary>

We foresee the need for an arbitrarily large set of static variable beyond just delta (e.g. for the sigmoid curve, we require explicit min/max levels)

</details>

<details>

<summary>State</summary>

We foresee the need for an arbitrarily large set of stateful variables. State is a bytes variable for an arbitrarily large set of stateful variables.

</details>

{% hint style="info" %}
Do note that the difference between props and state is just a convention for the curves that we have, and is not enforced for custom curves - someone could easily make props the stateful variable and state the static variable.
{% endhint %}

<table><thead><tr><th>Variables</th><th width="220">Intent of variable usage</th><th>DataType</th><th width="176">Limited Data Storage?</th></tr></thead><tbody><tr><td>Delta</td><td>Static - Changed by user only when you want to change the hyperparameters of pricing function</td><td>uint128</td><td>Limited</td></tr><tr><td>SpotPrice</td><td>Stateful - Changed by the pool automatically on each trade</td><td>uint128</td><td>Limited</td></tr><tr><td>Props</td><td>Static - Changed by user only when you want to change the hyperparameters of pricing function</td><td>bytes</td><td>Unlimited</td></tr><tr><td>State</td><td>Stateful - Changed by the pool automatically on each trade</td><td>bytes</td><td>Unlimited</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.collection.xyz/guides/technical-reference/bonding-curves/parameters-of-the-bonding-curves.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.