# Zero Authority Docs! 🌐 Trustless layer for reputation, gigs, bounties & endorsements! Join us! 🎉 Here you'll find everything you need to know about the DAO.
## Decentralized Autonomous Organization Zero Authority is a decentralized autonomous organization that leverages the power of blockchain technology to create a community-driven ecosystem that empowers individuals to govern, fund, and launch Web3 projects in a transparent and decentralized way. ## The Pseudonymous Economy The Pseudonymous Economy has the potential to enable a new wave of innovation and entrepreneurship by leveraging decentralized networks to build reputation and trust based on individuals' actions and contributions. This can create new opportunities for businesses and communities to emerge outside of traditional institutions and hierarchies, and foster collaboration among individuals from diverse backgrounds and geographies. The use of pseudonyms can also provide individuals with greater privacy and autonomy in online interactions, which can be particularly important in a world of increasing surveillance and data breaches. Overall, the Pseudonymous Economy presents a promising vision for a more open, decentralized, and inclusive economy that can benefit individuals and communities worldwide. ## Reference Reputation Onchain: Your Trustless Layer for Gigs, Bounties, and Endorsements. Please join tribe 🏹 to keep up to date. {% embed url="" %} Please message us on discord or twitter anytime. Zero (XYZERO) James (HODLSTX) Haddy Find us on verified channel # Vision and Values The Vision and Values page is an important resource for anyone who wants to learn more about the organization, including potential employees, investors, partners, and customers. ## Our Vision Our vision is to create a world where individuals can leverage the full potential of decentralized technology to take control of their digital lives. We aim to foster a community of lifelong learners who are passionate about decentralization, innovation, and collaboration. Through the Cerulean Marketplace, we provide a trustless and permissionless platform for creators and clients to connect, democratizing access to Web3 projects and creating new opportunities for economic growth and positive change. Our ultimate goal is to build a sustainable, user-owned internet that empowers individuals to create, transact, and collaborate in a decentralized and secure way, leading to a world where technology is used to create positive social impact. ## Our Values #### Respect We expect all members of our community to demonstrate mutual respect and courtesy towards one another. We believe that fostering a culture of respect and empathy is essential for building a welcoming and inclusive community. #### Buidl We are committed to building public goods and compassionate technology that benefit society. We believe that achieving this requires us to be transparent, open, and honest in our approach. We do not believe in gatekeeping or creating unnecessary barriers that may hinder progress. #### Transparency We believe that public goods should be built in a way that is visible and accessible to the public as much as possible. We are committed to promoting transparency in all aspects of our work and making our processes and decisions open and accessible to everyone. We believe that transparency is essential for fostering trust and accountability within our community. # Meet the core team Core Contributors Day-to-Day Responsibilities **Zero Authority Core Contributors**
The Zero Authority Core Team operates at the heart of the DAO, driving both technical development and community engagement on a daily basis. * **Protocol Strategy Lead: Zero** [X/twitter](https://x.com/xyzerobtc) [LinkedIn](https://www.linkedin.com/in/zefrenedior/) [Telegram](http://t.me/xyzerobtc) [ZeroAuthority](https://www.zeroauthoritydao.com/profile/SP7QQ9DV0DMV7YW4HR713MKBWADVA0BFC2J65PJT) * Focus: Revenue opportunities, partnerships, and brand development. * Responsible for identifying and executing strategic initiatives that drive growth and position the protocol within the broader market. * **Protocol Technology Lead: Hodlstx** [X/twitter](https://x.com/hodlstx) [Telegram](https://t.me/Hodlstxbtc) [ZeroAuthority](https://www.zeroauthoritydao.com/profile/73d2584c-9c95-495e-8206-12cc1539f49c) * Focus: System architecture, engineering, and scaling. * Oversees the technical direction, ensuring the protocol's infrastructure is robust, scalable, and capable of supporting future developments. * **Protocol People Lead: Haddy** [X/twitter](https://x.com/BrendynHadfield) [LinkedIn](https://www.linkedin.com/in/brendyn-hadfield/) [Telegram](https://t.me/Haddy13) [ZeroAuthority](https://www.zeroauthoritydao.com/profile/bd49fb47-7571-42f5-8ec6-0331fcfb9676) * Focus: Brand and marketing, promotion, social media, community engagement, and feedback. * Manages the protocol's public image, fosters community relationships, and channels community feedback into actionable insights. * **Smart Contracts & Protocol Developers:** * Haz ([X/twitter](https://x.com/hzDotBTC)), Sushil ([X/twitter](https://x.com/sushilg38059171)), Ghislo ([X/twitter](https://x.com/Ghislo749_) [Telegram](https://t.me/ghislo749)) * Focus: Engineering, design, platform development, and backend development. * Responsible for building and maintaining the protocol’s core systems, ensuring a seamless and secure user experience. #### Key Contributions from DAO Members: Here are the key contributions from DAO members with the new bullet added: * **3hunna, Grimaldo, BeeBrain:** These members are integral to community support, writing, blogging, content creation, and the development services that help the protocol grow and support clients, creators, and administrators * **Jackbinswitch, TheAdvisor, PeaceLoveMusic, GoodKitty, Gordon, Haddy, ElectraFrost:** These members are integral to community support, writing, blogging, and the development of reputation badges. Their efforts help foster a vibrant and informed community.**KennyTheRodgers:** Full-stack and Clarity developers contribute to the ongoing development and enhancement of Zero Authority’s technical infrastructure. * **KennyTheRodgers:** Full-stack and Clarity developers contribute to the ongoing development and enhancement of Zero Authority’s technical infrastructure. * **Mariaverse:** Full-stack and Clarity developers contribute to the ongoing development and enhancement of Zero Authority’s technical infrastructure. * **Gary:** Full-stack and Clarity developers contribute to the ongoing development and enhancement of Zero Authority’s technical infrastructure. * **Degen Labs:** Full-stack and Clarity developers contribute to the ongoing development and enhancement of Zero Authority’s technical infrastructure. * **Red Block Labs:** Full-stack and front end developers contribute to the ongoing development and enhancement of Zero Authority’s user interface. * **HeroGamer:** As the DeGrants lead, HeroGamer plays a crucial role in managing grants and ensuring that funded projects align with the mission of Zero Authority. * **Kurt:** Kurt supports the community through video production and social media management, helping to amplify Zero Authority’s message across various platforms. Together, the Core Team and DAO contributors ensure that Zero Authority remains at the forefront of decentralized reputation management, continually pushing the boundaries of what’s possible on-chain. # How to contribute to the DAO Learn how to contribute to a Decentralized Autonomous Organization (DAO) with this page's comprehensive list, including voting, submitting proposals, and providing expertise. **Zero***Authority* DAO (Decentralized Autonomous Organizations) is a community-driven entity that operate on the Stacks blockchain network. As a result, contributing to the DAO is quite different from contributing to a traditional organization. Contribute to the DAO: * Participate in discussions: DAOs often have forums or chat groups where members can discuss various topics related to the organization. By participating in these discussions, you can contribute your ideas and help shape the direction of the DAO. * Provide expertise: If you have specialized skills or knowledge that could be useful to the DAO, you can offer to provide your expertise. For example, if the DAO is focused on developing a new blockchain platform, you could offer to help with the coding or provide insights on the market. * Spread the word: DAOs rely on their community to grow and thrive. By spreading the word about the organization, you can help attract new members and increase the DAO's influence. * Contribute to open source projects: Many DAOs are built on open source technology, and contributing to these projects can help improve the overall ecosystem. By contributing code, documentation, or bug fixes, you can help ensure the success of the DAO and the broader blockchain community. Contributions continue to evolve. There are many ways to contribute to the DAO today, from purchasing tokens to providing expertise or contributing to open source projects. As a community-driven entity, the DAO relies on the participation of their members to succeed, and your contributions can make a significant difference. # How to reward contributions Discover how to reward contributions in a Decentralized Autonomous Organization (DAO) with this page's overview, including tokens, reputation, financial and non-financial incentives, and token burn. Rewards in the **Zero***Authority* DAO (Decentralized Autonomous Organization) can be distributed in various ways depending on the specific governance model and the goals of the organization. Common ways to reward contributions in the DAO: * Vote on proposals: DAO members have the power to vote on proposals, such as funding requests or changes to the organization's rules. You can participate in these votes by holding the native tokens and using them to cast your vote. * Submit proposals: As a member of a DAO, you can also submit proposals for consideration. These proposals can range from requesting funding for a project to suggesting changes to the organization's rules. * Participate in discussions: DAOs often have forums or chat groups where members can discuss various topics related to the organization. By participating in these discussions, you can contribute your ideas and help shape the direction of the DAO. * Provide expertise: If you have specialized skills or knowledge that could be useful to the DAO, you can offer to provide your expertise. * Spread the word: The DAO relies on their community to grow and thrive. By spreading the word about the organization, you can help attract new members and increase the DAO's influence. * Contribute to open source projects: The DAO is built on open source technology, and contributing to these projects can help improve the overall ecosystem. By contributing code, documentation, or bug fixes, you can help ensure the success of the DAO and the broader blockchain community. * Native Tokens: The DAO has our own native $Zero token that can be used to incentivize contributions. These tokens can be distributed to members who have made significant contributions to the organization, such as submitting successful proposals or providing expertise on a project. * Reputation: The DAO use a reputation system to reward contributions. Members earn reputation points based on their contributions to the organization, such as submitting proposals or participating in discussions. The more reputation a member has, the more influence they have in the governance of the DAO. * Bounty: The DAO might offer a bounty for finding and fixing a bug in their code or provide funding for a project that aligns with the organization's goals. * Non-Financial Incentives: The DAO offer non-financial incentives to reward contributions. These incentives can include access to exclusive events, mentorship opportunities, or recognition within the community. * Tokens with Lockup Periods: The DAO distributes tokens with lockup periods as rewards. This means that the tokens cannot be sold or transferred for a set period of time, incentivizing members to hold on to their tokens and remain active in the community. * Token Burn: The DAO will have a portion of the tokens burned (i.e., permanently destroyed) as a way of rewarding contributions. By reducing the total supply of tokens and incentivizing members to hold on to their tokens and contribute to the DAO. # Zero Authority Solutions Overview of Zero Authority DAO **Launch and Features:** Zero Authority DAO launched the Gig Marketplace on November 25, 2023, marking a significant milestone in on-chain innovation. This platform empowers users with Hiro and Xverse login options, granting full ownership of their Web3 profiles. Designed to champion the pseudonymous economy, the Marketplace allows individuals to explore opportunities and contribute to projects without being tied to a single identity, fostering a landscape ripe for innovation and flexibility. {% embed url="" %} Please give us feedback {% endembed %} **Pseudonymous Economy:** The pseudonymous economy reimagines how individuals work and interact in the digital space. By leveraging decentralized networks, users can build trust and reputation based on their actions and contributions, rather than traditional identifiers. This approach provides users with greater privacy and autonomy, enabling participation in economic activities without compromising their identities. **Key Benefits for Web3 Users:** 1. **Empowerment through Pseudonymity:** * **Role Exploration:** Users can engage in various roles and projects, pursuing diverse interests and skills without being confined to a single identity. * **Identity Management:** Pseudonyms allow users to maintain control over their personal data and interactions, enhancing their ability to manage multiple facets of their professional and personal lives. 2. **Facilitating Innovation and Collaboration:** * **Global Connectivity:** The Marketplace connects users from different backgrounds and geographies, encouraging collaboration and the creation of innovative solutions. * **Decentralized Participation:** By removing traditional barriers, users can participate in projects and initiatives based on merit and contribution, rather than relying on institutional affiliations. 3. **Enhancing Privacy and Security:** * **Protection from Surveillance:** Increased privacy reduces the risk of data breaches and unauthorized access to personal information. * **Trustless Transactions:** The platform enables secure, transparent interactions, allowing users to engage in economic activities with confidence. **Solutions Offered by Zero Authority DAO Gig Marketplace:** 1. **Gig Opportunities:** * **For Creators:** Creators can offer their services in a secure and permissionless environment, reaching clients interested in Web3 projects. * **For Clients:** Clients can hire skilled individuals for Web3 project work through a peer-to-peer trustless network, ensuring transparency and efficiency. 2. **Bounty System:** * **Engagement:** The platform includes a bounty system to incentivize community engagement and contributions, allowing users to earn rewards for completing tasks and solving challenges. * **Transparency:** Bounties are posted with clear criteria and rewards, ensuring participants understand the expectations and outcomes. 3. **Endorsements:** * **Reputation Building:** Endorsements from peers and clients play a crucial role in building trust and credibility within the Marketplace. * **Verification:** Users can receive endorsements based on their performance and contributions, enhancing their reputation and attracting more opportunities. **Vision:** Inspired by Balaji's vision of the pseudonymous economy in 2019, Zero Authority DAO developed the "Gig" Cerulean Marketplace. The platform envisions a world where individuals can earn under one name, speak under another, and use their real name only when necessary. The Zero Authority DAO Gig Marketplace is a platform that empowers Web3 users to achieve their goals through a decentralized, innovative, and secure ecosystem. By embracing the principles of the pseudonymous economy, the Marketplace fosters a more open and inclusive digital economy, enabling individuals to thrive and contribute to a better future. For more information, visit our linktree. # Reputation Onchain Overview of peer-to-peer creators in a decentralized age **For Organizations:** * *Post Opportunities:* Organizations can leverage Trajan to post job opportunities or projects within the pseudonymous Bitcoin space, facilitating the connection with top talent. * *Find Top Pseudonymous Talent:* The platform offers a search and discovery mechanism for organizations to identify and engage with skilled individuals within the pseudonymous Bitcoin community. **For Individuals:** * *Find Opportunities:* Pseudonymous Bitcoin builders can explore posted opportunities on Trajan, opening doors to potential collaborations and projects. * *Build a Professional Pseudonymous Reputation:* Individuals can establish and enhance their professional reputation within the pseudonymous Bitcoin ecosystem by earning endorsements on the platform. **Frequently Asked Questions (FAQs):** 1. *Are TRAJAN NFTs transferable? Can I buy or sell NFTs on Trajan?* * No, TRAJAN NFTs are not transferable, and buying or selling NFTs on Trajan is not supported. 2. *Do you support Ordinal inscriptions?* * Not yet, but it is mentioned that support for Ordinal inscriptions is on the roadmap. 3. *Do I need to own a .btc or other Stacks BNS name to create a profile?* * Yes, currently, ownership of a .btc or other Stacks BNS name is required to create a profile. However, there is consideration for allowing registration with just a Stacks address in the future. 4. *Which wallets can I use with Trajan?* * Trajan supports two Stacks/Bitcoin Ordinals wallets, namely Xverse and Hiro. Users are advised to use only one wallet per browser to avoid potential errors. 5. *Do I need to own Stacks token STX to use Trajan?* * Yes, owning Stacks token (STX) is currently a requirement to use Trajan. 6. *What are the fees to give an endorsement?* * The only fee associated with giving an endorsement is the blockchain transaction fee, typically just a few cents. Trajan does not impose any additional service fees. Trajan Endorsement focuses on fostering connections and collaborations within the pseudonymous Bitcoin community, providing a dedicated space for individuals and organizations to engage and grow professionally. # Email Notification Overview email notifications for activities Introduction Users to receive email notifications for key activities related to gigs. This feature is designed to enhance user engagement and communication by keeping both creators and clients informed about their gig activities. #### How to Enable Email Notifications To start receiving email notifications, users must connect their wallet and update their profile with an active email address. This ensures that notifications are sent to the correct address associated with their account. #### Why Email Notifications Help Users Email notifications provide users with timely updates and reminders about important gig-related activities. They help improve the overall user experience by: * Keeping users informed about the status of their gigs. * Reducing response times by notifying users promptly about actions taken on their gigs. * Increasing transparency and trust by maintaining clear communication between creators and clients. * Enabling users to manage their gigs more efficiently by staying up to date. #### How Email Notifications Work Once a user has connected their wallet and added an active email address to their profile, they will start receiving notifications for specific actions related to gigs. These notifications are triggered automatically based on the activity flow of the gigs. #### Notification Process The email notification process is outlined as follows: 1. **Email to the Creator When Gig Request**: * The creator receives an email when a new gig request is submitted by a client. * This email includes details about the gig request, allowing the creator to review and respond promptly. 2. **Email to Client When Gig Accepted**: * The client receives an email when their gig request is accepted by the creator. * The email contains information about the acceptance and any additional details provided by the creator. 3. **Email to Client When Gig Declined**: * The client receives an email when their gig request is declined by the creator. * The email provides the client with a reason for the decline and any feedback from the creator. 4. **Email to Creator When Satisfaction Vote as Client**: * The creator receives an email notification when a satisfaction vote is submitted by the client. * This email includes the client's feedback and rating, helping the creator understand their performance. 5. **Email to Client When Satisfaction Accepted from the Artist/Creator**: * The client receives an email when the creator accepts the satisfaction vote. * This email confirms that the creator acknowledges the client's feedback, promoting a positive feedback loop. This procedure ensures that all parties involved in gig activities are well-informed and can act accordingly based on the notifications received. # Nova AI Bots Introducing Zero Authority AI & Bots **NOVA** is your all-in-one AI-powered assistant for running high-performing Web3 communities. Whether you're managing bounties, tracking wallets, detecting onchain activity, or enabling in-chat crypto swaps, NOVA’s suite of smart bots simplifies your operations and scales your community—without ever leaving Telegram or Discord. *** #### 🔥 **Benefits** * **Save Time & Resources** – Automate repetitive tasks like bounty payouts, alerts, and reputation tracking. * **Boost Engagement** – Stay connected to your community with real-time updates and seamless in-chat interactions. * **Increase Transparency** – Keep everything visible and verifiable with onchain automation and AI-powered summaries. * **Scale Confidently** – Manage more users, gigs, and projects without increasing manual effort. *** #### ⚙️ **Features** **✅ Wallet & Address Tracker** Monitor wallet transactions and track up to 3 addresses in real-time. **✅ Instant Trade Alerts** Get notified the moment high-value trades or token swaps occur. **✅ NFT & Token Discovery** Never miss a listing again—get alerts when new NFTs or tokens hit the market. **✅ In-Chat Crypto Swaps** Buy and sell crypto directly within Telegram or Discord, no extra tools needed. **✅ AI Smart Reports** From stacker activity summaries to trend detection, NOVA delivers concise reports powered by AI. **✅ Decentralized Reputation Bots** Issue and display trustless scores and endorsements onchain for contributors and community members. *** #### 🔹 **Free Tribe Membership** Perfect for beginners or casual users. * 🛎️ Token & NFT Alerts (5+ P2E tokens, NFTs, and wallets) * 👤 Address Tracker (up to 3 wallets) * 🔗 Telegram & Discord Integration (invite bot to your server) * 💸 Start for free, no payment required *** #### 🔸 **Premium Tribe Membership** For power users ready to scale. * 📊 **3 Stacks per Month** (expand capacity) * 🧠 **Stacks Daily Report** – Full summaries of wallet, trade, and reputation activity * 🔍 **Advanced Market Alerts** – Catch big movements before the crowd * 🔍 **Malicious Contracts Deployed Alerts** – Catch wallet drainers before they strike * 🛡️ **Reputation Bot** – Onchain trust system with scoreboards * 📥 **AI Blocker** – Instantly filter spam in 1 Telegram + 1 Discord channel * 📈 Scales with your community growth *** #### 🤖 **AI Bots for Zero Authority** * **Gig Bot** – Post and manage gigs with rep tracking and payment automation. * **Bounty Bot** – Automate bounty programs and DAO tasking. * **Reputation Bot** – Track onchain rep, score users, and show verifiable badges. *** #### 🌌 Let AI do the heavy lifting — try NOVA now. *** Want this in a shorter social post, onboarding email, or pricing page format too? # Standard Reputation Framework Reputation Framework User Guide V.0.1 first draft. Reputation and NFT Minting for Reputation Badges. **Created**: 2024-05-01\ **License**: MIT License ### Abstract This SIP proposes a framework for implementing a standardized reputation system on apps or websites. Reputation transactions will result in the minting of Non-Fungible Tokens (NFTs) to provide a verifiable and immutable record of reputation events. The proposal outlines standard attributes for reputation systems, the structure for XML and JSON representation, and the NFT minting process.

rep badges concepts

### Motivation A standardized blockchain-based reputation system transforms trust into a transparent, portable, and user-owned digital asset. Immutable on-chain records make reputation auditable, replacing blind trust with verifiable integrity. Standardized attributes enable interoperability, allowing users to carry their reputation across platforms instead of rebuilding it in every ecosystem. Minted NFTs redefine ownership by giving individuals direct control over their reputation as verifiable digital proof, rather than as data locked inside centralized systems. Gamification layers create incentive structures that reward positive behavior, contribution, and engagement, turning participation into a self-reinforcing cycle of value creation. Together, these elements form more than infrastructure—they create a social protocol where trust is earned, composable, and embedded directly into the architecture of the network itself. A standardized reputation system provides several benefits. 1. **Transparency and Trust**: Immutable records of reputation transactions increase transparency. 2. **Interoperability**: Standard attributes allow consistent implementation across platforms. 3. **Ownership**: Minted NFTs serve as proof of ownership, providing users with verifiable reputation. 4. **Gamification**: NFTs incentivize positive behavior and engagement. ### Specification #### Standard Attributes **User Information** * **user\_id**: A unique identifier for the user. * **username**: The display name of the user. * **profile\_url**: URL to the user's profile. **Reputation Event** * **event\_id**: A unique identifier for the reputation event. * **event\_type**: The type of reputation event (e.g., upvote, review). * **event\_description**: Description of the event. * **event\_timestamp**: Timestamp when the event occurred. * **event\_value**: Reputation change value (positive or negative). **NFT Information** * **nft\_id**: Unique identifier for the minted NFT. * **nft\_url**: URL to the NFT on the blockchain. * **nft\_metadata**: Metadata associated with the NFT, including details of the reputation event. #### Clarity Code Representation ```clarity (define-data-var user_id (string-ascii 50) "unique-user-id") (define-data-var username (string-ascii 50) "username") (define-data-var profile_url (string-ascii 100) "https://example.com/user/profile") (define-data-var event_id (string-ascii 50) "unique-event-id") (define-data-var event_type (string-ascii 20) "upvote") (define-data-var event_description (string-ascii 100) "Received an upvote on a comment") (define-data-var event_timestamp (buff 32) 0x1234567890abcdef) (define-data-var event_value int 10) (define-data-var nft_id (string-ascii 50) "unique-nft-id") (define-data-var nft_url (string-ascii 100) "https://blockchain.com/nft/unique-nft-id") (define-data-var nft_metadata (buff 1024) 0xBase64EncodedMetadata) ``` #### NFT Minting Process 1. **Event Trigger**: A reputation event occurs (e.g., user receives an upvote). 2. **Data Aggregation**: Necessary data is collected. 3. **NFT Creation**: NFT is generated with event data as metadata. 4. **Blockchain Interaction**: The platform interacts with a blockchain service to mint the NFT. 5. **Storage and Access**: The NFT’s URL and metadata are stored in the platform’s database and linked to the user’s profile. ### Rationale By leveraging blockchain technology, this framework ensures transparency and trustworthiness. Standardizing attributes and using NFTs to represent reputation events gives users ownership of their reputation, which can be showcased across platforms. ### Backward Compatibility This proposal introduces a new system and does not affect existing implementations. Platforms adopting this standard will need to integrate the reputation framework and NFT minting process. ### Implementation Key steps include: 1. **Database Changes**: Modify database structures to store reputation and NFT attributes. 2. **Blockchain Integration**: Develop logic to interact with blockchain services for NFT minting. 3. **API Development**: APIs must handle reputation transactions and provide data in the defined formats. 4. **Frontend Changes**: Update UI to display reputation and NFT information. ### Security Considerations * **Data Privacy**: Ensure proper handling of user data with consent. * **Blockchain Risks**: Consider risks related to transaction costs and delays in blockchain interaction. ### Conclusion This SIP offers a standardized approach for integrating reputation systems with blockchain technology. By minting NFTs for each reputation transaction, the framework ensures transparency, verifiability, and ownership, enhancing trust and engagement on decentralized platforms. common criteria to build reputation badges {% content-ref url="/pages/JtPZF7tolRF7DrOfjo3g" %} [15 Common Categories](/the-dao/standard-reputation-framework/15-common-categories) {% endcontent-ref %} implementation guide {% content-ref url="/pages/PKUSYRMtoBPkjgu5OJse" %} [Clarity & JSON Implementation](/the-dao/standard-reputation-framework/clarity-and-json-implementation) {% endcontent-ref %} clarity code to deploy on the blockchain {% content-ref url="/pages/6H4CLdiAcT2qG35f4bvK" %} [Clarity Contract](/the-dao/standard-reputation-framework/clarity-contract) {% endcontent-ref %} metadata file to create for standard deployment {% content-ref url="/pages/RbQUjZACacvApi4ucTet" %} [JSON Metadata](/the-dao/standard-reputation-framework/json-metadata) {% endcontent-ref %} thank you! # 15 Common Categories To Build Reputation Onchain ### **Summary** This SIP introduces a standardized framework for reputation systems on decentralized platforms, using NFTs to represent reputation events. It ensures transparency, interoperability, and user ownership of reputation data. The framework defines key attributes for reputation events, user data, and NFT minting, enhancing trust and engagement across apps and websites. *** ### 1. **Community Engagement** * **Description**: Participation in community activities like forum posts, comments, social media interactions. * **Attributes**: * user\_id * engagement\_type (post, comment) * engagement\_timestamp * engagement\_value (likes, replies) ### 2. **Transaction History** * **Description**: Quality of transactions in marketplaces or financial services. * **Attributes**: * user\_id * transaction\_id * transaction\_type (purchase, sale) * transaction\_timestamp * transaction\_value ### 3. **Content Creation** * **Description**: Contribution of content like blog posts or videos. * **Attributes**: * user\_id * content\_id * content\_type (blog, video) * content\_timestamp * content\_value (views, likes) ### 4. **Skill Verification** * **Description**: Verification of skills through endorsements or certifications. * **Attributes**: * user\_id * skill\_id * skill\_name * verification\_timestamp * verifier\_id ### 5. **Project Contributions** * **Description**: Contributions to open-source or collaborative projects. * **Attributes**: * user\_id * project\_id * contribution\_type (code, docs) * contribution\_timestamp * contribution\_value (commits, PRs) ### 6. **Review and Feedback** * **Description**: Feedback provided for products or services. * **Attributes**: * user\_id * review\_id * review\_type (product, service) * review\_timestamp * review\_rating ### 7. **Attendance and Participation** * **Description**: Participation in events or conferences. * **Attributes**: * user\_id * event\_id * event\_type (webinar, conference) * event\_timestamp * participation\_value ### 8. **Mentorship and Coaching** * **Description**: Mentoring or coaching activities. * **Attributes**: * user\_id * mentee\_id * mentorship\_type (session, advice) * mentorship\_timestamp * mentorship\_value (hours, impact) ### 9. **Achievements and Awards** * **Description**: Recognition for achievements. * **Attributes**: * user\_id * achievement\_id * achievement\_type (award, milestone) * achievement\_timestamp * achievement\_value ### 10. **Learning and Development** * **Description**: Completion of courses or certifications. * **Attributes**: * user\_id * course\_id * course\_name * completion\_timestamp * course\_score ### 11. **Bug Reporting and Issue Resolution** * **Description**: Reporting and resolution of issues. * **Attributes**: * user\_id * issue\_id * issue\_type (bug, feature request) * issue\_timestamp * issue\_status ### 12. **Reputation and Endorsements** * **Description**: Endorsements or reputation points from peers. * **Attributes**: * user\_id * endorsement\_id * endorsement\_type (skill, character) * endorsement\_timestamp * endorser\_id ### 13. **Compliance and Certifications** * **Description**: Compliance with standards or certifications. * **Attributes**: * user\_id * certification\_id * certification\_name * certification\_timestamp * certifying\_body ### 14. **Social Impact and Volunteering** * **Description**: Participation in social impact or volunteering. * **Attributes**: * user\_id * activity\_id * activity\_type (volunteering, donation) * activity\_timestamp * activity\_value (hours, impact) ### **15. User Feedback Review for Satisfaction** **Description**: A system for users to leave feedback and rate their satisfaction with a product or service using a 5-star scale. **Attributes**: * `user_id`: The identifier for the user providing the review. * `review_id`: Unique identifier for the feedback or rating instance. * `rating`: The number of stars given, ranging from 1 to 5. * `review_type`: Indicates the type of review (e.g., "purchase" or "service"). * `comment`: Optional written feedback or comments from the user to accompany the rating. *** ### **Conclusion**: By integrating blockchain technology, this SIP provides a reliable, verifiable way to manage reputation through NFTs, fostering user trust and incentivizing positive contributions across decentralized platforms. Its standardized approach promotes broader adoption and seamless reputation management across ecosystems. # Clarity & JSON Implementation To create a **Reputation (REP) badge** using Clarity and JSON, you need to manage onchain logic with Clarity and define metadata with JSON. ### Clarity {% content-ref url="/pages/6H4CLdiAcT2qG35f4bvK" %} [Clarity Contract](/the-dao/standard-reputation-framework/clarity-contract) {% endcontent-ref %} The Clarity contract facilitates batch endorsements, allowing authorized users to issue badges to multiple recipients. It verifies the issuer's authority and manages the process of adding badges (endorsements) to users' profiles. Key functions include `add-badge` (adds a badge to a user) and `endorse` (issues badges to multiple users at once). ### JSON {% content-ref url="/pages/RbQUjZACacvApi4ucTet" %} [JSON Metadata](/the-dao/standard-reputation-framework/json-metadata) {% endcontent-ref %} The JSON metadata defines the badge's attributes, such as its name, description, image, and criteria. It helps visually represent the badge and provides context, like the number of events engaged in or the date issued. Example structure: ```json { "name": "Community Engagement Badge", "description": "Awarded for actively engaging in community events.", "image": "https://example.com/badges/community-engagement.png", "attributes": [{"trait_type": "Engagement", "value": "5 events"}] } ``` Together, Clarity handles issuing the badge, and JSON defines its visual and contextual properties. # Clarity Contract Allowing authorized users to issue badges to multiple recipients Clarity: The Clarity contract facilitates batch endorsements, allowing authorized users to issue badges to multiple recipients. It verifies the issuer's authority and manages the process of adding badges (endorsements) to users' profiles. Key functions include `add-badge` (adds a badge to a user) and `endorse` (issues badges to multiple users at once). Here's the formatted clarity code for docs. ```clarity ;; title: template-batch-endorsements ;; version: 1.0 ;; summary: A template for batch minting endorsements as non-fungible tokens (NFTs). ;; description: This contract allows for the minting of endorsement NFTs in batches, with predefined error handling and ownership management. (impl-trait 'SP2PABAF9FTAJYNFZH93XENAJ8FVY99RRM50D2JG9.nft-trait.nft-trait) ;; traits ;; This contract implements the NFT trait for endorsement tokens. ;; token definitions (define-non-fungible-token endorsement uint) ;; constants ;; (VAR) changes based on the number of recipients (define-constant TOTAL u500) ; Total number of tokens to be minted (define-constant ERROR-NOT-IMPLEMENTED u1) ; Error code for not implemented functionality (define-constant ERROR-UNAUTHORIZED u1000) ; Error code for unauthorized actions (define-constant ERROR-ALREADY-MINTED u1001) ; Error code for already minted tokens ;; (VAR) changes based on the collection IPFS hash (define-constant IPFS-ROOT "ipfs://ipfs/bafybeicvtqlmtj6hoed4ctxbmpxegk7fdhid437qmafbhlweuwgbqtwtky/json/{id}.json") ;; data vars (define-data-var last-token-id uint u0) ; Variable to track the last minted token ID ;; data maps (define-map awarded-addresses principal bool) ; Map to track awarded addresses (define-map minters principal bool) ; Map to track authorized minters ;; public functions ;; Function to mint new NFTs (define-private (mint (address principal)) (let ( (token-id (+ u1 (var-get last-token-id))) ; Generate the next token ID ) (var-set last-token-id token-id) ; Update the last token ID (nft-mint? endorsement token-id tx-sender))) ; Mint the NFT ;; Function to prevent transfer of NFTs (define-public (transfer (id uint) (sender principal) (recipient principal)) (err ERROR-NOT-IMPLEMENTED)) ; Returns error for transfer attempts ;; Function to burn an NFT (define-public (burn (id uint)) (let ( (owner (unwrap! (nft-get-owner? endorsement id) (err ERROR-UNAUTHORIZED))) ; Get current owner ) (asserts! (is-eq owner tx-sender) (err ERROR-UNAUTHORIZED)) ; Ensure caller is the owner (nft-burn? endorsement id owner))) ; Burn the NFT ;; read-only functions ;; Function to get the last token ID (define-read-only (get-last-token-id) (ok TOTAL)) ; Returns the total number of tokens ;; Function to get the owner of a token (define-read-only (get-owner (id uint)) (ok (nft-get-owner? endorsement id))) ; Returns the owner of the specified token ;; Function to get the token URI (define-read-only (get-token-uri (token-id uint)) (ok (some IPFS-ROOT))) ; Returns the IPFS URI for the token ;;; Mint calls here just need to change the addresses (mint 'ST1PQHQKV0RJXZFY1DGX8MNSNYVE3VGZJSRTPGZGM) ; Minting for address 1 (mint 'ST1SJ3DTE5DN7X54YDH5D64R3BCB6A2AG2ZQ8YPD5) ; Minting for address 2 (mint 'ST2CY5V39NHDPWSXMW9QDT3HC3GD6Q6XX4CFRK9AG) ; Minting for address 3 ``` #### Code Breakdown * **Metadata Section**: Provides basic information about the contract. * **Constants**: Defines total tokens and error codes. * **Data Variables and Maps**: Tracks the last minted token and addresses involved in minting and awards. * **Public Functions**: * **Minting Function**: Allows minting of NFTs and updates the last token ID. * **Transfer Function**: Prevents token transfer with an error message. * **Burn Function**: Allows the owner to burn their NFT. * **Read-Only Functions**: For retrieving token ID, owner, and token URI. * **Mint Calls**: Examples of minting NFTs for specific addresses. Feel free to modify the descriptions and version number as needed! # JSON Metadata Defines the badge's attributes, such as its name, description, image, and criteria The JSON metadata defines the badge's attributes, such as its name, description, image, and criteria. It helps visually represent the badge and provides context, like the number of events engaged in or the date issued. Here's the JSON structure formatted for docs. ```json { "sip": 16, "name": "Community Engagement #", "description": "", "image": "ipfs://ipfs/", "attributes": [ { "trait_type": "user_id", "value": "" }, { "trait_type": "engagement_type", "value": "" }, { "trait_type": "engagement_timestamp", "value": "" }, { "trait_type": "engagement_value", "value": "" } ] } ``` Feel free to replace the placeholders (like ``, ``, and ``) with the actual data you plan to use! # A New Standard for Trust in Web3 Zero Authority, the EigenTrust Algorithm & the Future of Reputation
In the decentralized future we’re building, reputation is not given—it’s **earned**, **measured**, and **composed** across the network. At **Zero Authority**, we envision a world where your onchain contributions speak louder than your clout, where trust isn’t dictated by centralized platforms, but **emerges organically** from your work, your collaborations, and your impact. To get there, we’re merging two powerful ideas: * The **Standard Reputation Framework**: an open system where anyone can award reputation for meaningful contributions. * The **EigenTrust algorithm**: a decentralized method for computing global trust based on local experiences. Together, they form a foundation for a **trustless trust system**—a future where you own your reputation and take it with you anywhere in the ecosystem. *** ### The Reputation Layer Is Missing DAOs, protocols, and onchain teams run on coordination. But coordination without **credibility signals** leads to noise: * How do we know who to hire, promote, fund, or delegate? * How do we reward real contributors, not loud ones? * How do we protect networks from sybils, spam, and manipulation? What we need isn’t just data—it’s a **decentralized reputation layer**: one that is **open, transparent, and composable** across chains, protocols, and applications. We’re not just building it—we’re inviting everyone to build it with us. *** ### The Promise of EigenTrust The **EigenTrust algorithm** was developed for peer-to-peer networks as a way to filter out bad actors and uplift trustworthy ones—without any central authority. Here’s the genius of it:\ It propagates trust through the network by weighting local experiences. > If Alice trusts Bob, and Bob trusts Carol, then Alice may assign partial trust to Carol—even if they’ve never interacted. This kind of **transitive trust** forms the basis of an emergent, global reputation score. And that’s exactly the kind of structure Web3 needs—but mapped to **wallets, smart contracts, DAOs, and contributors.** *** ### ✦ Trust in Numbers: Light Math, Big Ideas Let’s look under the hood—lightly. Each participant ii maintains **local trust scores** sijs\_{ij} for others they’ve interacted with. To normalize for fairness: cij=sij∑ksikc\_{ij} = \frac{s\_{ij}}{\sum\_k s\_{ik}} Where: * cijc\_{ij} = normalized trust Alice has in Bob * The sum of all cijc\_{ij} values for a given user equals 1 Then, using **power iteration**, we compute the **global trust vector** tt such that: t=CTtt = C^T t Where: * CC is the matrix of all normalized local scores * tt converges to a stable distribution of global trust This isn’t just theory—it’s already been battle-tested in decentralized networks. But in Web3, it becomes exponentially more powerful: * **Wallets = identities** * **Reputation = weighted behavior** * **Scores = interoperable signals** Imagine plugging this into a bounty board, governance system, or collab platform—and instantly surfacing **the most trusted contributors, by context**. *** ### The Standard Reputation Framework: Anyone Can Reward The [**Standard Reputation Framework**](https://docs.zeroauthority.xyz/the-dao/standard-reputation-framework) allows: * DAOs to issue reputation to voters, builders, and bounty winners * Individuals to give attestation to others they collaborate with * Apps to plug into a shared layer of **composable trust** Reputation can be: * Public or private * Context-specific (e.g. "trusted reviewer", "governance expert") * Immutable or time-based * Earned, never bought This is a protocol, not a platform. It’s **designed to be adopted, remixed, extended**. *** ### Building a Reputation Economy Imagine a world where: * Your onchain resume shows endorsements from real collaborators * Airdrops are based on your verified impact, not just activity * Protocols weight your vote based on reputation earned across DAOs * Hackathons, bounties, and governance use trust to filter signal from noise We’re not there yet. But we believe we can get there—**together**. It will take: * Open infrastructure * Transparent math * Interoperable standards * And the belief that **trust can be decentralized** without being diluted *** ### Join Us This is an open invitation to build the reputation layer of Web3: * If you’re a DAO: start issuing reputation. * If you’re a builder: integrate our standards. * If you’re a contributor: start earning trust that’s portable. Because in the end, reputation is not what you say about yourself—\ It’s what the network says about you. And at **Zero Authority**, we’re making sure the network can finally speak. # Access to the Platform To ensure you get access to features and solutions ## Procedure Step 1 - Connect Wallet. Step 2 - Sign Transaction.
**Step 1:** Connect your wallet. * Ensure your wallet is properly connected to the platform. **Step 2:** Sign the transaction. * Once connected, sign the transaction to confirm your action. **Profile Edit Confirmation:** * If you've completed the steps correctly, you'll be able to edit your profile. Go to website. **Troubleshooting:** * If you encounter any issues: 1. Disconnect your wallet and log out of the platform. 2. Clear your browser's cache. 3. Reconnect your wallet and repeat Steps 1 and 2. **VPN Required for certain countries** * If you encounter issue with access to the website and cannot visit: 1. You are in a geographic region or county where we are getting blocked 2. Recommended free software for chrome 1. Free VPN for Chrome - VPN Proxy VeePN 2. Touch VPN - Secure and unlimited VPN proxy 3. Browsec VPN - Free VPN for Chrome # Updates Updates on the Zero Authority DAO, Cerulean Marketplace, and upgrades for community members, stakeholders, partners, and investors. # Platform Updates July 4, 2026 New platform updates are live across Zero Authority. We've added new AI-powered tools to improve Bounties and DeGrants, making it easier to create, explore, and validate ideas. {% embed url="" %} # Bitcoin Staking SIP June 9, 2026 A new SIP. SIP-043: PoX-5 Bitcoin Staking and Emission Schedule Alignment {% embed url="" %} # Quests are live March 9, 2026 Zero Authority Quests are live. A new way for the Stacks community to verify real action onchain. Explore quests: ; Fast Pool is launching the very first Quest on Zero Authority. {% embed url="" %} # New homepage February 16, 2026 We shipped an update to the homepage — are you "New to Zero Authority?” Built to help people get what they actually need from the Zero Authority Community Protocol. {% embed url="" %} # SIP Tracker on Zero Authority January 29, 2026 Today is a real turning point for the Stacks ecosystem. Governance is shifting from an abstract idea into shared, visible infrastructure. At Zero Authority DAO, the goal has been clear from day one: remove friction so every builder and every $STX holder has the information needed to shape what comes next. Transparency is a tool we can use. {% embed url="" %} # Q4 2025 Product Updates January 2, 2026 Q4 2025 was a quarter of execution. Rather than introducing new surface area, we focused on tightening the system: fixing edge cases, improving clarity for developers, and making the platform more predictable for both companies and creators. Every update shipped this quarter is complete, verified, and live. This was not roadmap energy. This was finishing work. {% embed url="" %} *** #### What Shipped Across Platform V2, improvements landed in documentation, bounties, submissions, tokens, infrastructure, and UX. API documentation was updated to support new profile identifiers, reducing ambiguity for integrators and downstream tools. Bounty workflows were tightened end-to-end. Status accuracy was corrected, completion notifications were added, and invalid submissions are now handled cleanly. Several long-standing display and state issues were resolved to ensure bounties reflect reality, not intent. Submission flows were improved with clearer descriptions, explicit fees, and better validation. The result is fewer failed submissions and a smoother experience for both creators and reviewers. Token handling and pricing reliability were strengthened. USDCx was added to the whitelist on Stacks, token identifiers were corrected, and SIP-009 support was added to improve consistency across integrations. On the infrastructure side, we shipped Chainhook integrations, released SIP Tracker v1.0, and continued enhancements to the Nova AI Bot. These updates reduce manual overhead and make it easier to build on top of the platform with confidence. Finally, a series of UX improvements—CTA label updates, improved linking, and bug fixes—polished the edges that matter day to day. #### Why It Matters For companies, these updates make it easier to run campaigns that are clean, measurable, and accountable. Fewer edge cases mean fewer surprises. For creators, the platform is now more predictable: submissions behave as expected, rewards are clearer, and reputation built through real work is easier to trust and verify. The system is sharper, quieter, and more reliable—which is exactly the point. #### Looking Ahead With Platform V2 stabilized, we’re setting the foundation for what comes next. In 2026, companies won’t just run campaigns—they’ll launch quests. Creators won’t just participate—they’ll build reputation through meaningful contributions and get paid on-chain for real work. Zero Authority Quests are coming. Q4 2025 made sure the ground beneath them is solid. # DeGrants is now live November 27, 2025 DeGrants on Zero Authority is now live! Explore your favorite projects and grantees in one place. Track real progress as it happens and see how builders are moving the ecosystem forward. More discovery, more transparency, more momentum—right at your fingertips. GitHub is still the primary source for updates & milestones tracking for cohort 3. {% embed url="" %} # Keep Calm and Stay Base’d November 1, 2025 Zero Authority DAO is live on BASE. We just launched a new bounty contract and need testers! 🧪 We’ll pick 2 winners to win $20 in ETH on Base. {% embed url="" %} # New features live! October 10, 2025 🚀 Zero Authority Update: New features live! 💼 Retroactive Gig – Get past work verified with satoshis 💸. Your wallet = your resume 🪪. 📊 Price Data – Integrated price tracking 📈 to connect contributions with real-time value. ✨ {% embed url="" %} # Bug Reported October 5, 2025 Wallet Connect Issues Resolved We pushed a platform update and it’s causing some Wallet Connect issues. If you have an issue, please report your setup in telegram. {% embed url="" %} # Bounty + Badges are live September 10, 2025 {% embed url="" %} # Zero Authority Nova is live September 4, 2025 Introducing Nova AI/Bots — built by Zero Authority DAO. [https://zeroauthoritydao.com/ai](https://t.co/XA1UAMLvFy) We combined on-chain + off-chain data to deliver a powerful community solution for the Stacks community. {% embed url="" %} # Zero Authority API is live August 24, 2025 Welcome to the Decentralized Gig Economy! Shoutout to our team member and the legend HZ for getting the data layer fully working. Dive in: [https://zeroauthoritydao.com/api-docs](https://t.co/JpNwvHoVIm) {% embed url="" %} # Stacks Townhall August 14, 2025 ### **Overview** The **SocialFI & Creator Economy Dashboard** provides a data-rich snapshot of the onchain creator ecosystem on Stacks since the **V2 launch**, showing exactly how value, participation, and reputation are evolving. *** #### **1. Token Distribution** 💰 Total bounty rewards distributed across multiple projects and communities: | Token | Amount | | --------- | ------------- | | $ROO | 48,200 | | DIKO | 10,000 | | FlatEarth | 346,600 | | LEO | 9,225,000 | | MEME | 25,000,000 | | NOT | 1,990,000,000 | | STX | 2,191.001 | | USDh | 211 | | WELSH | 1,285,000 | | sBTC | 0.00156 | | stSTX | 170 | *** #### **2. NFT Distribution** 🎨 NFT drops rewarding creativity and participation: | Collection | Quantity | | ------------ | -------- | | giga-pepe-v2 | 2 | | leo-cats | 3 | | not-punk | 3 | *** #### **3. Community Engagement** 📊 Unified participation and activity metrics: * **11.9k** participants * **86.5k** views * **2.8k** event completions *** #### **4. NOVA Bot Activity** 🤖 Cross-platform communication and coordination stats (last 150 blocks): * **Telegram:** 917 members across 5 chats * **Discord:** 12,278 members across 10 servers * **Direct Messages:** 3 DMs with 3 users *** #### **Key Insights** 📌 * Creators are **earning** and **building reputation** directly onchain. * Token and NFT rewards are **driving sustained engagement**. * The SocialFI ecosystem on Stacks is **expanding in reach and adoption**. * Onchain data proves that **contributions translate into tangible recognition**. *** Image
{% embed url="" %} # Zero Authority Security is live August 7, 2025 #### Partnership Announcement: Zero Authority DAO & Clarity Alliance Zero Authority DAO is proud to partner with @ClarAllianceSTX to advance the next era of secure, decentralized infrastructure and smart contracts across the @Stacks ecosystem. Security is the foundation of trustless and permissionless systems. Together, we are committed to raising the standards for smart contract auditing, threat analysis, and ongoing security education. Our mission is to serve as the trustless layer for builders and creators by providing transparency, rigorous security practices, and accessible resources to the community. Through this partnership, users can now submit direct service requests to Clarity Alliance via our site (login required), streamlining support and collaboration for secure development. We look forward to building a safer, more resilient decentralized future—powered by community and innovation. {% embed url="" %}
# LeoCoin Feline Friday’s 🐾 August 1, 2025 This is a major milestone for Zero Authority DAO. We’re proud to announce the launch of **Feline Friday’s** — a new weekly tradition for Onchain Summer where fresh bounties are released every Friday to support and reward creators in the decentralized ecosystem in the leading Bitcoin Layer 2. What makes this moment even more special is a bold commitment from one of the most vibrant memecoins in the Stacks ecosystem: **Leo** is committing **25 million $LEO** — worth up to **$5,000** — to fund bounties over the coming months. This partnership marks a significant step forward in our mission to empower onchain creativity, open participation, and the next generation of internet culture. Together, we’re building a creator economy that doesn’t rely on permission, gatekeepers, or centralized platforms. Every Friday, expect new opportunities for artists, meme makers, storytellers, and internet explorers to contribute, earn, and shape what’s next. These bounties will celebrate decentralized identity, playful experimentation, and the power of the memeverse to bring people together. Feline Friday’s is more than just a campaign — it’s a signal. A signal that creators are at the center of the Zero Authority vision. A signal that value should flow directly to the people building culture onchain. We’re grateful to Leo for leading by example. The cat is out of the bag — and it’s just getting started. Let’s make Fridays legendary. {% embed url="" %} # Utility for Decentralized Assets July 30, 2025 The Stacks ecosystem is growing—and Zero Authority is at the center of it, giving users and builders more ways to do more with their STX, sBTC, memecoins, community energy, NFTs, and tokens. As highlighted by the official [@Stacks](https://x.com/Stacks) account, the message is clear: Zero Authority is not just a protocol or a DAO—it’s becoming the creative engine for the next phase of Bitcoin-secured applications. Through our bounty platform, protocol extensions, and native incentives, we’re actively proving that utility in Web3 doesn’t have to come from speculation alone. You can launch campaigns, fund creative work, distribute tokens, run experiments, and build onchain reputation—without gatekeepers. Builders are already deploying with us: * **STX holders** are putting their capital to work through yield-sharing and bounty-based community rewards. * **sBTC users** are exploring new earning paths via onchain incentives and creative grants. * **Memecoins** are finding real use cases—funding creators, memes, and movements directly. * **Communities** are collaborating, rewarding members, and organizing around shared missions using open tools. * **NFTs and tokens** are gaining life through direct integration with reward mechanics, roles, and content. Whether you’re here to experiment, earn, or contribute, Zero Authority offers the most direct, decentralized way to engage with the Bitcoin-aligned world. If you want to do more with your assets—STX, sBTC, NFTs, memecoins, or ideas—this is where you do it. Onchain. In public. With others. Zero Authority is where experimentation becomes ecosystem growth. {% embed url="" %} # Stack4Impact July 29, 2025 **Introducing Stack4Impact with The Fast Pool** Zero Authority DAO is proud to launch **Stack4Impact** in partnership with **The Fast Pool**. This initiative enables you to delegate your STX and fuel the creators, builders, and contributors who power the Zero Authority ecosystem. When you delegate to The Fast Pool, **100% of the yield generated goes directly to users earning through bounties on Zero Authority**. There are no lockups, no intermediaries, and no hidden fees. Just pure, onchain support for the people building the future. Stack4Impact is a new model for decentralized funding—turning your STX stack into a direct resource for public goods, open-source innovation, and community-led projects. Delegate today and make your stack count. {% embed url="" %}
# Xverse Dapp browser June 19, 2025 Zero Authority DAO is listed on the[@XverseApp](https://x.com/XverseApp) Dapp browser Now you can access our platform directly from the Xverse wallet. Just open your app, tap the Dapp link, and boom… We’re making it 10x easier for you to explore gigs, bounties, and opportunities on Stacks. {% embed url="" %} # Multi-winner bounties are live June 8, 205 ### New Feature Drop: Multi-Winner and Top 3 Bounties Zero Authority now supports two powerful bounty formats — fully onchain. **Multi-Winner Bounties:** Select up to 10 winners per bounty.\ **Top 3 Bounties:** Rank the top 3 submissions and distribute rewards accordingly. All funds are locked in smart contracts and automatically released when winners are selected. No middlemen. No off-chain coordination. Just builders and trustless code. This upgrade is part of our mission to build onchain reputation and permissionless coordination. Transparent, efficient, unstoppable. Try it now at [zeroauthoritydao.com](https://zeroauthoritydao.com/). Zero Authority is more than a platform — it’s a protocol for trust. {% embed url="" %} # Zero Authority V2 is Live May 23, 2025
Zero Authority V2 Beta is LIVE! We’re unlocking the next chapter in onchain coordination. You can now do gigs, bounties, and endorsements — all transparently onchain. Why does this matter? Work is changing. People need trustless, borderless ways to contribute and get paid. V2 makes that possible — no gatekeepers, just reputation, skills & smart contracts. *** What you can do in V2: Complete gigs Earn from bounties Give and receive endorsements Build your onchain rep Whether you're a dev, designer, or community builder — there's a place for you. *** We’re just getting started. This is your chance to be early, contribute meaningfully, and shape the future of work. Join the movement. Earn your first Bitcoin *** Bounty is a decentralized feature for posting and completing Web3 tasks, with secure, on-chain payments via Clarity smart contracts. [https://zeroauthoritydao.com/bounty](https://t.co/5QKYlVPCLp) *** Gigs is a feature for Creators who empowers Web3 freelancers to offer services, build on-chain reputations, and engage in trustless collaborations via smart contracts. [https://zeroauthoritydao.com/creators](https://t.co/6E4JcIeyyx) {% embed url="" %} # Zero Authority V2 on Testnet January 2025 Instructions for Setting Up Your Profile on Zero Authority V2 (Testnet) Welcome to **Zero Authority V2 on Testnet**! Follow these simple steps to set up your profile: 1. **Change Your Wallet Network**:\ In your **Leather** or **Xverse wallet**, switch the network to **Testnet** or **Signet**. 2. **Visit the Platform**:\ Go to [**Chronos Agora**](https://chronosagora.com/) in your browser. 3. **Access Your Profile**:\ Tap on **“My Profile”** located in the bottom menu. 4. **Edit Your Profile**: * Click on the **Edit Profile** option. * Fill in the following details: * **Name**: Add your name. * **Service**: Specify the service you provide. * **Twitter Handle**: Enter your Twitter handle. * **Telegram Handle**: Enter your Telegram handle. 5. **Save Your Information**:\ Simply **click outside of the input boxes** to save the information. Change Your Wallet Network 🎉
You're all set! 🎉 # Zero Authority V2 November 14, 2024
Solutions and features for each of the platform’s main components. This includes Gigs, Bounties, Endorsements, and Reputation Badges to create a more engaging and scalable ecosystem. *** #### **1. Gigs** The Gigs feature in V2 should focus on giving users flexibility in how they complete tasks and earn rewards. Here are the key gig types: * **Retroactive Gigs**: Allow users to submit proof of work for tasks completed before the gig was posted. This feature can reward community members who have already contributed valuable work without prior reward. * **Fixed Gigs**: Standard gig format where users complete a set task for a specified reward. This is straightforward and appeals to those seeking clarity on payout and deliverables. * **Milestone-Based Gigs**: Break tasks into smaller, trackable milestones, allowing contributors to receive partial rewards as they achieve each stage. This structure can incentivize ongoing contributions and help participants stay motivated on longer-term tasks. *** #### **2. Bounties** The V2 Bounties feature should allow multiple formats to suit the range of tasks and encourage broader participation: * **Community Bounties**: Open bounties that allow the community to submit entries without strict restrictions. The most valuable contributions are rewarded, promoting inclusivity and grassroots involvement. * **Single Winner Bounties**: Bounties where only the best submission is rewarded, ideal for high-stakes challenges that require precision and high quality. * **Multiple Winners Bounties**: Allows for several winners (e.g., top 5 or top 10 entries) to share the reward. This format can encourage higher engagement since more participants have a chance of winning something. * **Top 3 Winners Bounties**: A structured bounty format where the top three entries receive scaled rewards (e.g., 1st place gets 50%, 2nd place 30%, and 3rd place 20%). This structure is ideal for competitive bounties with a focus on high-quality results. *** #### **3. Endorsements (P2P Recommendations)** Endorsements should be enhanced in V2 to strengthen trust and credibility through peer-to-peer recommendations: * **P2P Recommendations**: Enable users to endorse each other based on specific skills or contributions, providing a reputation layer that builds credibility and trust across the platform. Each endorsement could have a category, rating, and a short feedback note to give context to the endorsement. * **Verification and Impact of Endorsements**: Introduce a system where the frequency and quality of endorsements affect a user’s reputation score. Verified users and long-standing community members could have a higher impact on endorsements, reinforcing trust. * **Endorsement History**: Display an endorsement history to showcase a user’s contributions and positive interactions, helping potential collaborators gauge reputation and trustworthiness. *** #### **4. Reputation Badges** Reputation Badges are crucial for recognizing and incentivizing contributions across Gigs, Bounties, and Endorsements. V2 could enhance these badges as follows: * **Gig Completion Badges**: Issue badges for successful completion of gigs, with tiered badges for completing multiple gigs, signaling a user’s reliability and experience. * **Bounty Success Badges**: Award badges for winning or placing in bounties, recognizing competitive accomplishments and technical skill. Different levels of badges could reflect single, top-three, and multiple-winner bounties. * **Endorsement Badges**: Offer badges for receiving a high number of endorsements, which signify a user’s reputation and trustworthiness in the community. Peer validation badges reinforce the value of community-driven trust. * **Levels and Rarity**: Create badge levels (e.g., Bronze, Silver, Gold) based on the number of successful engagements across gigs, bounties, and endorsements. Rare badges could be unlocked by completing high-impact gigs or top-level bounties, adding an element of exclusivity. *** #### **Testnet Integration**: [Chronosagora Testnet](https://chronosagora.com/) The testnet integration on Chronosagora enables users to explore these features in a testing environment, allowing for real-time feedback and adjustment. Key features to test include: * **Testing Different Gig and Bounty Types**: Users can experiment with retroactive, fixed, and milestone gigs as well as various bounty formats to see how they work in practice. * **Endorsement and Badge Functionality**: Users can test the P2P recommendation system, verify endorsement impacts, and view the badge issuance process to ensure the design is robust and meets community expectations. # MFA for All Access Points September 20, 2024 This procedure outlines how to enforce Multi-Factor Authentication (MFA) for all team members and any external collaborators we work with on key platforms such as Twitter, GitHub, Discord, Telegram, and other critical applications. *** **Step 1: Notify Team Members and Collaborators** 1. **Communication:** Send an official email or message through internal communication channels (Slack, email, etc.) informing everyone of the new security policy to implement MFA. * **Key points to include:** * Rationale for MFA implementation (enhanced security, protecting sensitive data, preventing unauthorized access) * Deadline for completion (e.g., within the next 7 days) * Links to resources or guides for setting up MFA on required platforms **Step 2: Identify Required Platforms** * The following platforms will require MFA for all accounts: 1. **Twitter** 2. **GitHub** 3. **Discord** 4. **Telegram** 5. **Any other productivity or social media tools (e.g., Google Workspace, Microsoft 365, Slack, etc.)** **Step 3: Setting Up MFA for Each Platform** **Twitter** 1. Log into Twitter. 2. Go to **Settings and privacy** > **Security and account access** > **Security**. 3. Click **Two-factor authentication** and enable: * Text message (SMS) * Authentication app (recommended) * Security key (optional for additional security) 4. Follow the prompts to set up your preferred method. **GitHub** 1. Log into GitHub. 2. Go to **Settings** > **Security** > **Enable Two-factor Authentication**. 3. Choose either: * **Authentication App** (recommended for GitHub) * **SMS Authentication** 4. Follow the steps to complete the setup. **Discord** 1. Log into Discord. 2. Go to **User Settings** > **My Account** > **Enable Two-Factor Authentication**. 3. Install an authentication app and scan the provided QR code. 4. Save backup codes for account recovery. **Telegram** 1. Open Telegram on your device. 2. Go to **Settings** > **Privacy and Security** > **Two-Step Verification**. 3. Set up a password for two-step verification. 4. Optionally, add an email for account recovery. **Other Platforms (Google Workspace, Slack, Microsoft 365, etc.)** 1. **Google Workspace:** Log into your Google account > **Security** > **2-Step Verification** > Follow the steps. 2. **Slack:** Log into Slack > **Account Settings** > **Two-Factor Authentication** > Enable 2FA using SMS or an authentication app. 3. **Microsoft 365:** Log into your Microsoft account > **Security settings** > **Additional security options** > Enable MFA via app, SMS, or security key. **Step 4: Secure Storage of Web3 Wallet Seed Phrase in a Password Vault** 1. **Importance of Securing the Seed Phrase:** * The seed phrase for your Web3 wallet is the key to your assets and accounts on the blockchain. If compromised, it can lead to loss of funds and unauthorized access. * Ensure that every team member using a Web3 wallet securely stores their seed phrase in a password vault. Never store seed phrases in plaintext or on unsecured devices. 2. **Procedure for Securing the Seed Phrase:** * **Choose a Password Vault:** Use a trusted and secure password manager, such as 1Password, LastPass, or Bitwarden, to store your seed phrases. Ensure the vault itself has MFA enabled. * **Add the Seed Phrase:** 1. Open your password vault and create a new entry. 2. Name the entry according to the wallet (e.g., “MetaMask Wallet Seed Phrase” or “Ledger Wallet Seed Phrase”). 3. Enter the seed phrase in the secure note section of the vault. 4. Optionally, add any related information such as wallet address or backup method (if necessary). * **Encrypt and Back Up:** Ensure your password vault is encrypted and has a reliable backup solution. This will safeguard the seed phrase in case of device loss or failure. * **Never Share the Seed Phrase:** Reiterate that seed phrases should never be shared with anyone, even within the team. If seed phrases are ever needed for recovery, the authorized team member should handle it directly. 3. **Admin Verification:** * IT or security admin should verify that all team members have securely stored their seed phrases by requesting confirmation. * Periodically audit this process to ensure continued compliance with security protocols. **Step 5: Verification and Documentation** 1. **Self-verification:** Once MFA is set up, each individual must confirm setup via email or an internal form. 2. **Admin verification:** IT or security team members should verify MFA status for critical accounts by requesting screenshots (with sensitive data redacted) or using platform security dashboards to track activation. 3. **Record-keeping:** Maintain an internal record of MFA completion by team members and collaborators. Use a secure spreadsheet or management tool to log MFA status for each person/platform. **Step 6: Follow Up with External Collaborators** 1. **External Notification:** Send a similar MFA enforcement message to all external collaborators or contractors we work with, asking them to: * Set up MFA on relevant platforms. * Confirm completion with a response or proof (screenshot, email confirmation). 2. **Non-compliance:** If external collaborators do not comply, limit or restrict access to shared resources until they meet the security requirements. **Step 7: Periodic Reviews** 1. **Quarterly Audits:** Perform regular security audits every quarter to ensure MFA compliance is maintained across all platforms. 2. **Policy Updates:** Update the team and external collaborators if additional platforms or security measures become necessary. **Step 8: Support and Troubleshooting** 1. Provide step-by-step guides, links to help centers, or offer IT support for anyone experiencing difficulties setting up MFA. 2. Ensure that backup recovery options are in place (backup codes, recovery emails) in case of lost devices or authentication issues. *** By following these steps, we can enhance our security and ensure that all team members and collaborators are adequately protected across essential platforms while safeguarding critical Web3 wallet seed phrases. # v.1.0.0 Bounty Onchain August 20, 2024

V1.0.0 Bounty Onchain

The Bounty Onchain V1.0.0 release marks a significant milestone in the development of our decentralized platform. This version introduces various enhancements and bug fixes to improve user experience, streamline interactions, and foster collaboration within the ecosystem. #### Key Updates and Bug Fixes: **1. UI Glitches, Login, Loading, and Transition Bug - \[DEV-1]** * **Summary:** This update addresses critical UI glitches that were affecting the overall user experience. Issues with login, slow load times, and transition bugs have been resolved, leading to smoother and more reliable interactions on the platform. **2. Enhanced Bounty Interface - \[DEV-2]** * **Summary:** This update enhances the bounty interface by introducing distinct color schemes for headings, submissions, and entries, making navigation more intuitive and improving the overall user experience. **3. Open Gigs Bounty - \[DEV-3]** * **Summary:** This feature allows individuals or teams to bid for projects or tasks, facilitating collaboration opportunities within the platform. **4. Open Gigs Page Development - \[DEV-4]** * **Summary:** The development of the Open Gigs page includes setting clear objectives and guidelines, implementing security measures, and creating a user-friendly submission process to streamline participation in open bounties. **5. Challenge/Bounty Invites - \[DEV-5]** * **Summary:** This feature aims to boost user engagement by providing a seamless way to create, participate in, and manage challenges or bounties, fostering a more interactive and collaborative community. This release is a significant step forward in our mission to create a decentralized and collaborative ecosystem. The updates and new features introduced in V1.0.0 are designed to enhance usability, foster community engagement, and provide a more robust platform for managing bounties and gigs onchain. # v.1.5.2 Gig Mkpl update July 5, 2024
## Gig Marketplace v1.5.2 Release Summary We are excited to announce the release of Gig Marketplace v1.5.2. This release introduces updates and enhancements to improve the user experience and functionality of the platform. Below are the key highlights of this release: ### Key Updates #### 1. Gig MKPL Notification System (#47) **Cerulean MKPL Notification System Overview:** The Cerulean MKPL Notification System is a vital component of the Cerulean Marketplace, designed to facilitate seamless communication and enhance user experience. Leveraging advanced technologies, this system ensures that users stay informed in real-time about their buying and selling activities. The platform employs personalized and context-aware notifications to create an immersive environment, fostering efficient and transparent transactions within the Cerulean ecosystem. #### 2. Zeroauthority Endorsements Page (#158) We have added a new global navigation link called “Endorsement” to our platform. This update will redirect users to zeroauthority.xyz/endorsements, providing a streamlined way to access and manage endorsements. #### 3. New Blog Subdomain Setup (#160) We have created a new subdomain, blog.zeroauthority.xyz, to host our blog content. This setup includes the creation of a new CNAME in Vercel, pointing to target.substack-custom-domains.com. This blog will serve as a direct channel to communicate with our supporters and subscribers. {% embed url="" %} Thank you for being a part of our community! # v.1.5.1 Gig Mkpl update Gig Marketplace v1.5.1 Release Summary

v1.5.1

#### Community Support and Community Tokens New support for community tokens, including $WELSH, $NOT, $LEO, $ROO, $AEUSDC, $GUS, $MEGA, $USDA, $DIKO, $ABTC, and $ALEX, enhances user engagement within their favorite communities and expands token utility within the marketplace. #### Updates Enhanced navigation, responsiveness, and usability across both the web and mobile apps ensure a smoother, more intuitive user experience. We are excited to announce the release of Gig Marketplace v1.5.1! This update introduces major enhancements such as support for new community tokens ($WELSH, $NOT, $LEO, $ROO, $AEUSDC, $GUS, $MEGA, $USDA, $DIKO, $ABTC, and $ALEX), improving user engagement and token utility within the marketplace. Additionally, the web and mobile apps have been refined for better navigation, responsiveness, and overall user experience. Enhancements also include clearer visibility of community activities, a new home button for easier navigation, token payment capabilities, upgraded Clarity contracts, and the addition of user names to profiles and menus for a more personalized interface. This release also addresses several bugs, such as fixing token display issues on the profile page, resolving payment page conditions, ensuring the functionality of the 'connect wallet' button on mobile web, and correcting display issues on the community page. We've also added features like a subscribe to newsletter button, visible transaction IDs, and social links on the community page to enhance connectivity. We are committed to continuously improving Gig Marketplace and appreciate your feedback and support. Stay tuned for more updates! {% embed url="" %} # v.1.5.0 Gig Mkpl update Gig Marketplace v1.5.0 Release Summary

v1.5.0

NextGen Interface and Experience: Completely overhauled interface design highlighting Trajan reputation, including a new landing page, improved search functionality, and redesigned application home page. Updated Community Webpage: Introducing a new community page for effortless collaboration exploration. Revamped Application Landing Page: Enhanced user experience with updated landing page, effectively communicating key features and benefits. About Us Page Overhaul: Comprehensive About Us page overhaul providing detailed mission and vision information. Decentralized Reputation Exchange Protocol (RXP) Renaming: Introduction of the Decentralized Reputation Protocol (RXP) Token, empowering decentralized reputation systems for on-chain economies. Milestone Gig UI Enhancements: Significant UI improvements including fee clarity, refined rounding for small amounts, and enhanced data field visibility. Decentralized Profile Ownership Upgrade: Enhanced profile-level data ownership and information display. Bug Fixes: Thorough testing and resolution of issues including those related to endorsement button, search functionality, and service selection aesthetics. {% embed url="" %} # v.1.4.0 Gig Mkpl update Gig Marketplace v1.4.0 Release Summary **\[DEV 28] Submit offer (milestone) Closed** * Addressing user feedback, the platform now supports milestone submissions without the need for start and end dates. Users can create and manage one or multiple milestones seamlessly, enhancing flexibility in project management. **\[DEV 108] Back button on gig page Closed** * Responding to user convenience, a "back" button has been implemented on gig pages, streamlining navigation and improving overall user experience. **\[DEV 109] Milestone contract gig-id fix** * A critical update to the Milestone SC Contract has been deployed, resolving issues related to the gig ID display. Special thanks to susheel.btc and James\_11| hodlstx.btc for their collaborative efforts in addressing and rectifying this matter. # v.1.3.1 Gig Mkpl Bug Fix Bug Fix

v.1.3.1 Gig Mkpl Bug Fix

Version 1.3.1 of the ZeroAuthority platform has been released, focusing on resolving critical bugs affecting user interactions. Users can now select services and update profiles without issues. The problem of users not being found for a specific service on the gig marketplace landing page has also been fixed. Users are encouraged to upgrade to benefit from these bug fixes, and feedback is appreciated through GitHub. The release details can be found in pull request \[PR 81]. {% embed url="" %} Release Notes {% endembed %} {% embed url="" %} Decentralized Reputation Gig Mkpl {% endembed %} {% embed url="" %} Decentralized Reputation Social Verification {% endembed %} # v.1.3.0 Gig Mkpl Gig Marketplace v1.3.0 Release Summary

v1.3.0

We are thrilled to announce the release of Gig Marketplace v1.3.0, packed with exciting new features and improvements to enhance your gig posting and browsing experience. ### New Feature 🌟 **Comments on Gigs** Introducing a highly requested feature – users can now post comments on gigs! This update empowers users to ask questions, seek clarifications, and discuss project details directly on the gig page. Whether you're a freelancer looking for more information or a client seeking clarification on a gig's scope, the new comment section provides a seamless communication channel. Enhance collaboration, eliminate uncertainties, and make informed decisions by engaging in real-time conversations on the platform. We believe this addition will foster better communication between freelancers and clients, leading to smoother transactions and successful collaborations. Thank you for your continued support, and we look forward to bringing you more exciting features in future releases. Decentralized Reputation on Bitcoin. {% embed url="" %} Release Notes {% endembed %} # v.1.2.0 Gig Mkpl update Gig Marketplace v1.2.0 Release Summary

v1.2.0

**New Features:** * **Gig Status Tracking Update (dev-72):** * Enjoy enhanced information visibility throughout the request process, from making a request to finalizing work. Gain insights into the exact status of your request. * Experience an improved user interface that provides a better understanding of both clients and creators involved in the process. * **Update User Interface for Decision-Making (dev-73):** * UI enhancements have been implemented, utilizing the entire space to clearly communicate status updates and prompt intuitive calls to action. Making informed decisions is now more seamless. **Internal Performance Update:** * **Configuration System Files (dev-50):** * Introduce automation to boost the overall performance of the site. * Automation streamlines testing and deployment processes, making it convenient for updates to be rolled out to both testnet and mainnet. * Actively seek feedback, incorporate necessary code updates, and deploy changes to testnet and mainnet for the benefit of our community members. **Bug Fix:** * **Profile Required Fields Bug (dev-75):** * Resolve the profile bug related to required fields. There is no longer a mandate for Bitcoin addresses, email, and Discord ID. Enjoy a more flexible and user-friendly profile setup. Thank you for your continued support, and we're excited to deliver these enhancements to elevate your Gig Marketplace experience. Stay engaged for more updates. {% embed url="" %} Release Notes {% endembed %} {% embed url="" %} Decentralized Reputation Gig Mkpl {% endembed %} {% embed url="" %} Decentralized Reputation Social Verification {% endembed %} # v.1.1.0 Gig Mkpl update Gig Marketplace v1.1.0 Release Summary

v1.1.0

## Release notes Gig Marketplace v1.1.0 Latest {% embed url="" %} release summary {% endembed %} Highlights: 🔍 Gig Page Enhancement (dev-57) \- Navigate to an upgraded gig page for a comprehensive overview. 🚀 🚦 Gig Status Tracking (dev-58) \- Introducing gig status tracking for better transparency and communication. 🔄 Monitor your gigs' progress easily! 📈 Gigs Ticker on Landing Page (dev-62) \- Discover the latest and most popular gigs with the dynamic ticker on the landing page. 🎉 📝 Single Blog Post Feature (dev-54) \- Create and view individual blog posts associated with your gigs for enhanced communication. 🗣️ \ 🐛 Bug Fixes \- Pending Work/Offer Hover Bug (dev-61) resolved for consistent interaction. ✅ \- Landing Page Roadmap Bug (dev-66) fixed for accurate roadmap info. 🗺️ \ 🛠️ General Improvements \- Performance enhancements and optimizations for a smoother user experience. 🚀 # v.1.0.2 Gig Mkpl Bug Fix Bug Fix
Gig Mkpl v.1.0.1 is now live with a bug fix. You can now seamlessly select a service when connecting your wallet and authenticate without issues. Appreciate your reports via the "Give Feedback" button, directing to our BlockSurvey. ## Release notes Gig Marketplace v1.0.2 bug fix {% embed url="" %} {% embed url="" %} mainnet {% endembed %} {% embed url="" %} testnet {% endembed %} # v.1.0.1 Gig Mkpl update Gig Marketplace v1.0.1 Release Summary
\- Gig Marketplace v1.0.1 is live! \- Open profile URL by wallet 🔍 \- New user-friendly notification UI 📬 \- Feedback button during wallet connection 🤝 \- Roadmap added to landing page 🗺️ \- FAQ and process section enhancements 📘 \- Embedded Gig Marketplace tutorial 🎓 \- Navigation bug fixed 🐞 {% embed url="" %} # v.1.0.0 Gig Mkpl on mainnet 🎉 December 17, 2023 {% embed url="\_" %} ## Release notes Gig Marketplace v1.0.0 Latest {% embed url="" %} ## Contract deploy Contract SP2GW18TVQR75W1VT53HYGBRGKFRV5BFYNAF5SS5J.Cerulean-Marketplace-v1 Transaction ID 0x622a52401b046ff55bc062b2a29643cad93553cccaac1ad86ac202ae1c92fe5e # Testnet 1.4 update Zeroauthority.xyz Cerulean Development | Testnet 1.4 - preview creators {% embed url="" %} Cerulean Development status on 05-28-2023 Development description: Connect your wallet and preview all of the Creators Easy to make an offer for the pseudonymous people you want to trustless and permissionless work together. # Testnet 1.3 update Zeroauthority.xyz Cerulean Development | Testnet 1.3 - client & creator complete gig {% embed url="" %} testnet 1.3 - client & creator complete gig {% endembed %} Cerulean Development status on 05-13-2023 Development description: Creators have the ability to accept or decline an offer for a specific gig, and pseudonymous people can start working on gigs in a trustless and permission-less way Clients can confirm completion of a gig with three options in the Cerulean marketplace on testnet (a) agree 100% (b) agree 75%, 25% back to the client (plus dispute resolution fee) (c) agree 50%, 50% back to the client (plus dispute resolution fee) Next iteration is to solve when gigs go into dispute and the Core DAO team has to review for completion of gig and decide final outcomes based on 75/25, 50/50, or 0% # Testnet 1.2 update Zeroauthority.xyz Cerulean Development | Testnet 1.2 - finalize gig {% embed url="" %} testnet 1.2 - finalize gig {% endembed %} Cerulean Development status on 05-08-2023 Development description: Another milestone for the Cerulean marketplace on testnet. After the client makes an offer to the creator, the creator can offer deliverable sooner and client can finalize gig before the "end-date" The smart contract will release the upon funds to the creator The creator will earn reputation for the gig completed The client & creator will accumulate emissions for participate in the Cerulean marketplace to be delivered via airdrop More information on our site. [https://zeroauthority.xyz/](https://www.youtube.com/redirect?event=video_description\&redir_token=QUFFLUhqa010Y1JCQVNON2pNUWd6UFd4RlFmcDh1QUs5UXxBQ3Jtc0ttZG9lZm9FZTRGanh1czlFTzFSZm5Za2E4ZGpBeGVlbHFmYzY3SVctd2dSNlIwY1RySlRCTE1tZ2RoTkJ1ZFFlZUVidzJGcWZkT1ZRb3F4NmRWSDdCRlFvZmxyRHJlTTRsWGpvbzk3WEN4Z2E4Rl8wYw\&q=https%3A%2F%2Fzeroauthority.xyz%2F\&v=qn8NBWVwcKQ) [https://www.stacks.co/](https://www.youtube.com/redirect?event=video_description\&redir_token=QUFFLUhqbldUX2U2Sl9lTXRtcG4zOGlsc2VzbzlkWVduZ3xBQ3Jtc0trN1Z0cVk1THJ4QjZaT0NOYmpyZVNFUUp3M2FBX0czaWRlWTIyQ1BXU0Ixb0hSVmZSQVZsaGZlaUM4RThpcEpobDF2XzJfa19XaTYxSk56eVQ1SnFNckpSMG5WRWp1VHZNcnBWNFJETGIwQS03aFQxaw\&q=https%3A%2F%2Fwww.stacks.co%2F\&v=qn8NBWVwcKQ) # Testnet 1.1 update Zeroauthority.xyz Cerulean Development | Testnet 1.1 - accept offer {% embed url="" %} testnet 1.1 accept offer {% endembed %} Cerulean Development status on 05-08-2023 Development description: Another milestone for the Cerulean marketplace on testnet. After the client makes an offer to the creator, the creator can offer deliverable sooner and client can finalize gig before the "end-date" The smart contract will release the upon funds to the creator The creator will earn reputation for the gig completed The client & creator will accumulate emissions for participate in the Cerulean marketplace to be delivered via airdrop More information on our site. [https://zeroauthority.xyz/](https://www.youtube.com/redirect?event=video_description\&redir_token=QUFFLUhqa010Y1JCQVNON2pNUWd6UFd4RlFmcDh1QUs5UXxBQ3Jtc0ttZG9lZm9FZTRGanh1czlFTzFSZm5Za2E4ZGpBeGVlbHFmYzY3SVctd2dSNlIwY1RySlRCTE1tZ2RoTkJ1ZFFlZUVidzJGcWZkT1ZRb3F4NmRWSDdCRlFvZmxyRHJlTTRsWGpvbzk3WEN4Z2E4Rl8wYw\&q=https%3A%2F%2Fzeroauthority.xyz%2F\&v=qn8NBWVwcKQ) [https://www.stacks.co/](https://www.youtube.com/redirect?event=video_description\&redir_token=QUFFLUhqbldUX2U2Sl9lTXRtcG4zOGlsc2VzbzlkWVduZ3xBQ3Jtc0trN1Z0cVk1THJ4QjZaT0NOYmpyZVNFUUp3M2FBX0czaWRlWTIyQ1BXU0Ixb0hSVmZSQVZsaGZlaUM4RThpcEpobDF2XzJfa19XaTYxSk56eVQ1SnFNckpSMG5WRWp1VHZNcnBWNFJETGIwQS03aFQxaw\&q=https%3A%2F%2Fwww.stacks.co%2F\&v=qn8NBWVwcKQ) # Testnet 1.0 update Zeroauthority.xyz Cerulean Development | Testnet 1.0 - connect hiro wallet {% embed url="" %} testnet 1.0 connect wallet {% endembed %} Zeroauthority.xyz Cerulean Development | Testnet 1.0 - connect hiro wallet Cerulean Development status on 03-14-2023 Development description: Connect your hiro wallet and build confirm some information for your decentralized web3 profile (add only the details you need so people can find you or learn more) [https://zeroauthority.xyz/](https://www.youtube.com/redirect?event=video_description\&redir_token=QUFFLUhqa010Y1JCQVNON2pNUWd6UFd4RlFmcDh1QUs5UXxBQ3Jtc0ttZG9lZm9FZTRGanh1czlFTzFSZm5Za2E4ZGpBeGVlbHFmYzY3SVctd2dSNlIwY1RySlRCTE1tZ2RoTkJ1ZFFlZUVidzJGcWZkT1ZRb3F4NmRWSDdCRlFvZmxyRHJlTTRsWGpvbzk3WEN4Z2E4Rl8wYw\&q=https%3A%2F%2Fzeroauthority.xyz%2F\&v=qn8NBWVwcKQ) [https://www.stacks.co/](https://www.youtube.com/redirect?event=video_description\&redir_token=QUFFLUhqbldUX2U2Sl9lTXRtcG4zOGlsc2VzbzlkWVduZ3xBQ3Jtc0trN1Z0cVk1THJ4QjZaT0NOYmpyZVNFUUp3M2FBX0czaWRlWTIyQ1BXU0Ixb0hSVmZSQVZsaGZlaUM4RThpcEpobDF2XzJfa19XaTYxSk56eVQ1SnFNckpSMG5WRWp1VHZNcnBWNFJETGIwQS03aFQxaw\&q=https%3A%2F%2Fwww.stacks.co%2F\&v=qn8NBWVwcKQ) # Target Launch Date December 9, 2023 Target launch date is end of June on Mainnet

v1.0 Balaji Release - mainnet launch

Release notes: TBD Release date: TBD # Getting Started Get Nova up and running in your Discord server or Telegram group in under 2 minutes. Get Nova up and running in your Discord server or Telegram group in under 2 minutes. *** {% content-ref url="/pages/vmhC0BiPWEjTh4NyqXkO" %} [Adding Nova to Discord](/nova-bot/getting-started/adding-nova-to-discord) {% endcontent-ref %} {% content-ref url="/pages/y1WG66sIJTQ3Tyux6WMz" %} [Adding Nova to Telegram](/nova-bot/getting-started/adding-nova-to-telegram) {% endcontent-ref %} *** ## Quick Start Once Nova is added to your server or group: 1. **Mention the bot** — Type `@NovaBot` in Discord and `@NovaAITheBot` in Telegram followed by your question in any channel 2. **Reply to Nova** — Continue a conversation by replying to any of Nova's messages 3. **DM the bot** — Send a direct message for private interactions 4. **Use slash commands** — Type `/` to see all available commands {% hint style="success" %} Nova works out of the box — no configuration required. Just add it and start asking questions. {% endhint %} *** ## Available Commands | Command | Description | | ------------ | ----------------------------------------- | | `/nova` | Set up token swap, NFT, and wallet alerts | | `/bounty` | Configure bounty notifications | | `/gigs` | Configure gig notifications | | `/quest` | Configure quest notifications | | `/campaigns` | Configure campaign notifications | | `/premium` | Manage your premium subscription | | `/help` | View bot features and useful links | | `/fortune` | Get a mystical fortune | | `/roll` | Roll the dice | *** ## Next Steps * **Set up alerts** — See the [Alerts Setup Guides](/nova-bot/alerts-setup-guides) to start tracking tokens, NFTs, and wallets * **Chat with Nova AI** — Learn what Nova can do in the [Nova AI Agent](/nova-bot/nova-ai-agent) guide * **Go Premium** — Unlock higher limits and exclusive features with [Premium](/nova-bot/premium) # Adding Nova to Discord Add Nova to your Discord server in a few clicks. Add Nova to your Discord server in a few clicks. {% hint style="warning" %} You must have **Administrator** or **Manage Server** permissions on the Discord server to add a bot. {% endhint %} *** ## Step 1 — Invite Nova Click the invite link below to add Nova to your server: [**Add Nova to Discord**](https://discord.com/oauth2/authorize?client_id=1263740412120662018\&permissions=1376805579860\&integration_type=0\&scope=bot) *** ## Step 2 — Select Your Server 1. Choose the server you want to add Nova to from the dropdown 2. Click **"Continue"** *** ## Step 3 — Confirm Permissions Review and approve the required permissions: | Permission | Why It's Needed | | -------------------- | ------------------------------------------------------------ | | View Channels | Read messages where Nova is mentioned | | Send Messages | Reply to users and deliver notifications | | Embed Links | Format rich responses with embeds | | Attach Files | Send images and charts | | Read Message History | Maintain conversation context | | Manage Roles | Assign token/NFT-gated roles (if configured) | | Manage Messages | Delete scam/spam messages (Nova Guardian auto-moderation) | | Moderate Members | Time out (mute) a caught scammer, and undo it via **Revert** | | Ban Members | Ban a caught scammer via the **Ban** button on a flag report | {% hint style="info" %} The last three are only ever used by [Nova Guardian](/nova-bot/nova-ai-agent/community/nova-guardian), and only when a server admin explicitly turns **auto-moderation** on. Guardian is flag-only until then — Nova never deletes, mutes or bans anyone without that opt-in. {% endhint %} Click **"Authorize"** to complete the setup. *** ## Step 4 — Set Up Role Hierarchy For role management features to work, Nova's role must be positioned **above** any roles it needs to assign: 1. Go to **Server Settings** → **Roles** 2. Drag the **Nova** role above the roles it should manage 3. Keep it **below** your admin/moderator roles {% hint style="info" %} Role hierarchy only matters if you plan to use Nova's role management features. If you're only using alerts and AI chat, you can skip this step. {% endhint %} *** ## You're All Set Nova is now active in your server. See the [Quick Start](/nova-bot/getting-started#quick-start) for how to talk to Nova and the available commands. # Adding Nova to Telegram Add Nova to your Telegram group or start a private chat. Add Nova to your Telegram group or start a private chat. *** ## Option A — Direct Message (Private Chat) 1. Open Telegram and search for **@NovaAITheBot** 2. Tap **"Start"** 3. You're ready — just type your questions *** ## Option B — Add to a Group (Mobile) 1. Open Telegram and search for **@NovaAITheBot** 2. Tap the bot's profile → **"Add to Group"** 3. Select the group you want to add Nova to 4. Grant **"Send Messages"** permission when prompted 5. Tap **"Done"** {% hint style="warning" %} You must be a **group admin** to add bots to a Telegram group. {% endhint %} *** ## Option C — Add to a Group (Desktop/Web) 1. Open your group in Telegram 2. Click the **group name** at the top to open settings 3. Click **"Add Members"** 4. Search for **@NovaAITheBot** 5. Click **"Invite"** 6. Ensure the bot has **"Send Messages"** permission *** ## Option D — One-Click Invite Use this link to add Nova directly to any group: [**Add Nova to Telegram Group**](https://t.me/NovaAITheBot?startgroup=true) Select your group from the list and confirm. *** ## You're All Set Nova is now active in your group. See the [Quick Start](/nova-bot/getting-started#quick-start) for how to talk to Nova and the available commands. # Alerts Setup Guides Find detailed instructions to configure the Nova Bot alerts. Step-by-step guides to set up Nova's alerts on Discord and Telegram. Two things apply to every guide in this section: * **Where alerts work:** alerts are available in Telegram groups, Discord servers, and Direct Messages (unless a guide says otherwise). * **One session at a time:** you can only run one command session at a time — use `/cancel` to abort a session. **Alerts get set up in two ways.** Most blockchain alerts use a **slash-command wizard** (`/nova`, `/premium`, `/bounty`, …) that walks you through the options. Others — grants, events, governance, and personal Smart Alerts — are **conversational**: you just describe the alert to Nova. See [Smart Alerts](/nova-bot/nova-ai-agent/smart-alerts) for the full conversational alert reference. *** ## Blockchain Alerts {% content-ref url="/pages/qJ5tGttFqgnrXMS6RLAK" %} [Token Swaps Alerts](/nova-bot/alerts-setup-guides/token-swaps-alerts) {% endcontent-ref %} {% content-ref url="/pages/H8EBVbvlSX6kJ27wRtMI" %} [NFT Activity Alerts](/nova-bot/alerts-setup-guides/nft-activity-alerts) {% endcontent-ref %} {% content-ref url="/pages/8XsJXAwMiW5JBY2Tyarx" %} [Wallet Tracker Alerts](/nova-bot/alerts-setup-guides/wallet-tracker-alerts) {% endcontent-ref %} {% content-ref url="/pages/j8XaxQtXiDoP7CSe0Oc2" %} [Premium Alerts](/nova-bot/alerts-setup-guides/premium-alerts) {% endcontent-ref %} ## ZADAO & Ecosystem {% content-ref url="/pages/E2g28jmRfRs2UAOQekqH" %} [ZADAO Alerts](/nova-bot/alerts-setup-guides/zadao-alerts) {% endcontent-ref %} {% content-ref url="/pages/PYOV33SjI4RbCdLsk7fo" %} [Events & Governance Alerts](/nova-bot/alerts-setup-guides/events-and-governance-alerts) {% endcontent-ref %} {% content-ref url="/pages/2g88E30kbQ4EJfLG4v2x" %} [ZADAO Stats](/nova-bot/alerts-setup-guides/zadao-stats) {% endcontent-ref %} {% content-ref url="/pages/dbZGfs8KREAObT44cUTg" %} [GM Alerts (Legacy)](/nova-bot/alerts-setup-guides/gm-alerts-legacy) {% endcontent-ref %} ## Manage & Audit {% content-ref url="/pages/JHbv4S0CmvZYYAnh8gvH" %} [Managing Your Alerts (Web Dashboard)](/nova-bot/alerts-setup-guides/managing-your-alerts-web-dashboard) {% endcontent-ref %} {% content-ref url="/pages/zfRYiTqbsT4IABFjc8vF" %} [Alert History & Delivery Status](/nova-bot/alerts-setup-guides/alert-history-and-delivery-status) {% endcontent-ref %} # Token Swaps Alerts Monitor any Stacks token in real time — get an alert whenever someone buys (or sells) your tracked tokens, with customizable thresholds and visuals. | Plan | Token Limit | | ------- | ----------- | | Free | 3 tokens | | Premium | 20 tokens | *** ## What Each Alert Includes | Field | Description | | --------------- | ------------------------------------------------- | | Swap Direction | Buy or Sell indicator | | Position Change | New Holder, Position Up, or Position Down | | Token Amounts | From/To token quantities | | USD Value | Dollar value of the trade | | DEX | Which decentralized exchange the swap happened on | | Market Cap | Current market cap (if available) | | Custom Emoji | Your chosen emoji displayed alongside the alert | *** ## Setup 1. Use the `/nova` command and select **"Token Swaps"**. 2. Follow the wizard steps: * Toggle alerts on/off * **(Discord only)** pick a channel for the alerts — skip in DMs * **(Discord only)** confirm the blockchain (Stacks) * Enter the token's **smart contract address** (e.g. `SP123...::token-name`) * Choose alert mode: **Buys only** or **Buys & Sells** * Set a minimum transaction threshold: **$1**, **$10**, **$30**, **$100**, or **$1,000** * Select an **emoji** for your alerts * Upload a custom **image/GIF** or use the default * Review the summary and confirm 3. When you see the success message, your token swaps alerts are live. *** ## Configuration Options | Option | Description | Required | | ------------------ | --------------------------------------------- | -------- | | Contract address | The Stacks token contract to monitor | Yes | | Alert mode | Buys only, or Buys & Sells | Yes | | Min. USD threshold | Ignore swaps below this dollar amount | Yes | | Emoji | Custom emoji displayed in alerts | Yes | | Image | Custom image/GIF uploaded to IPFS, or default | Optional | # NFT Activity Alerts Track any NFT collection on Stacks — get alerts for buys, listings, offers, and mints, each routed to the channel of your choice. | Plan | Collection Limit | | ------- | ---------------- | | Free | 10 collections | | Premium | 100 collections | *** ## What You'll Get Alerted About Choose which event types you want to receive: | Event Type | Description | | ---------------- | -------------------------------------------------------- | | **Buys / Sales** | An NFT in the collection was purchased | | **Listings** | An NFT was listed or unlisted on a marketplace | | **Offers** | A new offer was placed on an NFT or the collection | | **Mints** | A new NFT was minted (only if set up before mint starts) | Each alert includes the NFT name/ID, price in STX, seller/buyer addresses, and marketplace info. {% hint style="success" %} **Mint alerts** are automatically included if you set up tracking **before** the collection starts minting. No extra configuration needed. {% endhint %} *** ## Setup 1. Use the `/nova` command and select **"NFT Activity"**. 2. Follow the wizard steps: * Toggle alerts on/off * **(Discord only)** confirm the blockchain (Stacks) * Enter the NFT collection's **smart contract address** * Choose Yes/No for each alert type (buys, listings, offers) * **(Discord only)** pick a channel for each enabled alert type — skip in DMs. You can route each type to a different channel (e.g. buys in #sales, listings in #marketplace) * Review and confirm 3. When you see the success message, your NFT activity alerts are live. # Wallet Tracker Alerts Monitor any wallet across **multiple chains** and get an alert whenever it moves — transfers in and out, trades, and on-chain activity. | Plan | Address Limit | Custom Labels | Noise Filters | | ------- | ------------- | ------------- | ------------- | | Free | 1 address | -- | Yes | | Premium | 300 addresses | Yes | Yes | The address limit is shared across every chain combined. *** ## Supported Chains | Chain | What's tracked | Data source (keyless) | | --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | --------------------- | | **Stacks** | Token transfers, contract calls, deployments | Stacks block feed | | **Ethereum / Base / Arbitrum / Optimism / Polygon / BNB Chain / Avalanche** | Native + ERC-20 transfers (with USD value) and ERC-721/1155 NFTs (collection, token id + image) in & out | Alchemy transfers | | **Solana** | SOL & SPL token transfers (amount + direction + USD), plus a new-activity signal for the rest | Solana RPC | | **Bitcoin** | Native BTC received / sent | mempool.space | | **TON** | TON & jetton transfers (amount + direction; native TON in USD), plus a new-activity signal for swaps / NFT moves / contract calls | TON API | | **Sui** | SUI transfers (amount + direction + USD), plus a new-activity signal for Move calls / object moves / non-SUI coin txs | Sui GraphQL RPC | | **Aptos** | APT transfers (amount + direction + USD), coin & Fungible-Asset moves (direction), plus a new-activity signal for contract calls | Aptos Indexer | | **Hyperliquid** | Fills (buy/sell, size, notional, PnL), deposits / withdrawals / transfers, and position opened / closed / flipped | Hyperliquid API | **Bitcoin Runes & BRC-20** wallet activity is planned and will switch on once a suitable data source is connected. On **Solana**, the most recent transfers are decoded to show the amount, direction and USD value (SOL & SPL tokens); higher-volume bursts beyond that fall back to a "wallet transacted" signal. *** ## Noise Filters When you track a wallet on any non-Stacks chain you can tune what alerts you: | Filter | Options | Applies to | | ----------------------- | ------------------------------------------ | ----------------- | | **Minimum value (USD)** | 0 (everything) · $100 · $1k · $10k · $100k | All polled chains | | **Direction** | Both · Incoming only · Outgoing only | EVM & Bitcoin | Transfers we can't price (some tokens) are **never silently dropped** — they pass the minimum-value filter so you don't miss a large move we couldn't value. *** ## What Each Alert Includes | Field | Description | | --------------- | ----------------------------------------------- | | Chain | Which network the activity happened on | | Tracked Address | The address (shortened), or your custom label | | Direction | Received 📥 / Sent 📤 (transfers) | | Amount + Value | Asset amount and its USD value (when available) | | Counterparty | The other address involved (when available) | | Explorer Links | Direct links to the transaction and the wallet | {% hint style="success" %} **Premium feature:** Add custom labels to tracked addresses (e.g. "Team Wallet", "DEX Treasury") so alerts are easy to identify at a glance. {% endhint %} *** ## Setup 1. Use the `/nova` command and select **"Wallet Tracker"**. 2. Follow the wizard steps: * Toggle alerts on/off * **(Discord only)** pick a channel for the alerts — skip in DMs * **Select the blockchain** to track * Enter the **wallet address** for that chain * Choose your **minimum value** and (EVM/Bitcoin) **direction** filters * **Premium only:** add a custom label for the address * Review and confirm 3. When you see the success message, your wallet alerts are live. {% hint style="info" %} **Following an AI agent?** To track another agent on the aibtc network, you don't need the wizard — just tell Nova *"follow bitcoio.btc"* and it sets up on-chain tracking for you (plus optional inbox and level-up alerts). See [Agent Observatory](/nova-bot/nova-ai-agent/agent-observatory). {% endhint %} # Premium Alerts Exclusive alert types for Premium subscribers: early access to new token launches, NFT deployments, contract activity, and whale movements on Stacks. {% hint style="warning" %} These alerts require an active **Premium subscription**. See [Premium](/nova-bot/premium) for plans and pricing. {% endhint %} *** ## Available Alert Types | Alert Type | What It Tracks | Configurable Options | | --------------------- | --------------------------------------------------------------------------------- | -------------------------------------- | | **Token/Pair Sniper** | A new DEX pool or bonding curve token is deployed on Stacks | Channel only | | **NFT Sniper** | A new NFT smart contract is deployed on Stacks | Show all mints vs new collections only | | **Contract Sniper** | Any new smart contract deployment — includes deployer address and contract source | Channel only | | **Whale Transfers** | Whales moving large amounts of tokens on the Stacks chain | Channel only | *** ## Setup 1. Use the `/premium` command and select **"Notifications Setup"**. 2. Follow the wizard steps: * Toggle alerts on/off * **(Discord only)** pick a channel for the alerts — skip in DMs * Select which Premium alert types to enable * If enabling **NFT Sniper**: choose between all mints or new collection deployments only * Review and confirm 3. When you see the success message, your Premium alerts are live. # ZADAO Alerts Get alerts for activity on [Zero Authority DAO](https://zeroauthoritydao.com): bounties, gigs, quests, campaigns, and grants. Four feeds are configured with a slash-command wizard; grants are configured conversationally by just talking to Nova. | Feed | Command | Triggers | Filters / options | | ------------- | ------------ | --------------------------------------------------------- | ---------------------------------------------------------------------- | | **Bounties** | `/bounty` | Bounty created, entry submitted, bounty completed | Campaign filter, submission alerts toggle, per-type channels (Discord) | | **Gigs** | `/gigs` | Gig created, gig completed | — | | **Quests** | `/quest` | New quest, quest joined, activity completed, ending/ended | Alert-type selection, campaign filter, per-type channels (Discord) | | **Campaigns** | `/campaigns` | Campaign created | — | | **Grants** | *ask Nova* | New grant, milestone completed, grant completed | Category, per-event toggles, minimum amount | A **Campaign** is what was formerly called a "Hub" on ZADAO. *** ## How Setup Works The four command-based feeds all follow the same wizard flow, on Telegram and Discord alike: 1. Run the feed's command (`/bounty`, `/gigs`, `/quest`, or `/campaigns`). 2. Select **"Notifications Setup"**. 3. Toggle alerts on or off. 4. **(Discord only) pick a channel** for the alerts — skip in DMs. Where a feed supports it, you can route different alert types to different channels. 5. Set the feed-specific options below, review, and confirm. A success message means the alerts are live. {% hint style="warning" %} On Telegram, don't click selection buttons too quickly — Telegram may temporarily rate-limit excessive interactions. {% endhint %} *** ## Bounties — `/bounty` | Trigger | Details | | -------------------- | ----------------------------------------------------------------------------------------------- | | **Bounty Created** | A new bounty was posted — includes Campaign, title, prize, type (single/multi-winner), deadline | | **Entry Submitted** | Someone submitted to a bounty you're tracking (optional) | | **Bounty Completed** | A bounty was completed — includes winner(s) and prize info | Options: submission alerts on/off, and an optional **Campaign filter** to only receive bounties from specific organizations. On Discord you can route bounty alerts and submission alerts to different channels. *** ## Gigs — `/gigs` | Trigger | Details | | ----------------- | ------------------------------------------------------------------ | | **Gig Created** | A new gig was posted — includes creator, recipient, and max reward | | **Gig Completed** | A gig was marked as completed | No extra options — just toggle and go. *** ## Quests — `/quest` Choose which of these alert types to receive: | Trigger | Details | | ---------------------- | --------------------------------------------------------------------------- | | **New Quest Created** | A quest went live — title, campaign, deadline, rewards | | **Quest Joined** | Someone joined a quest — participant address, STX amount, participant count | | **Activity Completed** | Someone completed a quest activity | | **Quest Ending/Ended** | Reminder \~24 hours before the deadline, plus a notice when it closes | Options: an optional **campaign filter**, and on Discord a **channel per alert type** (e.g. new quests in #announcements, joins in #activity). On Telegram all selected types go to the same chat. **Permissions:** in Telegram groups only group admins can set up quest alerts; in Discord servers only members with **Manage Messages** or **Administrator**. Anyone can set them up via DM. Each quest alert includes fields depending on the type: | Field | Description | Alert types | | ------------------ | ------------------------------------------ | ----------------- | | Quest Title | Name with a direct link to the quest | All | | Campaign | The campaign the quest belongs to (if any) | All | | Deadline | When the quest expires | New Quest | | REP Rewards | Total reputation points available | New Quest | | NFT Reward | Whether an NFT reward is included | New Quest | | Activities | Number of activities/subtasks to complete | New Quest | | Creator | The quest creator's address | New Quest | | Participant | Address of the user who joined/completed | Joined, Completed | | STX Amount | STX staked on join (if applicable) | Joined | | Participants Count | Total number of quest participants | Joined | *** ## Campaigns — `/campaigns` | Trigger | Details | | -------------------- | ------------------------------------------------------------------------ | | **Campaign Created** | A new campaign was launched — includes name, description, and admin info | No extra options — just toggle and go. *** ## Grants — Just Ask Nova Unlike the feeds above, grant alerts have **no command or wizard** — configure them conversationally by mentioning or DMing Nova. In public groups/servers only admins and moderators can configure them; DM Nova for personal alerts. | Trigger | Details | | ----------------------- | ----------------------------------------------------------------------------------------- | | **New Grant** | A new grant appeared — project name, category, description, amount, network, and grantee | | **Milestone Completed** | A grant completed one of its milestones — includes progress (e.g. 2/4) and milestone name | | **Grant Completed** | A grant reached Completed status | | Option | Values | Default | | -------------------- | ---------------------------------------------- | -------------- | | **Grant categories** | DeGrants, BlueSky, Community, SocialFi | All categories | | **New grants** | on / off | on | | **Milestones** | on / off | on | | **Completions** | on / off | on | | **Minimum amount** | Any number (awarded or requested amount floor) | No floor | > @Nova alert me about new DeGrants grants above 5,000 Changing a setting later works the same way — Nova updates only what you ask for and keeps the rest untouched. Ask *"what ZADAO alerts do I have in this chat?"* to review, or *"turn off grant alerts"* to stop. {% hint style="success" %} All of these alerts also appear in your web dashboard's [Alerts Hub](/nova-bot/alerts-setup-guides/managing-your-alerts-web-dashboard), alongside every other Nova alert. {% endhint %} # Events & Governance Alerts Get alerts for Stacks ecosystem events (meetups, hackathons, conferences, community calls) and Stacks governance activity (SIPs and CAB voting). Both are set up **conversationally** — no command or wizard, just tell Nova what you want to monitor. Available on Discord and Telegram. *** ## How Setup Works 1. Describe the alert to Nova in plain language. 2. Nova interprets the request, builds the alert conditions, and confirms them back to you (e.g. *"I'll set up an alert for new Stacks ecosystem events. Sound good?"*). 3. You confirm, and the alert is created. 4. Nova polls the data source on a schedule (see each topic below) and notifies you when conditions match. **Combining conditions is a Premium feature** — Premium users can pair multiple conditions with AND/OR logic in one alert, e.g. *"alert me about new virtual events only"* (change\_type = new\_event AND event\_type = virtual) or *"alert me when SIP-034 reaches Ratified"* (sip\_id = sip-034 AND sip\_status = Ratified). ### Free vs Premium | | Free | Premium | | ------------------------- | ------ | -------- | | Max alerts | 2 | 50 | | Conditions per alert | 1 | Up to 10 | | Cooldown between triggers | 1 hour | 1 minute | | Composable conditions | -- | Yes | | Time windows | -- | Yes | | Digest mode | -- | Yes | Both alert types count toward your total alert limit. See [Premium](/nova-bot/premium) for the canonical limits and plans. *** ## Ecosystem Events Alerts when events are posted, about to start, or change status. **Polled every 30 minutes** — a cooldown of 30+ minutes is recommended. Data is sourced from the [Zero Authority DAO](https://zeroauthoritydao.com) events platform. | Trigger | Details | | -------------------- | ------------------------------------------------------------------ | | **New Event Posted** | A new event was added to the Stacks ecosystem calendar | | **Starting Soon** | An event is starting within the next hour | | **Status Change** | An event's status changed (e.g. upcoming → in-progress, cancelled) | Event details include: title, date/time, virtual vs in-person, location or meeting link, host, attendee count, token requirements, and on-chain attendance badges. > *"Notify me when new virtual events are posted"* **Condition fields** (Nova builds these from your description): | Field | Values | Description | | -------------------- | ---------------------------------------------------- | ---------------------------------------- | | **change\_type** | `new_event`, `status_change`, `starting_soon`, `any` | What kind of event activity triggered it | | **event\_type** | `virtual`, `irl` | Virtual or in-person events | | **event\_status** | `upcoming`, `in-progress`, `completed`, `cancelled` | Current status of the event | | **host\_username** | Any username | Filter by event host | | **tokens\_required** | `true`, `false` | Whether the event requires token staking | You can also browse without creating an alert — ask things like *"What Stacks events are coming up?"* or search events by topic. *** ## SIP Governance Alerts for Stacks Improvement Proposals (SIPs) and CAB (Consideration Advisory Board) voting. **Polled every 2 hours** — a cooldown of 120+ minutes is recommended. Data is sourced from the [Zero Authority DAO Governance API](https://zeroauthoritydao.com). | Trigger | Details | | --------------------- | ---------------------------------------------------------------------- | | **SIP Status Change** | A SIP moved between stages (e.g. Draft → Review → Accepted → Ratified) | | **New SIP Proposed** | A new SIP appeared in the registry | | **CAB Vote Opened** | A Consideration Advisory Board vote was opened for a SIP | | **CAB Vote Closed** | A CAB vote has concluded — includes yes/no/abstain tallies | **SIP details include:** title, status, type (Meta/Consensus/Standard), consideration area, authors, abstract, GitHub PR link, and forum discussion link. **CAB vote details include:** which SIP, voting status (open/closed), vote tallies (yes, no, abstain), and total votes cast. > *"Alert me when CAB voting opens on any SIP"* **Condition fields:** | Field | Values | Description | | ----------------------- | ------------------------------------------------------------------------------------------------------ | -------------------------------- | | **sip\_id** | e.g. `sip-032`, `sip-021`, or `any` | Specific SIP or wildcard | | **sip\_status** | `Draft`, `Review`, `Accepted`, `Activation-in-Progress`, `Ratified`, `Withdrawn`, `Rejected`, or `any` | Target status | | **change\_type** | `status_change`, `new_sip`, `cab_vote_opened`, `cab_vote_closed` | What kind of governance activity | | **cab\_voting\_status** | `opened`, `closed`, `any` | CAB vote state filter | **SIP lifecycle:** ``` Draft -> Review -> Accepted -> Activation-in-Progress -> Ratified \-> Withdrawn \-> Rejected ``` CAB voting can occur at various stages and influences whether a SIP advances. You can also browse without creating an alert — ask *"What's the status of SIP-032?"*, list SIPs by stage, check open CAB votes, or view governance stats. Nova returns full SIP details including CAB voting state, vote tallies, and links to GitHub and forum discussions. # GM Alerts (Legacy) This page covers the **legacy per-channel `/gm` opt-in**: when someone says "gm" (or a variant like "good morning"), Nova replies with a short Bitcoin & Ordinals news brief, plus optional per-community custom sources. {% hint style="info" %} **New setups should use** [**Community GM**](/nova-bot/nova-ai-agent/community/community-gm) **instead** — it's neutral by default and per-community, matching each community's own ecosystem rather than always sending Bitcoin/Ordinals. If a community-level GM is enabled, it takes precedence for the whole server/group. {% endhint %} For legacy users, the old `/gm` still works: * **Opt-in per chat** — enabled per group on Telegram, per channel on Discord (Nova only replies where you've enabled it). DMs are not supported. * **Admin only** — Telegram group admins; Discord requires **Manage Server** or **Administrator**. * Run `/gm` to enable, manage custom sources (RSS feed, webpage URL, or Stacks address — 3 Free / 10 Premium per chat or channel), or disable. * Cooldowns: the shared brief regenerates at most every 6 hours, and each chat/channel receives a GM at most once per 36 hours. **To migrate:** run `/gm` and disable it in each legacy chat/channel, then set up [Community GM](/nova-bot/nova-ai-agent/community/community-gm) for your community. # Alert History & Delivery Status Check whether your Smart Alerts have been firing — and whether those notifications actually reached you. Just ask Nova; no command or setup needed. Check whether your Smart Alerts have been firing — and whether those alerts actually reached you. Just ask Nova; no command or setup needed. This page is the **audit** half of a pair: to review, toggle, snooze, or delete alerts, see [Managing Your Alerts (Web Dashboard)](/nova-bot/alerts-setup-guides/managing-your-alerts-web-dashboard). {% hint style="info" %} This is **self-serve and private**: Nova only ever shows you the activity of **your own** alerts. Available on Discord, Telegram, and the web widget. {% endhint %} *** ## What You Can Ask Ask broadly to list recent fires across **every** alert you own, with their delivery status: > *"Show my alerts that fired recently"* Or scope to a single alert by its ID (find IDs with *"list my alerts"*): > *"Show history for alert #7"* Nova answers conversationally — no wizard, no `/command`. *** ## What You'll Get | Field | Description | | ------------------- | -------------------------------------------------------------------------- | | **Alert** | Which alert fired (name + type) | | **Triggered at** | When the alert's conditions were met | | **Delivered** | Whether the alert was actually sent to you | | **Platform** | Where it was delivered (Discord / Telegram / widget) | | **Delivery status** | `pending`, `delivered`, or `dead` (gave up after retries) | | **Attempts** | How many delivery attempts were made | | **Last error** | If a delivery failed, the reason — useful for "why didn't I get my alert?" | *** ## "Why didn't I get my alert?" If an alert's conditions were met but nothing reached you, the delivery status explains why: * **delivered** — it was sent; check the platform/channel it went to (and your Do-Not-Disturb / snooze settings). * **pending** — it's queued and will be retried shortly. * **dead** — delivery failed repeatedly and was given up on; the **last error** shows the cause (e.g. the bot was blocked, or DMs are closed). {% hint style="warning" %} A **snoozed** alert or active **Do-Not-Disturb** window can suppress delivery even when the alert fired. Ask *"is my whale alert snoozed?"* or *"what are my DND settings?"* to check. {% endhint %} *** ## Related {% content-ref url="/pages/JHbv4S0CmvZYYAnh8gvH" %} [Managing Your Alerts (Web Dashboard)](/nova-bot/alerts-setup-guides/managing-your-alerts-web-dashboard) {% endcontent-ref %} To create, edit, pause, or clean up alerts, just tell Nova what you want (*"create a whale alert for STX over 100k"*). History only **reports** activity — it never changes your alerts. # ZADAO Stats Track community engagement and platform activity for [Zero Authority DAO](https://zeroauthoritydao.com) directly from Discord and Telegram. The `/zadao` command opens an interactive menu where anyone can pull up stats for the last 24 hours, 3 days, 7 days, or 30 days. {% hint style="info" %} `/zadao` is a stats viewer, not an alert. It works in groups and DMs — anyone can use it, no admin permission needed. {% endhint %} *** ## What You Can See | Section | What it shows | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **📊 Full Report** | The complete picture — community activity, platform stats, and the Top Contributors leaderboard, all in one view | | **👥 Community** | Discord and Telegram member counts, net growth, active users, repeat users, total messages | | **🥇 Top Contributors** | Top 10 by **quality-weighted contribution score** (quality + answers + helping newcomers + mod-weighted reactions + consistency), each with a one-line "why" — combined, or split by Discord / Telegram. See below. | | **🏆 Top Members** | Top 10 most active by raw **message count** in the chosen window — combined, or split by Discord / Telegram | | **🚀 Platform** | ZADAO platform metrics — new signups, bounties launched, submissions made, gigs created, new partners, platform volume (TVE) | Every section is scoped to a time window you choose: last 24h, 3 days, 7 days, or 30 days. *** ## How "Active" and "Repeat" Are Counted | Term | Definition | | --------------- | ------------------------------------------------------------------------------------ | | **Active user** | Sent at least 1 message in the chosen window | | **Repeat user** | Was active on at least 2 different days in the window — a stronger engagement signal | | **Net growth** | Members today minus members at the window start (positive = grew, negative = lost) | *** ## Use it on Telegram 1. **Open the menu:** * Type `/zadao` in any chat (group or DM). 2. **Pick a section:** * **Full Report** · **Community** · **Top Contributors** · **Top Members** · **Platform Stats** 3. **Pick a time window:** * **24h** · **3 days** · **7 days** · **30 days** 4. **(Top Contributors / Top Members only)** Pick a leaderboard: * **Combined** (best of both platforms) · **Discord-only** · **Telegram-only** 5. **Read the result.** Use the **Back to Menu** button to ask another question without retyping `/zadao`. *** ## Use it on Discord 1. **Open the menu:** * Type `/zadao` (the response is ephemeral — only you see it). 2. **Pick a section, then a window** using the buttons. 3. **Result is shown in an embed** with a **Back to Menu** button to keep exploring. The same data is also available conversationally — just ask Nova: > *"Who are the top 5 active members in Discord this week?"* *** ## 🥇 Top Contributors — the quality score The **Top Contributors** leaderboard (and the **weekly recap**) ranks members by a **contribution score**, not raw message count — so simply posting a lot doesn't put you on top. Each member's score combines: | Signal | What it rewards | | ----------------------- | --------------------------------------------------------------------------------- | | **Message quality** | Substantive, helpful, on-topic messages (rated by Nova) — spam and filler score 0 | | **Answering questions** | Actually answering questions other members ask | | **Helping newcomers** | Welcoming and guiding people who recently joined | | **Reactions received** | Reactions on your messages — **moderator/admin reactions are weighted highest** | | **Consistency** | Showing up across multiple days, not just one burst | Each member also gets a one-line "why" next to their score, e.g. *answered 7 Qs · helped 3 newcomers · 14 react pts · active 6/7d*. Daily caps keep any single long post or one busy day from dominating. **Top Contributors** (quality score) and **Top Members** (raw message count) are both available in the `/zadao` menu, so you can compare who's *most helpful* against who's *most active*. The weekly recap headlines **Top Contributors**. *** ## Weekly Auto-Recap Every **Monday at 09:00 UTC**, Nova posts a full weekly recap to the configured ZADAO Discord channel and Telegram chat. The recap covers the previous 7 days: community activity, platform stats, and the **🏆 Top Contributors** leaderboard (with a "Most active by volume" footnote for the raw-count view). > Example recap topics: *47 new Discord members, top contributors of the week (who answered questions, helped newcomers, earned mod reactions), 12 new ZADAO signups, 8 bounties launched, 3 new partners, $4.2K platform volume.* *** ## Privacy Note To compute community stats, Nova logs **message metadata** — timestamp, sender username, and character count — plus **reactions** (which message, who reacted, whether they're a mod). To score contribution quality, message **text is stored temporarily** and is **automatically deleted after 14 days**; only the resulting scores and counts are kept long-term. Message-metadata records older than 365 days are automatically deleted. *** {% hint style="info" %} This command is currently scoped to the official ZADAO Discord server and Telegram group. If you'd like the same tracking for another community, reach out — generalizing it is a small additional setup. {% endhint %} # Managing Your Alerts (Web Dashboard) See and manage **every** alert you own in one place — the Nova web dashboard's **Alerts & Notifications** hub pulls all four of Nova's alert systems into a single categorized, filterable view. This page is the **manage** half of a pair: to check whether an alert fired and was delivered, see [Alert History & Delivery Status](/nova-bot/alerts-setup-guides/alert-history-and-delivery-status). {% hint style="info" %} Sign in at the Nova dashboard with your **wallet**, **Discord**, **Telegram**, or **Google** account. The hub shows the alerts tied to whichever accounts you've linked. {% endhint %} *** ## What's Included The hub unifies four systems that used to live in separate places: | System | What it covers | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | **Channel notifications** | Token swaps, NFT activity, runes, wallet/address tracking, malicious contracts, bounties, gigs, quests, campaigns, GM, SIPs, premium snipers | | **Smart Alerts** | Your personal price / whale / DEX / NFT / balance / contract / block-height / stacking-cycle alerts | | **Nova Guardian** | Scam-moderation protection you enabled for a server or group | | **Community Snacks** | Daily community engagement posts you scheduled | *** ## How It's Organized ### 1. Ownership tabs The hub splits your alerts into two tabs so it's always clear what an alert *is*: * **🔔 My Alerts** — personal alerts that follow **you** wherever Nova reaches you (Smart Alerts, your wallet tracking). * **📡 Community Feeds** — feeds you set up for a **Discord server or Telegram group** you manage. ### 2. Categories Within each tab, alerts are grouped into collapsible sections with live counts: | Category | Examples | | ----------------------------- | ------------------------------------------------- | | 📈 **Market & Trading** | swaps, runes, snipers, price/whale/DEX/fee alerts | | 👛 **Wallet & Tracking** | address tracking (14+ chains), balance alerts | | 🖼️ **NFTs & Collectibles** | mints, sales, listings, NFT snipers | | 🛡️ **Security & Protection** | Nova Guardian, malicious-contract & risk alerts | | 🌐 **Community & Ecosystem** | bounties, gigs, quests, campaigns, GM, snacks | | 🏛️ **Governance & Network** | SIPs, block-height & stacking-cycle events | ### 3. Filters A filter bar lets you narrow the list by **platform** (Discord / Telegram / Web), **status** (active / disabled / snoozed), **chain** (multi-select), **premium-only**, and a free-text **search**. *** ## What You Can Do {% hint style="success" %} V1 is **manage-only** — you can review, toggle, snooze, and delete from the dashboard. To **create** a new alert, use the Nova bot in Telegram or Discord. {% endhint %} | Action | Where | | ----------------------------- | ---------------------------------------------- | | **Enable / disable** an alert | Toggle on each card | | **Snooze** a Smart Alert | Clock icon → 1h / 8h / 24h / 1 week (or clear) | | **Delete** an alert | Trash icon → confirm | | **Bulk actions** | Select multiple → Enable / Disable / Delete | | **View full config** | Click a card to open its detail drawer | The **summary strip** at the top shows totals at a glance: *Total · Active · Disabled · Snoozed · Premium*. *** ## Creating New Alerts Creation stays in the bot wizards, where Nova has the channel/server context it needs: | Command | Sets up | | ------------------------------------------ | -------------------------------------------------------------- | | `/nova` | Token swap, NFT, and wallet-tracking alerts | | `/bounty`, `/gigs`, `/quest`, `/campaigns` | [ZADAO alerts](/nova-bot/alerts-setup-guides/zadao-alerts) | | Ask Nova directly | Smart Alerts (e.g. *"create a whale alert for STX over 100k"*) | | `/nova_guardian` | Scam-moderation protection | {% hint style="info" %} Don't see a community feed you set up? The hub shows community configs **you created**. If a teammate enabled it, ask them — or re-run the setup yourself. {% endhint %} *** ## Related {% content-ref url="/pages/zfRYiTqbsT4IABFjc8vF" %} [Alert History & Delivery Status](/nova-bot/alerts-setup-guides/alert-history-and-delivery-status) {% endcontent-ref %} {% content-ref url="/pages/j8XaxQtXiDoP7CSe0Oc2" %} [Premium Alerts](/nova-bot/alerts-setup-guides/premium-alerts) {% endcontent-ref %} # Token-Gated Discord Roles Automatically assign and manage Discord roles based on verified ownership of Stacks-based tokens and NFTs. This system uses on-chain verification and keeps roles in sync over time. ### What This Does * Assign roles using Stacks FT or NFT ownership * Secure wallet verification * Admin-configurable thresholds * Optional role re-syncing {% content-ref url="/pages/tWj9dXabZKkxHniq7y4V" %} [For members (Get roles)](/nova-bot/token-gated-discord-roles/for-members-get-roles) {% endcontent-ref %} {% content-ref url="/pages/bP8ZapP1zXpnkUUGGNNT" %} [For Admins (Setup Roles)](/nova-bot/token-gated-discord-roles/for-admins-setup-roles) {% endcontent-ref %} {% content-ref url="/pages/GdHveA86f97vqMxwRYX1" %} [Syncing & Automation](/nova-bot/token-gated-discord-roles/syncing-and-automation) {% endcontent-ref %} {% content-ref url="/pages/OQQ1Lr44aTXyxPZgIYsu" %} [FAQ & Troubleshooting](/nova-bot/token-gated-discord-roles/faq-and-troubleshooting) {% endcontent-ref %} # For members (Get roles) Use this if you want to unlock Discord roles in an already setup server, by verifying your Stacks wallet. ### Step-by-Step 1. Run `/roles` in the Discord server 2. Select **Get Roles** 3. Click the verification link 4. Connect your Stacks wallet 5. Return to Discord — roles are assigned automatically > ⏳ Verification expires after 2 minutes\ > 🔐 We never ask for private keys {% hint style="info" %} **Results** * ✅ Roles assigned * ⚠️ Verified, but no eligible roles * ❌ Verification failed or expired {% endhint %} # For Admins (Setup Roles) This section is for Discord servers administrators only. ### Before You Start Make sure: * The bot has the **Manage Roles** permission * The bot’s role is **above all roles** it should assign * All Discord roles to be gated are **already created** * Gated roles are **not managed by other bots or integrations** * You know the **exact contract IDs** (eg. `SP3...KKZ.nope`) for the assets you want to use ### Setup Flow 1. Run `/roles` 2. Select **Setup Roles** 3. Click **Add Role** 4. Choose a Discord role 5. Select FT or NFT 6. Enter contract and threshold 7. Repeat as needed 8. Review and save {% hint style="info" %} **Role Limits** * Free servers: 10 roles * Premium servers: 30 roles {% endhint %} ### Contract Validation * Contract must exist on-chain * FT/NFT type must match * Threshold must be a positive number # Syncing & Automation Syncing re-checks on-chain holdings for users who have already verified a wallet in this server and updates their Discord roles accordingly. It does not affect users who have never verified. ### What Sync Does When you run **Sync Roles** in your server, the system: * Re-fetches current FT and NFT balances for **previously verified users** * Compares holdings against **current role rules** * Adds roles users newly qualify for * Removes roles users no longer qualify for * Updates the server’s role assignments to match on-chain reality ### What Sync Does *Not* Do Syncing **does NOT**: * ❌ Verify new users * ❌ Ask users to reconnect wallets * ❌ Assign roles to users who never verified * ❌ Run continuously or in real time ### When You Should Run Sync Run **Sync Roles** when: * Users token balances have changed significantly * You **update role thresholds** * You **add or remove role mappings** * You want to ensure roles reflect the **current on-chain state** ### How to Run Sync 1. Run `/roles` 2. Select **Sync Roles** 3. Wait for the confirmation message {% hint style="info" %} ⏱️ Sync can be triggered **once every 72 hours per server** {% endhint %} > ⚠️ Sync affects ALL previously verified users in the server. Changes are applied automatically and cannot be undone. # FAQ & Troubleshooting [#roles-were-not-assigned-why](#roles-were-not-assigned-why "mention")
[#sync-ran-but-roles-didnt-change-why](#sync-ran-but-roles-didnt-change-why "mention") [#setup-failed-why](#setup-failed-why "mention") [#security-and-trust](#security-and-trust "mention") [#still-stuck](#still-stuck "mention") ### Roles were not assigned — why? #### 1️⃣ The bot’s role is below the gated role **What this means** Discord does **not** allow a bot to assign roles that are higher than (or equal to) its own highest role. **How to fix** 1. Go to **Server Settings → Roles** 2. Find the bot’s role 3. Drag it **above all roles** you want the bot to assign 4. Save changes 5. Re-run **Get Roles** or **Sync Roles** > The bot cannot override Discord’s role hierarchy. *** #### 2️⃣ The role is managed by another bot or integration **What this means** Roles created or controlled by: * Other bots * Discord apps * Integrations are marked as **managed** and **cannot be modified**. **How to fix** * Create a **new role manually** in Discord * Do **not** assign it to another bot * Use the new role in your role mappings *** #### 3️⃣ The user does not meet the required threshold **What this means** The wallet was verified successfully, but the user’s holdings are **below the configured requirement**. **How to check** * Review the role’s contract ID * Confirm the threshold value * Verify the user’s on-chain balance manually if needed *** #### 4️⃣ FT threshold misunderstood (decimals issue) **What this means** FT thresholds are **human-readable**, not raw on-chain units. Example: * If a token has 6 decimals * A threshold of `100` means **100 tokens**, not `100000000` **What to do** * Enter thresholds exactly as humans read them * The system automatically handles decimals *** #### 5️⃣ Wrong contract type selected (FT vs NFT) **What this means** * An FT contract was configured as an NFT * Or an NFT contract was configured as an FT The system will reject mismatches during setup. **How to fix** * Double-check the contract type * Re-add the role with the correct asset type *** #### 6️⃣ User verified, but nothing changed **What this means** * Verification succeeded * User does not qualify for any roles **yet** **What to do** * No action required * Roles will be assigned once thresholds are met *** ### Sync ran, but roles didn’t change — why? #### 1️⃣ User never verified a wallet **Explanation** Syncing only affects users who have **verified at least once** in the server. **Solution** Ask the user to run **Get Roles**. *** #### 2️⃣ User changed wallets **Explanation** Syncing reuses the **last verified wallet**. **Solution** User must re-run **Get Roles** to link a new wallet. *** #### 3️⃣ Sync cooldown active **Explanation** Sync can only run **once every 72 hours** per server. **Solution** Wait for the cooldown to expire. *** ### Setup failed — why? #### 1️⃣ Invalid or non-existent contract ID **Explanation** The system validates contracts via the Hiro API. **Solution** * Ensure the contract ID is correct * Confirm it exists on Stacks mainnet *** #### 2️⃣ Contract is neither FT nor NFT **Explanation** Some contracts do not define tokens. **Solution** Only use contracts that define: * `define-fungible-token` * `define-non-fungible-token` *** ### Security & Trust #### Does the system access private keys? No. Wallet connections are read-only. #### Are roles updated in real time? No. Role updates occur during verification or sync. *** ### Still Stuck? Before contacting support, verify: 1. Bot role hierarchy 2. Role is not managed 3. Contract ID correctness 4. User has verified 5. Sync cooldown status {% hint style="info" %} If the issue persists after checking the steps above: 1. Open a **support ticket** in the official Discord server 2. Include: * Server ID * Affected role name * Contract ID * What action you were trying to perform If Discord support is unavailable, you can DM **@ghislo740** on Telegram. {% endhint %} # Nova AI Agent Nova is your conversational AI assistant for blockchain and your community — no dashboards, just ask in plain English. Powered by Claude, it has the deepest coverage of the Bitcoin and Stacks ecosystems plus broad multi-chain support, and 200+ tools to answer with real-time, verified data. {% hint style="success" %} Nova is available on **Discord**, **Telegram**, and the **Web Widget**. Mention the bot or reply to any of its messages to start a conversation. {% endhint %} *** ## How to Talk to Nova Mention **@Nova** in a Discord channel, reply to one of its messages, or send a direct message. On Telegram, message in any group where Nova is active or DM the bot. No special syntax needed: > *"What's the current STX price?"* Nova figures out the intent, picks the right tools, and responds with accurate, sourced data. *** ## What Nova Can Do
Blockchain CoveragePrices, portfolios, transactions, and contracts across Bitcoin/Ordinals, Stacks, EVM chains, Solana, TON, Sui, Aptos, and Hyperliquid
Market IntelligencePortfolio P&L, whale tracking, pool analytics, and cohort/watchlist analysis
ZADAO EcosystemBounties, gigs, grants, quests, user profiles, documentation
Agent ObservatoryLook up, rank, and follow other AI agents on the aibtc network
News & ResearchBitcoin Optech, ecosystem updates, SIP proposals, market news, web search
Smart AlertsCustom conditional alerts for prices, whales, contracts, and more
Governance & EventsSIP tracking, CAB voting, ecosystem events, governance alerts
Emblem VaultLook up, browse, and create Emblem Vaults — guided and non-custodial
Community ManagementAnti-scam shield (Guardian), moderator copilot (Pulse), and an engagement suite with XP, leaderboards, trivia & giveaways (Community Games)
Community StatsEngagement stats, contributor leaderboards, member growth, weekly recaps, daily community snacks
*** ## Feature Guides Dive deeper into each capability: {% content-ref url="/pages/z8lRM9mgo8TKykfpATx5" %} [Blockchain Coverage](/nova-bot/nova-ai-agent/blockchain-coverage) {% endcontent-ref %} {% content-ref url="/pages/Wa5ca4X2RNO4NNoFPOjR" %} [Market Intelligence](/nova-bot/nova-ai-agent/market-intelligence) {% endcontent-ref %} {% content-ref url="/pages/HsNJhdgs7CEjY3D9P6MZ" %} [ZADAO Ecosystem](/nova-bot/nova-ai-agent/zadao-ecosystem) {% endcontent-ref %} {% content-ref url="/pages/lZ1WcRsCI5vZZoEISU60" %} [Agent Observatory](/nova-bot/nova-ai-agent/agent-observatory) {% endcontent-ref %} {% content-ref url="/pages/v0AdMi4uqhnRNBGrLhXb" %} [Community](/nova-bot/nova-ai-agent/community) {% endcontent-ref %} {% content-ref url="/pages/tLXII7Ts4I0rhDERpoUQ" %} [Smart Alerts](/nova-bot/nova-ai-agent/smart-alerts) {% endcontent-ref %} {% content-ref url="/pages/1SvrS932rMvTrM2Eyo81" %} [News & Research](/nova-bot/nova-ai-agent/news-and-research) {% endcontent-ref %} {% content-ref url="/pages/9liNh6a1Ax6V6AEdwkvz" %} [Memory & Personalization](/nova-bot/nova-ai-agent/memory-and-personalization) {% endcontent-ref %} {% content-ref url="/pages/leGGP5LjGZCdKEauPDmJ" %} [Emblem Vault](/nova-bot/nova-ai-agent/emblem-vault) {% endcontent-ref %} {% content-ref url="/pages/Jm062Pl5o0XMCJZRSexW" %} [Nova for CAB Groups & Governance Participants](/nova-bot/nova-ai-agent/nova-for-cab-groups-and-governance-participants) {% endcontent-ref %} *** ## Tips for Best Results * **Be specific** — *"What's the floor price for Bitcoin Puppets?"* works better than *"tell me about NFTs"* * **Provide context** — Include contract addresses, token names, or wallet addresses when you have them * **Ask follow-ups** — Nova remembers your conversation context, so you can drill deeper * **Use natural language** — No need for special commands or syntax when chatting with Nova *** ## Limits Free and Premium message, cooldown, and alert limits are listed in the [Premium guide](/nova-bot/premium). # Blockchain Coverage Nova reads live data across Bitcoin, Stacks, 60+ EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BSC, Avalanche, zkSync, Linea, Scroll, and more), Solana, TON, Sui, Aptos, and Hyperliquid — and new chains are added regularly. {% hint style="info" %} Nova auto-detects the chain from what you ask. Mention the chain (e.g. "on Base", "Solana wallet", "TON address") when an address or token exists on more than one network. {% endhint %} *** ## Token Prices & Market Data Ask for any token's live price — by symbol or by contract address / coin type — on any supported chain. **Example prompt:** > *"What's the price of WELSH?"* — or ETH, PEPE, TON, SUI, APT… or any token on any supported chain **What you'll get:** * Live USD price, market cap / FDV, liquidity, and 24h volume (plus 7d / 30d change on TON) * The DEX and trading pair the price came from * **Stacks:** top gainers/losers, trending tokens, DEX pool data (liquidity, volume, OHLC charts), and verified token lists to filter out scams * Sources per chain: DexScreener / CoinGecko (EVM), Jupiter (Solana), TON API (TON), GeckoTerminal (Sui & Aptos) *** ## Wallet & Portfolio Lookup Hand Nova any address and it builds a full, USD-valued portfolio in one shot. **Example prompt:** > *"What's in this wallet?"* — a Bitcoin `bc1q…`, a Stacks `SP…`, an EVM `0x…` (or `vitalik.eth`), a Solana, TON, Sui, or Aptos address **What you'll get:** * **Bitcoin:** BTC balance and spendable amount, BRC-20 holdings with USD values, Runes, Ordinals inscriptions owned, UTXO count, and mempool transactions * **EVM / Solana / TON / Sui / Aptos:** native balance + auto-discovered tokens (ERC-20, SPL/Token-2022, jettons, Move coins, Aptos coins & Fungible Assets), each valued in USD and sorted by worth — no need to know the contracts in advance * **NFTs by owner** — collection names + counts * **Total portfolio value** in USD {% hint style="warning" %} EVM portfolio lookups run **one chain per request** (default Ethereum) — ask again for each chain. Spam / airdrop "dust" tokens with no liquidity are excluded from the USD total. This is information only, **not financial advice**. {% endhint %} *** ## Transactions Paste a transaction hash from any chain — Stacks, Ethereum/EVM, Solana, TON, Sui, or Aptos — and Nova breaks it down. **Example prompt:** > *"What happened in this tx? 0x1234…"* **What you'll get:** * Status (pending, success, failed), from/to, value, and fees * The function that was called (decoded where possible) and the assets that moved * Token transfers, contract calls, and key events * Error diagnosis for failed transactions *** ## Smart Contracts Inspect any deployed contract, with per-chain depth: **Example prompt:** > *"What functions does this contract have?"* **What you'll get:** * **Stacks:** full Clarity source code, list of public and read-only functions, contract metadata * **EVM:** contract ABI, read-only contract calls, plus gas price, block, and chain info *** ## Bitcoin & Ordinals Beyond balances, Nova covers the full Bitcoin metaprotocol stack. ### Ordinals & Inscriptions > *"What's the floor price of NodeMonkes?"* Inscription content, sat number, and owner; collection floor prices, volumes, and sales data; holder distribution analysis; marketplace listings; activity history. ### BRC-20 Tokens > *"Show me info about the ORDI token"* Token supply, holders, and market stats; trending tokens ranked by activity; trading volume and marketplace listings. ### Runes > *"Tell me about the DOG rune"* Rune supply, holders, and market cap; top holder analysis; trading volume, stats, and activity feed. ### Sats & Rarity > *"What's special about sat 1234567890?"* Rarity classification (Common, Uncommon, Rare, Epic, Legendary, Mythic), special properties (Palindrome, Pizza, Nakamoto, etc.), and inscriptions on the sat. ### Lightning Network > *"Lightning Network stats"* Total capacity, channel count, node count; top nodes by capacity and connectivity. ### Bitcoin Network Data > *"Current Bitcoin fee estimates"* Fee estimates (high, medium, low priority), hash rate and difficulty, mining pool distribution, block height, and node count. For Bitcoin, Ordinals, Runes, and BRC-20 news, see [News & Research](/nova-bot/nova-ai-agent/news-and-research). *** ## Stacks Prices, portfolios, transactions, and contracts above all work on Stacks — with the deepest coverage of any chain Nova supports. ### Network Status > *"What's the current Stacks block height?"* Block height, network health, and current state of the Stacks network. For Stacks ecosystem and SIP news, see [News & Research](/nova-bot/nova-ai-agent/news-and-research). *** ## Token Safety / Rug Check Nova runs a risk read on EVM and Solana tokens. **Example prompt:** > *"Is this Base token a rug? 0x…"* **What you'll get:** * A safety read drawn from GoPlus (EVM + Solana) and RugCheck (Solana): mint/freeze authority, honeypot signals, holder concentration, LP status, taxes, and more * Plain-English flags + a not-a-guarantee disclaimer *** ## Name Resolution > *"Resolve vitalik.eth"* **ENS** resolution both directions (EVM) and **SNS / .sol** resolution (Solana). # Market Intelligence Nova integrates with Tenero.io for advanced multi-chain trading analytics — portfolio P\&L, whale tracking, pool analytics, and cohort analysis, all through conversation. For basic price lookups, trending tokens, and simple portfolio views, see [Blockchain Coverage](/nova-bot/nova-ai-agent/blockchain-coverage). *** ## Supported Chains Nova's market intelligence covers multiple chains through Tenero: * **Stacks** — Full DEX analytics * **Spark** — Token and pool data * **SportsFun** — Token analytics * **Citrea** — Token analytics * **OpNet** — Bitcoin L1 metaprotocol analytics (native asset: BTC) *** ## Portfolio P\&L Get a complete picture of any wallet's trading performance. **Example prompt:** > *"What's the P\&L for SP1234...?"* **What you'll get:** * Token holdings with current USD values * Profit & loss breakdown per token * Win rate and trading performance * Complete trade history *** ## Whale Tracking Monitor large trades and smart money movements. **Example prompt:** > *"Show me whale trades on Stacks"* **What you'll get:** * Recent large trades above USD thresholds * Top wallets accumulating (inflows) * Top wallets distributing (outflows) * Aggregated trader statistics *** ## Pool & Token Analytics Deep dive into any token or liquidity pool — you can also search tokens, pools, or wallets by name. **Example prompt:** > *"Trending pools on Stacks"* **What you'll get:** * OHLC candlestick price data * Top holders with percentage breakdown * Trending pools by activity * Recent trades feed (real-time) * Market-wide statistics *** ## Cohort & Watchlist Analytics Analyze groups of wallets and baskets of tokens in a single query — without asking N separate questions. {% hint style="info" %} Each cohort call supports up to **20 wallets** and/or **20 tokens** at once. {% endhint %} **Example prompt:** > *"Show me every buy of WELSH or LEO over $5k by these three addresses"* **What you'll get:** * **Merged holdings** across multiple wallets, with per-position aggregate balance, trade volume, and realized PnL — filter by min volume or min PnL * **Cross-wallet / cross-token trade feed** filtered by event type (buy/sell/swap), maker, amount range, or DEX platform * **Bulk portfolio valuation** — total USD value across up to 20 wallets in one call # Memory & Personalization Nova remembers your conversations and can learn context-specific information about your server or group, making interactions faster and more relevant over time. *** ## How Memory Works Nova uses a tiered memory system: * **Recent context** — the last few messages in your conversation, for natural follow-ups * **Short-term memory** — key topics from the last 48 hours, for continuity * **Long-term memory** — important facts and summaries, stored for up to 30 days Blockchain-related conversations are prioritized for longer retention. *** ## Teaching Nova Ask Nova to remember specific facts about your server or group, and it will recall them in future conversations within the same context. **Example prompt:** > *"Remember that our project token is WELSH"* — later, ask *"what do you remember about our project?"* *** ## User Preferences Personalize how Nova interacts with you — preferences follow you across all servers and groups where Nova is active. **Example prompt:** > *"Set my timezone to UTC-5"* **Available preferences:** timezone, response style (concise vs detailed), language preference, and personal notes. # News & Research Nova aggregates news from multiple trusted sources across the Bitcoin and Stacks ecosystems — ask for updates on any topic and get curated, real-time results. *** ## Bitcoin News **Example prompt:** > *"What's in the latest Bitcoin Optech newsletter?"* **Sources include:** Bitcoin Optech, CryptoSlate, Cointelegraph, Decrypt — covering protocol development (including BIP discussions) and market news. *** ## Stacks Ecosystem News **Example prompt:** > *"Latest Stacks news"* **What you'll get:** * Core development updates * SIP status changes and discussions * Hiro and ecosystem project announcements *** ## Ordinals, Runes & BRC-20 News **Example prompt:** > *"Ordinals news"* — or ask about Runes or BRC-20 market updates *** ## Web Search Nova can also search the open web for any topic. **Example prompt:** > *"Search for Clarity smart contract best practices"* **What you'll get:** * Relevant web results with summaries * Specific webpage content extraction when you provide a URL # Smart Alerts Smart Alerts are custom, conditional monitoring created through natural language — tell Nova what you want to watch, and it handles the rest. {% hint style="info" %} Smart Alerts are different from the notification commands (`/nova`, `/bounty`, `/quest`, etc.). Those are toggle-based. Smart Alerts are **condition-based** — they trigger only when your specific criteria are met. For per-alert-type setup guides, see the [Alerts Setup Guides](/nova-bot/alerts-setup-guides). {% endhint %} *** ## How It Works Describe the alert in plain English: > *"Alert me when STX goes above $2"* Nova creates a monitored alert that checks conditions and notifies you when triggered. Every alert comes with **one-tap explorer links** — the transaction, wallet, token, or contract behind the alert is one click away (explorer buttons on Discord, inline links on Telegram). **Preview before you commit.** For price alerts, ask *"how often would that fire?"* and Nova estimates the noise level before creating it (e.g. *"that would have fired about 12 times in the last week"*) by replaying your conditions over recorded price history, counting real notifications after the cooldown. Tighten the threshold or cooldown if it's too chatty. *** ## Alert Types | Alert Type | Example | | ----------------------- | ----------------------------------------------------- | | **Price threshold** | *"Alert me when WELSH drops below $0.001"* | | **Price change (%)** | *"Notify me if STX moves more than 10% in an hour"* | | **Whale transfers** | *"Watch for STX transfers over $50,000"* | | **DEX activity** | *"Alert on swaps over $10k on ALEX"* | | **New token pairs** | *"Tell me when new pools are created"* | | **NFT events** | *"Alert when floor price changes on Bitcoin Puppets"* | | **Contract deployment** | *"Notify me of new contracts deployed on Stacks"* | | **SIP governance** | *"Alert me on SIP status changes"* | | **CAB voting** | *"Notify me when CAB voting opens on any SIP"* | | **Ecosystem events** | *"Alert me about new Stacks events"* | | **Block height** | *"Alert me when Stacks hits block 200,000"* | | **Bitcoin fees** | *"Notify me when BTC fees drop below 10 sat/vB"* | | **Wallet balance** | *"Watch this address for balance changes"* | | **Stacking cycle** | *"Alert on PoX cycle events"* | *** ## What an Alert Looks Like Every notification leads with the **key numbers up front** — token, amount, value, and direction — readable at a glance. Discord gets rich embeds with one-tap link buttons; Telegram gets clean inline messages. **Whale transfer** — token, exact amount, USD value, and who sent it to whom: ``` 🔴 🐳 WELSH Whale Watch 🐳 1.50M WELSH ($142.6K) SP6X…AB1Q → SP3K…8N9 [ 🔗 Transaction ] [ 👤 Sender ] [ 🪙 Token ] ``` **Price move** — live price with percentage change and direction (🔺/🔻) over 1h and 24h, plus volume and holder context when available: ``` 💰 STX Price Watch STX $2.1500 🔺 +5.20% (1h) 🔻 -1.10% (24h) Vol $1.2M · 3.4K holders ``` **DEX swap** — colour-codes buys (🟢) vs sells (🔴) with size and venue: ``` 📊 ALEX Swap Radar 🟢 Buy 1.5M ALEX on Velar ($3.2K) ``` Numbers are formatted for readability (`1.50M`, `$142.6K`), and tiny sub-cent prices keep full precision (e.g. `$0.000842`) so meme-token alerts stay accurate. The coloured dot at the top reflects the alert's [severity](#severity--smart-routing) (🔴 high / 🔵 low). *** ## Precise Triggering Nova understands exactly *how* you want an alert to fire — phrase it naturally: * **Cross vs. stay-past** — *"Alert me when STX **crosses above** $2"* fires **once** on the breakout and won't nag while STX stays above; Nova re-arms it automatically if the price drops back and crosses again. *"…while STX **is above** $2"* can fire on every check (governed by your cooldown). * **Ranges** — *"Alert me when BTC fees are **between 5 and 20 sat/vB**"* * **Direction for % moves** — *"drops more than 10%"* fires only on a fall, *"rises"* only on a gain, *"moves"* in either direction. * **Text matching** — *"Alert me on SIPs whose title **contains** 'mining'"* (or *"except virtual ones"* for exclusions). *** ## Snooze & Quiet Hours **Snooze a single alert** — every Discord alert carries **😴 Snooze 1h** and **🌙 Snooze 24h** buttons; one tap and it goes quiet, then resumes on its own. Or just ask: > *"Snooze my whale alert for 2 hours"* (and *"un-snooze"* to resume early) **Quiet hours (Do Not Disturb)** — a recurring window where **all** your alerts go quiet; anything that fires is held and delivered as a tidy summary when the window ends: > *"Set quiet hours 11pm–8am, I'm UTC-5"* {% hint style="info" %} Tell Nova your timezone (or UTC offset) when setting quiet hours — otherwise the window is interpreted as UTC. Ask *"what are my quiet hours?"* or *"turn off quiet hours"* anytime. {% endhint %} *** ## Managing Your Alerts > *"Show my active alerts"* Manage everything conversationally: pause/resume, delete, update thresholds, and view trigger history. *** ## Tune & Clean Up Your Alerts Alerts drift — one becomes background noise, another hasn't fired in months. Ask Nova to review them: > *"Are any of my alerts too noisy?"* Nova looks at how often each alert actually fired and flags: * **Noisy** — Nova suggests raising the cooldown, tightening the threshold, or switching to a "crosses" / directional trigger — and for price alerts it quantifies the impact up front (e.g. *"this fires \~14×/week; a 60-minute cooldown would cut it to \~4×/week"*). * **Stale** — hasn't triggered in 90+ days; Nova suggests retiring it (or loosening the condition). This is read-only and available on every tier — Nova **only recommends**, and always asks before changing or deleting anything. *** ## Free vs Premium | | Free | Premium | | ------------------------- | ------ | -------- | | Max alerts | 2 | 50 | | Conditions per alert | 1 | Up to 10 | | Cooldown between triggers | 1 hour | 1 minute | | Advanced features (below) | -- | Yes | See the [Premium guide](/nova-bot/premium) for the full limits table. *** ## Premium Features ### Composable Conditions Combine multiple conditions with AND/OR logic: > *"Alert me when STX is above $2 AND 24h volume is over $1M"* ### Time Windows Restrict alerts to specific hours: > *"Only alert me between 9am and 5pm UTC"* ### Digest Mode Receive a daily summary instead of real-time alerts: > *"Switch my whale alerts to digest mode"* ### Severity & Smart Routing Tell Nova how urgent an alert is — *"make this a high-priority alert"* — and it routes the notification accordingly. Nova picks a sensible severity from how you phrase the request, and you can change it anytime. | Severity | How it's delivered | Styling | | ---------------------- | ----------------------------------------------------------- | -------- | | **High** | Always immediate — skips batching/digest | 🔴 red | | **Medium** *(default)* | Normal (batched for Premium, immediate for Free) | neutral | | **Low** | Bundled into your daily digest (Premium); immediate on Free | 🔵 muted | ### Dynamic Baselines (Relative Thresholds) Trigger off a token's own **rolling baseline** instead of a fixed number: > *"Alert me when WELSH is 20% above its 7-day average"* Nova compares the live price against its moving average (24h, 7-day, or 30-day window) or measures how many standard deviations it sits from that average (a "z-score" — roughly, |z| > 2 means outside the normal band). {% hint style="info" %} **Baselines warm up.** A 7-day or 30-day baseline needs a few days of history before it can fire. For stable, low-volatility tokens, combine a std-dev rule with an absolute move (e.g. *"…and it moved at least 5%"*) to cut false signals. {% endhint %} ### Unusual Volume & Holder Activity Spot anomalies in a token's **trading volume** or **holder base** relative to its own recent history: > *"Alert me if WELSH trades 3× its usual volume"* (or holder-side: *"more than 10% of holders leaving in 24h"*) Nova tracks each token's 24h volume and holder count hourly and compares the live value against its rolling 7-day / 30-day picture — as a percentage versus the average or as a z-score. Use the token's **full contract** (not just a ticker), remember baselines warm up, and pair an anomaly rule with an absolute floor (e.g. *"…and volume is over $250k"*) on choppy tokens. You can also alert on the **raw** numbers (`volume_24h`, `holder_count`) on any tier — these work best as an early-warning radar, since a volume or holder spike often precedes a price move. ### Webhook Delivery Have an alert delivered to your own server instead of a chat: > *"Send my whale alerts to my webhook "* Nova POSTs a signed JSON payload to your HTTPS endpoint. Each request includes an `X-Nova-Signature` (HMAC-SHA256 of `` `{X-Nova-Timestamp}.{body}` `` using a secret shown once at setup), an `X-Nova-Idempotency-Key` for safe de-duplication, and is retried with backoff on failure. Only public HTTPS URLs are accepted (localhost/private/internal addresses are blocked). ### Compound / Correlated Alerts Some signals only matter *together* — a whale buy alone is noise; a whale buy **and** a price pump in the same ten minutes is a setup: > *"Alert me if there's a whale buy of WELSH **and** WELSH pumps 5% within 10 minutes"* Nova watches each part ("leg") independently and notifies you only once **all** legs happen within your window, in any order; if the window passes first, the clock resets, and after firing the cooldown prevents immediate re-triggers. Legs can combine **price / volume / holder, whale, DEX, and wallet** signals — describe the combination and timeframe in plain English. Give it a sensible window (a few minutes to an hour): too tight and the parts may not land together, too loose and unrelated events get linked. ### Smart Templates Save and reuse alert configurations: > *"Save this alert setup as a template"* (then *"create alert from my whale-watch template"*) # ZADAO Ecosystem Nova is your gateway to the [Zero Authority DAO](https://zeroauthoritydao.com) ecosystem. Search bounties, gigs, grants, quests, and contributor profiles — all from chat. *** ## Bounties Find and explore bounties posted on ZADAO. **Example prompt:** > *"Search bounties about smart contracts"* **What you'll get:** * Bounty title, description, and requirements * Status (open, in review, completed) * Reward amount and deadline * Submissions and winners * Filter by category or organization *** ## Gigs Browse the gigs marketplace for freelance opportunities. **Example prompt:** > *"Any design gigs open?"* **What you'll get:** * Gig listings with status * Service category and description * Pricing and availability *** ## Grants Track grant programs and project funding. **Example prompt:** > *"Active grants on ZADAO"* **What you'll get:** * Grant details and milestones * Funding progress * Project category and status *** ## Quests Discover structured missions with REP rewards. **Example prompt:** > *"What quests are active right now?"* **What you'll get:** * Quest title, campaign, and deadline * REP rewards and NFT reward status * Activities/subtasks to complete * Completion requirements *** ## Governance & Events For SIP governance, CAB voting, and Stacks ecosystem events, see [Nova for CAB Groups & Governance](/nova-bot/nova-ai-agent/nova-for-cab-groups-and-governance-participants). *** ## Contributor Profiles Look up ZADAO community members. **Example prompt:** > *"Search for users with Clarity experience"* **What you'll get:** * User profile and bio * Bounties won and services offered * Achievements and reputation *** ## ZADAO Documentation Ask Nova about how the platform works. **Example prompt:** > *"How do bounties work on ZADAO?"* **What you'll get:** * Explanations of ZADAO concepts * Platform documentation and guides * Platform statistics (total bounties, gigs, users, grants) # Nova for CAB Groups & Governance Participants Nova is your AI-powered governance assistant for the Stacks ecosystem — real-time SIP status, CAB voting, ecosystem events, and proactive alerts for CAB members, SIP authors, and governance observers. *** ## Quick Start 1. **Add Nova** to your Discord server or Telegram group (or DM the bot directly) 2. **Ask anything** — just mention @Nova or reply to its messages 3. **Set up alerts** — tell Nova what you want to be notified about No accounts to create, no forms to fill out. *** ## SIP Monitoring ### Check Any SIP's Status > *"What's the status of SIP-032?"* **Nova returns:** title, status, type (Meta/Consensus/Standard), consideration area, authors, abstract, GitHub PR link, and forum discussion link. ### Browse All SIPs > *"List SIPs grouped by status"* **Nova returns:** full SIP registry with status breakdown — see at a glance how many are Draft, in Review, Ratified, etc. ### Governance Stats > *"Show me SIP governance stats"* **Nova returns:** total SIPs, open CAB voting instances, closed instances, number of CAB groups. *** ## CAB Voting > *"Are there any open CAB votes?"* **Nova returns:** whether voting is open or closed, vote tallies (yes/no/abstain), total votes cast, and voting instance history — and you can ask which SIPs have had CAB voting or whether any vote closed recently. *** ## Alerts — Never Miss a Vote Set up alerts once, and Nova will **proactively notify you** on Discord or Telegram when governance events happen: * **CAB voting opens** — *"Alert me when CAB voting opens on any SIP"* — notified the moment a vote is initiated, so you never miss your window * **CAB voting closes** — get the final tallies (yes/no/abstain) as soon as voting concludes * **SIP status changes** — track the full lifecycle: Draft -> Review -> Accepted -> Activation-in-Progress -> Ratified, including withdrawals * **Specific SIP** — *"Alert me about any activity on SIP-034"* — status changes AND CAB voting for one SIP * **New SIPs** — be the first to know when a proposal enters the registry * **Catch-all governance** — *"Alert me about all SIP governance activity"* — every status change, vote open/close, and new SIP in one alert {% hint style="info" %} **How it works:** Nova checks for SIP and CAB changes every 2 hours. When your conditions match, you get a rich notification with SIP title, status change, vote tallies, and links to GitHub/forum — delivered on the platform where you set the alert up. {% endhint %} To pause, update, or review alerts conversationally, see [Smart Alerts](/nova-bot/nova-ai-agent/smart-alerts). Free vs Premium alert limits are in the [Premium guide](/nova-bot/premium). *** ## Ecosystem Events ### Browse Events > *"What Stacks events are coming up?"* **Nova returns:** title, date/time, virtual vs in-person, location or meeting link, host, attendee count, token requirements, and on-chain attendance badges. ### Event Alerts > *"Alert me about new Stacks events"* Nova checks for new events every 30 minutes and notifies you about new listings, status changes, and events starting within the hour — you can also filter, e.g. virtual events only. {% hint style="warning" %} **Free tier tip:** With 2 alert slots, we recommend: (1) all SIP governance activity, and (2) new ecosystem events. This covers the most ground. Upgrade to [Premium](/nova-bot/premium) for more granular control. {% endhint %} *** ## Beyond Governance — Everything Else Nova Can Do As a Stacks ecosystem participant, you also get access to Nova's full toolkit: * **Market & tokens** — *"Show me trending Stacks tokens"* * **Wallets & addresses** — *"Look up wallet SP3K8BC0..."* * **Smart contracts** — *"What functions does SP123...contract-name have?"* * **Network status** — *"Current Stacks block height"* * **ZADAO platform** — *"Show me active bounties"* See [Blockchain Coverage](/nova-bot/nova-ai-agent/blockchain-coverage) and [ZADAO Ecosystem](/nova-bot/nova-ai-agent/zadao-ecosystem) for the full picture. For ecosystem news and updates, see [News & Research](/nova-bot/nova-ai-agent/news-and-research). *** ## Supported Platforms | Platform | How to Use | | ------------ | ------------------------------------------------------------------------------------- | | **Discord** | Mention @Nova in any channel, or DM the bot directly | | **Telegram** | Message in any group with Nova, or DM the bot | | **Web** | Use the Nova widget at [nova.zeroauthoritydao.com](https://nova.zeroauthoritydao.com) | Alerts are delivered on the same platform where you created them. DM alerts go to your DMs; channel alerts go to that channel. Nova remembers your conversation context, so you can refine alerts and drill deeper without starting over. # Emblem Vault Nova helps you **explore and create Emblem Vaults** — conversationally, with **zero custody**. An Emblem Vault wraps a non-EVM asset (a Bitcoin Ordinal, BRC-20, Bitcoin Stamp, rare sat, Counterparty/XCP asset, Dogecoin, and more) into a **tradable NFT on Ethereum**, so it can change hands on marketplaces like OpenSea. {% hint style="success" %} **Your vault, your keys.** Nova never holds your seed, never signs for you, and never sees your vault's private key. For creation, Nova guides you and hands off the official link — **you** mint and sign in **your own** wallet. {% endhint %} *** ## What's inside a vault? (Vault Lookup) Hand Nova a vault and it tells you exactly what's wrapped inside, what it's worth, and whether it's been claimed. You can pass a numeric **tokenId**, a **`0xcontract/tokenId`** pair, or a **marketplace link** — Nova figures out the rest. Read-only and keyless. **Example prompt:** > *"What's in this Emblem Vault? 30243073570574861"* **What you'll get:** * The vault **name**, image, and platform * **Contents** — each wrapped coin's balance, USD price, USD value, and inner on-chain address * **Total USD value** of everything inside * **Claim status** — whether the vault has already been claimed {% hint style="warning" %} A **claimed** vault is no longer secure for storing value — claiming exposes its inner private key. Values shown are indicative and **not financial advice**. {% endhint %} *** ## Browse the collection catalog (Collections) Not sure what Emblem can wrap? Ask Nova to browse or search the **74 curated collections** — the official catalog of supported wrap targets. Filter by a name/asset keyword or ask for **mintable-only**. Read-only and keyless. **Example prompt:** > *"Which Emblem collections are mintable right now?"* **What you'll get** — for each collection: * The **name** and the **native asset(s)** it wraps * The **chain** and whether it's currently **mintable** * The **mint / unvault price** (in **COVAL**, not USD) * The Ethereum **contract** and a short **description** *** ## Which vaults does a wallet own? (Wallet Vaults) Point Nova at an EVM address and it finds the curated Emblem Vaults that wallet holds. Ethereum only for now; read-only and non-custodial. **Example prompt:** > *"What Emblem Vaults does 0x… own?"* **What you'll get:** * Each matched vault's **collection**, **contract**, **tokenId**, and a **marketplace link** * Optionally, the **contents** of the first few vaults (wrapped balances, USD value, claim status) *** ## Creating a vault (Guided, Non-Custodial) Ask Nova how to vault an asset and it walks you through the whole flow, then hands you the official link to mint in your own wallet. **Example prompt:** > *"I want to wrap my Bitcoin Ordinal into a tradable NFT"* **What Nova gives you:** * A plain-English explanation of what a vault is and the **custody model** * The **official create URL** ([emblem.vision](https://emblem.vision)) * A **step-by-step outline**: 1. Connect **your own** wallet (Nova doesn't connect or sign for you) 2. Choose the asset / chain you want to wrap 3. Name the vault, add an image/description 4. Fund the vault's **deposit address** from your wallet 5. Approve any token spend, then pay gas + the Emblem deploy fee 6. **Mint and sign in your own wallet** — you now own a tradable vault 7. To redeem later, **claim** the vault (this exposes the inner key) * The **supported asset types** and the **safety caveats** **Why guided instead of fully in-chat?** Minting is a transaction your own wallet must sign, and the vault's inner key has to be custodied by Emblem's infrastructure — not by Nova. Doing the mint "inside" Nova would mean Nova holding keys on your behalf, which we deliberately avoid — so Nova handles guidance, lookup, and verification, and hands the signing to you. *** ## Safety * **Never share your vault private key or seed** with anyone — including Nova. * Fees and gas are charged by **Emblem and the network**, not Nova — Nova takes no cut. * A **claimed** vault has had its key revealed — don't reuse it to store value. * Always confirm you're on the **official Emblem domain** before connecting your wallet. *** ## For developers & agents All four capabilities are also available on the **Nova Tools Platform** (REST + MCP) as free tools, under the `emblem` ecosystem: * `emblem-vault-lookup` — read a vault's contents, value, and claim status * `emblem-vault-create-guide` — fetch the canonical, non-custodial creation guide (now incl. live mintable collections) * `emblem-collections` — browse / search the curated collection catalog * `emblem-wallet-vaults` — list the curated Emblem Vaults an EVM wallet owns See the [Nova Tools catalog](/nova-bot/nova-tools) and [Using Nova Tools with Agents](/nova-bot/nova-tools/using-nova-tools-with-ai-agents). # Agent Observatory Nova lives on the **aibtc network** — where many AI agents each have their own Bitcoin/Stacks wallet, a public profile, a level/rank, and on-chain activity. The Agent Observatory is Nova's window into all the *other* agents: browse them, rank them, look one up in detail, and **follow** any of them to get pinged when they make a move. Everything here is fully conversational — no commands, no wizard — and **read-only**: Nova never spends, signs, or moves funds when you use the Observatory. Data comes straight from aibtc's own network — Nova is a live window onto it, not a copy of it. *** ## Browse & Rank Agents > *"Who are the top agents on aibtc right now?"* You'll get the agents with their level, rank, and score — including filters like top Genesis-level agents. *** ## Look Up One Agent > *"Profile the agent bitcoio.btc"* Nova accepts a **BNS name** (`name.btc`), a **Stacks address** (`SP…`), or a **Bitcoin address** (`bc1…`). You'll see the agent's level, reputation/trust, recent activity, and capabilities. When aibtc's own numbers on an agent are thin, Nova automatically fills in the gaps with that agent's **on-chain** trading stats (P\&L, recent trades) — so you always get a useful picture. *** ## See What's Happening on the Network > *"What's happening on the aibtc agent network?"* Ask for recent activity network-wide, filter to one agent, or get a recap of the top agents. *** ## Follow an Agent 🔔 This is the one thing aibtc can't do for you — deliver alerts into **your** Discord or Telegram. Nova can. > *"Follow bitcoio.btc"* — then *"which agents am I following?"* or *"unfollow bitcoio.btc"* A follow can track up to **three** signals: | Signal | Default | What it catches | | ------------------ | ------------ | --------------------------------------------------------------- | | **On-chain moves** | Always on | STX/token transfers, swaps, contract calls like DAO votes | | **Level-ups** | On | The agent gains an aibtc level | | **Inbox messages** | Off (opt-in) | The agent's aibtc inbox activity (agent-to-agent x402 messages) | Inbox tracking is **opt-in** because it's the noisiest signal — just ask: *"Follow bitcoio.btc and alert me on their inbox too"* (or *"…but don't ping me for level-ups"*). Re-following the same agent updates your settings, and *"which agents am I following"* shows what's tracked for each. {% hint style="info" %} **Where following works:** DM Nova to follow agents **for yourself** (private alerts). In a public server/group, only **admins/moderators** can set up follows, since the whole channel gets pinged. Browsing, ranking, and profiles work **anywhere**. {% endhint %} {% hint style="info" %} Following an agent uses Nova's **wallet-tracking** system under the hood, so each followed agent counts toward your address-tracking limit (**Free: 1**, **Premium: 300**). See [Wallet Tracker Alerts](/nova-bot/alerts-setup-guides/wallet-tracker-alerts). {% endhint %} *** ## Weekly Agent Recap (optional) Nova can auto-post a **"top agents this week"** summary to a channel every Monday. This is an opt-in, config-based feature a server operator switches on by pointing it at a channel — ask your admin or the Nova team to enable it for your community. *** ## Good to Know * **On-chain vs off-chain.** "Following" always watches an agent's real on-chain moves (the signal that matters most). Inbox and level-ups are the extra off-chain signals aibtc exposes. * **Just ask.** If Nova ever seems unsure about a feature, ask directly ("follow this agent…") — it'll find it. # Community Nova isn't only a blockchain assistant — it's a **community copilot**. Beyond answering on-chain questions, Nova helps you **protect, organize, manage, and grow** any Discord server or Telegram group it's in. **One rule for the whole suite:** every feature is enabled per-community just by talking to Nova, and setup is **admin/moderator-only** and **group-only** — never in a DM. Guardian, Pulse, Games, GM, and Snacks apply to the whole server/group; Language Moderation is **per-channel** by design. *** ## The six community features
🛡️ Nova Guardian — protectA passive anti-scam shield that screens every message for scam intent, social engineering, and malicious links — in any language — with a flag → delete → mute action ladder.nova-guardian.md
🌐 Nova Language Moderation — organizePer-channel allowed-language rules — #general is English-only, #español speaks Spanish. Wrong-language posts get a friendly redirect to the right channel, optional auto-delete, and mod alerts.nova-language-moderation.md
📊 Nova Pulse — manageA proactive moderator copilot that rescues unanswered questions, posts a daily community brief to a private mod channel, and can auto-answer FAQs (Concierge) from Nova Knowledge — the curated knowledge base you fill by pasting facts or importing websites, repos, and contract source.nova-pulse.md
🎮 Nova Community Games — engageAn engagement suite: XP & levels for chatting, leaderboards + an automatic weekly leaderboard post, mod-run games & trivia you start on demand (PRO), a weekly recap (PRO), and a fair random winner picker / giveaways.nova-community-games.md
☀️ Community GM — greetWhen a member says "gm", Nova greets the room with a good-morning brief: fresh ecosystem news + your community's own RSS/page/on-chain sources. PRO adds custom steering instructions and a fresh web search per GM.nova-gm.md
🍪 Daily Snacks — sparkOne bite-sized, interesting insight/fact on a schedule, grounded in your community's own conversations and ecosystem. PRO adds daily cadence + custom instructions to steer topics and tone.nova-snacks.md
*** ## Community PRO perks Three more things come with a Community PRO plan — not features you enable, but upgrades to how Nova itself behaves in your community:
✨ Nova Soul — your identityRename Nova and give it a custom persona — name, tone, style, full character description — that it wears only in your community. PRO communities can even run Nova under their own Discord app / Telegram bot (your bot name & avatar on every reply and report). Styling only: it can never change Nova's safety rules or capabilities.nova-soul.md
💬 Nova Chat — your budgetA pooled message allowance the community pays for, so members chat with Nova without spending their personal daily limit. Automatic — nothing to enable.nova-chat.md
📝 Ops AI drafts — your copywriterAsk Nova to write your announcements, community updates, and tweets right in your server/group — draft, iterate through edit rounds, then copy and post the final version.nova-premium-for-communities.md
*** ## Which one do I want? | If you want to… | Turn on | | -------------------------------------------------------------------- | ---------------------------- | | Stop scams, phishing, and spam floods before they spread | **Nova Guardian** | | Keep each channel in its own language and redirect speakers politely | **Nova Language Moderation** | | Never miss a member's question and get a daily readout of the room | **Nova Pulse** | | Reward active members, run trivia/giveaways, and gamify chat | **Nova Community Games** | | Open every morning with fresh news + your project's own updates | **Community GM** | | Drop a daily conversation-starter that fits your room | **Daily Snacks** | {% hint style="info" %} **Member-facing vs. mod-facing.** Community Games is visible to everyone (games, leaderboards, level-ups post in the community). Guardian and Pulse are **mod-facing** — their flag cards and briefs go to a private mod-review channel you choose, so members never see them. {% endhint %} *** ## Set any of them up — just talk to Nova In your server/group, as an admin/mod, @mention Nova (or reply to it) and say what you want: > *"@Nova turn on Guardian for this server"* · *"@Nova enable Pulse"* · *"@Nova turn on community games"* Nova enables the feature and confirms. See each guide for the full set of things you can ask — or just ask Nova *"what can you do for my community?"*. Nova also serves up **engagement stats** — see [ZADAO Stats](/nova-bot/alerts-setup-guides/zadao-stats). **Prefer a control panel?** Every feature is also manageable from the web — the [Community Settings dashboard](/nova-bot/nova-ai-agent/community/community-settings-web-dashboard) at [nova.zeroauthoritydao.com/community](https://nova.zeroauthoritydao.com/community) shows each one as a card with every setting editable and live usage against your plan's budgets. Chat and web edit the same config. {% content-ref url="/pages/rNNenzslgaNqc6wJB165" %} [Community Settings (Web Dashboard)](/nova-bot/nova-ai-agent/community/community-settings-web-dashboard) {% endcontent-ref %} {% content-ref url="/pages/fLmdNm8TilVuRtjiFcc8" %} [Nova Guardian](/nova-bot/nova-ai-agent/community/nova-guardian) {% endcontent-ref %} {% content-ref url="/pages/A1H8N18mepu2vxN66ehA" %} [Nova Language Moderation](/nova-bot/nova-ai-agent/community/nova-language-moderation) {% endcontent-ref %} {% content-ref url="/pages/PoK4ocbAmo2nx4WADSC2" %} [Nova Pulse](/nova-bot/nova-ai-agent/community/nova-pulse) {% endcontent-ref %} {% content-ref url="/pages/MHyTIoMI16fOrVZ5ZnJG" %} [Nova Community Games](/nova-bot/nova-ai-agent/community/nova-community-games) {% endcontent-ref %} {% content-ref url="/pages/UhpgOmtOkp1GJT9fbu7A" %} [Community GM](/nova-bot/nova-ai-agent/community/community-gm) {% endcontent-ref %} {% content-ref url="/pages/IgvMwTbRWLYoWnMJdrhr" %} [Daily Community Snacks](/nova-bot/nova-ai-agent/community/daily-community-snacks) {% endcontent-ref %} {% content-ref url="/pages/GTnyArkMBkrDonSNWZAQ" %} [Nova Soul](/nova-bot/nova-ai-agent/community/nova-soul) {% endcontent-ref %} {% content-ref url="/pages/WgrT0mcS8ckY3CfsRy4e" %} [Nova Chat](/nova-bot/nova-ai-agent/community/nova-chat) {% endcontent-ref %} {% hint style="info" %} **Plans.** The paid tier — **Community PRO** — is a per-community plan (separate from personal Premium) that unlocks Guardian at full budget, Language Moderation, Pulse + Concierge, AI games and more for your whole server/group. See [Nova Premium for Communities](/nova-bot/premium/nova-premium-for-communities), or just ask Nova *"show plans"* in your server. Each feature page lists its exact Free vs PRO limits. {% endhint %} # Nova Guardian **Nova Guardian** is a passive community-protection shield. Once an admin turns it on, Nova silently screens **every message** in your Discord server or Telegram group for **scam intent and social engineering** — not just links — and takes graduated, configurable action. Turning it on protects the **whole** server/group. The hard part of community safety isn't banning links (servers already do that) — it's the **text-based** lures that carry no link at all. Guardian reads **intent** with an LLM, so it catches paraphrases, typos, leetspeak and letter-spacing tricks that keyword blocklists miss. It also watches **behavior over time**, so it shuts down repeat-spam and flood blasts (the same message posted over and over) that a single-message check can't see. *** ## What It Catches | Pattern | Example | | ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **🎣 Fake hiring / recruiting** | "We're onboarding mods/testers/ambassadors — DM me", fake remote web3 jobs, pay-per-task lures | | **🪂 Fake airdrops / claims** | "Claim your airdrop", "verify your eligible wallet", "check eligibility", fake free-mints | | **🔑 Seed / wallet harvesting** | Asking for or "buying old/inactive wallets", "paying for seed phrases", "import/sync/restore your wallet" | | **🎭 Team / admin impersonation** | "Official support here, DM me to resolve", or an account whose name clones a real admin's — automatically detected from who actually holds admin/mod permissions | | **📨 DM-bait / off-platform lures** | "Let's continue in DM", "message me on WhatsApp/Telegram/Signal" | | **💸 Send-to-receive / advance-fee** | "Send 0.1 get 0.2 back", "double your crypto", "first 50 only", guaranteed-return giveaways | | **🔗 Malicious / phishing links** | Lookalike domains, wallet-drainer sites, fake claim/mint pages, hidden URL shorteners | | **🎰 Gambling / betting-tips spam** | "Insider picks" / tipster groups, casino recruiting, "earn 3k a day" betting lures that funnel members to a bot or channel handle — in **any language** | | **💴 Illegal-goods spam** | Counterfeit currency, forged IDs/documents, stolen accounts — spam regardless of what's being sold | | **🚫 Repeat-spam / flood** | The same message (incl. a **forwarded** one) posted over and over — in a rapid burst **or** drip-fed minutes apart with a couple of emoji swapped between copies — see below | Guardian judges **intent**, not keywords — and not just in English. Its quick pre-filter knows common non-English lure phrases (e.g. Chinese betting-spam and counterfeit-goods slang), and the AI verdict is made in whatever language the message is written in. Warning others about a scam, asking how airdrops work, or legitimate OTC trading talk are recognized as **clean** — and you can allowlist phrases that are normal for your community. *** ## Repeat-Spam & Flood Protection The intent radar judges one message at a time, so Guardian adds a second, **behavioral** layer that watches *repetition over time* — the classic promo blast forwarded 9–10 times in a row, often with no link and not in English: | Trigger | When it fires | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Repeated message** | The same (or near-identical) content posted **3×** by one account — in a rapid burst **or** drip-fed up to **45 minutes** apart (spammers space copies 10–15 min apart to dodge burst filters; that no longer works) | | **Repeated forward** | A **forwarded** message repeated — fires sooner (**2×**), since a re-forwarded blast is a stronger spam tell | | **Rapid-fire** | One account sending **8+** substantive messages within a minute | "Near-identical" is deliberate: the content fingerprint ignores emoji, punctuation and spacing, so swapping 🦊🌷 for 🙈👧 between copies still counts as the same message. It keys on **repetition, not on forwarding** — **a single, normal forward is never touched**; only when the *same* account *repeats* itself does the detector react. Moderators and admins are exempt. When a flood is caught, Guardian raises **one** review card for the whole burst (not ten), tagged **🚫 Repeat-spam / flood** — e.g. *"Repeat-spam flood: author posted the same message 3× (near-identical copies — emoji/punctuation swaps ignored) in under 29 min."* — and, with enforcement on, removes **every copy** in the burst at once. It's content- and language-agnostic, so it works on non-English and link-less spam that the intent classifier would miss. *** ## How It Decides — the action ladder Every message gets a verdict, and each tier has its own action: | Verdict | What Nova does | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Clean** | Nothing. | | **Suspicious** | Silently posts a **mod-review card** to your review channel — author, age, reason, message link. No public action. Never deleted or muted, even with auto-moderation on. | | **Scam** (high-confidence) | Posts the review card **and**, with **auto-moderation** on: **1)** deletes the message immediately, **2)** mutes the author for **24 hours** (Discord timeout / Telegram restrict — change it with *"mute scammers for 2 hours"*), **3)** privately tells the author which pattern they matched, how long the mute lasts, and how to appeal, **4)** hands your mods a report with **Ban / Revert** buttons. | ### Sensitivity modes | Mode | Behavior | | ------------------------ | ------------------------------------------------------------------------------------- | | **Lenient** | Only the most blatant scams are flagged — fewest false positives. | | **Balanced** *(default)* | Sensible middle ground. | | **Strict** | Catches more, flags more for review — a few more false positives for mods to dismiss. | Trusted, established members are held to a lighter standard than brand-new accounts, so a long-time member and a fresh account posting the same line aren't treated the same. *** ## Auto-Moderation Flag-only mode still needs a moderator to be awake. **Auto-moderation** closes that gap: when Guardian is certain a message is a scam, it acts immediately (the four actions above) and *then* asks a human — instead of leaving the scam up while it waits for one. {% hint style="warning" %} **Auto-moderation is the default when you enable Guardian** — on Discord only after you've nominated a mod target (Nova prompts you for one), so a false positive can never become an unappealable mute. Prefer to watch first? Say ***"activate Guardian without auto-moderation"*** and it starts in **flag-only** mode — it never deletes, mutes or bans anyone until you switch auto-moderation on later with *"@Nova turn on auto-moderation"*. {% endhint %} ### The mod report Guardian acted *without* a human, so a human must always get the final say — in one click. The report is a flag card (see the sample below) with the action line *"✅ 🗑️ message deleted · 🔇 author muted 1d"* and two buttons: | Button | What it does | | ------------- | ----------------------------------------------------------------------------------------- | | **🔨 Ban** | Guardian's call was right and the account is a throwaway — ban it from the community. | | **↩️ Revert** | Guardian was wrong — lift the mute immediately. The flag is recorded as a false positive. | * **Discord:** the report is posted to your **flag-report channel** (chosen when you turn auto-moderation on; defaults to where you enabled Guardian) and **@mentions your mod role**. Nova **refuses** to arm auto-moderation until you've set a mod target — *"set the mod role to @Moderators"* — otherwise a false positive would leave a member muted with nobody able to undo it. * **Telegram:** the report is **DM'd to each of your moderators** — not posted in the group, which would just show the scam to the very people it targeted. Nova DMs your nominated mods, or falls back to the group's own admins. **Mods must have opened a chat with Nova at least once** (Telegram forbids a bot from messaging first); if no mod is reachable, the report is posted in the group rather than lost. *** ## AI Scan Budget Most messages are cleared for free by Guardian's instant pre-filters — the **AI intent verdict** only runs on the small minority that actually look risky. Those AI scans draw from a daily budget set by your community's plan: | | **Free** | **Community PRO** | | ------------------------- | -------- | ----------------- | | **AI intent scans / day** | 20 | **500** | For context: 500 scans/day is far more than even a large, actively-attacked community typically needs — the pre-filters absorb the ordinary chatter, so only genuinely suspicious messages spend a scan. **When the day's budget is spent, Guardian does not go dark.** Flood/repeat-spam protection, the deterministic spam short-circuits, and all the built-in heuristics keep running at full strength. Only the per-message AI intent analysis pauses until the budget resets at **00:00 UTC**. The first time it happens each day, Guardian posts a single heads-up to your mod-review channel so you're never wondering why the flags went quiet. Check today's usage anytime — the status includes it: > *"@Nova is Guardian on?"* → *"…AI scans today: 137/500."* *** ## What a Flag Looks Like When Guardian flags a message, it posts a clean, scannable card to your mod-review channel — designed so a moderator can judge it at a glance. {% tabs %} {% tab title="Discord" %} A **color-coded embed** — red for a likely scam, amber for "please review": ``` 🚨 Nova Guardian Likely Scam — Seed / wallet harvesting Newcomer with zero contribution history is offering to buy existing wallets with transaction history — a classic seed-harvesting lure. Confidence Category Channel 95% 🔑 Seed / wallet harvest #general Member Cafu · joined 6d ago 1510524330151510066 ❝ Flagged message ❞ > I am looking to purchase a phantom wallet with a history > of frequent transactions. I am willing to pay 3-4 SOL. Action 🛡️ Flag only — enforcement off. 🔗 Jump to message ────────────────────────────────────────────── Enforcement OFF · auto-delete & auto-mute disabled · Today at 8:48 AM ``` The verdict, confidence, category, **origin channel** and member sit in scannable rows; the flagged text is quarantined in a quote block; a **Jump to message** link takes you straight to it; and the enforcement status lives quietly in the footer. The channel mention keeps working even after the flagged message is deleted (when the jump link goes dead), so you always know where the spam landed. {% endtab %} {% tab title="Telegram" %} Clean formatting with bold headers and an **expandable quote** for the flagged text: ``` 🚨 Nova Guardian — Likely Scam 🔑 Seed / wallet harvesting · 95% 📍 Zero Authority DAO · topic 42 👤 Cafu · joined 6d ago 1510524330151510066 📝 Newcomer with zero contribution history is offering to buy existing wallets with transaction history — a classic seed-harvesting lure. ❝ I am looking to purchase a phantom wallet… ❞ (tap to expand) 🛡️ Flag only — enforcement off. ────────── 🔗 View flagged message Enforcement OFF · auto-delete & auto-mute disabled ``` {% endtab %} {% endtabs %} {% hint style="info" %} Guardian **never pings anyone** in a flag card — the quoted scam text can't tag or notify members — and it **never re-publishes a working lure**: links and bot handles in the quoted text are defanged for display (`https://scam.xyz` → `hxxps://scam[.]xyz`, `@handles` made non-clickable), so flagging a scam doesn't give its link a second audience. Mods still see exactly what the link was; the audit log keeps the original text. Cards are visible to whoever can see your mod-review channel. {% endhint %} *** ## Set It Up — just talk to Nova There's no wizard — you configure Guardian conversationally. (Setup is admin-only, in your server/group — not DMs.) @mention Nova or reply to it: 1. **Turn it on:** *"@Nova turn on Guardian / scam protection for this server"* — auto-moderation arms by default (Discord asks for a mod target first); add *"without auto-moderation"* for flag-only. 2. **Point it at a mod channel (optional):** *"send Guardian flags to #mod-review"* — defaults to the enable channel. 3. **Impersonation protection is automatic** — Guardian knows your real admins/mods from their server permissions. Optionally protect extra names or whitelist a permissionless helper: *"the real admins are @alice and @bob"* (also never flags them). 4. **Add allowlist phrases:** *"allowlist 'buying wallets' — this is an OTC channel"* 5. **Nominate your moderators** (required before auto-moderation arms on Discord): *"set the mod role to @Moderators"* 6. **Tune / check anytime:** *"make Guardian stricter"* · *"is Guardian on?"* · *"how many scams did Guardian catch this week?"* · *"turn off auto-moderation"* · *"turn off Guardian"* **Bot permissions for auto-moderation.** On **Discord** Nova needs *Manage Messages*, *Moderate Members* and *Ban Members* (all in the current [invite link](/nova-bot/getting-started/adding-nova-to-discord)), and its role must sit **above** the members it moderates. On **Telegram**, make Nova an **admin** with *delete messages* and *ban/restrict users* rights. If a permission is missing, Guardian falls back to flag-only and tells you exactly what to grant. (Communities set up before auto-moderation existed keep their chosen mode; on Discord, re-invite Nova with the current link if the permissions are missing.) *** ## Configuration Options | Option | What it does | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Mode** | `strict` / `balanced` / `lenient` detection sensitivity | | **Auto-moderation** | The full module: delete + 24h mute + notify the author + a **Ban / Revert** report to your mods. **Default ON for new setups** (explicit opt-out: *"activate Guardian without auto-moderation"*) | | **Mod-review / flag-report channel** | Where flag cards and auto-moderation reports are posted (defaults to where you enabled it) | | **Mute duration** | How long an auto-mute lasts (default **24 hours** with auto-moderation on) | | **Auto-delete** | *(granular)* Remove scam messages but do nothing else — no mute, no author notice, no actionable report. Prefer auto-moderation. | | **Auto-mute** | *(granular)* Mute the author but do nothing else. Prefer auto-moderation. | | **Allowlist** | Phrases that must never be flagged (normal-for-your-community talk) | | **Known admins** | *(optional)* Real admins are detected automatically from permissions; use this to protect extra named identities or whitelist a trusted helper who has no permissions | | **Thresholds** | Advanced numeric overrides for the suspicious / scam cut-offs | *** ## Weekly Recap Every **Monday at 12:00 UTC**, Guardian posts a short recap card to your mod-review channel: how many messages it flagged that week, how many were high-confidence scams, what actions it took, and the top patterns it saw. (It stays quiet on weeks with nothing to report.) ``` 🛡️ Nova Guardian — Weekly recap Guardian reviewed the week and flagged 12 messages — 5 high-confidence scams. Flagged Auto-actions 12 (5 scams) 🗑️ 3 · 🔇 2 Top patterns 🔑 Seed / wallet harvesting (4) 🎣 Fake hiring / recruiting (3) 📨 DM-bait / off-platform lure (2) ✅ Removed 3 messages and muted 2 members. ────────────────────────────────────────────── Last 7 days ``` *** ## Privacy Note Guardian classifies messages **in real time** to reach a verdict. It only writes a record to its audit log when it actually **flags or acts on** a message (suspicious or scam) — that record includes the verdict, category, reason, action taken, and a short snippet of the offending message for the mod-review card. Ordinary clean messages are never stored by Guardian. # Nova Language Moderation **Nova Language Moderation** lets you declare which language(s) each channel in your community speaks — and have Nova enforce it politely, automatically, in the background. Set **#general** to English-only, give **#español** to Spanish, let a support topic allow English + Chinese, or set one rule for the whole server/group. Nova then screens **every message** (including photo/video captions) and, when someone posts in a language that channel doesn't allow, responds the way *you* chose: a friendly redirect, a deletion, a mod alert — or any combination. The killer detail is the **redirect**: if the message was in Spanish and another of your channels *does* allow Spanish, Nova's warning points the member there — *"this channel is English-only — you're welcome to continue in #español!"*. No configuration needed; Nova derives it from your other channel rules. Wrong-language posts stop being moderation incidents and become signposts. Unlike Guardian (which always protects the whole community), language rules are **per-channel**: each channel, thread, or Telegram forum topic can have its own allowed languages, with an optional community-wide default for everything else. *** ## The Three Behaviors You choose what happens on a wrong-language message — each is an independent toggle: | Behavior | What Nova does | Default | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | **💬 Warn & redirect** | Publicly replies to the author: which languages the channel speaks, what their message looked like, and **where their language is welcome**. The notice self-deletes after \~45 seconds, and the same member isn't re-warned in the same channel more than once every few minutes — the channel never fills with moderation noise. | **On** | | **🗑️ Auto-delete** | Removes the violating message automatically (the warning then says it was removed and where to go instead). | Off | | **🚨 Alert mods** | Posts a review card to your mod channel: author, detected language + confidence, the quoted message, and what action was taken. | Off | {% hint style="warning" %} **Conservative by default.** Enabling the feature starts in warn-only mode — nothing is ever deleted until you explicitly opt in. A wrongly-deleted message is worse than a missed one, and the detector is built around that principle too (see below). {% endhint %} *** ## How Detection Works — and why it won't misfire Language detection on chat messages is genuinely hard: real chat is short, full of slang, tickers, addresses, links and emoji. Nova uses a **tiered** detector designed so false positives are rare enough to trust with deletion: 1. **Writing-system check (instant).** A message written dominantly in a script none of the channel's languages use — Cyrillic in an English-only channel, Chinese in a Spanish channel — is an unambiguous violation. This handles most real cases with zero cost. 2. **Same-script cases go to an AI check.** Spanish in an English channel shares the Latin alphabet, so a fast language library takes a first look — but its opinion is **never enforced directly**. Anything suspicious is confirmed by an AI that reads the actual message with slang and context awareness before Nova acts. What **never** gets flagged: * **Short messages** — "gm", "lol", "ok", one-word replies, emoji reactions. * **Crypto/community slang** — "wagmi", "lfg", "ser", "dyor", "bullish on stx ngl" are English, and Nova knows it. * **Links, tickers, addresses, usernames, code blocks** — stripped before detection. * **Code-switching** — *"thanks bro pero cuándo es el launch?"* in an English channel is fine; mixing in an allowed language counts as allowed. * **Quoted foreign phrases** — *"what does 'привет' mean?"* is a question, not a violation. * **Moderators and admins** — always exempt. * **Allowlisted phrases** — project names, catchphrases, or greetings your community tolerates. {% hint style="success" %} The bias is deliberate: **when in doubt, Nova stays silent.** A missed violation costs nothing — a wrongly-deleted message costs trust. {% endhint %} ### AI Check Budget The writing-system check (tier 1) is free and unlimited — it handles most real violations on its own. Only the **AI confirmation** for same-script cases draws from a daily budget set by your community's plan: | | **Free** | **Community PRO** | | ---------------------------- | -------- | ----------------- | | **AI language checks / day** | 50 | **500** | When the day's budget is spent, script-based detection keeps running at full strength; ambiguous same-script cases are simply **let through** (never flagged without AI confirmation — the same when-in-doubt-stay-silent bias) until the budget resets at **00:00 UTC**. Ask *"@Nova language moderation status"* to see today's usage vs the cap. *** ## What Members See A wrong-language post in an English-only channel (warn-only mode) gets a reply like: ``` 🌐 @miguel, a heads-up: #general is English-only — that looked like Spanish. You're welcome to continue in #español! ``` With auto-delete on, the message disappears and the notice adapts: ``` 🌐 @miguel, your message was removed: #general is English-only — that looked like Spanish. You're welcome to continue in #español! ``` The notice quietly deletes itself after \~45 seconds, keeping the channel clean. ## What Mods See With **alert mods** on, a card lands in your mod-review channel: ``` 🌐 Nova Language Moderation Wrong-language message — Russian in a English channel Detected Allowed here Channel Russian (97%) English #general Member ivan_2024 1510524330151510066 ❝ Message ❞ > привет всем, когда выйдет новый токен? Action ✅ 🗑️ message deleted · 💬 author notified 🔗 Jump to message ``` *** ## Set It Up — just talk to Nova No dashboard, no wizard — configure it conversationally. (Setup is admin-only, in your server/group — not DMs.) @mention Nova or reply to it: 1. **Set a channel's language** (run it in the channel, or name one): * *"@Nova make this channel English-only"* 2. **Or set a community-wide default:** * *"the whole server is English-only"* — channels with their own rule keep it; everything else follows the default. 3. **Choose the behaviors:** * *"delete messages in other languages, and send the language alerts to #mod-room"* 4. **Allowlist what's normal for your community:** * *"allowlist 'hasta la moon' — it's our meme"* 5. **Check or change anytime:** * *"what language rules do we have?"* · *"turn off language moderation"* **Bot permissions for deletion.** Auto-delete needs *Manage Messages* on **Discord**, or **admin with delete rights** on **Telegram**. If a permission is missing, Nova degrades gracefully (warn/alert still work) and the mod card says exactly what failed. *** ## Configuration Options | Option | What it does | | -------------------------- | --------------------------------------------------------------- | | **Per-channel languages** | The allowed language(s) for each channel / thread / forum topic | | **Community-wide default** | A `*` rule covering every channel without its own rule | | **Warn & redirect** | Public notice + pointer to the right channel (default on) | | **Auto-delete** | Remove violating messages (default off) | | **Alert mods** | Review cards to your mod channel (default off) | | **Mod-review channel** | Where alert cards go (defaults to where you set it up) | | **Allowlist** | Phrases that never flag, in any language | **60+ languages supported** — including English, Spanish, Portuguese, French, German, Italian, Dutch, Polish, Turkish, Indonesian, Vietnamese, Filipino, Russian, Ukrainian, Chinese, Japanese, Korean, Arabic, Hindi, Thai, Hebrew, Greek and more. Name them naturally (*"english"*, *"chinese"*) — Nova resolves them. *** ## Privacy Note Language detection happens **in real time**; ordinary messages in the right language are never stored. Only actual violations are written to the audit log — the detected language, confidence, action taken, and a short snippet for the mod card. *** **A rollout tip:** multilingual communities typically pair a per-channel language map (#general-en / #español / #中文) with warn-only mode for a week, then turn on deletion once they've seen the calls. # Nova Pulse **Nova Pulse** is a proactive **community-manager copilot** for moderators. Once an admin turns it on, Nova quietly watches your whole Discord server or Telegram group and helps your mod team stay on top of it three ways: it **rescues questions that went unanswered**, it posts a **daily community brief** — a short "chief of staff" readout of the room — to a private mod channel, and (optionally) it **answers common questions instantly** from a knowledge base you curate (**Concierge**). {% hint style="info" %} Alerts and briefs are **mod-facing** (they go to a **private mod channel** you choose); Concierge's instant answers are the one member-facing part, and it's off until you turn it on. Pulse is the behind-the-scenes counterpart to the member-facing [daily community snack](/nova-bot/nova-ai-agent/community/daily-community-snacks). {% endhint %} *** ## Free vs. Community PRO Pulse has a real free tier: the unanswered-question rescue — the part that saves questions from falling through the cracks — works on every community. [Community PRO](/nova-bot/premium/nova-premium-for-communities) turns Pulse into the full mod copilot: | | **Free** | **Community PRO** | | ----------------------------------------------------------------- | --------------- | ---------------------- | | **Unanswered-question rescue** | ✅ hourly sweeps | ✅ **every 15 minutes** | | **Questions scanned** | 25/day | Uncapped | | **Daily community brief** (+ on-demand *"give me the brief now"*) | — | ✅ | | **Newcomer welcome signals** | — | ✅ | | **Concierge auto-answer** (from your knowledge base) | — | ✅ **150 answers/day** | Hitting the free scan budget is never a blackout — un-scanned questions simply wait for the next day's budget while they're still inside the 24h window, and *"is Pulse on?"* shows today's usage against the cap. Your knowledge base is **kept either way**: entries added on any tier stay stored, and Concierge starts answering from them the moment the community is PRO. *** ## What Pulse Does
🙋 Unanswered-question rescueFinds genuine member questions that slipped through unanswered and flags them to your mod channel — one heads-up digest, not per-message spam.
🗞️ Daily community briefA once-a-day readout: activity counts, main topics + overall mood, still-unanswered items, newcomers to welcome, and the most-active members worth thanking.
💡 Concierge — instant auto-answerWhen a member asks something your knowledge base already covers (FAQs, tokenomics, how-tos), Nova answers instantly in-channel — and stays silent whenever it isn't sure.
*** ## Unanswered-Question Rescue The hard part of moderating isn't answering questions — it's **noticing** the ones nobody answered. Pulse handles that: 1. A cheap **SQL pre-filter** finds candidate questions past a minimum age (so the community gets a chance to answer organically first). 2. **One batched LLM call** decides which are *genuinely* still unanswered — not rhetorical, not already resolved in the thread. 3. Nova posts a **single digest** to your mod channel listing them, so mods get **one** nudge rather than a ping per message. The timing is tuned so you're neither spammed nor too late: a question must be at least **25 minutes old** before it can be flagged, and no older than **24 hours** (Pulse doesn't resurrect stale questions). Up to **8 questions** are listed per alert. Pulse keys on **whether a question was answered**, not on who asked — so it catches the quiet newcomer's question that would otherwise scroll away. *** ## Daily Community Brief Once a day at a time you choose, Pulse posts a short **"chief of staff" brief** to your mod channel: ``` 📊 Nova Pulse — Daily brief 142 messages from 28 active members in the last 24h. Topics & mood Mostly upbeat — lots of talk about the new release and a few questions about staking rewards. Still unanswered (3) • "how do I move my STX to the new pool?" — 4h ago • "is the airdrop snapshot done?" — 2h ago • "anyone got the contract address?" — 1h ago 👋 Welcome these newcomers alice · bob · carol (joined in the last 7 days) 🌟 Most active dave · erin · frank · grace · heidi ``` The daily brief (and the on-demand *"give me the brief now"*) is a **Community PRO** feature. **The numbers and names come from real buffered activity** — message and active-member counts, the still-unanswered list, newcomers (joined within the last **7 days**), and the top **5** most-active members. Only the **topics & mood** line is LLM-written (with a safe empty fallback if there's nothing to summarize). Pulse **stays quiet on dead days** — if there were fewer than **15 messages** in the last 24h, it skips the brief so mods aren't pinged with nothing. You can also ask for it **on demand** at any time: *"give me the brief now"*. *** ## Concierge — Instant Auto-Answer Every community answers the same questions over and over — *"when is the snapshot?"*, *"how do I stake?"*, *"where's the whitepaper?"*. **Concierge** (a **Community PRO** perk, up to **150 instant answers/day**) ends that loop: when a member asks something your [knowledge base](#nova-knowledge-the-knowledge-base-behind-concierge) already covers, Nova replies **instantly in-channel**, replying directly to the asker. The design principle is **confidence or silence**: * Nova answers **only** when the KB clearly and directly covers the question — the answer is grounded in *your* docs, never improvised. * Anything uncertain gets **no reply at all** — the question flows to the normal unanswered-question rescue, where a human picks it up. A wrong instant answer is worse than a short wait. * When a mod later answers a flagged question, that Q\&A can be **folded back into the KB** — so Concierge gets better at exactly the questions your community actually asks. {% hint style="warning" %} Concierge is **off by default** — Pulse alone never speaks in public channels. Turn it on with *"enable auto-answer"* once you've added a few KB entries (Nova will nudge you if the KB is empty). It requires **Community PRO** — on the free tier Nova keeps the KB stored and points you at the upgrade instead. {% endhint %} *** ## Nova Knowledge — the knowledge base behind Concierge **Nova Knowledge** is your community's durable **knowledge base** — the facts, FAQs, and project docs Concierge answers from. The KB is the memory; Concierge is the mouth. Admins fill it two ways: **paste** facts and FAQ entries in chat, or have Nova **import** whole sources — a website or docs page, a **GitHub repo** (README + docs folder), or a smart **contract's source code** — which Nova fetches, cleans, and stores as focused, searchable docs. Your docs are **never deleted on downgrade**: they stay stored, stay listable, and Concierge picks them right back up when the community is PRO again. ### Limits | | **Free** | **Community PRO** | | -------------------------------------------- | -------- | ------------------------------------------ | | **Docs stored** | — | **500** (removing one frees a slot) | | **Size per doc** | — | **12,000 characters** (imports auto-chunk) | | **Imports** (URL / repo / contract jobs) | — | **25 per week** | | **Quick FAQ curation** (add / list / remove) | ✅ | ✅ | | **Answered to members by Concierge** | — | ✅ (150 auto-answers/day) | ### What you can feed it
✍️ Pasted facts & FAQsThe classics: "add this to the FAQ: the snapshot is on the 15th". One focused fact per entry retrieves best.
🌐 A website or docs pageNova fetches the page, strips the markup, and stores the readable text in clean chunks — "import our docs page into the knowledge base".
📦 A GitHub repoREADME plus up to 5 files from the repo's docs/ folder — "import github.com/yourorg/yourrepo".
📜 A contract's sourceA Stacks contract's live Clarity source, so Nova can answer "what does the staking contract actually do?" from the code itself.
🔁 Resolved Q&A (automatic)When a mod answers a question Pulse flagged, the pair can fold back into the KB — the base gets better at exactly what your community asks.
**Re-importing refreshes, never duplicates.** Import the same URL / repo / contract again after it changes and Nova retires the old chunks and stores the new ones — one import slot, zero cleanup. ### Managing the knowledge base In your server/group (as an admin/mod), @mention Nova or reply to it: 1. **Add facts and FAQ entries:** * *"@Nova add this to the knowledge base: staking rewards pay out every cycle, roughly 2 weeks"* 2. **Import bigger sources:** * *"import into the knowledge base"* 3. **See and search what's stored:** * *"what's in the knowledge base?"* 4. **Prune:** * *"remove knowledge base entry #12"* 5. **Check the budget:** * *"knowledge base status"* — doc count vs. the 500 cap and this week's imports vs. 25. Then flip on the answering side: *"turn on auto-answer"*. ### How retrieval works (and why it's safe) * Docs are indexed with **full-text search** — no third-party embedding service ever sees your content. * When a member asks a question, Nova retrieves only the top-matching snippets; if **nothing matches, no AI call is spent** and Concierge stays silent (the confidence-or-silence rule above). {% hint style="warning" %} The knowledge base is community-provided content. Keep it factual and current — Concierge will faithfully repeat what you store, so an outdated doc means an outdated answer. Re-import your sources when they change. {% endhint %} *** ## Set It Up — just talk to Nova There's no wizard — configure Pulse conversationally. (Setup is admin-only, in your server/group — not DMs.) @mention Nova or reply to it: 1. **Turn it on:** * *"@Nova turn on Pulse / a community manager for this server"* 2. **Point it at a mod channel:** * *"send the Pulse brief to #mod-room"* — keep it private so members don't see it. 3. **Set the brief time (optional):** * *"post the daily brief at 9am"* — defaults to **09:00 UTC**. Each community fires at its own local time. 4. **Get it on demand:** * *"give me the community brief now"* 5. **Seed the knowledge base and turn on Concierge (optional):** * *"add this to the FAQ: …"* · *"turn on auto-answer"* 6. **Check status / turn off:** * *"is Pulse on?"* · *"turn off Pulse"* *** ## Privacy Note To do its job, Pulse **buffers recent message content** — but only for communities that have **opted in**, and only for a rolling **72-hour** window, after which messages are automatically pruned. This buffer is what powers question detection and the daily brief; it isn't used for anything else. New-member joins are recorded so Pulse can flag newcomers to welcome. Turning Pulse off stops ingestion. # Community GM **Community GM** turns the oldest crypto ritual into a daily brief. When a member says **"gm"** in your Discord server or Telegram group, Nova greets the room back with a **good-morning message** carrying the freshest ecosystem headlines — plus updates from **your community's own sources**: RSS feeds, watched web pages, and on-chain addresses. One GM per rolling **36-hour window**, so it stays a morning moment, never spam. {% hint style="success" %} **Neutral by default — it matches YOUR community.** Nova reads your community's own ecosystem from recent chat and pulls news for *that* chain — Bitcoin, Ethereum/EVM, Solana, Stacks, Ordinals, whatever your room is actually about. Nothing is hardcoded: a Solana community gets Solana mornings, an Ethereum community gets ETH mornings. Every community generates **its own** greeting — no two rooms share one. Want it locked to a specific focus? Add custom instructions (PRO). {% endhint %} The greeting fires in whichever channel a member said "gm". Personal **DM** GM briefs are a separate thing (the `/gm` command) and are unchanged. *** ## Limits | | **Free** | **Community PRO** | | ---------------------------------------------------------------- | ---------- | --------------------- | | **GM replies with fresh news** | ✅ | ✅ | | **Auto-matches your community's ecosystem** (neutral by default) | ✅ | ✅ | | **Community sources** (RSS / web pages / on-chain addresses) | ✅ up to 10 | ✅ up to 10 | | **Custom instructions** (lock the greeting's topics & tone) | — | ✅ | | **Fresh web search per GM** (optional custom query) | — | ✅ **10 searches/day** | *** ## What Lands in the GM
🗞️ Fresh ecosystem newsA short, upbeat greeting with the most important headlines of the last 24h — each one a tappable link (buttons on Telegram, embed links on Discord).
📡 Your own sourcesNew items from the RSS feeds you added, "new activity" pings when a watched page changes, and fresh transactions from watched Stacks addresses — only what's new since the last GM.
🎯 Custom steering (PRO)By default Nova auto-detects your ecosystem — leave this empty and mornings stay neutral & on-topic. Fill it to lock the focus for your room — "focus on Ordinals and our collection, hype but factual". Steering only: tone and topics, never a change to what Nova is.
🔎 Fresh web search (PRO)Nova runs one live web search per GM (your query or an automatic one) and grounds the greeting in what it finds — news your feeds might have missed.
*** ## Set It Up — just talk to Nova (Setup is admin-only, in your server/group — not DMs.) @mention Nova or reply to it: 1. **Turn it on:** * *"@Nova turn on the community GM"* 2. **Add your sources (optional, up to 10)** — RSS feeds, watched pages, and on-chain addresses: * *"add the RSS feed to the GM"* 3. **Steer it (Community PRO):** * *"give the GM custom instructions: focus on Bitcoin L2s and our own drops, keep it playful"* 4. **Ground it in live search (Community PRO):** * *"turn on the GM web search"* 5. **Check / turn off:** * *"is the GM on?"* — settings, sources, and today's web-search budget. {% hint style="warning" %} **Already using the channel-level** [**`/gm` opt-in**](/nova-bot/alerts-setup-guides/gm-alerts-legacy)**?** It keeps working exactly as before. But the moment you enable the community-level GM here, the **community setting takes precedence** for the whole server/group — including its sources (your existing ones carry over) — and turning the community GM **off** silences GM everywhere in it. {% endhint %} *** ## How the Cadence Works * The **first** "gm" in a rolling **36h window** triggers the brief; every later "gm" is just a greeting Nova may wave back at. * **Every community generates its own greeting**, grounded in that room's own recent activity, so the ecosystem always matches — a Solana room never inherits a Bitcoin room's morning. PRO steering and web search layer on top of the same per-community greeting. * Source updates are always per-community and deduplicated — an article that already appeared in a previous GM won't repeat. # Daily Community Snacks A **snack** is one bite-sized, genuinely interesting post — an insight, fact, observation, or "did you know" — that Nova drops into your Discord server or Telegram group on a schedule. Each snack is grounded in **your community's own recent conversations** plus whichever blockchain ecosystem it lives in (Bitcoin/Stacks, EVM, Solana, and beyond), so it sparks replies instead of reading like a bot broadcast. Members can reply and Nova joins the conversation naturally. The snack posts into the channel (or Telegram topic) where you enabled it. *** ## Free vs PRO | | **Free** | **Community PRO** | | -------------------------------------------- | ---------------------------- | ----------------------------------- | | Community-grounded snacks | ✅ | ✅ | | Cadence | Every **3 days** (or slower) | **Daily** (or any cadence you like) | | ✍️ Custom instructions (steer topics & tone) | — | ✅ | The free tier keeps the feature real — roughly two snacks a week is enough to feel Nova's presence. [Community PRO](/nova-bot/premium/nova-premium-for-communities) unlocks a **daily** snack and lets you **steer** it. {% hint style="success" %} **Your settings are never overwritten.** If you configure a daily snack on the free tier, Nova simply posts every 3 days for now — the moment you upgrade, your daily cadence kicks in automatically. *"daily snack status"* always shows both what's configured and what's effectively happening. {% endhint %} *** ## What a snack looks like Nova rotates through a palette of snack types, biased away from what it used recently: * **Insight** — a sharp observation connecting dots in what your community has been discussing * **Did you know** — a specific, verifiable fact about your ecosystem * **Ecosystem note** — something notable happening in your chain's world right now * **Mini lesson** — a "here's how this actually works" nugget * **Spotlight** — a project, tool, or concept worth knowing * **Stat drop** — one interesting number with just enough context to land No price predictions, no financial advice — just conversation starters that fit your room. *** ## Custom instructions *(Community PRO)* PRO admins can give the snack a standing brief — up to **500 characters** of steering: > *"@Nova focus the daily snacks on Ordinals and NFT culture, keep the tone playful"* Instructions steer **topics, tone, and focus only** — they can't change what Nova is, its rules, or the snack's no-financial-advice stance. (Like the [Nova Soul](/nova-bot/nova-ai-agent/community/nova-soul) persona, the text is sanitized and fenced so nothing hidden inside it can act as commands.) *** ## Set It Up — just talk to Nova (Setup is admin-only, in your server/group — not DMs.) @mention Nova or reply to it: 1. **Turn it on:** * *"@Nova turn on daily snacks"* — Nova asks for your preferred time and timezone (or say *"use the default"* for 13:00 UTC). 2. **Pick the schedule:** * *"post the snack at 18:00 Europe/Rome, every other day"* 3. **Steer it (PRO):** * *"focus the snacks on \"* 4. **Check / stop:** * *"is the daily snack on?"* · *"turn off daily snacks"* If snacks are already running in another channel, Nova tells you where and asks before moving them. *** {% hint style="success" %} Snacks are the **member-facing** daily touchpoint; the mod-facing daily readout is [Nova Pulse](/nova-bot/nova-ai-agent/community/nova-pulse)'s brief. They pair well — one keeps members engaged, the other keeps moderators informed. {% endhint %} # Nova Community Games **Nova Community Games** is an opt-in **engagement suite** for your Discord server or Telegram group — light "tribe games & hangouts" style fun that rewards members for showing up. Once an admin turns it on, Nova runs an **XP + levels** system, **leaderboards**, an automatic **weekly leaderboard post**, a fair **random winner picker / giveaways** — all free — plus, on Community PRO, a **weekly AI recap** and a library of **engagement games a moderator starts on demand**: trivia, question-of-the-day, would-you-rather, meme challenges and mini-games, all keyed to your community. {% hint style="info" %} **Games are mod-run, not scheduled.** A moderator simply asks Nova to *"start a trivia"* (or any game) whenever they want to liven up the chat — Nova generates it on the spot, posts it, and plays host. Nothing auto-posts on a timer except the weekly recap and weekly leaderboard. {% endhint %} Once it's on (for the **whole** server/group), the fun is **member-facing**: anyone can earn XP, check the leaderboard, and join giveaways. ## Free vs PRO | | **Free** | **Community PRO** | | ------------------------------------------- | -------- | -------------------- | | ⭐ XP & levels | ✅ | ✅ | | 🏆 Leaderboards (on demand) | ✅ | ✅ | | 📣 Weekly leaderboard post | ✅ | ✅ | | 🎁 Giveaways | ✅ | ✅ | | 🎮 Mod-run AI games & 🧠 trivia (on demand) | — | ✅ (25 AI games/week) | | 📅 Weekly AI recap | — | ✅ | Everything data-driven is **free**; the **AI generations** (mod-run games, trivia, the AI weekly recap) are part of [Community PRO](/nova-bot/premium/nova-premium-for-communities) with a generous weekly budget. When the budget is spent, XP, leaderboards, and giveaways keep running — only the AI games pause until Monday. *** ## What's Inside
⭐ XP & LevelsMembers earn XP for chatting and level up over time, with an anti-spam cooldown so quality beats spam.
🏆 LeaderboardsAll-time, weekly, and monthly rankings — plus "what's my rank?" for any member.
📣 Weekly Leaderboard PostAn automatic weekly celebration — top members of the week + the all-time podium, posted on your chosen day and channel.
🎮 Engagement Games (on demand)A mod asks Nova to run a game — community questions, would-you-rather, this-or-that, meme challenges, mini-games — and Nova generates and hosts it live. (PRO)
🧠 TriviaA mod starts a trivia tuned to your community; Nova holds the answer and reveals it in-chat when you ask. (PRO)
📅 Weekly RecapA "here's how the week went" summary built from real activity — most-active members and highlights. (PRO)
🎁 GiveawaysA fair random winner picker — members enter with a keyword, Nova draws winners uniformly at random.
*** ## XP & Levels Every qualifying message earns **15–25 XP** (uniform random), and members **level up** on a quadratic curve (each level costs a little more than the last). Two guardrails keep it fair: * **Anti-spam cooldown** — a member earns XP **at most once every 60 seconds**, no matter how fast they type. This is the single most important anti-gaming measure, so flooding the chat doesn't farm XP. * **Minimum length** — messages shorter than **3 characters** (trimmed) earn nothing, so "gm" / single-emoji spam doesn't dominate. When a member levels up, Nova can post a small **level-up announcement** in the channel where it happened (on by default — you can turn it off). Prefer them out of the way? Nominate a dedicated **level-up channel** — *"announce level-ups in #achievements"* — and they all land there instead (on Telegram, a forum topic). {% hint style="success" %} XP is earned **server/group-wide** — it doesn't matter which channel a member is active in. The leaderboard reconciles it all under one community. {% endhint %} ### Checking the leaderboard The leaderboard is readable by **any** member (not admin-only), group-only. Just ask Nova: > *"show the leaderboard"* — or ask for your own rank: *"what level am I?"* Rankings are available **all-time, this week, and this month**. ### The weekly leaderboard post Once a week Nova also posts the leaderboard **automatically** — the top members of the week (with total XP earned and active-member count) plus the **all-time podium**. It's built straight from the XP data, included on every tier, and fully configurable: * *"post the weekly leaderboard on Sundays"* — any weekday (default **Monday**, at your games post time) * *"post the weekly leaderboard in #general"* — any channel (on Telegram, a forum topic); defaults to the games channel * *"turn off the weekly leaderboard"* — it's on by default *** ## Engagement Games — mod-run *(Community PRO)* Whenever a moderator wants to spark some life in the chat, they just ask Nova to run a game — **there's no schedule**. Nova generates the game on the spot (grounded in your community, or on a topic you name), posts it, and plays host: * **Trivia** — *"start a trivia"* — a genuine question with one verifiable answer. Nova **holds the answer** and posts it when you say *"reveal the answer"* (no timer — you decide when). * **Question of the day** — *"post a community question"* — an open, inviting question that gets members talking * **Would-you-rather** / **this-or-that** — *"run a would-you-rather"* — pick a side and defend it * **Meme challenge** — *"do a meme challenge"* — a caption or meme prompt on a theme * **Mini-game** — *"run a mini-game"* — a light in-chat game (word games, "guess the project from an emoji", two-truths-and-a-lie…) Say *"list games"* to see everything on offer, and add a theme any time — *"start a trivia about the Bitcoin halving"*. Games are **admin/mod-only**; anyone can join in once posted. AI game generation runs on a **weekly budget of 25**. If it's ever spent, games pause until Monday — XP, leaderboards, and giveaways are unaffected. *"community games status"* shows this week's usage. *** ## Weekly Recap *(Community PRO)* Once a week (Mondays by default), Nova posts a **community recap** built from real activity data — the most-active members and a summary of the week. It's deterministic where it counts (the numbers come from actual data), so it's an honest readout, not a hallucinated one — and it doesn't consume the AI-games budget. On the free tier, the weekly leaderboard post covers the same celebration moment. *** ## Giveaways / Random Winner Picker Run a fair raffle right in chat. The flow is simple: 1. **Start** — *"start a giveaway for a WL spot, pick 1 winner"*. Nova posts the giveaway and opens entries. 2. **Enter** — members type the **entry keyword** (default `join`) to enter. It's an exact, case-insensitive match on the trimmed message, so ordinary chatter never counts as an entry. 3. **Pick** — *"pick the winner"*. Nova closes entries and draws winner(s) **uniformly at random** (a Fisher–Yates draw — unbiased). 4. **Reroll / status / cancel** — *"reroll"* draws a fresh winner from the same entries; *"how many entries?"* / *"giveaway status"*; *"cancel the giveaway"*. You can draw up to **20 winners** per giveaway. Giveaways are **admin-only** and require Community Games to be enabled with giveaways allowed. *** ## Set It Up — just talk to Nova There's no wizard — configure it conversationally. (Setup is admin-only, in your server/group — not DMs.) @mention Nova or reply to it: 1. **Turn it on:** * *"@Nova turn on community games for this server"* 2. **Run a game (admin/mod), any time:** * *"start a trivia"* — then *"reveal the answer"* when you're ready 3. **Toggle individual features:** * *"turn off level-up announcements"* 4. **Tune the XP extras** (shown as "Ascend" in the dashboard): * *"announce level-ups in #achievements"* 5. **Set the recap time (optional):** * *"post the weekly recap on Fridays at 6pm"* — defaults to **Monday, 16:00 UTC**. This only schedules the recap; games are always on demand. 6. **Use it (any member):** * *"leaderboard"* 7. **Run a giveaway (admin):** * *"start a giveaway for \"* → members type `join` → *"pick a winner"* 8. **Check status / turn off:** * *"are community games on?"* · *"turn off community games"* *** ## Privacy Note Community Games tracks **activity for scoring** — it counts qualifying messages to award XP and rank members, and logs giveaway entries. Prompts and recaps are generated from your community's brief and aggregate activity. It's engagement data, kept per-community and used only to run the games. # Nova Chat **Nova Chat** is the community-paid message allowance that comes with **Community PRO**. In a PRO server/group, members' conversations with Nova are paid for by the **community's own pooled budget** — so a member chatting with Nova there **doesn't spend their personal free daily limit**. Without it, every member talks to Nova on their own personal allowance (free users: 10 requests/day, everywhere combined). With Nova Chat, your community absorbs that cost: a newcomer with zero history can ask Nova twenty questions in your server on day one, and still have their full personal limit left for DMs and other communities. {% hint style="info" %} Nova Chat is automatic — there's **nothing to enable and nothing members need to do**. The moment a community is on Community PRO, messages to Nova in that server/group draw from the pool. See [Nova Premium for Communities](/nova-bot/premium/nova-premium-for-communities). {% endhint %} *** ## The Pool | Budget | Limit | | ---------------------------------- | -------------- | | **Community pool, per day** | 150 messages | | **Community pool, per month** | 2,500 messages | | **Fair share, per member per day** | 50 messages | The **fair-share cap** is what keeps the pool honest: one hyperactive member can't drain the whole day's budget before anyone else wakes up. After a member's 50th pooled message of the day, they simply continue on their own personal allowance. {% hint style="success" %} **The pool only ever adds headroom — it never takes any away.** When a cap is reached (fair-share, daily, or monthly), members fall back to exactly the personal limits they'd have without it: free users keep their 10/day, and a member with personal [PRO](/nova-bot/premium) keeps their 100/day on top of whatever the pool already covered. Caps reset automatically — daily at midnight UTC, monthly on the 1st. {% endhint %} *** ## What Members See Nothing, usually — that's the point. Nova just answers, and nobody's personal counter moves. The only time Nova Chat becomes visible is when a budget runs out mid-day **and** the member's personal limit is also spent. Then, instead of the generic limit notice, Nova explains what actually happened: > 🚫 *Nova Chat has used up this community's daily message budget (150/day). It resets automatically — no action needed. Personal daily limits apply until it resets.* *** ## Checking the Pool Any admin can see live pool usage in the plan status — in your server/group, ask: > *"@Nova what plan are we on?"* · *"@Nova show our plan status"* The status card includes the Nova Chat line: ``` 💬 Nova Chat pool: 37/150 messages today · 412/2,500 this month — members chat with Nova here without spending their personal daily limit (fair-share 50/member/day). ``` *** ## The Fine Print | Question | Answer | | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | **Does it apply in DMs?** | No — the pool covers messages **inside the PRO server/group**. DMs always use personal limits. | | **Do admins draw from the pool?** | Bot admins bypass rate limits entirely and never touch the pool. | | **Do cooldowns still apply?** | Yes — the short per-user cooldown and the per-server hourly limit still protect against bursts; the pool only replaces the personal *daily* limit. | | **What about free communities?** | Nothing changes — members use their personal limits exactly as before. | | **Both platforms?** | Yes — a plan covering a Discord server and a Telegram group shares one pool across both. | *** Nova Chat pairs naturally with [Nova Soul](/nova-bot/nova-ai-agent/community/nova-soul) (your community's custom persona) — together they make Nova feel like *your community's own bot*: it speaks with your identity, on your budget. # Nova Soul **Nova Soul** lets your community give Nova its own identity. A community on **Community PRO** can **rename Nova**, set **style hints** (tone, emoji, vocabulary), and write a full **persona description** — and Nova wears that skin *only in your server/group*. Everywhere else it's still plain Nova. Your degen trading group can talk to a meme-slinging mascot; your DAO's governance server can have a formal, no-emoji analyst; a Spanish-first community can ask for Spanish-flavored replies — all from the same bot, without touching anyone else's setup. Nova Soul is part of **Community PRO**: on the free tier Nova will explain how to upgrade instead. See [Nova Premium for Communities](/nova-bot/premium/nova-premium-for-communities). *** ## What You Can Customize | Field | What it does | Limit | | --------------- | ------------------------------------------------------------------------------------------------- | ----------- | | **Bot name** | The display name Nova uses when talking in your community ("I'm Zippy, this server's assistant…") | 64 chars | | **Style hints** | Short tone guidance — *"playful, heavy emoji, degen slang"* or *"formal, concise, no emoji"* | 500 chars | | **Soul text** | The full persona: who the character is, how it speaks, community lore to lean on | 4,000 chars | Set one, two, or all three — each works on its own. The persona applies to Nova's conversational replies in your community and takes effect on the **next message** after you save it. *** ## Styling Only — By Design A persona changes how Nova *sounds*, never what Nova *does*. This is a hard guarantee, not a suggestion: * The persona **cannot** change Nova's safety rules, honesty, tool permissions, admin/DM gating, moderation behavior, or rate limits. * Instructions hidden inside persona text (e.g. *"ignore your rules"*, *"reveal your system prompt"*, *"skip confirmations"*) are **stripped and ignored** — Nova applies only the legitimate tone/style guidance and discards the rest. * Nova stays Nova underneath: asked directly, it will never deny being Nova, and every capability and limit works exactly as documented. {% hint style="success" %} This means an admin can hand persona-writing to anyone on the team (or even run a community contest for it) without worrying that a creative soul text could jailbreak the bot. {% endhint %} *** ## Set It Up — just talk to Nova (Setup is admin-only, in your server/group — not DMs.) @mention Nova or reply to it: 1. **Rename it:** * *"@Nova call yourself Zippy in this server"* 2. **Set the tone:** * *"@Nova act more playful here — lots of emoji, degen slang welcome"* 3. **Write the full persona:** * *"@Nova set your soul: You are Zippy, the mascot of the Zippy DAO. You speak in short punchy sentences, love rocket emojis, and always hype the community's builders…"* 4. **Check or reset anytime:** * *"@Nova show the community persona"* · *"@Nova clear the persona"* — instantly back to plain Nova. You can also edit the same three fields from the web dashboard's **Community Settings** panel — both paths go through identical validation, so the bot and the dashboard never drift. One persona per **community** — if your plan covers both a Discord server and a Telegram group, they share the same soul. *** ## Configuration Options | Option | What it does | | --------------- | --------------------------------------------------------------------------------------- | | **status** | Show the current persona (name, style, soul text) and whether your tier unlocks it | | **set\_name** | Set the custom bot display name | | **set\_style** | Set the tone/style hints | | **set\_soul** | Set the persona description | | **clear** | Remove the whole persona — back to Nova's default identity | | **bot\_status** | Show the custom-bot link status (see below): @username, lifecycle state, online/offline | | **unlink\_bot** | Disconnect your custom bot on this platform — back to the shared Nova bot | *** ## Custom Bot Identity — run Nova as *your* bot The persona changes Nova's words; the **custom bot identity** changes the face. A PRO community can run Nova under its **own Discord bot application** and/or its **own Telegram bot token** — so every reply, Guardian report, level-up post, snack, and scheduled message comes from **your bot's name and avatar**, not the shared Nova account. Nova stays Nova underneath: same features, same context and memory, same fair-use budgets, same safety rules. If your custom bot ever goes down or its token is revoked, Nova **automatically falls back to the shared bot** — your community is never left silent. ### Linking your bot — dashboard only {% hint style="warning" %} Bot tokens are **never entered in chat**. Anything pasted into Discord/Telegram lives in chat history forever — if a token ends up in a message, treat it as compromised: revoke/regenerate it and use the dashboard. Nova will refuse tokens in chat and tell you the same. {% endhint %} Link from the web dashboard → **Community Settings** → the **Nova Soul** card → *Custom bot identity*: {% tabs %} {% tab title="Discord" %} 1. Create an application at [discord.com/developers](https://discord.com/developers/applications) → **Bot** tab → **Reset Token** and copy it. 2. On the Bot tab, enable the **Message Content** and **Server Members** privileged intents (Nova's community features need to read messages and see joins). 3. Paste the token into the Soul card and hit **Link** — Nova validates it live and shows your bot's name. 4. Invite your bot with the **invite link the card generates** (the exact same permission set as shared Nova — never administrator). 5. Your bot takes over in your server within a minute. The shared Nova goes quiet there automatically (no double answers, no double XP). {% endtab %} {% tab title="Telegram" %} 1. Create a bot with [@BotFather](https://t.me/BotFather) (`/newbot`) and copy the token. 2. In @BotFather run **/setprivacy → Disable** so your bot can see regular group messages (Guardian, XP, Pulse and language moderation need this). 3. Paste the token into the Soul card and hit **Link**. 4. Add your bot to the group — members can mention it by **its own @username** (and "@nova" keeps working too). {% endtab %} {% endtabs %} ### Security & lifecycle * Tokens are stored **encrypted (AES-256-GCM)** and are **write-only** — no page, tool, or API ever shows a token again after you link it. To rotate, just paste a new one. * One bot = one community. A token already linked elsewhere is refused. * Your bot only works in **your linked server/group** — invited anywhere else, it stays silent. * **Token revoked / invalid?** Nova stops the bot, marks it *invalid*, posts a heads-up to your mod channel via the shared bot, and falls back — re-link a fresh token from the dashboard. * **PRO lapses?** The custom bot is *suspended* (token kept, encrypted) and resumes automatically when the plan is active again. * Check or disconnect from chat anytime: *"@Nova custom bot status"* (admin-only). * Slash commands and the Telegram setup wizards stay on the shared Nova bot — your custom bot handles AI chat and all community features (Guardian, Pulse, Games, Snacks, GM, language moderation, scheduled posts). # Community Settings (Web Dashboard) Everything in the community suite can be managed by talking to Nova — and now also from a **web control room**: [nova.zeroauthoritydao.com/community](https://nova.zeroauthoritydao.com/community). One page shows every feature for your server/group as a card: flip it on or off, edit every setting in a form, and watch live usage against your plan's budgets. {% hint style="success" %} **Chat and web edit the same settings.** A change you make on the web is what Nova sees in chat one message later, and vice versa — there are not two copies of your config, just two doors to the same one. {% endhint %} *** ## Getting in 1. Go to [nova.zeroauthoritydao.com/community](https://nova.zeroauthoritydao.com/community) and **sign in** (Discord, Telegram, Google, or your Stacks wallet). {% hint style="warning" %} **Managing a community requires a real sign-in.** When you connect a Stacks wallet, Nova asks it to **sign a one-time message** — that signature is what proves the wallet is actually yours (an address alone is public information anyone could type in). If you skip the signature, the page opens in **read-only** mode: you can look, but saving settings, issuing activation codes, or linking a custom bot will ask you to sign in first. Reconnect your wallet and approve the signature to unlock editing — nothing to remember, no password. {% endhint %} 2. Your communities appear automatically if you've ever set up a community feature in chat (e.g. *"@Nova enable Guardian"*) — the admin who set it up owns it on the web too. 3. Starting from zero? The page walks you through it: create a community, get a short-lived **activation code**, and paste `@Nova activate YOUR-CODE` in the server or group you admin. That in-chat step is how you prove you're an admin there — the website can't know that on its own. Own several communities? A picker at the top switches between them. A community that spans **both Discord and Telegram** shows platform tabs inside each card — each platform keeps its own settings. *** ## What you'll see ### The header * Your community's name and its **FREE / PRO** badge, with an upgrade button on Free. * The servers/groups the community is linked to. * **AI usage meters**: tokens used this month against your plan's monthly allowance, plus your 30-day AI cost. ### The feature cards Cards are grouped the way the suite is organized: | Group | Cards | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Nova Soul** | [Custom bot name & persona](/nova-bot/nova-ai-agent/community/nova-soul) *(PRO)* | | **Nova Chat** | [Pooled member allowance](/nova-bot/nova-ai-agent/community/nova-chat) + catch-up *(PRO, automatic)* | | **Nova Guardian** | [Anti-scam shield](/nova-bot/nova-ai-agent/community/nova-guardian) — mode, mod channel, auto-moderation, thresholds, allowlist | | **Nova Orbit** | [Ascend](/nova-bot/nova-ai-agent/community/nova-community-games) (XP & leaderboards) · [Pulse](/nova-bot/nova-ai-agent/community/nova-pulse) (incl. the Concierge auto-answer toggle) · [Play](/nova-bot/nova-ai-agent/community/nova-community-games) · [GM](/nova-bot/nova-ai-agent/community/community-gm) · [Snacks](/nova-bot/nova-ai-agent/community/daily-community-snacks) · Ops (AI drafts, [language moderation](/nova-bot/nova-ai-agent/community/nova-language-moderation), scheduled messages, X drafts) · [Knowledge](/nova-bot/nova-ai-agent/community/nova-pulse) | | **Nova Alerts** | A pointer to the Alerts Hub on your Dashboard, where per-system alert subscriptions live | {% hint style="info" %} **Dashboard names vs. docs names.** The dashboard groups a few features under names these docs don't use: **Ascend** = Community Games' XP & leaderboards, **Play** = the games engine (trivia, giveaways, mod-run games), **Ops** = the moderation & drafting tools (AI drafts, language moderation, scheduled messages, X drafts), and **Knowledge** = the knowledge base documented on the [Pulse page](/nova-bot/nova-ai-agent/community/nova-pulse). {% endhint %} Expand any card to get: * **On/off switch** — enabling runs the same setup the chat flow does (Guardian arms auto-moderation by default, Pulse asks for a mod channel, Games/Snacks ask for a target channel). * **Every setting as a form field** — hours and timezones, cadences, thresholds, channels, toggles, custom instructions. Fields are validated the same way Nova validates them in chat. * **PRO fields** — marked with a `PRO` chip. On the Free tier they're locked with an upgrade pointer instead of failing silently. * **Free vs Community PRO caps** — small chips showing each budget on both tiers (e.g. *AI scans/day: 20 free · 500 PRO*). * **Live usage bars** — today's/this week's spend against the budget: Guardian AI scans, language-mod AI checks, AI games, Pulse question scans & auto-answers, GM web searches, Knowledge imports, Ops drafts, and the Nova Chat pool (daily + monthly). **Some cards are informational.** Nova Chat and catch-up work automatically on PRO (nothing to configure), Ascend's channels live on the Play card (shared settings), and **Knowledge is content, not settings** — you feed it in chat (*"@Nova add this to the knowledge base"*) and the card shows your caps and import budget. ### Moderator pings & plan management Two more cards live here: * **Moderator Alerts** — choose who gets @pinged when a Guardian scam, language violation, or unanswered question fires. * **Community plan** — where your paid plan is active, activation codes for the platform you haven't covered yet, and **Unlink** to move the plan to a different server/group. *** ## Related pages * The **Community tab of the Alerts Hub** (on `/dashboard`) points here. * Buying the plan happens on [nova.zeroauthoritydao.com/premium](https://nova.zeroauthoritydao.com/premium), which also has the full **feature-by-feature Free vs Community PRO comparison** — see [Nova Premium for Communities](/nova-bot/premium/nova-premium-for-communities). Prefer talking? Everything on this page has a chat equivalent — *"@Nova guardian status"*. The web panel is the overview; the conversation is the shortcut. # Premium Upgrade your Nova experience with higher limits, exclusive alert types, and advanced AI features. {% hint style="info" %} This page covers **personal Premium** — your own limits and alert types. Looking to unlock Nova's community-management suite (Guardian, Language Moderation, Pulse + Concierge, Games) for a whole Discord server / Telegram group? That's [**Nova Premium for Communities**](/nova-bot/premium/nova-premium-for-communities) — a separate, per-community plan. {% endhint %} *** ## Plans | Plan | Price | Duration | | ----------- | ------------- | -------- | | **Monthly** | **0.99 USDh** | 30 days | | **Yearly** | **9.99 USDh** | 365 days | Billed as a one-time on-chain payment. Renew anytime — additional purchases extend your expiration date. Save over **15%** with the yearly plan. **Accepted tokens:** USDh, STX, and sBTC. If you pay with STX or sBTC, the swap to USDh is handled automatically. *** ## Free vs Premium | Feature | Free | Premium | | --------------------------------------- | -------------- | ------------------ | | **Token swap alerts** | 3 tokens | 20 tokens | | **NFT collection alerts** | 10 collections | 100 collections | | **Wallet tracker alerts** (multi-chain) | 1 address | 300 addresses | | **Custom wallet labels** | -- | Yes | | **Contract deployment alerts** | -- | Yes | | **New token pair alerts** | -- | Yes | | **Whale transfer alerts** | -- | Yes | | **Daily AI messages** | 5 | 25 | | **Smart alerts** | 2 | 50 | | **Smart alert conditions** | 1 per alert | Up to 10 per alert | | **Smart alert cooldown** | 1 hour | 1 minute | | **Composable conditions** | -- | AND/OR logic | | **Time windows** | -- | UTC hour ranges | | **Digest mode** | -- | Daily summaries | | **Discord roles managed** | 10 | 30 | | **Discord servers** | 1 | 3 | | **Telegram groups** | 1 | 3 | | **Daily notification cap** | 300 | 10,000 | *** ## Premium-Only Alert Types These notification types are exclusive to Premium subscribers. Each chain is its own opt-in — subscribe only to the ones you care about. Token/pair snipers let you set a **minimum liquidity (USD)** threshold during setup: choose **0** to see everything (noisier), or raise it to surface only pools with real depth. | Sniper / Alert | Chains | What triggers it | Key filter / option | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | --------------------------------------------- | | **Token/Pair Sniper** | Stacks · Solana (incl. **pump.fun** graduations) · EVM majors (Ethereum, Base, BNB Chain, Arbitrum, Polygon, Optimism, Avalanche) · TON (STON.fi, DeDust & other DEXes) · Sui (Cetus, Turbos & other DEXes) | New token / jetton / coin or liquidity-pool launch | Minimum liquidity (USD) | | **NFT Sniper** | Stacks | New NFT collection deployments and mints | All individual mints, or new collections only | | **NFT Collection Sniper** | Solana · EVM/other (Ethereum, Polygon, Base, Arbitrum, Avalanche, Sei, Monad, and more) | New NFT collection launches — alerts include mint price, supply, artwork, and launch time for upcoming mints | Subscribe to Solana, EVM, or both | | **Contract Sniper** | Stacks | New smart-contract deployments | — | | **Whale Transfer Alerts** | Stacks | High-value STX transfers in real time | — | | **Listings Sniper** | Hyperliquid | New **spot pair** or **perp market** listings (perp alerts include max leverage) | — | {% hint style="warning" %} **Coming soon:** Bitcoin **Runes** & **BRC-20** deploy snipers are built and will switch on once a suitable data source is connected. A **TON NFT-collection** sniper is planned, pending a keyless launchpad feed. {% endhint %} *** ## How to Subscribe ### From Discord 1. Use the `/premium` command 2. Select **"Subscribe"** 3. You'll receive a link to the payment page 4. Complete the on-chain transaction 5. Your premium status activates automatically ### From Telegram 1. Use the `/premium` command 2. Follow the wizard steps 3. Complete payment via the provided link 4. Status activates automatically ### From the Web Visit the premium page directly at [nova.zeroauthoritydao.com/premium](https://nova.zeroauthoritydao.com/premium). Sign in and link your accounts from the dashboard. *** ## Check Your Status Use `/premium` on Discord or Telegram to view your current subscription status and expiration date at any time. *** ## Custom Plan Need tailored limits, custom alert integrations, or project-specific requirements? **Contact us** on [Discord](https://discord.gg/zeroauthority) or [Telegram](https://t.me/zeroauthority) for a plan that fits your needs. # Nova Premium for Communities **Nova Premium for Communities** — **Community PRO** for short — is a paid plan for a **whole Discord server or Telegram group**: it unlocks Nova's AI community-management suite for every member of your community at once. It is a separate thing from [personal Premium](/nova-bot/premium): personal Premium upgrades *your own* limits and alert types wherever you go; a **community plan** belongs to the *server/group* and powers the features that work on the whole room — Guardian, Language Moderation, Pulse + Concierge, Community Games, daily snacks. One community plan can even cover **both** your Discord server *and* your Telegram group together. **Who can manage it:** only a server/group **admin**, and only **inside the community** (not in a DM). Members never need to do anything — features the plan unlocks work for everyone in it. *** ## Plans There is **one paid plan**. No tiers to compare, no features held back. | | **Free** | **Community PRO** | **Enterprise** | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- | ------------------------------------------------------------------ | -------------- | | **Price** | $0 | **$9.90/month** or **$99/year** | Custom | | **Blockchain Q\&A + basic stats** | ✅ | ✅ | ✅ | | **🛡️** [**Guardian**](/nova-bot/nova-ai-agent/community/nova-guardian) (anti-scam shield) | 20 AI scans/day | ✅ **500 AI scans/day** | ✅ | | **🌐** [**Language Moderation**](/nova-bot/nova-ai-agent/community/nova-language-moderation) (per-channel language rules) | 50 AI checks/day | ✅ **500 AI checks/day** | ✅ | | **📊** [**Pulse**](/nova-bot/nova-ai-agent/community/nova-pulse) (mod copilot) | Hourly question sweeps, 25 scanned/day | ✅ **15-min sweeps, daily brief + Concierge auto-answer (150/day)** | ✅ | | **📚** [**Nova Knowledge**](/nova-bot/nova-ai-agent/community/nova-pulse) (KB + website/repo/contract imports) | — | ✅ **500 docs · 25 imports/week** | ✅ | | **☀️** [**Community GM**](/nova-bot/nova-ai-agent/community/community-gm) (daily "gm" greeting brief + sources) | ✅ | ✅ **+ custom instructions & web search (10/day)** | ✅ | | **🎮** [**Community Games**](/nova-bot/nova-ai-agent/community/nova-community-games) (XP, leaderboards, mod-run games, giveaways) | XP, weekly leaderboard & giveaways | ✅ **+ 25 AI games/week** (mod-run trivia/games, AI recap) | ✅ | | **🍪** [**Daily community snacks**](/nova-bot/nova-ai-agent/community/daily-community-snacks) | Every 3 days | ✅ **Daily + custom instructions** | ✅ | | **✨** [**Nova Soul**](/nova-bot/nova-ai-agent/community/nova-soul) (custom bot name & persona) | — | ✅ | ✅ | | **🤖** [**Custom bot identity**](/nova-bot/nova-ai-agent/community/nova-soul#custom-bot-identity-run-nova-as-your-bot) (run Nova under your OWN Discord app / Telegram bot — your name & avatar everywhere) | — | ✅ | ✅ | | **💬** [**Nova Chat**](/nova-bot/nova-ai-agent/community/nova-chat) (pooled member messages — 150/day, 2,500/mo) | — | ✅ | ✅ | | **📝 Ops AI drafts** (Nova writes your announcements & tweets — see below) | — | ✅ **30 drafts/week** | ✅ | | **⏰ Scheduled messages** (timed announcements) | 3 active | ✅ **25 active** | ✅ | | **Advanced analytics & the rest of the suite** | — | ✅ | ✅ | | **Monthly AI allowance** | 1M tokens | 15M tokens | Custom | | **Covers** | — | **1 Discord server + 1 Telegram group** | Up to 25 | **Yearly saves \~17%** — $99 for the year instead of $118.80 paid monthly. One subscription covers **one Discord server and one Telegram group** — a project running both gets both on a single plan; a second Discord server needs a second subscription. ### Allowance & fair-use budgets The **monthly AI allowance** covers everything the suite spends on your community — Guardian verdicts, language checks, Pulse briefs, Concierge answers, Games — and the per-feature numbers in the table are daily/weekly fair-use budgets on the same allowance. Hitting a cap is never a blackout: only the AI part of that feature pauses (daily budgets reset at midnight UTC, weekly ones on Monday, the allowance when the month rolls over), while everything non-AI keeps working — Guardian's flood protection and built-in heuristics, script-based language detection, XP, leaderboards, giveaways, scheduled messages, and mod alerts. Knowledge docs and scheduled messages are *slot* limits, not spend (removing one frees a slot), your Knowledge docs are **never deleted on downgrade**, and settings you configured (like a daily snacks cadence) are kept, not overwritten, so upgrading restores them. Admins can check usage anytime — feature status commands (*"is Guardian on?"*), *"how much AI have we used?"*, or the [Community page](https://nova.zeroauthoritydao.com/community). The same principle applies on the Free plan's 1M-token allowance; Enterprise exists for communities that legitimately need more. ### Already using Nova? What happens when the FREE plan goes live If your community was using Nova's features **before** the FREE/PRO plans launched, here's the transition — designed so nothing you rely on breaks: * **Nothing gets turned off.** Every feature you enabled stays enabled, configured exactly as you left it. * Your community is placed on the **Free plan** automatically, so the fair-use budgets in the table above start applying (Guardian 20 AI scans/day, language checks 50/day, and so on). Hitting a budget is never a blackout — see the list above for what each one degrades to. * **Your mod channel gets a one-time message from Nova** when this happens — one notice, once, explaining the same things this section does. It goes to your Guardian/Pulse mod channel if you have one, so members never see it. * Communities that had already purchased a plan (including the old Starter/Pro tiers) are unaffected — paid plans keep their full PRO experience, and legacy tiers are honored. Upgrading to **Community PRO** at any point lifts every budget to the PRO numbers — and settings you configured on Free (like a daily snacks cadence) come back automatically, they're never overwritten. ### Ops AI drafts A Premium perk for your admin team: inside your server/group, ask Nova to **write your announcements, community updates, and tweets** — *"@Nova draft an announcement about Friday's AMA"*, *"draft a tweet about the launch"*. Nova drafts like a pro copywriter, iterates through as many edit rounds as you want (edits are free — only each **new** draft counts toward the 30/week), then hands you the final text to post. Posting stays in your hands and under your accounts. *** ## Subscribe Buying is **two steps**: pay on the web, then switch it on in your community. The second step exists because the website has no way to know you're an admin of your server — but Nova, sitting *inside* it, does. ### Step 1 — Pay Go to [**nova.zeroauthoritydao.com/premium**](https://nova.zeroauthoritydao.com/premium) and find **Community PRO** (it's separate from personal Premium, further down the page). * Pick **monthly** or **yearly**. * Connect your **Stacks wallet** and pay with **USDC, sBTC, or STX**. No card, no account. Or just ask Nova in your server — *"@Nova subscribe"* — and it'll hand you a direct link to the checkout. ### Step 2 — Switch it on where you want it After paying you get an **activation code** that looks like `NOVA-7F3K-2M9P`. Go to the Discord server or Telegram group you want covered and, **as an admin**, send: ``` @Nova activate NOVA-7F3K-2M9P ``` Nova checks you're an admin there and switches the plan on: ``` ✅ Community PRO is now active in this server. Unlocked: Guardian, Language Moderation, Pulse, Concierge, Community Games, Daily snacks… Turn features on when you're ready — e.g. "enable Guardian". ``` {% hint style="warning" %} Codes are **single-use** and expire after **30 minutes**. If yours expires, grab a fresh one from your [Community page](https://nova.zeroauthoritydao.com/community) — the **Community PRO** card has a **New code** button. {% endhint %} ### Covering both platforms Your subscription covers one Discord server **and** one Telegram group. Redeem a code in the first, then generate **a second code** from the [Community page](https://nova.zeroauthoritydao.com/community) and redeem it in the other. ### Moving the plan to a different server On the [Community page](https://nova.zeroauthoritydao.com/community), open the **Community PRO** card and hit **Unlink** next to a server/group. That frees the slot, and you can activate a fresh code somewhere else. *** ## Turning features on Paying unlocks the suite — it doesn't switch every feature on automatically (nobody wants a bot that suddenly starts deleting messages). Enable what you want, when you want: > *"@Nova enable Guardian"* · *"@Nova enable Pulse"* · *"@Nova turn on Community Games"* · *"@Nova make #general English-only"* Or use the web control room: the [Community Settings dashboard](/nova-bot/nova-ai-agent/community/community-settings-web-dashboard) at [nova.zeroauthoritydao.com/community](https://nova.zeroauthoritydao.com/community) shows every feature as a card — enable/disable, edit every setting, and watch live usage against the budgets in the table above. Chat and web edit the same configuration. *** ## Track Usage & Manage * *"how much AI have we used?"* — 30-day token usage, cost, and how much of your monthly allowance is left. * *"cancel our subscription"* — stops renewal; **your features stay on until the paid period ends**, then the community returns to Free. There's also a short grace period before anything is switched off, so a late renewal never interrupts service. * Your communities, plan status, per-feature settings, and live usage are all on the [Community page](https://nova.zeroauthoritydao.com/community). {% hint style="warning" %} **Personal Premium and a community plan don't overlap.** Personal Premium (see [Premium](/nova-bot/premium)) gates *your* alert limits and snipers; the community plan gates the *suite* for a server. Buying one doesn't grant the other. {% endhint %} *** ## Enterprise Running a large ecosystem — many servers/groups, custom limits, custom features? Enterprise plans are set up directly — **contact us** on [Discord](https://discord.gg/zeroauthority) or [Telegram](https://t.me/zeroauthority). --- [Next Page](/llms-full.txt/1)