> For the complete documentation index, see [llms.txt](https://docs.bunnypark.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunnypark.com/basic-information/tokenomics/bunnypark-token-bp.md). # BunnyPark Token (BP) ### BunnyPark Token (BP) Token name:BunnyPark\ Token ticker:BP\ Blockchain:BinanceSmartChain(BEP-20)\ Contract Address:0xACB8f52DC63BB752a51186D1c55868ADbFfEe9C1 ### Token Output (Major Updates) BP output follows Binance Smart Chain blocks. The initial output was at block height 6871000 and thereafter, the output is reduced every 864000 blocks (about one month), each time reducing the current output by 10%, for a total of 21 cycles. The total output duration is 22 cycles (months). As of the current OnePage update (the 7th cycle), the output data is as follows: ![](/files/NZkSlzxF9oL8JUw1QKjb) ### Important Notes: \* King was auctioned off on Binance NFT. Therefore, the output allocation before the ShareCard was transferred to BSC does not apply. \* A total of 790 Warriors and 20,000 Astronauts were sold via public sale. ### Team and Developer Share (Major Updates) BunnyPark team owns 5% of the effective circulating tokens (total amount shown in the block – total number in Burn Address = effective circulating amount). According to the original terms, BunnyPark team owns 5% of BP block output.\ According to the new terms, BunnyPark team owns 5% of the effective circulating amount. This modification means that team’s share will be destroyed simultaneously with the destruction quantity. The SaaS fund share comes from the original developer support share, and the ratio is the same as the team. The first minting record by team (at 45,000,000 effective circulation): 1554cbc 669517da --- # 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://docs.bunnypark.com/basic-information/tokenomics/bunnypark-token-bp.md?ask=&goal= ``` `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.