> 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/creator-bond.md).

# Creator bond

A creator bond is an ETH pot that a launch creator posts against a promise to keep a floor balance of the token across registered wallets. If the floor fails, the pot can be slashed and shared with holders who burn tokens.

## Who it is for

Creators who want to back a holding commitment with ETH, and holders who want a consequence if that commitment is broken.

## How it works

`CreatorBondFactory` lets the launch creator of a Polypad token open a bond. Only the launch creator can open one, and only for tokens launched through Polypad.

{% stepper %}
{% step %}

### Open the bond

The creator posts ETH, sets an end time, registers wallets, and sets a sell allowance. State: **Pending**.
{% endstep %}

{% step %}

### Confirm wallets

Every registered wallet other than the creator confirms with `confirmWallet`. The creator can `cancel()` while the bond is pending. When all confirm, the bond is **Active**.
{% endstep %}

{% step %}

### Hold the floor

The combined balance of registered wallets must stay at or above `floor = committed * (10,000 - allowanceBps) / 10,000`.
{% endstep %}

{% step %}

### Slash or refund

If the floor fails before the end, anyone can call `slash()`. After a slash, holders outside the registered set can burn tokens through `redeem()` at a rate fixed at slash time. After the end, the creator can `refund()` only if the floor still holds.
{% endstep %}
{% endstepper %}

## Limits

| Parameter              | Value    |
| ---------------------- | -------- |
| Minimum bond           | 0.01 ETH |
| Minimum duration       | 7 days   |
| Maximum sell allowance | 20%      |

## Key properties

* No admin key, no oracle, nothing upgradeable.
* Tokens sent into registered wallets only raise the sum, so outsiders cannot grief a bond.
* Staking or vesting committed tokens lowers the counted balance, so it counts as a move.
* Redemption rates are fixed at slash time (`pot / totalSupply`), so total claims cannot exceed the pot.

## What a bond does not do

A bond does not stop the creator from selling tokens that sit outside the registered wallets. It does not keep a price. It slashes only the posted ETH, and only when the registered wallets miss the floor.

## Contract

CreatorBondFactory: [`0x876170251e30F99E27119AF0e90648A88D508f97`](https://robinhoodchain.blockscout.com/address/0x876170251e30F99E27119AF0e90648A88D508f97) (Sourcify exact match)

## Risks

The contracts are **Not audited.** A bond is a commitment mechanism, not a promise about outcomes.


---

# 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/creator-bond.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.
