> For the complete documentation index, see [llms.txt](https://whitepaper.angryfloki.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.angryfloki.com/roadmap.md).

# Roadmap

### **Initial Phase**

**Timeline: 01**

\- Inception of the AngryFloki project

\- Gathering public interest

\- Rigorous marketing campaigns

\- Deploying our Smart Contract

\- Website launch

\- NFT Integration idea

\- Developing our unique Minigame demo

\- Presale announcement

\- Multiple audits

\- 5k telegram members

\- Grand Launch

&#x20;

### **Commercial Phase**

**Timeline: 02**

\- Kicking off banner ads campaigns: Poocoin, Dextool, BSCscan

\- Offline Ads: New York City billboard Ad, SpaceX billboard ads

\- Listing on Coinsniper, Coinhunt, Coinhunter, etc

\- Collaboration with Twitter and Telegram influencers

\- Post launch iPhone13 and Samsung Z Fold 3 giveaway

\- CG & CMC listing

\- Cointiger listing

\- Hotbit listing

\- 15k Telegram members

\- ETH Bridge at Uniswap

\- Compiling our NFT Collection

\- Launching the AngryFloki Charity Drive

&#x20;

### **Adoption Phase**

**Timeline: 03**

\- Several CEX listing

\- Huge Influencer Marketing Campaigns

\- Constant Poocoin ads, Bscscan Ads, Dextools Ads

\- AngryFloki Wallet Launch

\- NFT x Minigames Launch

\- 50k Telegram Members

\- 2nd Charity Drive

&#x20;

**Summit Phase**\
**Timeline: 04**

\- Huge Partnership

\- Further CEX Listings

\- Massive Marketing Drive

\- AngryFloki Swab Launch

\- AngryFloki NFT Marketplace Entry

\- 100k holders

\- 3rd Charity Drive


---

# 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://whitepaper.angryfloki.com/roadmap.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.
