> For the complete documentation index, see [llms.txt](https://docs.trybasket.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trybasket.live/developers-and-api/events-memos-and-subgraph.md).

# Events, memos & subgraph

This page explains how Basket activity can be indexed.

### Event sources

Developers can index B20 mint and burn activity plus pool-level asset flows.

### Memo usage

Basket uses B20 memos to label mint and burn events with a `bytes32` tag.

That gives indexers a stable hook for classifying issuance activity.

### Subgraph status

Subgraph and indexing architecture details are `TBD`.

### Event model

Basket indexing needs two layers of information:

| Layer                            | What it answers                           |
| -------------------------------- | ----------------------------------------- |
| Token-level mint and burn events | When supply changed                       |
| Pool- and route-level activity   | Why supply changed and what backing moved |

### Why memos matter for indexers

Without labels, an indexer can see that supply changed.

With memos, an indexer can classify that change as an investment, redemption, or other operational flow if Basket defines those conventions.

### What a complete event reference should include

| Topic                | Why it matters                                  |
| -------------------- | ----------------------------------------------- |
| Event name           | Tells indexers what to subscribe to             |
| Emitting component   | Tells indexers where the signal comes from      |
| Core fields          | Tells indexers what to decode                   |
| Memo conventions     | Tells indexers how to classify the action       |
| Ordering assumptions | Tells indexers how to reconstruct the lifecycle |

<details>

<summary>Why event docs matter even when the chain is public</summary>

Public events tell you what happened.

Good documentation tells you how Basket intends those events to be interpreted together.

That reduces ambiguity for dashboards, subgraphs, and explorers.

</details>

### What to publish here later

* Event list
* Field definitions
* Memo conventions
* Indexing examples
* Subgraph endpoints


---

# 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.trybasket.live/developers-and-api/events-memos-and-subgraph.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.