# Bonding and Listing Mechanics

When a new asset enters the Aces.fun ecosystem, its token undergoes a bonding phase that transforms initial interest into active market dynamics. As retail participants engage with the newly created token, they progressively contribute to reaching the bonding target. Once the bonding target is achieved, the token pairs with $ACES in a liquidity pool permanently, creating an active trading market on decentralized exchanges. This milestone initiates a seven-day claim window where the asset itself becomes available for purchase. By structuring the process this way, we ensure organic market formation and price discovery before enabling direct asset acquisition, aligning the interests of traders, potential buyers, and sellers while maintaining market stability.

* Gating purchases until after bonding ensures traders are motivated to push to bond
* Bonding pushes the token to DEX, increasing visibility
* Bonding signals an important milestone to the community and buyers

### **Bond Target Formulas**

The asset’s listing price determines how much $ACES must be staked to establish its bonding curve. A higher listing price leads to a larger initial market cap. This model leverages a square root pricing formula for smooth price growth and predictable on-chain behavior.

This listing deposit is a vital component of the platform’s integrity.

* Prevents fraudulent listings or uncommitted sellers
* Fronts initial liquidity
* Sets the starting marketcap
* Supports the $ACES token
* Is tied to the Bonding Target to reduce complexity

<kbd>List(x) = <pocket@aces.fun> to learn more</kbd>&#x20;

<kbd>Bond(y) = <pocket@aces.fun> to learn more</kbd>&#x20;

**Where:**

* x is the listing price in USD and the result is the $ACES needed to launch in USD
* y is the Bond Target

Here are the key price points from our formula:

<table data-header-hidden><thead><tr><th></th><th></th><th width="213"></th><th></th></tr></thead><tbody><tr><td>Listing Price</td><td>Listing %</td><td>ACES need to List in $</td><td>Bond Amount</td></tr><tr><td>$10,000</td><td>15.00%</td><td>$1,500</td><td>$37,500</td></tr><tr><td>$50,000</td><td>5.34%</td><td>$2,671</td><td>$66,766</td></tr><tr><td>$100,000</td><td>3.26%</td><td>$3,256</td><td>$81,399</td></tr><tr><td>$500,000</td><td>1.12%</td><td>$5,597</td><td>$139,930</td></tr><tr><td>$1,000,000</td><td>0.73%</td><td>$7,324</td><td>$183,095</td></tr><tr><td>$5,000,000</td><td>0.29%</td><td>$14,575</td><td>$364,373</td></tr></tbody></table>

### Keep the Math Square and Simple

This square root bonding curve is highly gas-efficient for Ethereum smart contracts because it uses only basic arithmetic (addition, subtraction, division) and a single square root operation. Solidity already provides optimized implementations of square root via established libraries like OpenZeppelin, often using bitwise operations for faster computations. Unlike exponential or logarithmic curves that may demand more complex math or floating-point logic, this formula stays within the integer realm, greatly reducing computational overhead.

The curve relies on a few fixed constants and one dynamic input, x (e.g., the deposit amount), meaning there’s no need for storing multiple parameters or maintaining complex state variables. Because it doesn’t require bounds checking beyond verifying the domain, the curve extends naturally to higher values without adding complexity or extra logic branches. This simplicity not only keeps gas costs predictable and low but also bolsters security and makes the code easier to audit.


---

# 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.aces.fun/initial-product-offering-ipo/bonding-and-listing-mechanics.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.
