# TGE Roadmap

## **Overview**

At Hattori, we work with a flexible, milestone-driven approach rather than rigid deadlines or fixed dates. Our focus is on achieving key project goals, ensuring each step is thoroughly completed before moving forward.

Once all milestones are met, we'll seamlessly transition to the [Token Generation Event](/pre-tge-vesting-mechanics.md) (TGE). This method allows us to adapt to market trends, user feedback, and community needs while maintaining a commitment to delivering a high-quality experience.

Timelines may shift slightly based on strategic priorities, but this ensures the project evolves in the best way possible for our ecosystem and its members. As of now, we're planning to conduct the TGE soon.

## **Road to TGE**

We want the process to be clear and easy to follow. When every step on this roadmap is completed, we'll make an official announcement and the TGE will begin.

Before, we sometimes shared early dates because the community asked for a rough timeframe. But TGE preparation is the most complex part of the whole system, and some dates had to be moved. This created confusion instead of clarity.

So now we follow a simple rule: no exact dates, only real progress. This roadmap shows what is already finished, what is in progress, and what is still ahead. You can always check this page to understand how close we are to the TGE.

<details>

<summary><strong>Step 1: Test stages</strong> <img src="/files/ig52Wcv2xfnIwy8rjult" alt="" data-size="line"></summary>

* Early ecosystem testing
* Telegram mini-app launch
* Closed test stage for ambassadors
* Open test stage #1
* Open test stage #2

</details>

<details>

<summary><strong>Step 2: Prepare for scaling</strong> <img src="/files/ig52Wcv2xfnIwy8rjult" alt="" data-size="line"></summary>

* Test and prepare servers and other project infrastructure for scaling

</details>

<details>

<summary><strong>Step 3:  Boosted engagement</strong> <img src="/files/ig52Wcv2xfnIwy8rjult" alt="" data-size="line"></summary>

* Influencer onboarding flow
* Social events

</details>

<details>

<summary><strong>Step 4: Improve retention</strong> <img src="/files/ig52Wcv2xfnIwy8rjult" alt="" data-size="line"></summary>

* Improve UX in Telegram Mini App
* Launch social events

</details>

<details>

<summary><strong>Step 5: Smart Contracts</strong> <img src="/files/ig52Wcv2xfnIwy8rjult" alt="" data-size="line"></summary>

* $HATTORI Jetton core contracts
* Treasury reward system
* Initial economic logic

</details>

<details>

<summary><strong>Step 6: Backend Infrastructure</strong> <img src="/files/ig52Wcv2xfnIwy8rjult" alt="" data-size="line"></summary>

* Core server architecture
* Secure configuration and internal tools
* Wallet connection
* Communication between the TMA and the blockchain

</details>

<details>

<summary><strong>Step 7: Testnet Deployment</strong> <img src="/files/ig52Wcv2xfnIwy8rjult" alt="" data-size="line"></summary>

* All contracts deployed to the testnet
* Backend deployed to the dev environment
* All transaction flows work on the testnet

</details>

<details>

<summary><strong>Step 8: TMA Alpha</strong> <img src="/files/ig52Wcv2xfnIwy8rjult" alt="" data-size="line"></summary>

* Full user journey working on testnet
* Debug tools for the test team
* Internal testing with controlled accounts

</details>

<details>

<summary><strong>Step 9: DEX Development</strong> <img src="/files/7P9itz9ksiAP6RLNSCyt" alt="" data-size="line"></summary>

* DEX smart contracts&#x20;
* Swap UI
* Admin and monitoring tools

</details>

#### **Step 10: Final Process Polishing** <img src="https://docs.playhattori.io/~gitbook/image?url=https%3A%2F%2F1600250607-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FOztbzZyXUmP3BH4IPnha%252Fuploads%252FYMXFA908vHSxaZi4MYLC%252FGroup%25201%2520%283%29.png%3Falt%3Dmedia%26token%3Df7bbb474-9ece-4e4c-8fce-bef462b87afb&#x26;width=160&#x26;dpr=3&#x26;quality=100&#x26;sign=a41fa1cc&#x26;sv=2" alt="" data-size="line">

* CJM UX and UI polishing
* Full integration of the DEX

#### **Step 11: Production Readiness** <img src="https://docs.playhattori.io/~gitbook/image?url=https%3A%2F%2F1600250607-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FOztbzZyXUmP3BH4IPnha%252Fuploads%252FYMXFA908vHSxaZi4MYLC%252FGroup%25201%2520%283%29.png%3Falt%3Dmedia%26token%3Df7bbb474-9ece-4e4c-8fce-bef462b87afb&#x26;width=160&#x26;dpr=3&#x26;quality=100&#x26;sign=a41fa1cc&#x26;sv=2" alt="" data-size="line">

* Security audit
* Performance optimization
* Preparation for TGE
* TGE launch on TON
* Pre-TGE token airdrop

#### **Step 12: Post-TGE flow** <img src="https://docs.playhattori.io/~gitbook/image?url=https%3A%2F%2F1600250607-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FOztbzZyXUmP3BH4IPnha%252Fuploads%252FrDMgRELBDoAY4Gjc7H0a%252FGroup%25203%2520%281%29.png%3Falt%3Dmedia%26token%3Df3d594be-8873-4d07-9cdc-02c5376572e5&#x26;width=160&#x26;dpr=3&#x26;quality=100&#x26;sign=e05d8ddf&#x26;sv=2" alt="" data-size="line">

* Bridge to EVM
* Launch $HATTORI on Base
* Bridge to Solana
* Launch $HATTORI on Solana

At this moment most of the work is already done. Several final phases are actively in progress, and once all steps reach the finish line, we'll move to the TGE.

{% hint style="info" %}
For detailed information on the **TGE mechanics**, its structure, and how it will be implemented, please refer to the next chapter: [Pre-TGE vesting mechanics](/pre-tge-vesting-mechanics.md)
{% endhint %}

{% content-ref url="/pages/2VNDGAxO80Y1m61FdQM8" %}
[Pre-TGE vesting mechanics](/pre-tge-vesting-mechanics.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.playhattori.io/tge-roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.