> For the complete documentation index, see [llms.txt](https://wherls.gitbook.io/wherls/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wherls.gitbook.io/wherls/why-usdwherls-is-a-bep-20-token.md).

# Why $Wherls Is a BEP-20 Token?

**The $WHERLS token is deployed on the Binance Smart Chain (BSC) using the BEP-20 standard, one of the most widely adopted token frameworks in the blockchain ecosystem. The choice of BEP-20 is both strategic and practical, offering numerous benefits for scalability, speed, cost-efficiency, and integration.**

✅ **Key Reasons for Choosing BEP-20:**

* **Low Transaction Fees:**

  BEP-20 tokens operate on a high-performance network with significantly lower gas fees compared to Ethereum and other L1 chains — making it ideal for microtransactions, NFT trading, and staking.
* **Fast Confirmation Times:**

  Transactions on the BNB Chain are confirmed in seconds, enabling real-time trading and seamless user experiences across the Wherls ecosystem.
* **High Compatibility:**

  BEP-20 tokens are supported by most major wallets, DEXs, and blockchain tools, ensuring frictionless integration and accessibility.
* **Robust Ecosystem:**

  Binance Smart Chain hosts a large number of DeFi, GameFi, and NFT platforms, making it easier for Wherls to collaborate, scale, and reach new audiences.
* **Security and Standardization:**

  The BEP-20 standard is secure, flexible, and battle-tested — ensuring $WHERLS adheres to best practices while allowing advanced functionalities like burning, minting, and staking.


---

# 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://wherls.gitbook.io/wherls/why-usdwherls-is-a-bep-20-token.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.