# Tokenomics **Token Structure Overview** The native cryptographically secure fungible protocol token of DIGARD, $DIGA, is a digital token-based representation of an executable programming script deployed on a blockchain network. It serves as a transferable representation of governance and utility functions specified in the protocol/code of DIGARD, designed as a~~n~~ utility token within the ecosystem. $DIGA is a functional multi-utility token facilitating decentralized exchange and settlement between participants on DIGARD without relying on intermediaries such as centralized institutions. It is not a publicly accepted medium of exchange and is exclusively for use within DIGARD’s ecosystem. $DIGA does not confer shareholding, ownership, or profit participation rights and is not intended as a security or investment in any jurisdiction. Ownership of $DIGA provides no rights beyond its utility within DIGARD, and its secondary market pricing is not influenced by any mechanisms or schemes controlled by DIGARD’s contributors. Tokens distributed during initial periods aim to fund project development, build market awareness, and encourage community engagement without constituting a regular business of token distribution. **Key Economic Role of $DIGA** $DIGA incentivizes contributions to and participation in DIGARD’s ecosystem, enabling a mutually beneficial structure where active participants are fairly compensated for their efforts. Non-participating users or passive holders of $DIGA do not receive incentives, ensuring that the ecosystem thrives on active engagement.The economic model of $DIGA revolves around interactions between DIGARD, Developers, and Users. **1. Economic Flow** DIGARD’s ecosystem consists of three core participants:**DIGARD Platform**:Provides foundational tools, infrastructure for apps and community activities. * **Developers**: Use DIGARD’s SDK/BDK for app integration, NFT/token launches, and analytics tools. **Developers**:Build and contribute to DIGARD’s ecosystem by creating games, NFTs, and other interactive features. * **Economic Contribution**: For integration services and tools. * **Incentives**: Developers receive $DIGA rewards based on app quality, user engagement, and ecosystem contribution. **Users**:Engage with DIGARD’s games, quests, and events, driving platform liquidity and interaction. * **Economic Participation**: Earn $DIGA by completing quests and engaging in community activities. * **Value Addition**: Player activities contribute to data generation and platform growth **2. Token Utility and Ecosystem Role** DIGARD's native token is integral to its ecosystem, serving multiple functions: * **Governance**: Token holders can participate in decision-making through a decentralized autonomous organization (DAO). * **Transaction Fees**: Facilitates seamless transactions and incentivizes network activities. * **Incentives**: Supports user acquisition by providing rewards for quests, user engagement, and ecosystem contributions. **3. Incentive Structures for Participants** To encourage participation across developers, users, and community members: * **Developer Incentives**: Tokens awarded for building on DIGARD or contributing tools to the ecosystem. * **User Rewards**: Tokens distributed for completing quests, staking, or achieving milestones. * **Community Engagement**: Airdrops and rewards for active community members and contributors. --- # 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://digard.gitbook.io/digard-whitepaper/tokenomics.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.