> For the complete documentation index, see [llms.txt](https://nora-2.gitbook.io/nora-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nora-2.gitbook.io/nora-docs/community-engagement.md). # Community Engagement At the heart of NORA’s development is a strong focus on community engagement. The success of any Web3 project is deeply intertwined with the involvement and feedback of its user base. NORA is dedicated to creating a community-first approach, where **users** have a **voice**, and their **feedback** directly influences the project’s direction. #### **9.1. Building Trust Through Transparency** One of NORA’s key values is **transparency**. The team regularly provides **progress updates**, shares **roadmaps**, and holds **community calls** to discuss project developments. By maintaining transparency about the project’s objectives and challenges, NORA builds trust and strengthens its bond with the community. * **Example**: Monthly **AMA (Ask Me Anything)** sessions are hosted on **Discord** or **Telegram**, where team members engage with the community, answer questions, and gather valuable feedback. This gives users a direct line to the team and a chance to shape the future of NORA. #### **9.2. Community Incentives** NORA rewards active participation through a variety of **community incentive programs**. Users who contribute by testing new features, providing valuable feedback, or creating content (tutorials, reviews, etc.) are rewarded with **NORA tokens**. * **Example**: **Referral programs** incentivize users to invite others to join the platform, allowing them to earn rewards and gain recognition within the community. Additionally, **content creators** who produce educational material, tutorials, or guides about the platform are rewarded for their efforts. #### **9.3. Governance and DAO** As a Web3 project, NORA believes in the power of **decentralized governance**. The platform's token holders are encouraged to participate in decision-making through the **DAO (Decentralized Autonomous Organization)**, where they can vote on key proposals, governance models, and future platform developments. * **Example**: NORA token holders have the power to vote on **platform upgrades**, **new features**, and **tokenomics changes**. This ensures that the community has a direct influence over the direction of the platform. #### **9.4. Educational Initiatives** To foster a stronger understanding of cryptocurrency, blockchain, and the NORA platform itself, NORA offers a variety of educational resources. The platform’s **community-driven content** and **tutorials** empower users to deepen their knowledge, enabling them to make informed decisions within the crypto space. * **Example**: Regularly updated **blogs**, **videos**, and **online webinars** will be available to guide users through the nuances of crypto and help them navigate the evolving landscape of Web3 technologies. --- # 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://nora-2.gitbook.io/nora-docs/community-engagement.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.