> For the complete documentation index, see [llms.txt](https://hakkafinance.gitbook.io/hakka-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hakkafinance.gitbook.io/hakka-wiki/hakka-token/token-metrics.md).
# Token Metrics
**NAME:** Hakka Finance\
\
**TYPE:** ERC-20 (Ethereum-based token)\
**SYMBOL:** HAKKA\
**CONTRACT ADDRESS:** 0x0E29e5AbbB5FD88e28b2d355774e73BD47dE3bcd\
**DECIMALS:** 18
\
**MAX SUPPLY:** 2,147,483,647 \
**TOTAL SUPPLY:** 635,982,513 (max supply - burned tokens)\
**CIRCULATING SUPPLY (As of 30th July 2021)**: \~228,379,180\
\
\
**After the 22nd of September, the following changes were made:**
1. 1,511,501,134 HAKKA (70.24% of Total Supply) were burned.\
(32% Liquidity Mining + 20% Future Sales + 17.5% Ecosystem Fund + 19M of Bootstrap Fund)
2. Bootstrap fund stakeholders and HAKKA team extended lockups and vesting. More than 2M HAKKA locked up for 24 months, and roughly 18M HAKKA (team tokens) vesting extended from 12 months to 21 months.
[**For source info and additional reading, please visit the financial statements article released by the core contributors.**](https://medium.com/hakkafinance/financial-statements-of-hakka-finance-646674369a3d)
---
# 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://hakkafinance.gitbook.io/hakka-wiki/hakka-token/token-metrics.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.