# What is Boda Token? ## Introduction Boda Token was first created on BNB Chain in April 2021 as a community-owned memecoin. \ Version 2 (V2) upgrade of Boda Token was launched on September 21 2021, changing it into a community-owned hyper-deflationary USDT reward token. \ The current token in operation is BODAV2. \ Audited by Certik. Complete KYCed Team primarily operating out of Australia. ## BODA V2 Contract Address 0xdc847755343C3A2B94d6aFC0aAE57651E1b14064 Verified Contract on BSCSCAN - Name - Boda Decimals - 18 Symbol - BODAV2 Chain - Binance Chain (BEP20) ## Main Features ### Earn $USDT Earn USDT automatically just for holding BODAV2 tokens. From every buy transaction, 6% of the buy fee is converted to $USDT automatically. From every sell transaction, 13% of the sell fee is converted to $USDT automatically. This allows holders to earn up to 19% in $USDT from every combined buy and sell transaction. The reward system operates in the same manner that dividends operate within shares on the stock market. The more tokens you hold, the more rewards you will earn. USDT BEP20 Token Address - 0X55d398326f99059fF775485246999027B3197955 {% hint style="info" %} Currently, a minimum of 3 Billion (3,000,000,000) tokens is required to qualify for $USDT reward earning. This limit is in place to prevent manipulation of the reward system, but can be adjusted in the future based on community voting. {% endhint %} ### Auto-Burning 2% from every Buy & Sell order is auto-burned. This means that BODA V2 is a hyper-deflationary token where overall supply will continue to decrease over time. Burning supply and removing it from circulation means that the overall value and scarcity of the token will increase with each transaction, as will the per-token share of rewards for holders. Fewer tokens in supply = more rewards for holders. {% hint style="info" %} Auto-Burned tokens are locked in the BODAV2 Smart Contract Address forever and can never be removed - {% endhint %} ### Manual Burning 4% from every Buy & 5% from every Sell order is stored for a Manual Token Supply Reduction. \ Reducing the supply of a token helps to make the token more scarce and increase its value over time, as there will be fewer tokens available in the open market. \ A lower token supply gives an increase to the token value and the USDT rewards share per token. ### Token Buy Back & Burn Revenue collected from sources such as the Merchandise Store, NFTs, BODASwap, Yield Farm, Cross Chain Bridge Exchange, and Ad Revenue will aid in the token buyback and burn of BODA V2.\ Token Buyback and Burn can help decrease token supply and increase token value, in addition to increasing USDT rewards share per token. {% hint style="info" %} Manually Burned tokens are sent to the dead wallet address - {% endhint %} {% content-ref url="merchandise" %} [merchandise](https://boda-token.gitbook.io/boda-docs/boda-token/merchandise) {% endcontent-ref %} ### BodaSwap Exchange The BODA Swap Exchange will trade tokens without slippage fees, allowing users to gain more tokens per swap. BabyDoge will be the first token to be listed, with more to follow! {% content-ref url="../bodaswap/what-is-bodaswap" %} [what-is-bodaswap](https://boda-token.gitbook.io/boda-docs/bodaswap/what-is-bodaswap) {% endcontent-ref %} ### Dashboard App The BODA V2 Dashboard dApp is where holders can track and monitor their USDT reward earnings. {% content-ref url="dashboard-app" %} [dashboard-app](https://boda-token.gitbook.io/boda-docs/boda-token/dashboard-app) {% endcontent-ref %} --- # 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://boda-token.gitbook.io/boda-docs/boda-token/what-is-boda-token.md?ask= ``` 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.