> For the complete documentation index, see [llms.txt](https://peeps-2.gitbook.io/peeps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/how-it-works/features.md).

# features

## No-code token creation

Creators can configure and launch a token through a guided form without writing or deploying Solidity manually.

## Fair-launch flow

Every supported launch uses a public on-chain process. The final implementation should disclose whether creators can make an initial purchase, whether purchase limits exist and whether any wallet receives tokens before public trading.

## Instant on-chain trading

After deployment, users can buy and sell through the launch mechanism using their own wallet. Transactions settle on Robinhood Chain.

## Bonding-curve discovery

Before graduation, the interface can display progress toward the configured liquidity or market threshold.

## Automatic graduation

When the on-chain graduation condition is reached, the system can create or activate an external liquidity pool according to the deployed contracts.

## Creator earnings

Creators may receive a disclosed share of eligible trading or liquidity-pool fees. The exact percentage and claim mechanism must match the deployed contracts.

## Token pages

Each launch can include:

* name and ticker
* image and description
* contract address
* creator wallet
* price and volume data
* bonding-curve progress
* holder and transaction activity
* social links
* risk or MBI indicators

## Discovery tools

Planned discovery surfaces include new launches, trending tokens, final-stretch launches, graduated tokens and live activity.

## Community-first identity

PEEPS is designed to help a launch become more than a contract address. Community links, creator updates and visible activity give users a place to understand the culture around a token.


---

# 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://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/how-it-works/features.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.