# The ZBU Token

<figure><img src="https://3951810624-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FICnj5yRS4DlaeDN2V5pS%2Fuploads%2FHz0jNLvivX8BF0GbuSbW%2FZeebu%20Whitepaper%20Diagrams%20(9).png?alt=media&#x26;token=7144dd1f-4472-4124-bdd5-bedc8b3f0273" alt=""><figcaption></figcaption></figure>

ZBU is a loyalty utility token based on Ethereum and the Binance Smart Chain that fuels the Zeebu platform for customers and merchants. The token smart contracts are developed with OpenZeppline contracts, leveraging their battle-tested libraries to enhance security and reduce vulnerabilities.

The ZBU token incorporates several technical features, including safeguards to prevent the accidental sending of tokens to the token address itself. This is achieved through the implementation of a “require” function that verifies the recipient is not the same as the token contract address. Additionally, ZBU includes a cliff and vesting function to lock a predetermined amount of tokens for a specified duration within designated contracts, such as liquidity pools. Custom bridges for the Binance Smart Chain and EVM chain have also been developed to facilitate the seamless movement of tokens between pools on different chains.

ZBU also includes several upgradability features. The token and vesting contracts themselves are not upgradeable, but the token outposts, which are the token contracts on other networks, are upgradeable as necessary to respond to changes in bridge contracts. Additionally, the loyalty reward contract is designed to be upgradeable to support the introduction of new loyalty use cases.


---

# 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://zeebu.gitbook.io/zeebu-whitepaper-v2.0/uzhRGn79HnwkCMDad1EE/the-zbu-token.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.