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

# Welcome to FlokiCash

<figure><img src="/files/ufXYTteKgNhIC9kEj6gO" alt=""><figcaption></figcaption></figure>

## Overview

[***Current FlokiCash contracts available on BSC:***](https://bscscan.com/token/0xA11ff9976018Fda2a8c4ccfa6fFBe8423c5aB668) 0xA11ff9976018Fda2a8c4ccfa6fFBe8423c5aB668

> Please be wary of any solicitation from another contract, the community currently has only one contract on the <mark style="color:purple;">BSC</mark> chain.

* Name : <mark style="background-color:orange;">Floki Cash.</mark>
* Symbol: <mark style="background-color:orange;">FlokiCash.</mark>
* Total Supply: <mark style="background-color:orange;">10,000,000,000,000.</mark>
* Burned: <mark style="background-color:orange;">50%.</mark>
* Use to Develop for the Ecosystem: <mark style="background-color:orange;">5%.</mark>
* Founders and Team: <mark style="background-color:orange;">5%.</mark>
* Buy/sell tax: <mark style="background-color:orange;">No tax.</mark>

> 🔥 <mark style="color:blue;">**Tokens burned:**</mark>&#x20;
>
> Community creator <mark style="background-color:green;">SatoshiMavis</mark> burned 50% of the total supply right after the token launch. The burning mechanism is still very promising in the future when a series of dApps are adopted, which will reduce the supply and increase the value of FlokiCash. [Tokens burn](https://bscscan.com/token/0xA11ff9976018Fda2a8c4ccfa6fFBe8423c5aB668?a=0x000000000000000000000000000000000000dead)<mark style="color:blue;">ed.</mark>
>
> 🔥 <mark style="color:blue;">**LP will be locked:**</mark>
>
> The entire liquidity token (LP) has been completely locked by <mark style="color:orange;background-color:green;">SatoshiMavis</mark> for 5 years, now the project will go strong: [Click here](https://floki-cash.gitbook.io/welcome/overview/lp-tokens-locked)

Linktr.ee: <https://linktr.ee/flokicash>

**Join the community of passionate holders who believe in the power of FlokiCash to revolutionize the crypto world."**

## Quick links

{% content-ref url="/pages/2AJlSV3c6p5OaBTd7Hew" %}
[How to Buy?](/welcome/overview/how-to-buy.md)
{% endcontent-ref %}

{% content-ref url="/pages/wmi8Jo9G3ideBU8kfPAO" %}
[Wallets to Hold?](/welcome/overview/wallets-to-hold.md)
{% endcontent-ref %}

## The Future

{% content-ref url="/pages/mwhiqZxWReptyt8qKcAh" %}
[Let's go up together](/welcome/the-future-of-flokicash/lets-go-up-together.md)
{% endcontent-ref %}

{% content-ref url="/pages/F8gQtp1pKdvpEBeiv1IE" %}
[dApps](/welcome/the-future-of-flokicash/lets-go-up-together/dapps.md)
{% endcontent-ref %}

{% content-ref url="/pages/dVg5BoCn0t6iGeT7EIa4" %}
[Flokireum.Com](/welcome/the-future-of-flokicash/lets-go-up-together/flokireum.com.md)
{% endcontent-ref %}


---

# 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-cash.gitbook.io/welcome/welcome-to-flokicash.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.