> For the complete documentation index, see [llms.txt](https://agp.aevo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agp.aevo.xyz/approved-proposals/agp-1.5-tge-update/introduction.md).

# Introduction

In AGP-1 we laid the foundation for a new governance and tokenomics model which slated a TGE for February 1st — this included $AEVO launch, $RBN/$AEVO staking, and other $AEVO-related growth initiatives. Since AGP-1, we’ve been working tirelessly to add new listings, ship new products, improve the exchange experience, deliver robust $RBN/$AEVO tokenomics, and bolster platform security.

Although we pride ourselves in our shipping speed, when it comes to user funds we prioritize security above all else. We have decided to run $AEVO / staking / new exchange-related smart contracts through one more round of audits ahead of the big day, and delay TGE.

Therefore, we must propose some corrections to the original proposal, so that the timing is consistent with the latest developments.


---

# 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://agp.aevo.xyz/approved-proposals/agp-1.5-tge-update/introduction.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.