> For the complete documentation index, see [llms.txt](https://harmonic-protocol-1.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://harmonic-protocol-1.gitbook.io/documentation/security-and-trannsparency.md). # Security & Transparency #### Tokenomics Harmonic introduces a transparent and minimalistic token distribution model designed to align incentives between users, validators, and the protocol:\ \ A total supply of **100,000,000 HARMO** tokens will be issued. During the initial mint phase, **66% of the total supply (66,000,000 HARMO)** will be available for users to mint directly through the protocol. Once the minting phase is completed, **33% of the supply** will be added as **liquidity** to ensure stable market depth and long-term sustainability. The remaining **1%** will be allocated to the **Harmonic Treasury**, supporting future development and ecosystem initiatives. #### Smart Contracts All Harmonic contracts - including the router, factory, and validator registry - are **fully verified and public** on the Base explorer. They can be audited and reviewed by anyone to ensure transparency and fairness. #### Permanent Integrity Each 402 request includes: * The user’s signature * A backend-verified signature confirming it comes from the Harmonic dApp * A nonce to prevent replay Once a trade is validated, it cannot be reversed or replayed. All liquidity and transfers are handled through the router, ensuring a secure and predictable flow. #### Risk Notes Harmonic is an experimental protocol. Although designed for transparency and fairness, it introduces new mechanisms (human validation, bribes, gasless trading) that may behave unpredictably under high load or malicious usage. Users and validators participate **at their own risk**. --- # 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://harmonic-protocol-1.gitbook.io/documentation/security-and-trannsparency.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.