> For the complete documentation index, see [llms.txt](https://nikepig.gitbook.io/nikepig/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nikepig.gitbook.io/nikepig/whitepaper/nikepig-whitepaper/introduction/tokenomics.md). # Tokenomics ### Fair Launch & No Creator Tokens: $NIKEPIG had a fair launch with no tokens allocated to creators or developers. All tokens have been accessible to the community from the start, ensuring true decentralization. There were no pre-sales, private sales, or exclusive allocations, staying true to a community-first approach. ### Circulating Supply At launch, 100% of total supply was released onto the open market. 10% was eventually burnt, leaving the remaining 90% of supply in circulation. ### Burned Supply Since launch, the community has actively participated in token burns, reducing the original supply by 10%. This deflationary mechanism has brought the total supply from 1 billion to 900 million tokens, creating scarcity and potentially increasing value over time. ### Total Supply Overview * Initial Supply: 1 billion * Current Supply: 900 million (after 10% burn) * 90% in Circulation: 900 million tokens available to the public from day one * 10% Burned: 100 million tokens ### NikePig boasts one of the fairest supply distributions among top memecoins on Cardano. Here's why: * **Fully Circulated Supply**: The entire $NIKEPIG supply is already in circulation, there were no team allocations or reserved funds. This means the playing field is completely level. * **Team Buys Openly**: Unlike many projects, the Nike CTO Team actively purchases $NIKEPIG from the open market, just like everyone else. No preferential treatment. This aligns the team’s incentives with the community, ensuring they are equally invested in the success of the project. --- # 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://nikepig.gitbook.io/nikepig/whitepaper/nikepig-whitepaper/introduction/tokenomics.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.