# Platform Fee Structure and Holder Tiers VINOS is used to pay for services on the Invinos platform, including access to the zkMixer, AI modules, and future encrypted utilities. Rather than using a flat fee, Invinos implements a dynamic pricing model that rewards holders and supports platform sustainability. #### Platform Service Fees * **1% fee** is applied to standard users with no token holdings. * **0.5% fee** is applied to users holding 100,000 or more VINOS. * **0.25% fee** is applied to users holding 250,000 or more VINOS. * **0.1% fee** is applied to users holding at least 1% of the total supply. Fees are calculated and processed within the app using local logic. There is no wallet connection, login, or identity requirement. #### Holder Tiers Different holding levels unlock different types of utility. However, only one tier grants actual access to new platform features. * Holding **100,000 VINOS** grants fee reduction only. * Holding **250,000 VINOS** grants a higher discount but no feature unlocks. * Holding **1% of the total supply** grants the highest fee discount available but still no platform access. * Holding **1,000,000 VINOS or more** is the only way to receive early access. This tier unlocks new features before public release, access to internal betas, unreleased modules, and special testing environments. This design ensures that early access is reserved for users deeply invested in the platform. --- # 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://invinos.gitbook.io/invinos/vinos-tokenomics/platform-fee-structure-and-holder-tiers.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.