> For the complete documentation index, see [llms.txt](https://floki-millions.gitbook.io/floki-millions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://floki-millions.gitbook.io/floki-millions/eth-launch.md).

# ETH Launch

**Q:** When will Floki Millions launch on ETH? 

**A:** TBA, although it will happen before the end of January 2022.

**Q:** Should I sell my existing tokens? 

**A:** No! You can move your tokens over to ETH and sell then at a higher price!

**Q:** Will I get taxed when sending my tokens over to ETH? 

**A:** No.

**Q:** Will I receive the same amount of tokens when I move over to ETH?

**A:** Yes

**Q:** Why are we launching on ETH? 

**A:** ETH investors are known to invest large sums into projects & HODL long-term.

**Q:** What are the benefits to the existing HOLDERS? 

**A:** The price of ETH will moon and you can send your tokens over to sell at a much higher price, making more profit than in BSC.

**Q:** Can I buy more tokens now? 

**A:** Yes! Increase your moonbag before ETH launch!

Should you have any other questions or concerns feel free to message someone from the team!


---

# 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://floki-millions.gitbook.io/floki-millions/eth-launch.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.