> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/events-and-indexing.md).

# Events & Indexing

Event emitters, business meanings, lifecycle transitions and reconciliation rules for Launchpad data integrations.

Use the production Classic Core, Forwarder and Holder ABIs from SDK 1.0.0 on Arc Mainnet (`5042`). Discover Token, Curve and Holder addresses from registered bindings and confirmed receipts.

| Source                         | Track                                                        |
| ------------------------------ | ------------------------------------------------------------ |
| Factory and Curve              | Token creation, trades, actual spending and graduation state |
| GraduationCoordinator and Hook | Official pool, fee accrual and settlement                    |
| FeeEscrow                      | Credits and withdrawals by recipient and asset               |
| HolderDistributorFactory       | Registered per-launch Holder binding                         |
| Holder Distributor             | Revenue collection, Epoch publication, claims and rollover   |

Use the complete receipt: an initial-buy trade can appear before token creation, and related events need not be adjacent. Validate the emitter and registered project relationship. After confirmation, refresh lifecycle and recipient state.

Holder claims use `claim` with the on-chain Epoch number, beneficiary, Quote/project-token amounts and proof. Publication is not payment.

Persist chain ID, block hash, transaction hash and log index, and handle reorganizations. Keep amounts as integers. Avoid counting accrual, collection and payment as separate revenue; see [Fees and Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/fees-and-claims).


---

# 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://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/events-and-indexing.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.
