--- id: about/vision-and-values title: "Vision and Values" description: "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." product: zadao canonical: https://zeroauthoritydao.ai/docs/about/vision-and-values related: [about] tokens: 424 --- # Vision and Values States Zero Authority's vision of a user-owned internet built through the Cerulean Marketplace, and its three values: respect, buidl and transparency. ## 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. --- id: guides/add-nova title: "Add Nova to Discord or Telegram" description: "Invite Nova to your server or group and ask it your first question." product: nova canonical: https://zeroauthoritydao.ai/docs/guides/add-nova related: [guides] tokens: 208 --- # Add Nova to Discord or Telegram Nova will be in your Discord server or Telegram group, answering anyone who tags it. ## Check you are an admin On Discord you need Administrator or Manage Server permission. On Telegram you must be a group admin. [Full guide](https://zeroauthoritydao.ai/docs/nova/get-started.md) ## Invite Nova to Discord Open the invite link, pick your server, approve the permissions and press Authorize. To use roles later, drag Nova's role above the roles it should give. [Full guide](https://zeroauthoritydao.ai/docs/nova/get-started/discord.md) ## Or add Nova to Telegram Use the one-click invite link, pick your group and confirm. It makes Nova an admin with the rights Guardian and other tools need. Added it another way? Promote Nova to admin. [Full guide](https://zeroauthoritydao.ai/docs/nova/get-started/telegram.md) ## Say hello Tag @NovaBot on Discord or @NovaAITheBot on Telegram with a question, or reply to one of its messages. Run `/help` to see what it can do. [Full guide](https://zeroauthoritydao.ai/docs/nova/get-started.md) --- id: guides/connect-an-agent-over-mcp title: "Connect an AI agent to Nova Tools" description: "Give your agent Nova's tools over MCP, with no API key." product: nova canonical: https://zeroauthoritydao.ai/docs/guides/connect-an-agent-over-mcp related: [guides] tokens: 186 --- # Connect an AI agent to Nova Tools Your agent will see Nova's tools with their inputs and prices, and can call the free ones right away. ## Add the MCP server Point your agent's MCP client at `https://nova.zeroauthoritydao.com/mcp` over Streamable HTTP. There is no API key, subscription or sign-up. [Full guide](https://zeroauthoritydao.ai/docs/build/nova-tools-for-agents.md) ## Send your Stacks address Set `AGENT_STACKS_ADDRESS` to your Stacks address. Identified agents get higher rate limits than anonymous callers. [Full guide](https://zeroauthoritydao.ai/docs/build/nova-tools-for-agents.md) ## List the tools Call `tools/list`. Every tool comes back with its input schema and price. You can also browse them on [Nova Tools](https://zeroauthoritydao.ai/tools). [Full guide](https://zeroauthoritydao.ai/docs/nova/tools.md) ## Call a tool Free tools run straight away, within the rate limits. Paid tools answer with HTTP 402 and are paid per call with x402. [Full guide](https://zeroauthoritydao.ai/docs/build/x402.md) --- id: guides/post-a-bounty title: "Post a bounty and pick winners" description: "Fund a task, collect submissions and pay the best ones." product: zadao canonical: https://zeroauthoritydao.ai/docs/guides/post-a-bounty related: [guides] tokens: 276 --- # Post a bounty and pick winners You will have a funded bounty onchain, with the reward locked in a smart contract and paid to the winners you pick. ## Connect your wallet Anyone with a connected and authenticated wallet can create a bounty. [Full guide](https://zeroauthoritydao.ai/docs/profile/access.md) ## Pick or create a campaign Each bounty sits in a campaign (formerly called a hub) for your project. Select yours, or create one with your name and details. [Full guide](https://zeroauthoritydao.ai/docs/work/bounties/create.md) ## Write the brief and set the reward Add a clear title and description, the reward and an end date. Choose how the prize is shared: one winner, several winners splitting it equally, the top 3, or a custom split (up to 10 places). [Full guide](https://zeroauthoritydao.ai/docs/work/bounties/create.md) ## Post it onchain Review the details and post the bounty. The smart contract locks the reward, and everyone can see and enter the bounty. You can also ask Nova in the web chat to draft it and sign the card it opens. [Full guide](https://zeroauthoritydao.ai/docs/nova/zadao-ecosystem.md) ## Select the winners After the end date, open My Bounties, review the entries and press Select Winner. The contract releases the funds to the winners. There is no hard deadline, but pick soon. [Full guide](https://zeroauthoritydao.ai/docs/work/bounties/select-winners.md) --- id: guides/submit-to-a-bounty title: "Find a bounty and submit your work" description: "Pick an open bounty, send your entry before the deadline and get paid if you win." product: zadao canonical: https://zeroauthoritydao.ai/docs/guides/submit-to-a-bounty related: [guides] tokens: 289 --- # Find a bounty and submit your work You will have an entry on an open bounty. If the creator picks you, the smart contract sends your reward to your wallet. ## Connect your wallet Connect your Stacks wallet and sign the message to prove it is yours. If something goes wrong, disconnect, clear your browser cache and try again. [Full guide](https://zeroauthoritydao.ai/docs/profile/access.md) ## Find a bounty that fits Browse open bounties on [Bounties](https://zeroauthoritydao.ai/bounties). You can also ask Nova, for example "Search bounties about smart contracts", or run `/scout` to get picks for your skills by direct message. [Full guide](https://zeroauthoritydao.ai/docs/nova/scout.md) ## Read the brief and submit Check the task, the reward and the end date, then send your entry from the bounty page. Some bounties check your work for you: you connect X and submit your post, or the action is verified onchain. [Full guide](https://zeroauthoritydao.ai/docs/work/bounties.md) ## Submit before the end date Submissions close at 11:59 PM UTC on the end date. After that the contract accepts no new entries. [Full guide](https://zeroauthoritydao.ai/docs/work/bounties/select-winners.md) ## Wait for the winners The creator reviews the entries and selects the winners. The smart contract then sends the reward straight to each winner's wallet. Add your email to your profile to hear when it happens. [Full guide](https://zeroauthoritydao.ai/docs/profile/email-notifications.md) --- id: nova title: "Nova" description: "Nova is your conversational AI assistant for blockchain and your community — no dashboards, just ask in plain English." product: nova canonical: https://zeroauthoritydao.ai/docs/nova related: [nova/get-started, nova/alerts, nova/blockchain-coverage, nova/market-intelligence, nova/memory-and-personalization, nova/news-and-research, nova/smart-alerts, nova/zadao-ecosystem, nova/cab-groups, nova/emblem-vault, nova/agent-observatory, nova/community, nova/plans, nova/tools, nova/scout, nova/spaghettipunk-club] tokens: 851 --- # Nova Nova is an AI assistant on Discord, Telegram and the web widget that answers blockchain and community questions in plain English, with deepest coverage of Bitcoin and Stacks. This page lists what it can do and links each guide. 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. > [!TIP] > Nova is available on **Discord**, **Telegram**, and the **Web Widget**. Mention the bot or reply to any of its messages to start a conversation. *** ## How to Talk to Nova In a server or group, tag Nova or reply to one of its messages: it is **@NovaBot** on Discord (pick it from the @ list so it becomes a real mention) and **@NovaAITheBot** on Telegram. In a direct message no tag is needed. Examples in these docs written as _"@Nova …"_ mean "tag Nova, then say this". 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 Coverage** — Prices, portfolios, transactions, and contracts across Bitcoin/Ordinals, Stacks, EVM chains, Solana, TON, Sui, Aptos, and Hyperliquid - **Market Intelligence** — Portfolio P&L, whale tracking, pool analytics, and cohort/watchlist analysis - **ZADAO Ecosystem** — Bounties, gigs, grants, quests, user profiles, documentation - **Nova Scout** — Bounties, grants and hackathons that fit your skills, sent to your DMs - **Agent Observatory** — Look up, rank, and follow other AI agents on the aibtc network - **News & Research** — Bitcoin Optech, ecosystem updates, SIP proposals, market news, web search - **Smart Alerts** — Custom conditional alerts for prices, whales, contracts, and more - **Governance & Events** — SIP tracking, CAB voting, ecosystem events, governance alerts - **Emblem Vault** — Look up, browse, and create Emblem Vaults — guided and non-custodial - **Community Management** — Anti-scam shield (Guardian), moderator copilot (Pulse), and an engagement suite with XP, leaderboards, trivia & giveaways (Community Games) - **Community Stats** — Engagement stats, contributor leaderboards, member growth, weekly recaps, daily community snacks *** ## Feature Guides Dive deeper into each capability: - [Blockchain Coverage](https://zeroauthoritydao.ai/docs/nova/blockchain-coverage.md) - [Market Intelligence](https://zeroauthoritydao.ai/docs/nova/market-intelligence.md) - [ZADAO Ecosystem](https://zeroauthoritydao.ai/docs/nova/zadao-ecosystem.md) - [Nova Scout](https://zeroauthoritydao.ai/docs/nova/scout.md) - [Agent Observatory](https://zeroauthoritydao.ai/docs/nova/agent-observatory.md) - [Community — Guardian, Pulse & Community Games](https://zeroauthoritydao.ai/docs/nova/community.md) - [Smart Alerts](https://zeroauthoritydao.ai/docs/nova/smart-alerts.md) - [News & Research](https://zeroauthoritydao.ai/docs/nova/news-and-research.md) - [Memory & Personalization](https://zeroauthoritydao.ai/docs/nova/memory-and-personalization.md) - [Emblem Vault](https://zeroauthoritydao.ai/docs/nova/emblem-vault.md) - [SpaghettiPunk Club](https://zeroauthoritydao.ai/docs/nova/spaghettipunk-club.md) - [Nova for CAB Groups & Governance](https://zeroauthoritydao.ai/docs/nova/cab-groups.md) *** ## 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](https://zeroauthoritydao.ai/docs/nova/plans.md). --- id: about/team title: "Meet the core team" description: "Core Contributors Day-to-Day Responsibilities" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/team related: [about] tokens: 855 --- # Meet the core team Lists Zero Authority's core team (Zero, Hodlstx, Haddy and the protocol developers) with their responsibilities, and the DAO members who contribute content, development, grants and video. **Zero Authority Core Contributors** ![](https://zeroauthoritydao.ai/docs/img/85efd61abbd1.webp) 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: * **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, Mariaverse, Gary, 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. --- id: guides/get-paid-for-a-gig title: "Get paid for a gig" description: "Accept a gig offer, deliver the work and receive the funds held in the contract." product: zadao canonical: https://zeroauthoritydao.ai/docs/guides/get-paid-for-a-gig related: [guides] tokens: 272 --- # Get paid for a gig You will have accepted a gig onchain, delivered your work and had the client release your payment from the smart contract. ## Set up your profile Connect your wallet and fill in your profile with your skills, experience and pay rates, so clients can find you and send you offers. Add an email to get told when an offer arrives. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs.md) ## Accept the offer Open Received gigs, review the offer and press Accept (or Decline). Then accept the gig onchain with your wallet. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs/v2.md) ## Submit your deliverables When the work is done, go back to Received gigs and submit your deliverables: a link to the work and a comment. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs/v2.md) ## Get paid The client reviews your submission and confirms the release of funds from the smart contract, then rates the gig onchain. On a milestone gig, each milestone is paid when the client marks it complete. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs/milestones.md) ## If the client goes quiet On a milestone gig, if the end date passes and the client has not acted within 5 days, you can trigger the redemption yourself and receive the remaining funds for your completed work. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs/milestones.md) --- id: guides/hire-with-a-gig title: "Hire a creator with a gig" description: "Send a gig offer, lock the payment onchain and release it when the work is done." product: zadao canonical: https://zeroauthoritydao.ai/docs/guides/hire-with-a-gig related: [guides] tokens: 226 --- # Hire a creator with a gig You will have hired a creator with funds held in a smart contract, and paid them once you approved the work. ## Find a creator Browse [Creators](https://zeroauthoritydao.ai/creators), or ask Nova, for example "Search for users with Clarity experience". Connect your wallet before you make an offer. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs/offer-and-accept.md) ## Send an offer On the creator's profile, press Offer and choose Fixed or Milestone. A milestone gig can have up to 5 milestones and an end date. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs/milestones.md) ## Create the gig onchain Write the gig details, review them and create the gig onchain. The payment is held in the smart contract until you release it. The creator then accepts the gig onchain. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs/v2.md) ## Review and release the funds When the creator submits deliverables, open Sent gigs and review them. Confirm the release of funds with a comment, then rate the gig onchain. On a milestone gig, mark each milestone complete to pay for it. [Full guide](https://zeroauthoritydao.ai/docs/work/gigs/v2.md) --- id: guides/pay-per-call-with-x402 title: "Pay per call with x402" description: "Pay for a Nova tool call inline, in STX, sBTC or USDCx on Stacks." product: nova canonical: https://zeroauthoritydao.ai/docs/guides/pay-per-call-with-x402 related: [guides] tokens: 191 --- # Pay per call with x402 Your code will pay for a paid Nova tool in the same request, and only be charged if the tool runs. ## Call the tool Send a POST to the tool's `/api/tools//run` endpoint with its input. A paid tool answers with HTTP 402 and a `payment-required` header listing the accepted payments. [Full guide](https://zeroauthoritydao.ai/docs/build/x402.md) ## Pick a token and sign Choose STX, sBTC or USDCx from the options. Build a sponsored Stacks transaction with zero fee, so the payer pays no gas, and sign it. [Full guide](https://zeroauthoritydao.ai/docs/build/x402.md) ## Retry with the payment Send the same request again with a `payment-signature` header holding the signed payment. [Full guide](https://zeroauthoritydao.ai/docs/build/x402.md) ## Read the result You get the tool output and a receipt in the `payment-response` header. Payment settles only after the tool succeeds, so a failed call costs nothing. [Full guide](https://zeroauthoritydao.ai/docs/build/x402.md) --- id: guides/protect-your-community title: "Protect your community from scams and spam" description: "Turn on Guardian and set language rules by talking to Nova." product: nova canonical: https://zeroauthoritydao.ai/docs/guides/protect-your-community related: [guides] tokens: 298 --- # Protect your community from scams and spam Nova will screen every message for scams and repeat spam, and keep each channel in the languages you choose. ## Give Nova the right permissions Nova needs to delete messages and mute or ban members. On Discord, use the current invite link and keep Nova's role above the members it moderates. On Telegram, make Nova an admin with delete and ban rights. [Full guide](https://zeroauthoritydao.ai/docs/nova/community/guardian.md) ## Turn on Guardian As an admin, in your server or group, say "@Nova turn on Guardian". On Discord, also set who reviews flags: "set the mod role to @Moderators". To watch first, say "activate Guardian without auto-moderation". [Full guide](https://zeroauthoritydao.ai/docs/nova/community/guardian.md) ## Choose where flags go Say "send Guardian flags to #mod-review". Mods can undo any wrong call with the Revert button on the report. [Full guide](https://zeroauthoritydao.ai/docs/nova/community/guardian.md) ## Set channel languages Say "@Nova make this channel English-only", or set one rule for the whole server. Nova starts by warning only and points people to a channel that speaks their language. [Full guide](https://zeroauthoritydao.ai/docs/nova/community/language-moderation.md) ## Check and adjust Ask "is Guardian on?" or "what language rules do we have?". You can also change everything on the Community Settings dashboard. [Full guide](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md) --- id: work title: "Work and earn" description: "Bounties, gigs and quests: how to post work, do work and get paid on Zero Authority." product: zadao canonical: https://zeroauthoritydao.ai/docs/work related: [work/bounties, work/quests, work/gigs] tokens: 57 --- # Work and earn Projects post bounties, hire creators with gigs and set quests. Creators do the work, get paid from escrow on Stacks and build reputation. Everything on Zero Authority that pays: bounties for open tasks, gigs for hiring one creator, and quests for short tasks that pay in reputation. Live listings are on [Bounties](https://zeroauthoritydao.ai/bounties), [Work](https://zeroauthoritydao.ai/work) and [Quests](https://zeroauthoritydao.ai/quests). --- id: about/contribute title: "How to contribute to the DAO" description: "Learn how to contribute to a Decentralized Autonomous Organization (DAO) with this page's comprehensive list, including voting, submitting proposals, and providing expertise." product: zadao canonical: https://zeroauthoritydao.ai/docs/about/contribute related: [about] tokens: 540 --- # How to contribute to the DAO Lists ways to contribute to Zero Authority DAO on Stacks: voting and submitting proposals, joining discussions, offering expertise, spreading the word and contributing to open source. **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: * 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. 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. For how contributions are rewarded, see [How to reward contributions](https://zeroauthoritydao.ai/docs/about/rewarding-contributions.md). --- id: guides/join-a-quest title: "Join a quest" description: "Find an active quest, complete its activities and earn REP." product: zadao canonical: https://zeroauthoritydao.ai/docs/guides/join-a-quest related: [guides] tokens: 216 --- # Join a quest You will have joined a quest and completed its activities. Your participation is recorded onchain and builds your reputation. ## Connect your wallet Anyone with a connected and authenticated wallet can join and complete quests. Your wallet holds your actions, rewards and reputation. [Full guide](https://zeroauthoritydao.ai/docs/work/quests/get-started.md) ## Find an active quest Browse [Quests](https://zeroauthoritydao.ai/quests), or ask Nova "What quests are active right now?". You will see each quest's deadline, REP rewards, any NFT reward and the activities to complete. [Full guide](https://zeroauthoritydao.ai/docs/nova/zadao-ecosystem.md) ## Join and complete the activities Join the quest and work through its activities before the deadline. Each activity is one thing for you to do. [Full guide](https://zeroauthoritydao.ai/docs/work/quests/screenshots.md) ## Keep contributing Quests are not contests with a single winner. Rewards follow steady participation and reputation built across quests, and they are sent onchain to the selected wallets. [Full guide](https://zeroauthoritydao.ai/docs/work/quests/how-to-win.md) --- id: guides/read-zero-authority-data title: "Read Zero Authority data with the API" description: "Get bounties, gigs, creators, quests and governance data over REST." product: zadao canonical: https://zeroauthoritydao.ai/docs/guides/read-zero-authority-data related: [guides] tokens: 175 --- # Read Zero Authority data with the API You will know where the Zero Authority API lives and have the spec to call it from your own code. ## Open the API reference Zero Authority's public data, including bounties, gigs, creators, quests and governance, is open over REST. Start with the reference at zeroauthoritydao.com/api-docs. [Full guide](https://zeroauthoritydao.ai/docs/build.md) ## Get the OpenAPI spec Download the spec from zeroauthoritydao.com/openapi-spec.yaml to see every endpoint and generate a client if you like. [Full guide](https://zeroauthoritydao.ai/docs/build.md) ## Call the API Send requests to the base URL `https://zeroauthoritydao.com/api`, using the paths from the reference. [Full guide](https://zeroauthoritydao.ai/docs/build.md) ## Or ask Nova To look things up without code, ask Nova, for example "Active grants on ZADAO" or "Any design gigs open?". [Full guide](https://zeroauthoritydao.ai/docs/nova/zadao-ecosystem.md) --- id: guides/reward-contributors title: "Reward contributors with an NFT or badge" description: "Give an NFT as a bounty prize and let participants mint a badge." product: zadao canonical: https://zeroauthoritydao.ai/docs/guides/reward-contributors related: [guides] tokens: 202 --- # Reward contributors with an NFT or badge You will have a bounty that pays its winner an NFT, and a landing page where participants can mint a badge. ## Start a single-winner bounty Go to Bounties and press Create Bounty. Add the title, description and requirements, and select Single Winner as the type. [Full guide](https://zeroauthoritydao.ai/docs/work/bounties/nft-rewards.md) ## Choose the NFT reward At the bottom of the reward section, select NFT Reward and choose the NFT to give. Then set the end date. [Full guide](https://zeroauthoritydao.ai/docs/work/bounties/nft-rewards.md) ## Add a badge Add a landing page to the bounty with a heading, subheading and description. Upload a custom badge, or the default images are used. Publish it so participants can mint the badge. [Full guide](https://zeroauthoritydao.ai/docs/work/bounties/mint-a-badge.md) ## Select the winner When the deadline passes, review the submissions and press Select Winner. The NFT goes to the winner automatically. [Full guide](https://zeroauthoritydao.ai/docs/work/bounties/nft-rewards.md) --- id: guides/upgrade-to-community-pro title: "Upgrade to Community PRO" description: "Pay for the community plan and switch it on in your server or group." product: nova canonical: https://zeroauthoritydao.ai/docs/guides/upgrade-to-community-pro related: [guides] tokens: 228 --- # Upgrade to Community PRO Your server or group will be on Community PRO, with higher limits and PRO features ready to turn on. ## Compare the plans Community PRO is a plan for a whole server or group, separate from personal Premium. One plan covers one Discord server and one Telegram group. For the current price, see [Plans](https://zeroauthoritydao.ai/plans). [Full guide](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md) ## Pay with your Stacks wallet Choose Community PRO, pick monthly or yearly, connect your Stacks wallet and pay. No card or account is needed. [Full guide](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md) ## Activate it in your community You get a single-use activation code that expires after 30 minutes. As an admin, post `@NovaBot activate YOUR-CODE` on Discord or `@NovaAITheBot activate YOUR-CODE` on Telegram. [Full guide](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md) ## Turn on the features you want Paying does not switch features on. Ask Nova, for example "@Nova enable Guardian", or use the Community Settings dashboard. [Full guide](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md) --- id: profile title: "Profile and reputation" description: "Signing in, your profile, email notifications and how reputation is earned and recorded on-chain." product: zadao canonical: https://zeroauthoritydao.ai/docs/profile related: [profile/reputation, profile/email-notifications, profile/reputation-framework, profile/access] tokens: 52 --- # Profile and reputation Your profile carries the reputation you earn from finished work. These pages explain how access works and how reputation is recorded on-chain. Your work on Zero Authority builds a record others can check: REP, badges and an Onchain Score. Find creators by their record on [Creators](https://zeroauthoritydao.ai/creators) and the top earners on the [Leaderboard](https://zeroauthoritydao.ai/leaderboard). --- id: about/rewarding-contributions title: "How to reward contributions" description: "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." product: zadao canonical: https://zeroauthoritydao.ai/docs/about/rewarding-contributions related: [about] tokens: 481 --- # How to reward contributions Lists how Zero Authority DAO rewards contributions: the $Zero token, reputation points that add governance influence, bounties, non-financial incentives, tokens with lockup periods and token burns. 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. The ways to contribute (voting, proposals, discussions, expertise, spreading the word, open source) are listed in [How to contribute to the DAO](https://zeroauthoritydao.ai/docs/about/contribute.md). The DAO is built on open source technology. Common ways to reward contributions in the DAO: * 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. --- id: govern title: "Govern and fund" description: "Stacks Improvement Proposals and community grants: follow governance and apply for funding." product: zadao canonical: https://zeroauthoritydao.ai/docs/govern related: [govern/grants, govern/sips] tokens: 37 --- # Govern and fund Follow Stacks Improvement Proposals from idea to activation, vote if you are in a CAB, and apply for community-led grants. How the Stacks community changes the network and funds its own work. Live proposals are on [STXGOV](https://zeroauthoritydao.ai/stxgov) and grants on [DeGrants](https://zeroauthoritydao.ai/degrants). --- id: about/solutions title: "Zero Authority Solutions" description: "Overview of Zero Authority DAO" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/solutions related: [about, about/solutions/nova] tokens: 941 --- # Zero Authority Solutions Describes the Zero Authority DAO Gig Marketplace, launched November 25, 2023 with Hiro and Xverse login, and its solutions for Web3 users: gigs, bounties and endorsements, inspired by the pseudonymous economy. **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. [Please give us feedback]() **Pseudonymous Economy:** Users build trust and reputation from their actions and contributions rather than traditional identifiers. See [The Pseudonymous Economy](https://zeroauthoritydao.ai/docs/about.md#the-pseudonymous-economy). **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](https://linktr.ee/zeroauthoritydao). --- id: build title: "Build" description: "APIs, MCP and payments for developers and AI agents building on Zero Authority and Nova." product: both canonical: https://zeroauthoritydao.ai/docs/build related: [build/nova-tools-for-agents, build/x402] tokens: 346 --- # Build Read Zero Authority data over its REST API, give an AI agent Nova's tools over MCP or REST, and pay per call with x402. No API key needed for Nova Tools. ## Zero Authority API Zero Authority's public data (bounties, gigs, creators, quests, governance) is available over REST. - Reference: [zeroauthoritydao.com/api-docs](https://zeroauthoritydao.com/api-docs) - OpenAPI spec: [zeroauthoritydao.com/openapi-spec.yaml](https://zeroauthoritydao.com/openapi-spec.yaml) - Base URL: `https://zeroauthoritydao.com/api` ## Nova Tools The tools Nova uses in chat are open to people and agents. Free tools are rate-limited; paid tools are paid per call with x402 in STX, sBTC or USDCx on Stacks. No API keys, no subscriptions, no registration. - MCP server: `https://nova.zeroauthoritydao.com/mcp` - Agent manifest: [nova.zeroauthoritydao.com/.well-known/agent.json](https://nova.zeroauthoritydao.com/.well-known/agent.json) - OpenAPI: [nova.zeroauthoritydao.com/api/tools/openapi.json](https://nova.zeroauthoritydao.com/api/tools/openapi.json) - Browse and try them: [Nova Tools](https://zeroauthoritydao.ai/tools) Start with [Using Nova Tools with AI agents](https://zeroauthoritydao.ai/docs/build/nova-tools-for-agents.md) and the [x402 payment guide](https://zeroauthoritydao.ai/docs/build/x402.md). ## These docs, for agents - Every page as markdown: add `.md` to its URL, or send `Accept: text/markdown` - Index of all pages: [/llms.txt](https://zeroauthoritydao.ai/llms.txt), every page in one file: [/llms-full.txt](https://zeroauthoritydao.ai/llms-full.txt) - Machine-readable index: [/docs/index.json](https://zeroauthoritydao.ai/docs/index.json.md) - Search: `GET /api/docs/search?q=your+question` --- id: about title: "About Zero Authority" description: "Who Zero Authority DAO is, what it believes and where it is going." product: zadao canonical: https://zeroauthoritydao.ai/docs/about related: [about/vision-and-values, about/team, about/contribute, about/rewarding-contributions, about/solutions, about/stakeholder-updates, about/roadmap, about/strategic-pillars, about/plan-h2-2026] tokens: 438 --- # About Zero Authority Introduces Zero Authority as a DAO for governing, funding and launching Web3 projects, explains the pseudonymous economy, and lists the team's X accounts and official linktree. 🌐 Trustless layer for reputation, gigs, bounties & endorsements! Join us! 🎉 Here you'll find everything you need to know about the DAO. ![](https://zeroauthoritydao.ai/docs/img/4472e854c37a.webp) ## 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. Please message us on discord or twitter anytime. Zero (XYZERO) James (HODLSTX) Haddy Find us on verified channel --- id: profile/reputation title: "Reputation Onchain" description: "Overview of peer-to-peer creators in a decentralized age" product: zadao canonical: https://zeroauthoritydao.ai/docs/profile/reputation related: [profile] tokens: 540 --- # Reputation Onchain Trajan lets organizations post opportunities and find pseudonymous Bitcoin talent, and lets individuals build reputation through endorsements. Includes an FAQ on wallets, BNS names and fees. **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. --- id: changelog title: "Changelog" description: "What changed on Zero Authority and Nova, newest first." product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog related: [changelog/boost-a-bounty-feature-guide, changelog/new-zero-authority-updates, changelog/new-zero-authority-updates-1, changelog/new-bounty-features, changelog/stackingdao-treasure-hunt, changelog/zest-treasure-hunt, changelog/platform-updates, changelog/bitcoin-staking-sip, changelog/quests-are-live, changelog/new-homepage, changelog/sip-tracker-on-zero-authority, changelog/q4-2025-product-updates, changelog/degrants-is-now-live, changelog/keep-calm-and-stay-based, changelog/new-features-live, changelog/bug-reported, changelog/bounty-and-badges-are-live, changelog/zero-authority-nova-is-live, changelog/zero-authority-api-is-live, changelog/stacks-townhall, changelog/zero-authority-security-is-live, changelog/leocoin-feline-fridays, changelog/utility-for-decentralized-assets, changelog/stack4impact, changelog/xverse-dapp-browser, changelog/multi-winner-bounties-are-live, changelog/zero-authority-v2-is-live, changelog/zero-authority-v2-on-testnet, changelog/zero-authority-v2, changelog/mfa-for-all-access-points, changelog/v1-0-0-bounty-onchain, changelog/v1-5-2-gig-mkpl-update, changelog/v1-5-1-gig-mkpl-update, changelog/v1-5-0-gig-mkpl-update, changelog/v1-4-0-gig-mkpl-update, changelog/v1-3-1-gig-mkpl-bug-fix, changelog/v1-3-0-gig-mkpl, changelog/v1-2-0-gig-mkpl-update, changelog/v1-1-0-gig-mkpl-update, changelog/v1-0-2-gig-mkpl-bug-fix, changelog/v1-0-1-gig-mkpl-update, changelog/v1-0-0-gig-mkpl-on-mainnet, changelog/testnet-1-4-update, changelog/testnet-1-3-update, changelog/testnet-1-2-update, changelog/testnet-1-1-update, changelog/testnet-1-0-update, changelog/target-launch-date] tokens: 19 --- # Changelog What changed on Zero Authority and Nova, newest first. Release notes and announcements for Zero Authority and Nova, newest first. --- id: profile/email-notifications title: "Email Notification" description: "Overview email notifications for activities" product: zadao canonical: https://zeroauthoritydao.ai/docs/profile/email-notifications related: [profile] tokens: 697 --- # Email Notification Add an email to your profile to get emails about gigs: new requests, accepted or declined offers and satisfaction votes. 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. --- id: about/solutions/nova title: "Nova AI Bots" description: "Introducing Zero Authority AI & Bots" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/solutions/nova related: [about/solutions] tokens: 250 --- # Nova AI Bots Lists the Nova community features and Zero Authority bots from Nova's introduction (in-chat swaps, reputation bots, Gig, Bounty and Reputation Bots) and points to the Nova docs for current features and plans. **NOVA** is Zero Authority's AI-powered assistant for Web3 communities on Telegram and Discord. What Nova does today, how to add it and its plans are in the [Nova docs](https://zeroauthoritydao.ai/docs/nova.md) and [Nova plans](https://zeroauthoritydao.ai/docs/nova/plans.md). This page adds the Zero Authority bots and the community features described when Nova was introduced: * **In-Chat Crypto Swaps** – Buy and sell crypto directly within Telegram or Discord. * **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. * **AI Blocker** (Premium) – Filter spam in 1 Telegram + 1 Discord channel. #### 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. --- id: legal title: "Legal" description: "Terms of service and privacy policies for Zero Authority and Nova." product: zadao canonical: https://zeroauthoritydao.ai/docs/legal related: [legal/nova-privacy, legal/nova-terms, legal/terms, legal/privacy] tokens: 183 --- # Legal Explains that using the Zero Authority D/B/A Trajan platform means accepting its Terms of Service and Privacy Policy, effective January 1, 2026, and links both. By accessing or using the Zero Authority D/B/A Trajan platform and website (), you agree to our Terms of Service and Privacy Policy, which govern your use of the platform, including data collection, processing, storage, and on-chain interactions. Your continued use constitutes acceptance of these terms, including provisions related to decentralized systems, blockchain data, user rights, platform governance, liability limitations, and data protection practices, all of which are designed to ensure lawful use, platform integrity, user privacy, and responsible participation within the Zero Authority ecosystem. - [Terms of Service](https://zeroauthoritydao.ai/docs/legal/terms.md) - [Privacy Policy](https://zeroauthoritydao.ai/docs/legal/privacy.md) --- id: guides title: "Guides" description: "Step-by-step guides for the most common tasks." product: both canonical: https://zeroauthoritydao.ai/docs/guides related: [guides/add-nova, guides/connect-an-agent-over-mcp, guides/post-a-bounty, guides/submit-to-a-bounty, guides/get-paid-for-a-gig, guides/hire-with-a-gig, guides/pay-per-call-with-x402, guides/protect-your-community, guides/join-a-quest, guides/read-zero-authority-data, guides/reward-contributors, guides/upgrade-to-community-pro] tokens: 24 --- # Guides Step-by-step guides for the most common tasks. Short walkthroughs for one task each, with links to the full pages when you need more detail. --- id: profile/reputation-framework title: "Standard Reputation Framework" description: "Reputation Framework User Guide V.0.1 first draft. Reputation and NFT Minting for Reputation Badges." product: zadao canonical: https://zeroauthoritydao.ai/docs/profile/reputation-framework related: [profile, profile/reputation-framework/15-common-categories, profile/reputation-framework/clarity-contract, profile/reputation-framework/json-metadata, profile/reputation-framework/a-new-standard-for-trust-in-web3] tokens: 1579 --- # Standard Reputation Framework A draft standard for reputation on apps and websites: each reputation event mints an NFT. Defines the attributes, the minting process and how to implement badges with Clarity and JSON. **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](https://zeroauthoritydao.ai/docs/img/0fd7ab12e4f0.webp) *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. ### Implementation guide Common criteria to build reputation badges are in [15 Common Categories](https://zeroauthoritydao.ai/docs/profile/reputation-framework/15-common-categories.md). To create a **Reputation (REP) badge**, you manage onchain logic with Clarity and define metadata with JSON. Clarity handles issuing the badge, and JSON defines its visual and contextual properties. * [Clarity Contract](https://zeroauthoritydao.ai/docs/profile/reputation-framework/clarity-contract.md): the code to deploy on the blockchain. It allows authorized users to issue badges to multiple recipients at once. * [JSON Metadata](https://zeroauthoritydao.ai/docs/profile/reputation-framework/json-metadata.md): the metadata file to create for standard deployment, with the badge's name, description, image and criteria. A minimal metadata example: ```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"}] } ``` --- id: profile/reputation-framework/15-common-categories title: "15 Common Categories" description: "To Build Reputation Onchain" product: zadao canonical: https://zeroauthoritydao.ai/docs/profile/reputation-framework/15-common-categories related: [profile/reputation-framework] tokens: 1021 --- # 15 Common Categories Fifteen common categories of reputation events, such as community engagement, content creation and skill verification, each with the attributes to record. Fifteen common categories of reputation events, with the attributes to record for each, for use with the [Standard Reputation Framework](https://zeroauthoritydao.ai/docs/profile/reputation-framework.md). *** ### 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. --- id: profile/reputation-framework/clarity-contract title: "Clarity Contract" description: "Allowing authorized users to issue badges to multiple recipients" product: zadao canonical: https://zeroauthoritydao.ai/docs/profile/reputation-framework/clarity-contract related: [profile/reputation-framework] tokens: 1006 --- # Clarity Contract A Clarity contract template that mints non-transferable endorsement NFTs (reputation badges) in batches, with the full code and a breakdown. 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! --- id: profile/reputation-framework/json-metadata title: "JSON Metadata" description: "Defines the badge's attributes, such as its name, description, image, and criteria" product: zadao canonical: https://zeroauthoritydao.ai/docs/profile/reputation-framework/json-metadata related: [profile/reputation-framework] tokens: 221 --- # JSON Metadata The JSON metadata template for a reputation badge: name, description, IPFS image and attributes such as user_id and engagement type. 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! --- id: profile/reputation-framework/a-new-standard-for-trust-in-web3 title: "A New Standard for Trust in Web3" description: "Zero Authority, the EigenTrust Algorithm & the Future of Reputation" product: zadao canonical: https://zeroauthoritydao.ai/docs/profile/reputation-framework/a-new-standard-for-trust-in-web3 related: [profile/reputation-framework] tokens: 1163 --- # A New Standard for Trust in Web3 Why Zero Authority combines its Standard Reputation Framework with the EigenTrust algorithm to compute trust across wallets from local trust scores. ![](https://zeroauthoritydao.ai/docs/img/e807b49e4f0b.webp) 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 `i` maintains **local trust scores** `s_ij` for others they’ve interacted with. To normalize for fairness: ``` c_ij = s_ij / Σ_k s_ik ``` Where: * `c_ij` = normalized trust Alice has in Bob * The sum of all `c_ij` values for a given user equals 1 Then, using **power iteration**, we compute the **global trust vector** `t` such that: ``` t = Cᵀ t ``` Where: * `C` is the matrix of all normalized local scores * `t` 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://zeroauthoritydao.ai/docs/profile/reputation-framework.md) 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. --- id: profile/access title: "Access to the Platform" description: "To ensure you get access to features and solutions" product: zadao canonical: https://zeroauthoritydao.ai/docs/profile/access related: [profile] tokens: 329 --- # Access to the Platform Sign in by connecting your wallet and signing a transaction, then edit your profile. Covers troubleshooting and VPN options for regions where the site is blocked. ## Procedure Step 1 - Connect Wallet. Step 2 - Sign Transaction. ![](https://zeroauthoritydao.ai/docs/img/5860e51ae198.webp) **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 --- id: changelog/zero-authority-v2-on-testnet title: "Set up your profile on Zero Authority V2 testnet" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/zero-authority-v2-on-testnet related: [changelog] tokens: 243 --- # Set up your profile on Zero Authority V2 testnet Steps to switch a Leather or Xverse wallet to testnet and set up a profile on Zero Authority V2 at Chronos Agora. 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 🎉 ![](https://zeroauthoritydao.ai/docs/img/29fc875581b2.webp) You're all set! 🎉 --- id: changelog/v1-5-1-gig-mkpl-update title: "Gig Marketplace v1.5.1" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-5-1-gig-mkpl-update related: [changelog] tokens: 451 --- # Gig Marketplace v1.5.1 Gig Marketplace v1.5.1 adds payments in community tokens such as $WELSH, $LEO and $ALEX, and improves the web and mobile apps. ![v1.5.1](https://zeroauthoritydao.ai/docs/img/20da876406b3.webp) *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! [Release notes on GitHub](https://github.com/zeroauthority-dao/overview/releases/tag/mkpl-1.5.1) --- id: changelog/v1-5-0-gig-mkpl-update title: "Gig Marketplace v1.5.0" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-5-0-gig-mkpl-update related: [changelog] tokens: 331 --- # Gig Marketplace v1.5.0 Gig Marketplace v1.5.0 redesigns the interface around Trajan reputation, with new landing, community and About pages and milestone UI fixes. ![v1.5.0](https://zeroauthoritydao.ai/docs/img/dec713b062b8.webp) *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. [Release notes on GitHub](https://github.com/zeroauthority-dao/Overview/releases/tag/mkpl-1.5.0) --- id: changelog/v1-4-0-gig-mkpl-update title: "Gig Marketplace v1.4.0" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-4-0-gig-mkpl-update related: [changelog] tokens: 192 --- # Gig Marketplace v1.4.0 Gig Marketplace v1.4.0 allows milestones without start and end dates, adds a back button on gig pages and fixes the milestone gig ID. **\[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. --- id: changelog/v1-3-1-gig-mkpl-bug-fix title: "Gig Marketplace v1.3.1 bug fix" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-3-1-gig-mkpl-bug-fix related: [changelog] tokens: 199 --- # Gig Marketplace v1.3.1 bug fix Gig Marketplace v1.3.1 fixes selecting services, updating profiles and finding users by service on the landing page. ![v.1.3.1 Gig Mkpl Bug Fix](https://zeroauthoritydao.ai/docs/img/07dab342a3b0.webp) *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]. [Release Notes]() [Decentralized Reputation Gig Mkpl]() [Decentralized Reputation Social Verification]() --- id: changelog/v1-3-0-gig-mkpl title: "Gig Marketplace v1.3.0: comments on gigs" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-3-0-gig-mkpl related: [changelog] tokens: 293 --- # Gig Marketplace v1.3.0: comments on gigs Gig Marketplace v1.3.0 lets users post comments on gigs to ask questions and discuss project details. ![v1.3.0](https://zeroauthoritydao.ai/docs/img/cb44e342efab.webp) *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. [Release Notes]() --- id: changelog/v1-2-0-gig-mkpl-update title: "Gig Marketplace v1.2.0" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-2-0-gig-mkpl-update related: [changelog] tokens: 435 --- # Gig Marketplace v1.2.0 Gig Marketplace v1.2.0 improves gig status tracking and decision screens, automates deploys, and drops required profile fields. ![v1.2.0](https://zeroauthoritydao.ai/docs/img/d54581a6c24f.webp) *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. [Release Notes]() [Decentralized Reputation Gig Mkpl]() [Decentralized Reputation Social Verification]() --- id: changelog/v1-1-0-gig-mkpl-update title: "Gig Marketplace v1.1.0" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-1-0-gig-mkpl-update related: [changelog] tokens: 251 --- # Gig Marketplace v1.1.0 Gig Marketplace v1.1.0 adds an upgraded gig page, gig status tracking, a gigs ticker and blog posts, and fixes hover and roadmap bugs. ![v1.1.0](https://zeroauthoritydao.ai/docs/img/37b5d590b025.webp) *v1.1.0* ## Release notes Gig Marketplace v1.1.0 Latest [release summary]() 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. 🚀 --- id: changelog/v1-0-2-gig-mkpl-bug-fix title: "Gig Marketplace v1.0.2 bug fix" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-0-2-gig-mkpl-bug-fix related: [changelog] tokens: 126 --- # Gig Marketplace v1.0.2 bug fix Gig Marketplace v1.0.2 fixes selecting a service and signing in when connecting a wallet. ![](https://zeroauthoritydao.ai/docs/img/f588f1ec69ef.webp) 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 [Release notes on GitHub](https://github.com/zeroauthority-dao/Overview/releases/tag/mkpl-1.0.2) [mainnet](https://zeroauthority.xyz/) [testnet]() --- id: changelog/v1-0-1-gig-mkpl-update title: "Gig Marketplace v1.0.1" product: zadao canonical: https://zeroauthoritydao.ai/docs/changelog/v1-0-1-gig-mkpl-update related: [changelog] tokens: 107 --- # Gig Marketplace v1.0.1 Gig Marketplace v1.0.1 adds profile URLs by wallet, a new notification UI, a feedback button, a roadmap and a tutorial, and fixes navigation. ![](https://zeroauthoritydao.ai/docs/img/098fa9921a2f.webp) - 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 🐞 [Release notes on GitHub](https://github.com/zeroauthority-dao/Overview/releases/tag/mkpl-1.0.1) --- id: nova/get-started title: "Getting Started" description: "Get Nova up and running in your Discord server or Telegram group in under 2 minutes." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/get-started related: [nova, nova/get-started/discord, nova/get-started/telegram] tokens: 634 --- # Getting Started Add Nova to Discord or Telegram, then mention it, reply to it or DM it to ask questions. Lists every slash command and where to go next. - [Adding Nova to Discord](https://zeroauthoritydao.ai/docs/nova/get-started/discord.md) - [Adding Nova to Telegram](https://zeroauthoritydao.ai/docs/nova/get-started/telegram.md) *** ## 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 > [!TIP] > Nova works out of the box — no configuration required. Just add it and start asking questions. When you add it, Nova posts a short welcome for admins with the first steps. *** ## Available Commands Run `/help` (or `/start` on Telegram) to see this list in the app, with example questions you can tap to try. | Group | Command | What it does | | --- | --- | --- | | **Ask Nova** | `/help` | What Nova can do, with tappable example prompts | | | `/prompts` | Browse and run curated prompts | | | `/stacks` | Explore the Stacks ecosystem | | **Alerts** | `/nova` | Token swap, NFT and wallet-tracker alerts | | | `/scout` | Bounties, grants and hackathons picked for you | | **Community admin** | `/gm` | Community GM greeting | | | `/roles` | [Community Roles: token-, NFT- and level-gated roles](https://zeroauthoritydao.ai/docs/nova/community/roles.md) (Discord only) | | **ZADAO** | `/zadao` | Zero Authority DAO community and platform stats | | | `/bounty` | Bounties and bounty notifications | | | `/quest` | Quests and quest notifications | | | `/gigs` | Gigs and gig notifications | | | `/campaigns` | Campaigns and campaign notifications | | **PRO** | `/premium` | Manage your personal PRO subscription | | **More** | `/fortune`, `/roll` | Fortune cookie and dice (Discord only) | | | `/cancel` | Reset any ongoing command (Telegram only) | Guardian, Harbor, Pulse, Games, Language Moderation and Snacks have no command: an admin or moderator turns them on by asking Nova in the server or group, for example _"@Nova turn on Guardian"_. See [Community](https://zeroauthoritydao.ai/docs/nova/community.md). *** ## Next Steps * **Set up alerts** — See the [Alerts Setup Guides](https://zeroauthoritydao.ai/docs/nova/alerts.md) to start tracking tokens, NFTs, and wallets * **Chat with Nova AI** — Learn what Nova can do in the [Nova AI Agent](https://zeroauthoritydao.ai/docs/nova.md) guide * **Run your community** — Turn on moderation, welcomes and engagement tools in [Community](https://zeroauthoritydao.ai/docs/nova/community.md) * **Go Premium** — Unlock higher limits and exclusive features with [Premium](https://zeroauthoritydao.ai/docs/nova/plans.md) --- id: nova/get-started/discord title: "Adding Nova to Discord" description: "Add Nova to your Discord server in a few clicks." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/get-started/discord related: [nova/get-started] tokens: 618 --- # Adding Nova to Discord Invite Nova to your Discord server, approve its permissions and place its role in the hierarchy. Needs Administrator or Manage Server. > [!WARNING] > You must have **Administrator** or **Manage Server** permissions on the Discord server to add a bot. *** ## 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 | > [!NOTE] > The last three are only ever used by [Nova Guardian](https://zeroauthoritydao.ai/docs/nova/community/guardian.md), 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. 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 > [!NOTE] > 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. *** ## You're All Set Nova is now active in your server. See the [Quick Start](https://zeroauthoritydao.ai/docs/nova/get-started.md#quick-start) for how to talk to Nova and the available commands. --- id: nova/get-started/telegram title: "Adding Nova to Telegram" description: "Add Nova to your Telegram group or start a private chat." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/get-started/telegram related: [nova/get-started] tokens: 386 --- # Adding Nova to Telegram Start a private chat with @NovaAITheBot or add it to a Telegram group, ideally as admin with the one-click invite so Guardian, Language Moderation and Harbor can act. ## 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"** > [!WARNING] > You must be a **group admin** to add bots to a Telegram group. *** ## 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 to a group and make it an admin in one step: [**Add Nova to Telegram Group**](https://t.me/NovaAITheBot?startgroup=true&admin=delete_messages+restrict_members) Select your group from the list and confirm. Telegram asks for two admin rights, **Delete messages** and **Ban users**, which Guardian, Language Moderation and Harbor use. You can untick either one. The same button is on `/start` in a private chat with Nova. > [!NOTE] > Added Nova another way? Promote it to admin in the group settings so it can see every message and member join. *** ## You're All Set Nova is now active in your group. See the [Quick Start](https://zeroauthoritydao.ai/docs/nova/get-started.md#quick-start) for how to talk to Nova and the available commands. --- id: nova/alerts title: "Alerts Setup Guides" description: "Step-by-step guides to set up Nova's alerts on Discord and Telegram." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts related: [nova, nova/alerts/token-swaps, nova/alerts/nft-activity, nova/alerts/wallet-tracker, nova/alerts/premium, nova/alerts/zadao, nova/alerts/events-and-governance, nova/alerts/history, nova/alerts/zadao-stats, nova/alerts/manage] tokens: 367 --- # Alerts Setup Guides Index of Nova's alert setup guides: slash-command wizards for token, NFT, wallet and Premium alerts, conversational alerts for grants, events and governance, and pages for managing and auditing your alerts. 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](https://zeroauthoritydao.ai/docs/nova/smart-alerts.md) for the full conversational alert reference. *** ## Blockchain Alerts - [Token Swaps Alerts](https://zeroauthoritydao.ai/docs/nova/alerts/token-swaps.md) - [NFT Activity Alerts](https://zeroauthoritydao.ai/docs/nova/alerts/nft-activity.md) - [Wallet Tracker Alerts](https://zeroauthoritydao.ai/docs/nova/alerts/wallet-tracker.md) - [Premium Alerts](https://zeroauthoritydao.ai/docs/nova/alerts/premium.md) ## ZADAO & Ecosystem - [ZADAO Alerts](https://zeroauthoritydao.ai/docs/nova/alerts/zadao.md) — bounties, gigs, quests, campaigns, and grants - [Events & Governance Alerts](https://zeroauthoritydao.ai/docs/nova/alerts/events-and-governance.md) — ecosystem events, SIPs, and CAB voting - [ZADAO Stats](https://zeroauthoritydao.ai/docs/nova/alerts/zadao-stats.md) — community & platform stats viewer (not an alert) - [Legacy `/gm` opt-in](https://zeroauthoritydao.ai/docs/nova/community/gm.md#legacy-gm-opt-in) ## Manage & Audit - [Managing Your Alerts (Web Dashboard)](https://zeroauthoritydao.ai/docs/nova/alerts/manage.md) - [Alert History & Delivery Status](https://zeroauthoritydao.ai/docs/nova/alerts/history.md) --- id: nova/alerts/token-swaps title: "Token Swaps Alerts" description: "Monitor any Stacks token in real time — get an alert whenever someone buys (or sells) your tracked tokens, with customizable thresholds and visuals." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/token-swaps related: [nova/alerts] tokens: 531 --- # Token Swaps Alerts Track a Stacks token with /nova and get an alert on every buy (or sell) above your chosen USD threshold, with DEX, amounts, position change and your own emoji and image. | 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 | --- id: nova/alerts/nft-activity title: "NFT Activity Alerts" description: "Track any NFT collection on Stacks — get alerts for buys, listings, offers, and mints, each routed to the channel of your choice." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/nft-activity related: [nova/alerts] tokens: 380 --- # NFT Activity Alerts Track a Stacks NFT collection with /nova and get alerts for buys, listings, offers and mints, each routed to its own channel if you like. | 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. > [!TIP] > **Mint alerts** are automatically included if you set up tracking **before** the collection starts minting. No extra configuration needed. *** ## 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. --- id: nova/alerts/wallet-tracker title: "Wallet Tracker Alerts" description: "Monitor any wallet across multiple chains and get an alert whenever it moves — transfers in and out, trades, and on-chain activity." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/wallet-tracker related: [nova/alerts] tokens: 1021 --- # Wallet Tracker Alerts Track wallets on Stacks, EVM chains, Solana, Bitcoin, TON, Sui, Aptos and Hyperliquid with /nova and get an alert when they move funds, filtered by minimum value and direction. Free and Premium both include noise filters; Premium raises the address limit and adds custom labels. The address limit is shared across every chain combined — see the [Premium guide](https://zeroauthoritydao.ai/docs/nova/plans.md) for the numbers. *** ## 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 | > [!TIP] > **Premium feature:** Add custom labels to tracked addresses (e.g. "Team Wallet", "DEX Treasury") so alerts are easy to identify at a glance. *** ## 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. > [!NOTE] > **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](https://zeroauthoritydao.ai/docs/nova/agent-observatory.md). --- id: nova/alerts/premium title: "Premium Alerts" description: "Exclusive alert types for Premium subscribers: early access to new token launches, NFT deployments, contract activity, and whale movements on Stacks." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/premium related: [nova/alerts] tokens: 203 --- # Premium Alerts How to turn on Premium-only alerts (snipers for new tokens, NFTs and contracts, plus whale transfers) with the /premium wizard. Requires a Premium subscription. > [!WARNING] > These alerts require an active **Premium subscription**. See [Premium](https://zeroauthoritydao.ai/docs/nova/plans.md) for plans and pricing. *** ## Available Alert Types The Premium-only alert types (Token/Pair, NFT, NFT Collection, Contract and Listings snipers, and Whale Transfers), with the chains each covers, are listed in [Premium](https://zeroauthoritydao.ai/docs/nova/plans.md#premium-only-alert-types). *** ## 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. --- id: nova/alerts/zadao title: "ZADAO Alerts" description: "Get alerts for activity on Zero Authority DAO: bounties, gigs, quests, campaigns, and grants. Four feeds are configured with a slash-command wizard; grants are configured conversationally by just talking to Nova." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/zadao related: [nova/alerts] tokens: 2186 --- # ZADAO Alerts Get alerts for Zero Authority DAO bounties, gigs, quests and campaigns through /bounty, /gigs, /quest and /campaigns, and for grants by asking Nova. Lists every trigger and filter for each feed. | Feed | Command | Triggers | Filters / options | | ------------- | ------------ | ------------------------------------------------------------ | -------------------------------------------------------- | | **Bounties** | `/bounty` | Bounty created, entry submitted, bounty boosted, bounty completed, participants rewarded | 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. > [!WARNING] > On Telegram, don't click selection buttons too quickly — Telegram may temporarily rate-limit excessive interactions. *** ## Bounties — `/bounty` | Trigger | Details | | -------------------- | ------------------------------------------------------------------------------------------- | | **Bounty Created** | A new bounty was posted — includes Campaign, title, prize, type (single winner, multi-winner, NFT or custom split), deadline. A custom split lists the reward for each winner place | | **Entry Submitted** | Someone submitted to a bounty you're tracking (optional) | | **Bounty Boosted** | Someone added STX, a token or an NFT on top of a bounty's prize with **Boost a Bounty** — includes the boost, who sent it, and the bounty's boost pool so far | | **Bounty Completed** | A bounty was completed — includes winner(s) and prize info; for a custom split, who won each place and what they got. If the bounty was boosted, the boost pool the winners can now claim | | **Participants Rewarded** | After the winners were picked, someone paid the bounty's participants directly — includes how many, how much each, and the total | 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. Boost and reward alerts go with the bounty alerts and follow the same Campaign filter. ### Boost a Bounty Anyone can boost an open ZADAO bounty to make it more rewarding. The boost goes to the winners, split the same way as the prize (equally, 60/30/10 for a top-3 bounty, or each place's share for a custom split). If the bounty is cancelled, or stays open for about 90 days without winners, boosters can take their boost back. Very small boosts are not announced, so a channel isn't flooded with dust. To see a bounty's boost pool at any time, ask Nova: > @Nova has the meme contest bounty been boosted? *** ## 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. > [!TIP] > All of these alerts also appear in your web dashboard's [Alerts Hub](https://zeroauthoritydao.ai/docs/nova/alerts/manage.md), alongside every other Nova alert. --- id: nova/alerts/events-and-governance title: "Events & Governance Alerts" description: "Get alerts for Stacks ecosystem events (meetups, hackathons, conferences, community calls) and Stacks governance activity (SIPs and CAB voting)." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/events-and-governance related: [nova/alerts] tokens: 1508 --- # Events & Governance Alerts Set up alerts for Stacks ecosystem events and SIP/CAB governance by describing them to Nova. Lists every trigger, condition field and polling interval (30 minutes for events, 2 hours for governance). 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 Both alert types count toward your total alert limit. Free and Premium limits (alert count, conditions per alert, cooldown, time windows, digest mode) are in [Smart Alerts](https://zeroauthoritydao.ai/docs/nova/smart-alerts.md#free-vs-premium) and the [Premium guide](https://zeroauthoritydao.ai/docs/nova/plans.md). *** ## 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. --- id: nova/alerts/history title: "Alert History & Delivery Status" description: "Check whether your Smart Alerts have been firing — and whether those alerts actually reached you. Just ask Nova; no command or setup needed." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/history related: [nova/alerts] tokens: 661 --- # Alert History & Delivery Status Ask Nova which of your Smart Alerts fired recently and whether each was delivered, with status, attempts and the last error, to answer "why didn't I get my alert?". Read-only and private to you. 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)](https://zeroauthoritydao.ai/docs/nova/alerts/manage.md). > [!NOTE] > 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. *** ## 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). > [!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. *** ## Related - [Managing Your Alerts (Web Dashboard)](https://zeroauthoritydao.ai/docs/nova/alerts/manage.md) 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. --- id: nova/alerts/zadao-stats title: "ZADAO Stats" description: "Track community engagement and platform activity for Zero Authority DAO directly from Discord and Telegram." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/zadao-stats related: [nova/alerts] tokens: 1498 --- # ZADAO Stats /zadao opens a stats menu for Zero Authority DAO: community growth, active members, a quality-weighted Top Contributors leaderboard and platform metrics over 24h to 30 days, plus a weekly Monday recap. 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. > [!NOTE] > `/zadao` is a stats viewer, not an alert. It works in groups and DMs — anyone can use it, no admin permission needed. *** ## 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. *** > [!NOTE] > 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. --- id: nova/alerts/manage title: "Managing Your Alerts (Web Dashboard)" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/alerts/manage related: [nova/alerts] tokens: 980 --- # Managing Your Alerts (Web Dashboard) The Alerts & Notifications hub on the Nova web dashboard shows every alert you own in one filterable view, where you can enable, disable, snooze, bulk-edit and delete them. New alerts are still created in the bot. 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](https://zeroauthoritydao.ai/docs/nova/alerts/history.md). > [!NOTE] > 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. *** ## What's Included The hub unifies five 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 | | **Nova Scout** | Your personal opportunity digest: interests, schedule and saved count. Pause or delete it here | *** ## 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** | Nova Scout, 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 > [!TIP] > 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. | 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](https://zeroauthoritydao.ai/docs/nova/alerts/zadao.md) | | Ask Nova directly | Smart Alerts (e.g. _"create a whale alert for STX over 100k"_) | | `/nova_guardian` | Scam-moderation protection | | `/scout` | [Nova Scout](https://zeroauthoritydao.ai/docs/nova/scout.md) opportunity digest | > [!NOTE] > 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. *** ## Related - [Alert History & Delivery Status](https://zeroauthoritydao.ai/docs/nova/alerts/history.md) - [Premium Alerts](https://zeroauthoritydao.ai/docs/nova/alerts/premium.md) --- id: nova/community/roles title: "Community Roles" product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/roles related: [nova/community] tokens: 1802 --- # Community Roles Community Roles gives Discord roles automatically for wallet holdings on Stacks, EVM, Solana or Bitcoin, for Ascend levels, and on PRO for time in the server, activity and holding time. Nova re-checks and updates them. **Community Roles** give Discord roles to members for what they have earned: what their wallets hold on Stacks, EVM chains, Solana or Bitcoin, the level they reached by chatting, how long they have been around and how active they are, or several of these together. You write a rule once ("the Holder role for 1,000 of our token", "the Elder role at level 20") and Nova grants the role and keeps it in line. *** ## How it works A **rule** gives one role for one thing. Several rules can give the same role, and one member can earn several roles. | A rule can ask for | Example | | --- | --- | | **A holding**: at least an amount of one asset on one chain | The Holder role for 1,000 of a token | | **A level**: an [Ascend](https://zeroauthoritydao.ai/docs/nova/community/community-games.md) level, with no wallet at all | The Elder role at level 20 | | **A holding and a level**: the member needs both | The Core role for 1,000 of a token and level 10 | | **A verified wallet**: any member who proved a wallet, whatever it holds | A Verified role | | **The member themselves** (Community PRO): time in the server and activity, with no wallet | The OG role for members of 180 days who were active on 20 days | On **Community PRO** any rule can also ask for more, and the member then needs all of it. You choose the numbers, so "active" means what your community wants it to mean: | Condition | What it counts | Example | | --- | --- | --- | | Days in the server | Days since the member joined (leaving and coming back starts again) | Member for 180 days | | Active days, ever | Different days the member sent a real message. Never taken away | Active on 20 days | | Active days of the last 30 | The same, for the last 30 days. The role comes off when a member goes quiet and comes back when they return | Active on 4 of the last 30 days | | Days held | How long the member has held a rule's amount | Diamond Hands for 1,000 of a token held 90 days | A role for time in the server always needs a sign of activity as well (a level, or active days), so it never goes to an account that joined long ago and never spoke. Active days are counted from the day Ascend was turned on. **Days held are counted by Nova**, from the first check that finds the amount in the member's verified wallet. Nova does not see what a wallet held before the member verified, and the count starts again from zero if a re-check finds them below the amount. Nobody gets a "held 90 days" role on day one, so ask holders to verify early. A holding can be on any of these chains: | Chain | What a rule can require | | --- | --- | | Stacks | A token or an NFT collection | | Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche | An ERC-20 token or an ERC-721 NFT collection | | Solana | An SPL token | | Bitcoin | A BTC balance | **Level roles** need nothing from the member: Nova gives the role the moment they reach the level. Levels come from Ascend, so turn it on first (_"@Nova turn on XP and levels"_). A role that only time brings (the 180th day in the server, the 90th day of holding) arrives at the next automatic re-check, or at once when the member asks for their roles. **Holding roles** need a wallet: a member verifies one wallet for each chain your rules use. They get a private link, connect the wallet and sign a message to prove it is theirs. Signing is not a transaction and costs nothing. Nova reads the holdings on chain and adds the roles. From then on Nova re-checks members on a schedule, so someone who sells below the amount loses the role and someone who buys in gets it. A member who asks for their roles is told what they still lack for the ones they did not get, for example _"level 7 of 10"_ or _"400 of 1,000"_. Two things Nova will not do. It never gives a role that carries moderation or admin permissions. And if holdings or a level cannot be read at re-check time, the roles that depend on it are left exactly as they are: an outage never strips roles. Chains are checked separately, so a problem on one chain does not hold up the roles from another. *** ## Free vs Community PRO | | Free | Community PRO | | --- | --- | --- | | Role rules per server (any kind, any chain) | 5 | 30 | | Automatic re-check of holdings | Every week | Every day | | Manual re-sync | Once every 72 hours | Once every 6 hours | | Holding, level and verified-wallet rules | ✓ | ✓ | | Level roles given the moment the level is reached | ✓ | ✓ | | Roles for time in the server and activity | — | ✓ | | "Held for N days" on a holding rule | — | ✓ | | "Get my roles" button | ✓ | ✓ | A server that ends up over its rule limit keeps every rule working and can still edit or remove them. It only cannot add more. The same goes for a server that leaves Community PRO: its time, activity and holding-time rules keep working and can be lowered or removed, not added or raised. *** ## Set it up (Discord only) 1. In **Server Settings > Roles**, create the role and drag **Nova's role above it**. Nova needs the *Manage Roles* permission. 2. As an admin, tell Nova the rule in your server. For a holding, give the exact contract, and the network for an EVM token: > _"@Nova give the Holder role to anyone with 1000 of SP2ABC...XYZ.my-token"_ > _"@Nova give the Elder role at level 20"_ > _"@Nova give the Core role to anyone with 1000 of SP2ABC...XYZ.my-token and level 10"_ > _"@Nova give the OG role to members who have been here 180 days and were active on at least 20 days"_ (Community PRO) > _"@Nova give Diamond Hands to anyone who has held 1000 of SP2ABC...XYZ.my-token for 90 days"_ (Community PRO) 3. Give members a way to get their roles. Post a button in a channel: > _"@Nova post the roles button in #roles"_ Members can also run `/roles` and choose **Get Roles**. Either way they see the roles they have earned and what is still missing, and get their wallet link when a rule asks for a wallet. 4. Check or change it any time: _"@Nova show our role rules"_ lists every rule with how many members hold its role. _"@Nova change the Elder level to 25"_, _"@Nova remove rule #2"_ and _"@Nova re-sync roles"_ do what they say. The same rules are on the **Community Roles** card under Nova Harbor in the [Community Settings dashboard](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md), and in `/roles` under **Setup Roles** (server Administrators). Chat, dashboard and command edit one list. > [!NOTE] > **Added a rule for members who already qualify?** A member already at the level, or who verified a wallet before the rule existed, gets the role at the next re-sync with nothing to do, or at once by pressing the button. A member verifies one wallet on each chain, and a wallet counts for one Discord account per server: verifying it from a second account moves its roles to that account. > [!WARNING] > **Not supported yet.** Roles for leaderboard rank, a ladder that keeps only the highest role, and holding time read from chain history. For holdings: ERC-1155 tokens, Solana NFT collections, and Runes, BRC-20 or Ordinals on Bitcoin; smart-contract wallets (such as Safe) cannot be verified on EVM. If a role is not being given, ask _"@Nova show our role rules"_: a rule Nova cannot act on says why. --- id: nova/blockchain-coverage title: "Blockchain Coverage" product: nova canonical: https://zeroauthoritydao.ai/docs/nova/blockchain-coverage related: [nova] tokens: 1480 --- # Blockchain Coverage Ask Nova for live prices, wallet portfolios, transactions and contracts on Bitcoin, Stacks, 60+ EVM chains, Solana, TON, Sui, Aptos and Hyperliquid, plus Ordinals, Runes, Zest, rug checks and ENS/SNS names. 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. > [!NOTE] > 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. *** ## 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 > [!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**. *** ## 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](https://zeroauthoritydao.ai/docs/nova/news-and-research.md). *** ## 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. ### Zest & stBTC > _"How is the Zest stBTC Vault doing?"_ · _"Is my Zest loan safe?"_ · _"What are Zest's sBTC rates?"_ * **Zest lending:** your supplied and borrowed assets, health factor and liquidation line, and every market's rates, on Zest's current and older markets * **Zest stBTC Vault:** size, earned yield next to Zest's target, leverage, room left under the cap, withdrawal wait and fees, plus your own shares and pending withdrawals * **stBTC (Stacking DAO):** shown in wallet lookups with its value in sBTC Set alerts for liquidation risk, vault room and ready withdrawals: see [Smart Alerts](https://zeroauthoritydao.ai/docs/nova/smart-alerts.md). > [!WARNING] > The yield shown is what the vault has earned so far; Zest's target is not a promise. Information only, **not financial advice**. For Stacks ecosystem and SIP news, see [News & Research](https://zeroauthoritydao.ai/docs/nova/news-and-research.md). *** ## 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). --- id: nova/market-intelligence title: "Market Intelligence" description: "Nova integrates with Tenero.io for advanced multi-chain trading analytics — portfolio P&L, whale tracking, pool analytics, and cohort analysis, all through conversation." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/market-intelligence related: [nova] tokens: 569 --- # Market Intelligence Through Tenero, Nova gives wallet P&L, whale trades, pool and token analytics, and cohort analysis of up to 20 wallets or tokens at once, on Stacks, Spark, SportsFun, Citrea and OpNet. 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](https://zeroauthoritydao.ai/docs/nova/blockchain-coverage.md). *** ## 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. > [!NOTE] > Each cohort call supports up to **20 wallets** and/or **20 tokens** at once. **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 --- id: nova/memory-and-personalization title: "Memory & Personalization" description: "Nova remembers your conversations and can learn context-specific information about your server or group, making interactions faster and more relevant over time." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/memory-and-personalization related: [nova] tokens: 244 --- # Memory & Personalization Nova keeps recent, short-term and up to 30-day memory of your conversations, can be taught facts about your server or group, and stores personal preferences like timezone and response style. ## 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. --- id: nova/news-and-research title: "News & Research" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/news-and-research related: [nova] tokens: 212 --- # News & Research Ask Nova for Bitcoin, Stacks, Ordinals, Runes and BRC-20 news from sources like Bitcoin Optech and Cointelegraph, or have it search the web and extract a page you link. ## 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 --- id: nova/smart-alerts title: "Smart Alerts" description: "Smart Alerts are custom, conditional monitoring created through natural language — tell Nova what you want to watch, and it handles the rest." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/smart-alerts related: [nova] tokens: 2613 --- # Smart Alerts Describe an alert in plain English (price, whale, DEX, NFT, SIP, fees, wallet, Zest and more) and Nova watches for it. Covers trigger wording, snooze and quiet hours, cleanup, and Premium extras like AND/OR, digests and webhooks. > [!NOTE] > 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](https://zeroauthoritydao.ai/docs/nova/alerts.md). *** ## 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"_ | | **Zest liquidation risk** | _"Warn me if my Zest health factor drops below 1.2"_ | | **Zest vault room** | _"Tell me when the Zest stBTC Vault has room again"_ | | **Zest withdrawal ready** | _"Tell me when my Zest vault withdrawal can be claimed"_ | *** ## 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"_ > [!NOTE] > 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. *** ## 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](https://zeroauthoritydao.ai/docs/nova/plans.md) 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). > [!NOTE] > **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. ### 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 https://myapp.example.com/nova-hook"_ 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"_) --- id: nova/zadao-ecosystem title: "ZADAO Ecosystem" description: "Nova is your gateway to the Zero Authority DAO ecosystem. Search bounties, gigs, grants, quests, and contributor profiles — all from chat." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/zadao-ecosystem related: [nova] tokens: 947 --- # ZADAO Ecosystem Search Zero Authority DAO bounties, gigs, grants, quests, contributor profiles and docs from chat, and on zadao.ai create a bounty, pay for finished work or publish a price-on-request listing with a wallet signature. ## 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 * For a custom-split bounty, the reward for each winner place ### Create a bounty from chat In the web chat at [zeroauthoritydao.ai](https://zeroauthoritydao.ai), Nova drafts the bounty and opens a card you review and sign with your wallet. Pick how the prize is shared: one winner, several winners splitting it equally, the top 3, or a **custom split** where you set what each place gets (up to 10 places). > _"Create a 170 STX bounty for beginner tutorials in my campaign: 75 STX for 1st, 55 for 2nd, 40 for 3rd, ending October 31"_ A custom split can also offer a **bonus NFT** to one place: give Nova the collection's contract id, the token id and the place that wins it. > _"Add my NFT SP2PABAF9FTAJYNFZH93XENAJ8FVY99RRM50D2JG9.my-collection #42 as a bonus for 1st place"_ > [!NOTE] > The NFT must come from a collection Zero Authority accepts. It leaves your wallet into the bounty's escrow when you sign, and the contract charges a small STX fee for holding it. The signing card shows the NFT, the place that gets it and the fee before you sign. *** ## 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 ### Pay for finished work Already worked with someone and the job is done? Ask Nova to pay them and record it, for example _"Pay SP... 200 STX for the logo they delivered last week"_. On zadao.ai a signing card opens: the payment goes straight to them in one transaction, with ZADAO's fee on top and no escrow, and the gig is recorded as completed so it counts toward both your REP. ### Price-on-request listings Some work has no fixed price, like _"I will build your app; the price depends on the scope"_. Ask Nova to publish your Work listing as **price on request**: it has no packages, just a typical turnaround, the token you quote in and, if you like, a "from" price. Say in the description what is not included, such as hosting or domains. Buyers press "Request a quote" on the listing, you answer in the conversation with a custom offer, and the buyer pays that offer into escrow. Nova will not hire such a listing at a fixed price; it suggests asking the seller for a quote instead. *** ## 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](https://zeroauthoritydao.ai/docs/nova/cab-groups.md). *** ## 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) --- id: nova/cab-groups title: "Nova for CAB Groups & Governance Participants" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/cab-groups related: [nova] tokens: 1114 --- # Nova for CAB Groups & Governance Participants For CAB members and SIP followers: ask Nova for any SIP's status, CAB vote tallies and upcoming Stacks events, and set alerts so you never miss a vote opening or closing. ## 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 > [!NOTE] > **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. To pause, update, or review alerts conversationally, see [Smart Alerts](https://zeroauthoritydao.ai/docs/nova/smart-alerts.md). Free vs Premium alert limits are in the [Premium guide](https://zeroauthoritydao.ai/docs/nova/plans.md). *** ## 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. > [!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](https://zeroauthoritydao.ai/docs/nova/plans.md) for more granular control. *** ## 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](https://zeroauthoritydao.ai/docs/nova/blockchain-coverage.md) and [ZADAO Ecosystem](https://zeroauthoritydao.ai/docs/nova/zadao-ecosystem.md) for the full picture. For ecosystem news and updates, see [News & Research](https://zeroauthoritydao.ai/docs/nova/news-and-research.md). *** ## 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. --- id: nova/emblem-vault title: "Emblem Vault" description: "Nova helps you explore and create Emblem Vaults — conversationally, with zero custody." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/emblem-vault related: [nova] tokens: 1198 --- # Emblem Vault Nova looks up what an Emblem Vault holds and its value, browses the collection catalog, finds vaults a wallet owns, and guides you to create one in your own wallet. Nova never holds keys or signs. 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. > [!TIP] > **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. *** ## 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 > [!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**. *** ## 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](https://zeroauthoritydao.ai/docs/nova/tools.md) and [Using Nova Tools with Agents](https://zeroauthoritydao.ai/docs/build/nova-tools-for-agents.md). --- id: nova/agent-observatory title: "Agent Observatory" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/agent-observatory related: [nova] tokens: 862 --- # Agent Observatory Browse, rank and look up AI agents on the aibtc network, and follow one to get alerts on its on-chain moves, level-ups and inbox in your Discord or Telegram. Read-only: Nova never moves funds here. 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. > [!NOTE] > **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**. > [!NOTE] > Following an agent uses Nova's **wallet-tracking** system under the hood, so each followed agent counts toward your address-tracking limit (listed in the [Premium guide](https://zeroauthoritydao.ai/docs/nova/plans.md)). See [Wallet Tracker Alerts](https://zeroauthoritydao.ai/docs/nova/alerts/wallet-tracker.md). *** ## 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. --- id: nova/community title: "Community" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community related: [nova, nova/community/roles, nova/community/guardian, nova/community/language-moderation, nova/community/pulse, nova/community/gm, nova/community/snacks, nova/community/community-games, nova/community/chat, nova/community/soul, nova/community/settings-dashboard, nova/community/flares, nova/community/harbor, nova/community/relay, nova/community/warp] tokens: 2926 --- # Community Overview of Nova's community features for Discord and Telegram (Guardian, Harbor, Roles, Language Moderation, Pulse, Games, GM, Snacks, Relay, Warp, Flares), with a guide to choosing and turning them on by asking Nova. **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, Harbor, Community Roles, Pulse, Games, GM, Snacks, Relay and Flares apply to the whole server/group; Warp links one channel with your Telegram group; Language Moderation is **per-channel** by design. *** ## The community features - **🛡️ Nova Guardian — protect** — A 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. [Guide](https://zeroauthoritydao.ai/docs/nova/community/guardian.md) - **⚓ Nova Harbor — welcome** — Automatically **welcomes every new member** with your template or an AI-personal message, link buttons, burst batching and a raid guard. PRO adds **first-message welcomes**, a **DM onboarding series**, **auto-roles & role buttons**, goodbyes and member milestones. [Guide](https://zeroauthoritydao.ai/docs/nova/community/harbor.md) - **🪙 Community Roles — reward holders and regulars** — **Discord roles members earn**: by what their verified wallet holds (Stacks, EVM chains, Solana or Bitcoin), by the level they reached chatting, or both. Community PRO adds roles for long-time active members and for how long a token has been held. A level role arrives the moment the level is reached; Nova re-checks holdings on a schedule and adds or removes roles as they change. Discord only. [Guide](https://zeroauthoritydao.ai/docs/nova/community/roles.md) - **🌐 Nova Language Moderation — organize** — Per-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. [Guide](https://zeroauthoritydao.ai/docs/nova/community/language-moderation.md) - **📊 Nova Pulse — manage** — A 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. [Guide](https://zeroauthoritydao.ai/docs/nova/community/pulse.md) - **🎮 Nova Community Games — engage** — An 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**. [Guide](https://zeroauthoritydao.ai/docs/nova/community/community-games.md) - **☀️ Community GM — greet** — When 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. [Guide](https://zeroauthoritydao.ai/docs/nova/community/gm.md) - **🍪 Daily Snacks — spark** — One 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. [Guide](https://zeroauthoritydao.ai/docs/nova/community/snacks.md) - **📡 Nova Relay — catch up** — A recap of your community's public chat, **Discord and Telegram merged into one**: **one pinned live message** Nova keeps up to date every few hours, or a new post each day. A few short lines on what the team announced and what people talked about, in the voice and look you choose. **Community PRO.** [Guide](https://zeroauthoritydao.ai/docs/nova/community/relay.md) - **🌌 Nova Warp — connect** — Your **Discord channel and Telegram group as one live chat**: what a member posts on one side appears on the other within seconds, under their name, with replies, edits and deletions following. Nobody is pinged across. **Community PRO.** [Guide](https://zeroauthoritydao.ai/docs/nova/community/warp.md) - **✨ Nova Quasar: Flares — grow** — **Automatic posts** that fire when something real happens: a member milestone, a level milestone, a new leaderboard leader, your anniversary. Turn a rule on once and Nova publishes in your own channel. PRO adds **token holder and governance triggers** and your **persona voice**. [Guide](https://zeroauthoritydao.ai/docs/nova/community/flares.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 identity** — Rename 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. [Guide](https://zeroauthoritydao.ai/docs/nova/community/soul.md) - **💬 Nova Chat — your budget** — A **pooled message allowance** the community pays for, so members chat with Nova **without spending their own AI allowance**. Automatic — nothing to enable. [Guide](https://zeroauthoritydao.ai/docs/nova/community/chat.md) - **📝 Ops AI drafts — your copywriter** — Ask 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. [Guide](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md) *** ## Discord and Telegram: shared or separate? One community on Nova can hold a Discord server **and** a Telegram group. The **plan** covers both. You turn each feature on in each place, but **its settings are shared by default**: change Guardian's mode or allowlist in your Discord server and your Telegram group gets the same change. When you turn a feature on in the second place, it starts with the settings of the first. What stays **separate** is what only makes sense in one place: channels, topics and roles, options that exist on one platform only, and a few choices that depend on the size of each chat. | Feature | Shared between Discord and Telegram | Separate in each place | | --- | --- | --- | | Nova Soul | The custom name and persona (always one for the community) | — | | Guardian | Mode, auto-moderation, auto-delete, auto-mute, mute duration, thresholds, **allowlist** | Mod channel, known admins | | Language Moderation | Warn, auto-delete, alert mods, **allowlist**, languages allowed everywhere | Per-channel rules, mod channel | | Harbor | Welcome, goodbye and ban messages, link buttons, AI welcomes, DM onboarding, timing and raid guard | Welcome channel or topic, Discord card and roles, Telegram join notices, when to welcome, member milestones | | Pulse | Unanswered alerts, daily brief and its time, newcomer welcomes, Concierge | Mod channel | | Knowledge | Concierge answers from the entries added in both places | Each entry stays listed where it was added | | Ascend and Play | XP on/off, level-up shoutouts, weekly leaderboard day, games, giveaways, recap time | Channels; members' **XP and levels** are counted apart | | GM, Snacks | Custom instructions, web search, time and cadence | — | | Flares | Daily limit, AI line, footer note | Channel or topic, card color, rules | | Relay | Mode, rhythm, look, language, time, pinning | Places, channels left out, member role, Discord format, Telegram collapsing | | Warp | Staff messages stay on their side | The linked channel or topic, member role, who manages it | The AI usage meter, AI Boosts and your team are always one for the whole community. Daily and monthly counts (scans, answers, welcomes...) are still counted in each place. Community Roles are Discord only. **Want them separate?** On the [Community page](https://nova.zeroauthoritydao.com/community), open the feature's card and turn off **Same settings on Discord and Telegram** (for Knowledge: **One knowledge base for Discord and Telegram**). Nothing is deleted: each place keeps its current values and changes stop being copied. Turning it back on asks which place's settings both should use. If the two places don't match (for example, they were set up before sharing existed), the card shows what differs and lets you pick a side; until then, each change you save is copied. When you change a shared setting in chat, Nova tells you it was also applied to the other place. A value the other place can't take is left as it was and Nova says why: for example, auto-moderation isn't copied into a Discord server until it has a moderator role to report to. *** ## Which one do I want? | If you want to… | Turn on | | --- | --- | | Stop scams, phishing, and spam floods before they spread | **Nova Guardian** | | Greet every newcomer and onboard them (DMs, roles, first steps) | **Nova Harbor** | | Give Discord roles to holders of your token or NFT, or to members who reach a level | **Community Roles** | | 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** | | Give members who were away a pinned recap of the chat, live or daily | **Nova Relay** | | Stop splitting your community between Discord and Telegram | **Nova Warp** | | Announce milestones automatically, with no calendar to maintain | **Nova Quasar: Flares** | > [!NOTE] > **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. *** ## Set any of them up — just talk to Nova In your server/group, as an admin/mod, tag Nova (**@NovaBot** on Discord, **@NovaAITheBot** on Telegram) or reply to it, and say what you want. _"@Nova"_ in the examples stands for that tag: > _"@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](https://zeroauthoritydao.ai/docs/nova/alerts/zadao-stats.md). **Prefer a control panel?** Every feature is also manageable from the web — the [Community Settings dashboard](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md) 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. - [Community Settings (Web Dashboard)](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md) - [Nova Guardian](https://zeroauthoritydao.ai/docs/nova/community/guardian.md) - [Nova Harbor](https://zeroauthoritydao.ai/docs/nova/community/harbor.md) - [Community Roles](https://zeroauthoritydao.ai/docs/nova/community/roles.md) - [Nova Language Moderation](https://zeroauthoritydao.ai/docs/nova/community/language-moderation.md) - [Nova Pulse](https://zeroauthoritydao.ai/docs/nova/community/pulse.md) - [Nova Community Games](https://zeroauthoritydao.ai/docs/nova/community/community-games.md) - [Community GM](https://zeroauthoritydao.ai/docs/nova/community/gm.md) - [Daily Community Snacks](https://zeroauthoritydao.ai/docs/nova/community/snacks.md) - [Nova Relay](https://zeroauthoritydao.ai/docs/nova/community/relay.md) - [Nova Warp](https://zeroauthoritydao.ai/docs/nova/community/warp.md) - [Nova Quasar: Flares](https://zeroauthoritydao.ai/docs/nova/community/flares.md) - [Nova Soul](https://zeroauthoritydao.ai/docs/nova/community/soul.md) - [Nova Chat](https://zeroauthoritydao.ai/docs/nova/community/chat.md) > [!NOTE] > **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](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md), or just ask Nova *"show plans"* in your server. Each feature page lists its exact Free vs PRO limits. --- id: nova/community/guardian title: "Nova Guardian" description: "Nova Guardian is a passive community-protection shield." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/guardian related: [nova/community] tokens: 4003 --- # Nova Guardian Guardian screens every message for scams, social engineering, bad links and repeat spam, in any language. It flags suspicious posts to mods and, with auto-moderation, deletes scams and mutes the author with a Ban/Revert report. **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 | | **🎯 Address harvesting / giveaway lures** | "If you need 5 SOL, send your SOL address", "drop your wallet address below", "who wants free ETH?" — fake generosity that collects wallet addresses | | **🔗 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. > [!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"*. ### 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. #### 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. #### 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 ``` > [!NOTE] > 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. *** ## 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](https://zeroauthoritydao.ai/docs/nova/get-started/discord.md)), 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 | **Discord and Telegram share these settings.** In a community with both, the mode, auto-moderation, mute duration, thresholds and allowlist are the same in your server and your group: a phrase you allowlist on one side is allowlisted on the other. The mod channel and known admins stay per place. To keep them separate, turn off **Same settings on Discord and Telegram** on the Guardian card. The allowlist matches any message that contains the phrase, so a domain (*"allowlist ourproject.xyz"*) works too. See [shared or separate](https://zeroauthoritydao.ai/docs/nova/community.md#discord-and-telegram-shared-or-separate). *** ## 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. --- id: nova/community/language-moderation title: "Nova Language Moderation" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/language-moderation related: [nova/community] tokens: 2092 --- # Nova Language Moderation Set which languages each channel allows and Nova warns, redirects to the right channel, deletes or alerts mods when someone posts in another language. Starts in warn-only mode and stays silent when unsure. **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 | > [!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). *** ## 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. > [!TIP] > The bias is deliberate: **when in doubt, Nova stays silent.** A missed violation costs nothing — a wrongly-deleted message costs trust. ### 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 | In a community with Discord and Telegram, warn, auto-delete, alert mods, the allowlist and the languages allowed everywhere are shared between them. Per-channel rules and the mod channel stay per place, since channels differ. See [shared or separate](https://zeroauthoritydao.ai/docs/nova/community.md#discord-and-telegram-shared-or-separate). **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. --- id: nova/community/pulse title: "Nova Pulse" description: "Nova Pulse is a proactive community-manager copilot for moderators." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/pulse related: [nova/community] tokens: 2733 --- # Nova Pulse Pulse is a mod copilot: it flags member questions nobody answered, and on Community PRO posts a daily brief to the mod channel and can auto-answer FAQs from a knowledge base you fill or import (Concierge). **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**). > [!NOTE] > 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](https://zeroauthoritydao.ai/docs/nova/community/snacks.md). *** ## 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](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md) 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 rescue** — Finds genuine member questions that slipped through unanswered and flags them to your mod channel — one heads-up digest, not per-message spam. - **🗞️ Daily community brief** — A 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-answer** — When 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 member's question was answered** — so it catches the quiet newcomer's question that would otherwise scroll away. Questions asked by your own moderators and admins are never flagged, and a moderator's follow-up question ("which wallet are you using?") doesn't count as an answer. *** ## 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. > [!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. *** ## 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. In a community with Discord and Telegram, Concierge answers from the entries added in both places, so you add a fact once. Each entry stays listed where it was added. To keep them apart, turn off **One knowledge base for Discord and Telegram** on the Knowledge card. ### 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 & FAQs** — The classics: *"add this to the FAQ: the snapshot is on the 15th"*. One focused fact per entry retrieves best. - **🌐 A website or docs page** — Nova fetches the page, strips the markup, and stores the readable text in clean chunks — *"import our docs page into the knowledge base"*. - **📦 A GitHub repo** — README plus up to 5 files from the repo's `docs/` folder — *"import github.com/yourorg/yourrepo"*. - **📜 A contract's source** — A 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 https://docs.myproject.xyz/tokenomics 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). > [!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. *** ## 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. --- id: nova/community/gm title: "Community GM" description: "Community GM turns the oldest crypto ritual into a daily brief." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/gm related: [nova/community] tokens: 1233 --- # Community GM When a member says "gm", Nova replies once per 36 hours with a morning brief of ecosystem news and your community's own feeds, matched to your ecosystem. PRO adds custom instructions and web search. Also covers the legacy /gm opt-in. **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. > [!TIP] > **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). 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 news** — A 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 sources** — New 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 https://myproject.xyz/feed.xml 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. > [!WARNING] > **Already using the channel-level [`/gm` opt-in](#legacy-gm-opt-in)?** 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. *** ## 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. *** ## Legacy `/gm` opt-in New setups should use the community GM above. For legacy users, the old per-channel `/gm` still works: 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. * **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 the community GM as described above. --- id: nova/community/snacks title: "Daily Community Snacks" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/snacks related: [nova/community] tokens: 826 --- # Daily Community Snacks Snacks are short insight or fact posts Nova drops on a schedule, based on your community's recent chat and ecosystem. Free posts every 3 days; Community PRO allows daily posts and custom instructions. 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](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md) unlocks a **daily** snack and lets you **steer** it. > [!TIP] > **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. *** ## 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](https://zeroauthoritydao.ai/docs/nova/community/soul.md) 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. *** > [!TIP] > Snacks are the **member-facing** daily touchpoint; the mod-facing daily readout is [Nova Pulse](https://zeroauthoritydao.ai/docs/nova/community/pulse.md)'s brief. They pair well — one keeps members engaged, the other keeps moderators informed. --- id: nova/community/community-games title: "Nova Community Games" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/community-games related: [nova/community] tokens: 2137 --- # Nova Community Games Community Games gives your server or group XP and levels, leaderboards, a weekly leaderboard post and giveaways for free; Community PRO adds mod-run AI games and trivia and a weekly recap. **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. > [!NOTE] > **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. 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](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md) 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 & Levels** — Members earn XP for chatting and level up over time, with an anti-spam cooldown so quality beats spam. - **🏆 Leaderboards** — All-time, weekly, and monthly rankings — plus "what's my rank?" for any member. - **📣 Weekly Leaderboard Post** — An 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)* - **🧠 Trivia** — A mod starts a trivia tuned to your community; Nova holds the answer and reveals it in-chat when you ask. *(PRO)* - **📅 Weekly Recap** — A "here's how the week went" summary built from real activity — most-active members and highlights. *(PRO)* - **🎁 Giveaways** — A 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). On Discord a level can also give a role: see [Community Roles](https://zeroauthoritydao.ai/docs/nova/community/roles.md). > [!TIP] > XP is earned **server/group-wide** — it doesn't matter which channel a member is active in. Your Discord server and your Telegram group each keep their own XP, levels and leaderboard: a member's activity on one side does not count on the other. ### 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. --- id: nova/community/chat title: "Nova Chat" description: "Nova Chat is the community-paid message allowance that comes with Community PRO." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/chat related: [nova/community] tokens: 897 --- # Nova Chat On Community PRO, members' messages to Nova in the server or group draw from a shared community pool (150 a day, 2,500 a month, 50 per member per day) instead of their own AI allowance. Nothing to enable. **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 own AI allowance**. Without it, every member talks to Nova on their own [personal allowance](https://zeroauthoritydao.ai/docs/nova/plans.md). 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 allowance left for DMs and other communities. > [!NOTE] > 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](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md). *** ## 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. > [!TIP] > **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 allowance](https://zeroauthoritydao.ai/docs/nova/plans.md) they'd have without it, on top of whatever the pool already covered. Only real answers draw from the pool — clarifying questions, short acknowledgements, and error notices are free. Caps reset automatically — daily at 00:00 UTC, monthly on the 1st. *** ## What Members See Nothing, usually — that's the point. Nova just answers, and nobody's personal allowance moves. The only time Nova Chat becomes visible is when a budget runs out mid-day **and** the member's own allowance is also used up. 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. Each member uses their own allowance 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 own AI allowance (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 your own allowance. | | **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 allowance. | | **What about free communities?** | Nothing changes — members use their own allowance 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](https://zeroauthoritydao.ai/docs/nova/community/soul.md) (your community's custom persona) — together they make Nova feel like *your community's own bot*: it speaks with your identity, on your budget. --- id: nova/community/soul title: "Nova Soul" description: "Nova Soul lets your community give Nova its own identity." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/soul related: [nova/community] tokens: 1725 --- # Nova Soul On Community PRO, rename Nova and give it a custom persona used only in your community, or run it under your own Discord app or Telegram bot. The persona changes style only, never rules or capabilities. **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](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md). *** ## 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. > [!TIP] > 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. *** ## 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 > [!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. Link from the web dashboard → **Community Settings** → the **Nova Soul** card → *Custom bot identity*: #### 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). #### 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). ### 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). --- id: nova/community/settings-dashboard title: "Community Settings (Web Dashboard)" description: "Everything in the community suite can be managed by talking to Nova — and now also from a web control room: nova.zeroauthoritydao.com/community." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard related: [nova/community] tokens: 2302 --- # Community Settings (Web Dashboard) The web dashboard at nova.zeroauthoritydao.com/community shows every community feature as a card to switch on, configure and watch usage, and lets owners add admins and moderators to a team. 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. > [!TIP] > **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. *** ## Getting in 1. Go to [nova.zeroauthoritydao.com/community](https://nova.zeroauthoritydao.com/community) and **sign in** (Discord, Telegram, Google, or your Stacks wallet). > [!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. 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 the command the page gives you (`@NovaBot activate YOUR-CODE` on Discord, `@NovaAITheBot activate YOUR-CODE` on Telegram) 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. Most settings are shared between the two: saving on either tab updates both, and the card's **Same settings on Discord and Telegram** switch keeps them separate instead. Channels, topics, roles and one-platform options always stay per tab. See [shared or separate](https://zeroauthoritydao.ai/docs/nova/community.md#discord-and-telegram-shared-or-separate). *** ## 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 meter**: how much of your plan's monthly AI allowance you have used, from 0% to 100%. ### The feature cards Cards are grouped the way the suite is organized: | Group | Cards | | --- | --- | | **Nova Soul** | [Custom bot name & persona](https://zeroauthoritydao.ai/docs/nova/community/soul.md) *(PRO)* | | **Nova Chat** | [Pooled member allowance](https://zeroauthoritydao.ai/docs/nova/community/chat.md) + catch-up *(PRO, automatic)* | | **Nova Guardian** | [Anti-scam shield](https://zeroauthoritydao.ai/docs/nova/community/guardian.md) — mode, mod channel, auto-moderation, thresholds, allowlist | | **Nova Harbor** | [Welcomes & onboarding](https://zeroauthoritydao.ai/docs/nova/community/harbor.md) · [Community Roles](https://zeroauthoritydao.ai/docs/nova/community/roles.md): role rules (holdings, levels, verified wallets), members per role, re-sync, the roles button (Discord) | | **Nova Orbit** | [Ascend](https://zeroauthoritydao.ai/docs/nova/community/community-games.md) (XP & leaderboards) · [Pulse](https://zeroauthoritydao.ai/docs/nova/community/pulse.md) (incl. the Concierge auto-answer toggle) · [Play](https://zeroauthoritydao.ai/docs/nova/community/community-games.md) · [GM](https://zeroauthoritydao.ai/docs/nova/community/gm.md) · [Snacks](https://zeroauthoritydao.ai/docs/nova/community/snacks.md) · Ops (AI drafts, [language moderation](https://zeroauthoritydao.ai/docs/nova/community/language-moderation.md), scheduled messages, X drafts) · [Knowledge](https://zeroauthoritydao.ai/docs/nova/community/pulse.md) · [Relay](https://zeroauthoritydao.ai/docs/nova/community/relay.md) (live pinned message or daily post: rhythm, period, places, look, channels left out) *(PRO)* · [Warp](https://zeroauthoritydao.ai/docs/nova/community/warp.md) (the Discord channel or Telegram topic linked into one chat) *(PRO)* | | **Nova Quasar** | [Flares](https://zeroauthoritydao.ai/docs/nova/community/flares.md): automatic milestone posts (channel, daily limit, AI line, footer note) | | **Nova Alerts** | A pointer to the Alerts Hub on your Dashboard, where per-system alert subscriptions live | **Delete community data.** At the bottom of the page the **owner** (not admins or moderators) can permanently delete everything Nova stores for the community: every feature's settings, member XP and activity records, moderation records, the knowledge base, buffered messages, the team and the community itself. You type the community's name to confirm. It cannot be undone, an active plan is not refunded, and payment references are kept for accounting. Members delete their own personal data by asking Nova _"delete my data"_. > [!NOTE] > **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](https://zeroauthoritydao.ai/docs/nova/community/pulse.md). 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. *** ## Your team One person no longer has to run the dashboard alone. The **Team** card lets a community's owner and admins give other people access to the same page. | | Owner | Admin | Moderator | | --- | --- | --- | --- | | See the dashboard, usage and leaderboard | ✓ | ✓ | ✓ | | Edit feature settings and moderator pings | ✓ | ✓ | ✓ | | [Nova Soul](https://zeroauthoritydao.ai/docs/nova/community/soul.md) persona and custom bot | ✓ | ✓ | view only | | Activation codes, linking and unlinking servers/groups | ✓ | ✓ | – | | Invite and remove moderators, see the activity log | ✓ | ✓ | – | | Invite, promote and remove admins | ✓ | – | – | | Transfer ownership | ✓ | – | – | **Seats:** 3 on Free, 10 on Community PRO. The owner, each member and each pending invite take one seat. If a community drops back to Free above the cap, nobody is removed; you just can't add more. Two ways to add someone: 1. **Invite link** — press **Invite**, pick a role and send the link. It is single-use (one link per person), expires after 7 days and is shown only when you create it. The person signs in (any method) and joins. The Team card lists each link as not used yet, used (and by whom), revoked or expired. 2. **Add from your server or group admins** — the card lists the people who already administer your linked Discord server or Telegram group. One click adds them, and Nova messages them when it can. Their access starts when they sign in to Nova with that Discord or Telegram account. A shared community shows up in the picker with the role beside its name. Anyone can leave a team from their own row, and every change made from the dashboard is listed under **Show recent activity** with who made it. > [!NOTE] > **Dashboard roles and chat permissions are separate.** A dashboard moderator gets no extra powers in chat, and a server or group admin gets no dashboard access until they are added. In chat, Nova still checks whether you are an admin of the 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](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md). Prefer talking? Everything on this page has a chat equivalent — *"@Nova guardian status"*. The web panel is the overview; the conversation is the shortcut. --- id: nova/plans title: "Premium" description: "Upgrade your Nova experience with higher limits, exclusive alert types, and advanced AI features." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/plans related: [nova, nova/plans/community-pro] tokens: 1556 --- # Premium Personal Premium raises your own alert limits, AI allowance and server count and unlocks sniper and whale alerts. Covers the Free vs Premium table, how the AI allowance works and how to subscribe. > [!NOTE] > 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](https://zeroauthoritydao.ai/docs/nova/plans/community-pro.md)** — a separate, per-community plan. *** ## Plans | Plan | Price | Duration | | ----------- | ------------------ | --------- | | **Monthly** | **$1.90** | 30 days | | **Yearly** | **$14.90** | 365 days | Billed as a one-time on-chain payment. Renew anytime — additional purchases extend your expiration date. The yearly plan costs less than twelve months. **Accepted tokens:** USDh, USDCx, aeUSDC, STX, and sBTC. Stablecoins pay the exact USD price; STX and sBTC are quoted at the live market price. *** ## 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) | 3 addresses | 300 addresses | | **Custom wallet labels** | -- | Yes | | **Contract deployment alerts** | -- | Yes | | **New token pair alerts** | -- | Yes | | **Whale transfer alerts** | -- | Yes | | **AI usage allowance** (one allowance for Discord, Telegram, the widget and the Nova web chat) | Standard | 5x larger | | **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 | | **Malicious contract alerts** | 1 | 3 | | **Active alerts per server / group** | 10 | 20 | | **Daily notification cap** | 500 | 10,000 | | **[Nova Scout](https://zeroauthoritydao.ai/docs/nova/scout.md)** (opportunity digest) | Included | Included | The daily notification cap resets at **00:00 UTC**. In a **Community PRO** server or group, your messages to Nova there draw from the community's pool instead of your own allowance — see [Nova Chat](https://zeroauthoritydao.ai/docs/nova/community/chat.md). *** ## Your AI Usage Allowance How much you can ask Nova is an allowance, not a message count: a long research answer uses more of it than a quick price check. Nova shows it as two percentages. | Window | What it covers | | --- | --- | | **Session** | Your use over the last 5 hours | | **Week** | Your use over the last 7 days | Both windows roll: there is no reset time to wait for, your use simply frees up as it gets older. When one is full, Nova tells you about how long until it has room again. Only real answers use the allowance — clarifying questions, short acknowledgements, and error notices are free. See your percentages any time with `/premium` on Discord or Telegram, in the widget's account menu, or on your [Dashboard](https://nova.zeroauthoritydao.com/dashboard). > */premium* *** ## 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) | — | > [!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. *** ## How to Subscribe 1. Use `/premium` on Discord or Telegram — you'll see the Free vs Premium comparison, the price, and an **Upgrade** button. Or go straight to [Plans](https://zeroauthoritydao.ai/plans). 2. Sign in on the premium page and link your Discord / Telegram accounts. 3. Complete the on-chain payment. 4. Your Premium status activates automatically. *** ## 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. --- id: nova/plans/community-pro title: "Nova Premium for Communities" description: "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." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/plans/community-pro related: [nova/plans] tokens: 2650 --- # Nova Premium for Communities Community PRO is one paid plan for a whole Discord server plus Telegram group that raises every community feature's budget. Covers what each tier includes, how to pay and activate with a code, and usage tracking. It is a separate thing from [personal Premium](https://zeroauthoritydao.ai/docs/nova/plans.md): 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** | Free | **$9.90/month** or **$99/year** | Custom | | **Blockchain Q&A + basic stats** | ✅ | ✅ | ✅ | | **🛡️ [Guardian](https://zeroauthoritydao.ai/docs/nova/community/guardian.md)** (anti-scam shield) | 20 AI scans/day | ✅ **500 AI scans/day** | ✅ | | **🪙 [Community Roles](https://zeroauthoritydao.ai/docs/nova/community/roles.md)** (Discord roles for holders and for levels) | 5 rules, weekly re-check | ✅ **30 rules, daily re-check, roles for time in the server, activity and holding time** | ✅ | | **🌐 [Language Moderation](https://zeroauthoritydao.ai/docs/nova/community/language-moderation.md)** (per-channel language rules) | 50 AI checks/day | ✅ **500 AI checks/day** | ✅ | | **📊 [Pulse](https://zeroauthoritydao.ai/docs/nova/community/pulse.md)** (mod copilot) | Hourly question sweeps, 25 scanned/day | ✅ **15-min sweeps, daily brief + Concierge auto-answer (150/day)** | ✅ | | **📚 [Nova Knowledge](https://zeroauthoritydao.ai/docs/nova/community/pulse.md)** (KB + website/repo/contract imports) | — | ✅ **500 docs · 25 imports/week** | ✅ | | **☀️ [Community GM](https://zeroauthoritydao.ai/docs/nova/community/gm.md)** (daily "gm" greeting brief + sources) | ✅ | ✅ **+ custom instructions & web search (10/day)** | ✅ | | **🎮 [Community Games](https://zeroauthoritydao.ai/docs/nova/community/community-games.md)** (XP, leaderboards, mod-run games, giveaways) | XP, weekly leaderboard & giveaways | ✅ **+ 25 AI games/week** (mod-run trivia/games, AI recap) | ✅ | | **🍪 [Daily community snacks](https://zeroauthoritydao.ai/docs/nova/community/snacks.md)** | Every 3 days | ✅ **Daily + custom instructions** | ✅ | | **📡 [Nova Relay](https://zeroauthoritydao.ai/docs/nova/community/relay.md)** (recap of the public chat, Discord + Telegram merged: one live pinned message or a daily post) | — | ✅ **Live or daily + 2 on demand/day** | ✅ | | **🌌 [Nova Warp](https://zeroauthoritydao.ai/docs/nova/community/warp.md)** (your Discord channel and Telegram group as one live chat) | — | ✅ | ✅ | | **✨ [Nova Soul](https://zeroauthoritydao.ai/docs/nova/community/soul.md)** (custom bot name & persona) | — | ✅ | ✅ | | **🤖 [Custom bot identity](https://zeroauthoritydao.ai/docs/nova/community/soul.md#custom-bot-identity-run-nova-as-your-bot)** (run Nova under your OWN Discord app / Telegram bot — your name & avatar everywhere) | — | ✅ | ✅ | | **💬 [Nova Chat](https://zeroauthoritydao.ai/docs/nova/community/chat.md)** (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 costs less** than twelve months 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. **Running out on PRO?** The owner or an admin can add an **AI Boost** from the usage meter on the [Community page](https://nova.zeroauthoritydao.com/community): each one adds a third of the monthly allowance for 30 days (the price is shown there). It is one payment from the Stacks wallet linked to your Nova account, nothing renews, and up to 6 can be active at once. ### 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 **[Plans](https://zeroauthoritydao.ai/plans)** and find **Community PRO** (it's separate from personal PRO). * 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**, tag Nova with the code. The dashboard gives you a ready-to-paste command for each platform: ``` @NovaBot activate NOVA-7F3K-2M9P (Discord) @NovaAITheBot activate NOVA-7F3K-2M9P (Telegram) ``` 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". ``` > [!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. ### 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](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md) 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). > [!WARNING] > **Personal Premium and a community plan don't overlap.** Personal Premium (see [Premium](https://zeroauthoritydao.ai/docs/nova/plans.md)) gates *your* alert limits and snipers; the community plan gates the *suite* for a server. Buying one doesn't grant the other. *** ## 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). --- id: nova/tools title: "Nova Tools" product: nova canonical: https://zeroauthoritydao.ai/docs/nova/tools related: [nova, nova/tools/trending, nova/tools/supported-chains, nova/tools/stealth-buy, nova/tools/transaction-simulation, nova/tools/mempool-inspector] tokens: 2937 --- # Nova Tools Nova Tools is the catalog of Nova's blockchain tools, run from the web dashboard or by AI agents over MCP or REST with x402 payment. Lists every capability, which are free or paid, and rate limits. Nova Tools is a multi-chain blockchain toolkit — deepest coverage of Bitcoin and Stacks, plus 60+ EVM networks, Solana, TON, Sui, Aptos, and Hyperliquid — with a growing set of community-ecosystem tools (Nova is both a blockchain assistant and a community assistant). Run tools from the [dashboard](https://nova.zeroauthoritydao.com/tools), or connect an AI agent via MCP or REST. > [!NOTE] > Tools are available to humans (dashboard) and AI agents (MCP / REST API with x402 payment). Nova Premium subscribers get unlimited access to all tools. *** ## How to read this catalog Nova ships **one tool per chain** for each capability, so the catalog is grouped by capability. Which chains each capability covers — plus the **community-ecosystem tools** (ZADAO, Emblem Vault) — lives in the [Supported Chains](https://zeroauthoritydao.ai/docs/nova/tools/supported-chains.md) coverage matrix. The live [Nova Tools dashboard](https://nova.zeroauthoritydao.com/tools) is the searchable, filterable source of truth. **Slug conventions.** Slugs are chain-prefixed, so the canonical slug is `-` — e.g. `stacks-token-price`, `evm-token-price`, `hyperliquid-token-price` — and you can filter a chain's whole toolset by its prefix. Community-ecosystem tools use `-` instead (e.g. `zadao-bounties`). Renamed Stacks/Bitcoin tools keep their **old slug as an alias**: the previous `POST /api/tools//run` URL and the `nova_` MCP id still resolve, so existing integrations keep working. - [Supported Chains](https://zeroauthoritydao.ai/docs/nova/tools/supported-chains.md) *** ## Token Intelligence | Capability | Slug pattern | Price | Description | | ---------- | ------------ | ----- | ----------- | | **Token Price** | `-token-price` | Free | Live USD price, 24h change, market cap, volume, liquidity, holder count (Hyperliquid adds perp mark/oracle price, funding rate, open interest) | | **Token Analytics** | `-token-analytics` | 💰 500 sats | AI deep-dive report: price, market data, holder distribution, volume, on-chain metrics, ecosystem context | | **Token Risk Check** | `-token-risk-check` | 💰 500 sats | Conservative rug-check / risk score (0–100): liquidity, holder concentration, mint/freeze authority, honeypot, owner powers, taxes | | **Token Holders** | `-token-holders` | Free | Holder distribution: top wallets, top-10/top-20 concentration %, supply breakdown, per-holder USD values | | **Token OHLC** | `-token-ohlc` | Free | Historical OHLC price candles over a chosen interval for charting & technical analysis | ## Wallet & Portfolio | Capability | Slug pattern | Price | Description | | ---------- | ------------ | ----- | ----------- | | **Wallet Lookup** | `-wallet-lookup` | Free | Aggregate portfolio: native + token holdings with USD values, NFTs, total value (Stacks adds BNS, staking, DeFi positions, P&L; Hyperliquid returns the perp account + spot balances) | | **NFT Holdings** | `stacks-nft-holdings` | Free | All Stacks (SIP-009) NFTs held by an address: collections, artwork, counts, BNS name | | **Address Activity** | `-address-activity` | Free | Recent transaction history with direction, asset, amount, and counterparty | | **DEX Trade History** | `-dex-trade-history` | 💰 500 sats | A wallet's recent swaps (DEX-agnostic): tokens, amounts, USD/gas, DEX source, tx hash | | **Wallet P&L** | `stacks-wallet-pnl` | Free | Realized profit-and-loss: per-token & aggregate winners vs losers across a wallet's trading history | ## DeFi & Markets | Capability | Slug pattern | Price | Description | | ---------- | ------------ | ----- | ----------- | | **Market Overview** | `-market-overview` | Free | Chain DeFi dashboard: TVL, DEX volume, top protocols, gainers/losers, trending pools (Hyperliquid: market-wide perps overview) | | **Zest Position** | `stacks-zest-position` | Free | Zest lending position: supplied/borrowed assets, interest, APYs, USD values, health factor | | **Zest Markets** | `stacks-zest-markets` | Free | Zest market overview: supply/borrow APY, TVL, utilization, LTV & liquidation threshold per asset | | **DeFi LP Positions** | `stacks-defi-lp-positions` | Free | Velar + Bitflow LP positions: pool pair, underlying amounts, USD value, pool share | | **DeFi Pools** | `stacks-defi-pools` | Free | Liquidity pools across DEXes: filter by token, sort by TVL/volume/APY | | **Whale Watch** | `stacks-whale-watch` | Free | Large trades on Stacks DEXes: big buys/sells, net flows, whale sentiment by timeframe | | **Trader Stats** | `stacks-trader-stats` | Free | Market-wide trading stats over a timeframe: active traders, trade counts, volume | ## Derivatives & Perps | Capability | Slug | Price | Description | | ---------- | ---- | ----- | ----------- | | **Funding Rates** | `hyperliquid-funding` | Free | Perp funding rates: all coins ranked by magnitude, or one coin's rate + predicted next funding across venues (Hyperliquid vs Binance vs Bybit) + ~24h history | | **Order Book** | `hyperliquid-orderbook` | Free | Live L2 order book: best bid/ask, mid, spread, liquidity within 1% of mid, top price levels | ## Contract Inspection | Capability | Slug pattern | Price | Description | | ---------- | ------------ | ----- | ----------- | | **Contract Scanner** | `-contract-scanner` | 💰 500 sats | AI security audit of verified source (proxy-aware): access control, asset flows, upgradeability, reentrancy/rug patterns | | **Contract Reader** | `-contract-reader` | Free | Smart-contract explorer: functions, variables, events, inline read-only calls (EVM is proxy-aware) | | **Contract Diff** | `stacks-contract-diff` | Free | Compare two Stacks contracts: functions/maps/vars added, removed, or changed; new admin fns highlighted; optional source diff | | **Program Read** | `solana-program-read` | Free | Read a Solana account/program state: owner, executable, balance, decoded SPL/system/stake | | **Calldata Encoder** | `-encode-calldata` | Free | Build ready-to-sign call data from plain args (inverse of the tx decoder). Read-only — never signs or broadcasts | ## Transactions & Network | Capability | Slug pattern | Price | Description | | ---------- | ------------ | ----- | ----------- | | **Transaction Decoder** | `-tx-decoder` | Free | Decode any tx: status, function summary, balance changes, events, gas/fee, error diagnosis | | **Transaction Simulation** | `-tx-simulate` | Free | Dry-run a transfer / swap / contract call without broadcasting: success-or-revert, asset changes, real fees, honeypot check ([guide](https://zeroauthoritydao.ai/docs/nova/tools/transaction-simulation.md)) | | **Stacks Network** | `stacks-network` | Free | Block height, PoX stacking cycle, mempool stats, server version | | **Mempool Inspector** | `-mempool-inspector` | Free | Congestion snapshot, per-address pending txs, or a per-tx "stuck" diagnosis ([guide](https://zeroauthoritydao.ai/docs/nova/tools/mempool-inspector.md)) | | **Stacking Info** | `stacks-stacking-info` | Free | PoX cycle details + per-address stacking: locked STX, unlock cycle, solo/pool, stSTX/liSTX | | **Bitcoin Fees** | `bitcoin-fees` | Free | Mempool fee rates with cost estimates for typical tx sizes and congestion assessment | | **Bitcoin Network Stats** | `bitcoin-network-stats` | Free | Block height, difficulty & next retarget, hashrate, mempool backlog | | **Bitcoin Mining Stats** | `bitcoin-mining-stats` | Free | Mining-pool distribution & hashrate over a window: blocks, difficulty, top 10 pools | | **Bitcoin Lightning Stats** | `bitcoin-lightning-stats` | Free | Lightning Network overview: capacity, channels, nodes, avg channel size, growth | | **Stacks SIP Updates** | `stacks-sip` | Free | Recent Stacks Improvement Proposal governance updates: title, status, link, date | ## Identity & Addresses | Capability | Slug pattern | Price | Description | | ---------- | ------------ | ----- | ----------- | | **BNS Resolver** | `stacks-bns-resolver` | Free | Resolve a Stacks address to its BNS identity: primary name, all names, namespace, profile | | **BNS Bulk Resolve** | `stacks-bns-bulk-resolve` | Free | Resolve up to 25 addresses to primary BNS names at once → `{ address: name }` map | | **Bitcoin Address** | `bitcoin-address` | Free | BTC balance, tx count, Ordinals, BRC-20, Runes, Sats Names. Legacy / SegWit / Taproot | ## Bitcoin Meta-Protocol | Capability | Slug pattern | Price | Description | | ---------- | ------------ | ----- | ----------- | | **Inscription Info** | `bitcoin-inscription-info` | 💰 500 sats | Single Ordinals inscription by id: number, content type/size, sat rarity, genesis block, owner | | **Ordinals Collection** | `bitcoin-ordinals-collection` | 💰 500 sats | Ordinals collection by Best-In-Slot slug: metadata + supply/market stats | | **Runes Info** | `bitcoin-runes-info` | 💰 500 sats | Runes token by name: id, symbol, divisibility, supply, mint terms/progress, top holders | | **BRC-20 Info** | `bitcoin-brc20-info` | 💰 500 sats | BRC-20 token by ticker: supply, deployer, deploy time, holder count, top holders | ## News & Digest | Capability | Slug pattern | Price | Description | | ---------- | ------------ | ----- | ----------- | | **Chain News** | `-news` | Free | Latest ecosystem headlines per chain (Bitcoin, Stacks, EVM, Solana, TON, Sui, Aptos), combining market and protocol-development sources | | **Stacks Daily Digest** | `stacks-digest` | Free | Daily ecosystem digest (9 AM UTC): dev updates, DeFi activity, community highlights. No args = today; `mode: date` for a past day, `mode: history` for a list | ## Trading | Capability | Slug | Price | Description | | ---------- | ---- | ----- | ----------- | | **Stealth Buy** `BETA` | `stacks-stealth-buy` | 💰 x402 | Buy a token without it being tied to your main wallet in charts/feeds — fresh temp wallet + split orders (not anonymous). **Beta — moves real funds; read the guide first** | - [Stealth Buy guide](https://zeroauthoritydao.ai/docs/nova/tools/stealth-buy.md) *** ## For Humans 1. Go to [Nova Tools](https://nova.zeroauthoritydao.com/tools) 2. Select a tool and fill in the input form 3. **Premium users**: Click "Run Tool" — results appear immediately 4. **Non-premium users**: Click "Run Tool" — pick a payment method (STX, sBTC, or USDCx), approve in your wallet, and results appear after payment. If tool execution fails after payment verification, your wallet is never charged — see the [x402 guide](https://zeroauthoritydao.ai/docs/build/x402.md) *** ## For AI Agents 1. **MCP Server** — `npx @nova/mcp-server` or connect to `https://nova.zeroauthoritydao.com/mcp` 2. **REST API** — `POST /api/tools/:slug/run` with x402 inline payment 3. **Discovery** — `GET /.well-known/agent.json` (agent manifest), `GET /api/tools/openapi.json` (OpenAPI spec), `GET /llms.txt` (llms.txt index) - [Using Nova Tools with Agents](https://zeroauthoritydao.ai/docs/build/nova-tools-for-agents.md) - [x402 Payment Integration](https://zeroauthoritydao.ai/docs/build/x402.md) *** ## Trending & Usage Stats See which tools the community uses most, with week/month/all-time trends and a REST-vs-MCP breakdown: [Trending & Usage Stats](https://zeroauthoritydao.ai/docs/nova/tools/trending.md). *** ## Pricing | Access Level | Paid Tools | Free Tools | | ------------ | ---------- | ---------- | | **Nova Premium** | Free, unlimited | Free, unlimited | | **Dashboard user** (non-premium) | x402 payment per use | Free, rate-limited | | **AI agent** (Stacks address) | x402 payment per use | Free, rate-limited | **Rate limits:** identified agents (x402 / wallet-identified): **10 req/min, 240 req/hour**. Anonymous IPs: **5 req/min, 120 req/hour**. **Accepted payment tokens:** STX, sBTC, USDCx — all on Stacks mainnet. > [!NOTE] > Get [Nova Premium](https://nova.zeroauthoritydao.com/premium) for unlimited access to all current and future tools. --- id: build/nova-tools-for-agents title: "Using Nova Tools with AI Agents" description: "Nova's tools are available to AI agents via the Model Context Protocol (MCP) and a standard REST API with x402 inline payments on Stacks mainnet." product: nova canonical: https://zeroauthoritydao.ai/docs/build/nova-tools-for-agents related: [build] tokens: 806 --- # Using Nova Tools with AI Agents Explains how AI agents connect to Nova Tools over MCP or REST, discover tools, which callers pay per call with x402, and the rate limits for identified and anonymous agents. > [!NOTE] > No API keys, no subscriptions, no registration. Free tools run subject to rate limits; paid tools are paid per request via x402 — see the [x402 Payment Guide](https://zeroauthoritydao.ai/docs/build/x402.md) for payment mechanics, accepted tokens, and safety guarantees. --- ## Connecting ### Option 1: MCP Server (Recommended) Install the Nova MCP server to give your agent native tool access: ```bash npx @nova/mcp-server ``` Or connect directly via Streamable HTTP: ``` https://nova.zeroauthoritydao.com/mcp ``` **Environment variables** (optional): | Variable | Default | Description | |----------|---------|-------------| | `NOVA_API_URL` | `https://nova.zeroauthoritydao.com` | Nova API base URL | | `AGENT_STACKS_ADDRESS` | — | Your Stacks address, sent as identity for the higher agent rate limits | ### Option 2: REST API (Direct) Call tool endpoints directly with standard HTTP: ```bash curl -X POST https://nova.zeroauthoritydao.com/api/tools/stacks-token-analytics/run \ -H "Content-Type: application/json" \ -d '{"input": {"token": "WELSH"}}' ``` Paid tools return **HTTP 402** with payment requirements — the [x402 Payment Guide](https://zeroauthoritydao.ai/docs/build/x402.md) covers how to complete payment and retry. --- ## Tool Discovery The full catalog (50+ tools across Stacks, Bitcoin, EVM, Solana, TON, Sui, Aptos, Hyperliquid, and community ecosystems) is in the [Tools catalog](https://zeroauthoritydao.ai/docs/nova/tools.md). Machine-readable listings: | Endpoint | What it returns | |----------|-----------------| | `GET /api/tools` | Tool list with slugs, input schemas, and pricing | | `GET /.well-known/agent.json` | Agent manifest: tools, schemas, payment options, MCP endpoint info | | `GET /api/tools/openapi.json` | OpenAPI spec | | `GET /llms.txt` | llms.txt index | Over MCP, call `tools/list` — every tool is auto-discovered with full input schemas and pricing. --- ## Payment Model | Caller Type | Paid Tools | Free Tools | |-------------|-----------|------------| | **Nova Premium** (JWT) | Free within the monthly included-calls limit | Free, unlimited | | **Identified agent** (Stacks address) | x402 payment per call | Free, rate-limited | | **Anonymous** (IP only) | x402 payment per call | Free, stricter rate limits | Payment mechanics — headers, the 402 flow, accepted tokens, errors, and the verify → execute → settle safety guarantee — live in the [x402 Payment Guide](https://zeroauthoritydao.ai/docs/build/x402.md). --- ## Rate Limits | Caller Type | Limit | |-------------|-------| | Identified agent (x402 / wallet-identified) | **10 req/min, 240 req/hour** | | Anonymous (per IP) | **5 req/min, 120 req/hour** | Exceeding limits returns **429 Too Many Requests** (never 402). Include your Stacks address (`AGENT_STACKS_ADDRESS` / `X-STACKS-ADDRESS`) to get the higher agent limits. --- ## Example: Full Agent Flow 1. **Discover tools**: `GET /.well-known/agent.json` 2. **Call a tool**: `POST /api/tools/stacks-token-analytics/run` with `{"input": {"token": "WELSH"}}` 3. **Receive 402**: parse the `payment-required` header for payment options 4. **Sign payment** and **retry** with the `payment-signature` header ([details](https://zeroauthoritydao.ai/docs/build/x402.md)) 5. **Receive results**: tool output in the body, settlement receipt in the `payment-response` header --- id: nova/tools/trending title: "Trending Tools & Usage Stats" description: "See which Nova tools the community is actually using. The Tools page now shows a live Trending Tools panel — a ranked, real-time view of the most-used tools across both the REST API and the MCP server." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/tools/trending related: [nova/tools] tokens: 614 --- # Trending Tools & Usage Stats The Trending Tools panel ranks the most-used Nova tools by week, month or all time, with trend arrows and the REST vs MCP split. Aggregate only; also available at GET /api/tools/stats. > [!NOTE] > Usage stats cover the **Tools Platform** — the tools Nova serves externally via the dashboard, REST API, and MCP. They count successful tool runs only. Nova's in-chat conversational abilities (Telegram/Discord/widget) are separate and not included here. *** ## What You'll See | Element | Description | | ------- | ----------- | | **Ranked tools** | The most-used tools for the selected period, with an animated usage bar | | **Time range** | Toggle between **Week**, **Month**, and **All-time** | | **Trend arrows** | Week-over-week change (▲ up / ▼ down) vs the previous equal-length period | | **REST · MCP split** | What share of each tool's usage came via the MCP server vs the REST API | | **Headline totals** | Total runs, unique callers, and success rate for the period | | **Daily sparkline** | A compact chart of daily activity across the range | | **Card badges** | Tools are flagged **★ Most used** or **🔥 Trending** directly on their cards | *** ## How Trending Is Calculated - **Most used** — ranked purely by number of successful runs in the selected period. - **Trending** — a tool whose usage grew meaningfully versus the previous equal-length period (e.g. this week vs last week). - To keep things honest, a tool needs a **minimum volume** before a trend percentage is shown — so a tool going from 1 → 3 calls won't be labelled "+200% 🔥". Low-traffic tools simply show no arrow. - **All-time** has no trend arrows (there's no prior period to compare against). > [!TIP] > Numbers refresh every few minutes. They reflect **successful** runs only — failed or abandoned attempts are excluded so the rankings aren't inflated by retries. *** ## Privacy The public trending view is **aggregate only**. It never exposes who called a tool: - ✅ Shown: tool name, run counts, REST/MCP split, trends, success rate, unique-caller **count**. - ❌ Never shown publicly: caller wallet addresses, IP addresses, or revenue. Caller-level detail and revenue are visible **only** to platform admins in the internal dashboard. *** ## For Builders Want the raw numbers? The same aggregate data powers a public endpoint: ``` GET /api/tools/stats?range=week|month|all ``` It returns ranked per-tool usage, headline totals, and a daily series — all aggregate, no identities. Responses are cached for a few minutes. The **MCP vs REST split** is the quickest way to see what agents lean on versus what people run from the dashboard. --- id: build/x402 title: "x402 Payment Integration Guide" description: "This page covers the payment mechanics for Nova Tools: headers, the 402 flow, accepted tokens, errors, and the facilitator." product: nova canonical: https://zeroauthoritydao.ai/docs/build/x402 related: [build] tokens: 1554 --- # x402 Payment Integration Guide Explains how paying for Nova Tools with x402 works: the three payment headers, the 402 flow step by step, STX, sBTC and USDCx on Stacks mainnet, error codes and the AIBTC facilitator. This page covers the payment **mechanics** for Nova Tools: headers, the 402 flow, accepted tokens, errors, and the facilitator. For how to connect an agent, discover tools, and the rate limits, see [Using Nova Tools with AI Agents](https://zeroauthoritydao.ai/docs/build/nova-tools-for-agents.md). > [!NOTE] > x402 is an HTTP-native payment protocol. Payment happens inline with the API call — no pre-registration, no API keys, no subscriptions. --- ## How It Works The x402 protocol uses three HTTP headers to negotiate payment: | Header | Direction | Content | |--------|-----------|---------| | `payment-required` | Server → Client (402 response) | Base64-encoded payment requirements | | `payment-signature` | Client → Server (retry request) | Base64-encoded signed payment | | `payment-response` | Server → Client (200 response) | Base64-encoded settlement receipt | ### Flow Diagram ``` Client Server AIBTC Facilitator │ │ │ │─── POST /api/tools/:slug/run ──────>│ │ │ │ │ │<── 402 + payment-required header ───│ │ │ │ │ │ (client signs tx in wallet) │ │ │ │ │ │─── POST /run + payment-signature ──>│ │ │ │─── POST /verify ──────────────>│ │ │<── { isValid: true } ─────────│ │ │ │ │ │ (executes tool) │ │ │ │ │ │─── POST /settle ──────────────>│ │ │<── { success, txid } ─────────│ │ │ │ │<── 200 + payment-response header ───│ │ ``` > [!TIP] > **Key safety feature**: the flow is **verify → execute → settle**. Settlement only happens AFTER successful tool execution — if the tool fails, payment is never settled and your wallet is not charged. --- ## Step-by-Step Each step is shown in one language (curl or TypeScript); the other works the same way. ### 1. Call the Tool ```bash curl -X POST https://nova.zeroauthoritydao.com/api/tools/stacks-token-analytics/run \ -H "Content-Type: application/json" \ -d '{"input": {"token": "WELSH"}}' ``` ### 2. Receive 402 Response ```http HTTP/1.1 402 Payment Required payment-required: eyJ4NDAyVmVyc2lvbiI6Mi4uLn0= Content-Type: application/json { "error": "PAYMENT_REQUIRED", "tool": { "slug": "stacks-token-analytics", "name": "Deep Token Analytics", "price_sats": 500 }, "accepts": [ { "scheme": "exact", "network": "stacks:mainnet", "asset": "STX", "amount": "5000", "payTo": "SP...", "maxTimeoutSeconds": 300, "display": "~0.0050 STX" }, { "scheme": "exact", "network": "stacks:mainnet", "asset": "SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4.sbtc-token", "amount": "500", "payTo": "SP...", "maxTimeoutSeconds": 300, "display": "500 sats" }, { "scheme": "exact", "network": "stacks:mainnet", "asset": "SP120SBRBQJ00MCWS7TM5R8WJNTTKD5K0HFRC2CNE.usdcx", "amount": "250", "payTo": "SP...", "maxTimeoutSeconds": 300, "display": "~$2.50" } ] } ``` ### 3. Sign Payment Build a Stacks transaction for the chosen token. It must be **sponsored** (`sponsored: true` — the AIBTC relay pays gas) with **zero fee** (`fee: 0n`). ```typescript import { makeSTXTokenTransfer } from '@stacks/transactions' const tx = await makeSTXTokenTransfer({ recipient: accept.payTo, amount: BigInt(accept.amount), senderKey: privateKey, network: 'mainnet', sponsored: true, fee: 0n, }) const paymentPayload = { txid: tx.txid(), asset: 'STX', amount: accept.amount, from: senderAddress, to: accept.payTo, network: 'stacks:mainnet', } const paymentSignature = btoa(JSON.stringify(paymentPayload)) ``` ### 4. Retry with Payment Repeat the request from step 1 with one extra header: `payment-signature: `. ### 5. Receive Results ```http HTTP/1.1 200 OK payment-response: eyJzdWNjZXNzIjp0cnVlLC4uLn0= Content-Type: application/json { "runId": "uuid", "status": "completed", "output": { ... } } ``` --- ## Supported Payment Tokens All payments are on **Stacks mainnet**. | Token | Contract | Unit | |-------|----------|------| | STX | Native | microSTX (1 STX = 1,000,000 uSTX) | | sBTC | `SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4.sbtc-token` | satoshis | | USDCx | `SP120SBRBQJ00MCWS7TM5R8WJNTTKD5K0HFRC2CNE.usdcx` | base units | --- ## Error Handling | HTTP Status | Error Code | Meaning | |-------------|-----------|---------| | 402 | `PAYMENT_REQUIRED` | Payment needed — see `accepts[]` for options | | 400 | `PAYMENT_INVALID` | Payment signature invalid or verification failed | | 400 | `VALIDATION_ERROR` | Tool input validation failed | | 401 | `IDENTITY_REQUIRED` | Must provide JWT or `X-STACKS-ADDRESS` for free tools | | 429 | `RATE_LIMITED` | Too many requests — wait and retry | --- ## AIBTC Facilitator Nova uses the [AIBTC x402 Sponsor Relay](https://x402-relay.aibtc.com) for payment verification and settlement. The facilitator: - Verifies payment signatures match requirements - Sponsors transaction gas fees (gasless for the payer) - Broadcasts transactions to Stacks mainnet - Returns settlement receipts with txid The facilitator is **non-custodial** — it can only execute transactions the client has already signed. --- ## Premium Users Nova Premium subscribers authenticate with a JWT and skip the x402 flow: paid tools run without per-call payment within the plan's monthly included-calls limit. --- id: nova/tools/supported-chains title: "Supported Chains" description: "Which Nova Tools capabilities run on which chain, read live from the tool catalog." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/tools/supported-chains related: [nova/tools] tokens: 73 --- # Supported Chains Coverage matrix showing which Nova Tools capabilities are live on Stacks, Bitcoin, EVM, Solana, TON, Sui, Aptos and Hyperliquid, plus the ZADAO and Emblem Vault ecosystem tools. Nova ships **one tool per chain** for each capability, named `-`. This page is the coverage matrix: which capabilities are live on which chain. For descriptions, see the [Nova Tools catalog](https://zeroauthoritydao.ai/docs/nova/tools.md); to try them, [Nova Tools](https://zeroauthoritydao.ai/tools). "EVM" covers 60+ EVM networks (Ethereum, Base, Arbitrum, Optimism, Polygon, BSC, Avalanche, …) through one tool family. Bitcoin/Stacks are non-EVM and have their own deep tooling; Solana is a separate surface. ## Capability × chain coverage | Capability | Stacks | Bitcoin | EVM | Solana | TON | Sui | Aptos | Hyperliquid | | ---------- | :----: | :----: | :----: | :----: | :----: | :----: | :----: | :----: | | Token Price | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Token Analytics 💰 | ✓ | — | ✓ | ✓ | — | — | — | — | | Token Risk Check 💰 | ✓ | — | ✓ | ✓ | — | — | — | — | | Token Holders | ✓ | — | ✓ | ✓ | — | — | — | — | | Token OHLC | ✓ | — | — | — | — | — | — | ✓ | | Wallet Lookup | ✓ | — | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | NFT Holdings | ✓ | — | — | — | — | — | — | — | | Address Activity | ✓ | — | ✓ | ✓ | ✓ | ✓ | ✓ | — | | DEX Trade History 💰 | ✓ | — | ✓ | ✓ | — | — | — | — | | Wallet P&L | ✓ | — | — | — | — | — | — | — | | Market Overview | ✓ | — | ✓ | ✓ | — | — | — | ✓ | | Zest Position | ✓ | — | — | — | — | — | — | — | | Zest Markets | ✓ | — | — | — | — | — | — | — | | DeFi LP Positions | ✓ | — | — | — | — | — | — | — | | DeFi Pools | ✓ | — | — | — | — | — | — | — | | Whale Watch | ✓ | — | — | — | — | — | — | — | | Trader Stats | ✓ | — | — | — | — | — | — | — | | Funding Rates | — | — | — | — | — | — | — | ✓ | | Order Book | — | — | — | — | — | — | — | ✓ | | Contract Scanner 💰 | ✓ | — | ✓ | — | — | — | — | — | | Contract Reader | ✓ | — | ✓ | — | — | — | — | — | | Contract Diff | ✓ | — | — | — | — | — | — | — | | Program Read | — | — | — | ✓ | — | — | — | — | | Calldata Encoder | ✓ | — | ✓ | — | — | — | — | — | | Transaction Decoder | ✓ | — | ✓ | ✓ | ✓ | ✓ | ✓ | — | | Stacks Network | ✓ | — | — | — | — | — | — | — | | Mempool Inspector | ✓ | ✓ | ✓ | — | — | — | — | — | | Stacking Info | ✓ | — | — | — | — | — | — | — | | Fees | — | ✓ | — | — | — | — | — | — | | Network Stats | — | ✓ | — | — | — | — | — | — | | Mining Stats | — | ✓ | — | — | — | — | — | — | | Lightning Stats | — | ✓ | — | — | — | — | — | — | | SIP Updates | ✓ | — | — | — | — | — | — | — | | Transaction Simulation | ✓ | — | ✓ | ✓ | — | — | — | — | | BNS Resolver | ✓ | — | — | — | — | — | — | — | | BNS Bulk Resolve | ✓ | — | — | — | — | — | — | — | | Address Lookup | — | ✓ | — | — | — | — | — | — | | Inscription Info 💰 | — | ✓ | — | — | — | — | — | — | | Ordinals Collection 💰 | — | ✓ | — | — | — | — | — | — | | Runes Info 💰 | — | ✓ | — | — | — | — | — | — | | BRC-20 Info 💰 | — | ✓ | — | — | — | — | — | — | | News | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | — | | Daily Digest | ✓ | — | — | — | — | — | — | — | | Stealth Buy `BETA` | ✓ | — | — | — | — | — | — | — | 💰 = paid tool. Everything else is free (rate-limited for non-premium). ## Open gaps - **Whale Watch** exists for Stacks only — `evm-whale-watch` / `solana-whale-watch` have no production-viable free data source (they need a paid Bitquery/Birdeye tier). Documented, not yet shipped. New chains extend the columns above without adding new rows to the catalog — each new chain reuses the existing capability set. ## Community & Ecosystem Nova is **both a blockchain assistant and a community assistant**. These tools surface off-chain community data and ecosystem-partner integrations (e.g. Emblem Vault) and are not tied to a single chain — their slugs are `-`. ### ZADAO | Tool | Capability | Price | | ---- | ---------- | ----- | | `zadao-bounties` | Bounties | Free | | `zadao-gigs` | Gigs | Free | | `zadao-grants` | Grants | Free | | `zadao-quests` | Quests | Free | | `zadao-docs` | Docs Search | Free | ### Emblem Vault | Tool | Capability | Price | | ---- | ---------- | ----- | | `emblem-vault-lookup` | Vault Lookup | Free | | `emblem-vault-create-guide` | Vault Create Guide | Free | | `emblem-collections` | Collections | Free | | `emblem-wallet-vaults` | Wallet Vaults | Free | --- id: nova/tools/stealth-buy title: "Stealth Buy" description: "Stealth Buy makes a token purchase look like organic market activity." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/tools/stealth-buy related: [nova/tools] tokens: 1568 --- # Stealth Buy Beta tool that buys a Stacks token through a fresh temporary wallet in several spaced orders on Bitflow, then sweeps tokens and leftover STX back to you. Hides attribution in charts, not your identity. Moves real funds. Stealth Buy makes a token purchase look like organic market activity. Instead of one large order from your wallet, it funds a fresh **temporary wallet** and executes your buy as a series of smaller, time-spaced orders — then sweeps everything (the tokens it bought **and** any leftover STX) straight back to your wallet. > [!WARNING] > **BETA — use small amounts.** Stealth Buy moves **real funds** through automated temporary wallets and is still under active testing. Start with a small test amount and don't commit more than you're comfortable risking while it's in beta. *** ## How It Works ``` You fund a temp wallet with STX → bot runs N spaced buys → bot sweeps tokens + leftover STX back to you ``` 1. **Pick a target and your parameters** — choose a curated target token, the total amount (USD), how many buys to split it into, the interval between them, and your slippage tolerance. 2. **Fund the temporary wallet** — Nova generates a brand-new wallet and shows you its address. You send **STX** to it covering both the swap budget **and** the gas reserve (so the wallet can pay its own transaction fees). 3. **The buys run automatically** — the bot executes each split as a swap (`STX → target token`) on **Bitflow**, spaced by your interval plus a small random jitter, with your slippage enforced as on-chain post-conditions. 4. **Any failed buy is retried** — if a split can't be placed or a swap reverts on-chain, the bot automatically re-buys it (where balance allows) so a run of *N* buys aims to land *N* confirmed buys. 5. **Everything is swept back** — when the buys finish, the bought tokens and any leftover STX are transferred back to the wallet you funded from. You always fund with **STX only** — it covers the swap amount *and* the gas for every split, so the temp wallet never runs out of fees mid-run. *** ## Target Tokens To guarantee a reliable swap route, Stealth Buy uses a **curated preset list** of targets that each have a verified STX trading pair. Free-text contract addresses are not accepted. | Target | Notes | | ------ | ----------------------------- | | WELSH | Verified STX pair | | LEO | Verified STX pair | | NOT | Verified STX pair | | sBTC | Verified STX pair | More targets are added over time as their liquidity and pairs are vetted. *** ## Parameters & Limits | Setting | Range / Rule | | ----------------- | ------------------------------------------------------- | | **Amount (USD)** | Minimum **$3** total, and at least **$1.50 per split** | | **Number of buys**| **1–20** splits | | **Interval** | **1–30 seconds** between buys (plus 5–10s random jitter)| | **Slippage** | **0.5%–10%** (enforced as on-chain post-conditions) | | **Funding token** | **STX only** (swap budget + `0.1 STX × number of buys` gas reserve; any unused gas is returned) | With Stacks fast blocks (~5–6 seconds), buys are *submitted* at your chosen interval and typically *confirm* within a block or two. Actual amounts received vary with slippage, price movement, and pool liquidity. *** ## Your Funds Are Protected Real funds are at stake, so the temp-wallet lifecycle is built to fail safe: - **Fresh wallet per run.** Every run uses a brand-new temporary wallet. Its private key is **AES-256-GCM encrypted at rest** and never logged. - **No double-spending.** Each split broadcasts **at most one** swap. A buy is only re-attempted when its previous transaction is *proven* failed on-chain (or never broadcast), so the run never spends more than you funded. - **Always swept back to you.** Bought tokens and leftover STX are returned to the wallet that funded the run. - **Key destroyed only after on-chain confirmation.** The encrypted key is wiped **only after two independent on-chain reads confirm the temp wallet is empty** — never merely because a sweep was broadcast. If anything is still pending, the key is kept. - **Automatic recovery.** A safety job runs every few minutes to recover funds from any wallet that didn't fully sweep, and in-progress runs are recovered if the service restarts. - **No charge on failure.** Payment uses the x402 two-phase flow — if execution can't proceed, funds sent to the temp wallet are swept back. > [!WARNING] > **It hides attribution, not your identity — this is not anonymity.** The buys originate from a fresh wallet, so they aren't directly attributed to your main wallet in charts, trade feeds, or copy-trade bots. But **both** the funding transfer (your wallet → temp wallet) **and** the return sweep (temp wallet → your wallet) are public on-chain and linkable, so anyone doing chain analysis can connect the buy back to you. Stealth Buy obscures the purchase from casual on-chain watchers and trading apps; it does **not** make it private. *** ## Using It From the Dashboard 1. Go to [Nova Tools](https://nova.zeroauthoritydao.com/tools) and open **Stealth Buy**. 2. Select a **target token** from the dropdown. 3. Enter the **amount (USD)**, **number of buys**, **interval**, and **slippage**. A live estimate shows your per-swap amount, gas reserve, total funding, and expected duration. 4. Click to start, then **send the requested STX** to the temp wallet address shown (swap budget + gas reserve). 5. Watch the progress panel as each buy executes — it shows a live split-by-split feed, the **return transactions** when funds are swept back, and a **"Track every transaction on Stacks Explorer"** link to the temp wallet so you can follow every pending and confirmed tx yourself. When finished, your tokens and any leftover STX arrive back in your wallet. In Discord/Telegram, Stealth Buy is **admin-only and DM-only** for security. The dashboard is the primary way to use it. *** ## Disclaimer Stealth Buy is a **beta** feature that interacts with live decentralized exchanges using real assets. Token swaps are subject to slippage, price movement, and available liquidity, and outcomes are not guaranteed. Use small amounts while the tool is in beta, and only commit funds you are comfortable risking. Stealth Buy does not provide trading or financial advice. --- id: nova/tools/transaction-simulation title: "Transaction Simulation (Pre-flight / Dry-run)" description: "Transaction Simulation lets you dry-run a proposed transaction before you ever sign it." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/tools/transaction-simulation related: [nova/tools] tokens: 986 --- # Transaction Simulation (Pre-flight / Dry-run) Dry-run a transfer, swap or contract call on Stacks, EVM or Solana against live state without signing or broadcasting, to see if it would succeed, what moves, the fee, and whether a token can be sold. Transaction Simulation lets you **dry-run a proposed transaction before you ever sign it**. You describe an action — a transfer, a swap, a contract or program call — and Nova runs it against **live on-chain state** and tells you what *would* happen, **without broadcasting anything and without moving any funds**. You get back: whether the transaction would **succeed or revert** (and the reason), the **asset changes** (who gains or loses what), the real **fee / gas / compute cost**, and — for tokens — a **honeypot / sellability** verdict. > [!TIP] > **Read-only and keyless.** Simulation never signs, never broadcasts, and never moves funds. The "from" address does **not** have to be yours — you can simulate from any address. No admin or DM required. > [!WARNING] > A simulation reflects **current chain state at the moment you run it**. It is not a guarantee the real transaction will behave identically later (state, prices, and liquidity move), and it is **not financial advice**. *** ## Supported Chains | Chain | What it covers | | ----- | -------------- | | **Stacks** | STX transfers (fee + balance check), Clarity contract calls (real evaluation of read-only functions; ABI validation + fee + static asset-movement scan for state-changing functions), SIP-010 sellability scan | | **EVM** (Ethereum, Base, Arbitrum, Optimism, Polygon, BSC, Avalanche) | Native + ERC-20 transfers, arbitrary contract calls (success/revert + gas), ERC-20 honeypot/sellability | | **Solana** | Native SOL + SPL transfers, arbitrary program instructions, fully-serialized transactions (e.g. a Jupiter swap), SPL sellability | *** ## What You Can Simulate | Action | What you provide | What you get | | ------ | ---------------- | ------------ | | **Transfer** | `from`, `to`, `amount` (+ token/mint for a token transfer) | success/revert, asset changes, fee/gas/compute | | **Contract / program call** | the contract (or program) + function/calldata + args | success or revert (+ reason), cost, asset movements where derivable | | **Sellability / honeypot** | `token` (+ a `holder` that owns it) | a verdict: **sellable**, **likely honeypot**, or **inconclusive** | *** ## Honeypot / Sellability Check The headline check. A *honeypot* token lets you **buy** but blocks you from **selling**. Transaction Simulation tests the sell side directly: - **EVM** — `eth_call`-executes a transfer of the holder's full balance against live state. If the transfer **reverts** or **returns false** (blacklist, pause, trading-disabled), the token is flagged as a likely honeypot. - **Solana** — simulates moving the SPL token out of the holder. A **frozen / non-transferable** token fails here. - **Stacks** — statically scans the SIP-010 `transfer` source for **pause flags, blacklist maps, and owner-only guards** that could block sells. For a full Clarity audit, pair it with the **Token Risk Check**. The sell test needs a **holder that actually owns the token** (for example, an address that just bought it). If the holder's balance is `0`, the result is **inconclusive** rather than a false "honeypot." On the current RPC tier, fee-on-transfer **tax %** is not measured on EVM. *** ## Example Prompts > "Simulate sending 0.5 ETH from 0xabc… to 0xdef… on Base — will it go through and what's the gas?" > "Dry-run calling `claim` on SP….my-contract — would it revert?" > "Is 0x… on Ethereum a honeypot? Can this wallet actually sell it?" > "Preview swapping this Jupiter transaction before I sign it." *(pass the serialized transaction)* > "What would this STX transfer cost and does my wallet cover it?" *** ## Using It From an Agent (x402 / MCP) The per-chain tools are exposed on the public Tools Platform as `stacks-tx-simulate`, `evm-tx-simulate`, and `solana-tx-simulate` (REST + MCP). Agents can call them to **verify sellability before relying on a token** or to **pre-flight a transaction before broadcasting it themselves**. --- id: nova/tools/mempool-inspector title: "Mempool Inspector" description: "The Mempool Inspector answers three everyday questions about pending (unconfirmed) transactions: how congested is the network right now, do I have anything stuck, and why hasn't my transaction confirmed." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/tools/mempool-inspector related: [nova/tools] tokens: 1280 --- # Mempool Inspector Check how congested Stacks, Bitcoin or EVM chains are, list an address's pending transactions, or diagnose why one transaction is stuck (fee too low, nonce gap, RBF/CPFP). Read-only. The Mempool Inspector answers three everyday questions about **pending (unconfirmed) transactions**: *how congested is the network right now*, *do I have anything stuck*, and *why hasn't my transaction confirmed*. It works on **Stacks**, **Bitcoin**, and **EVM** chains, each with the same three modes. > [!TIP] > **Read-only and keyless.** The Inspector only reads public mempool / RPC data — it never signs, broadcasts, or moves funds, and needs no admin or DM. Stacks (Hiro) and Bitcoin (mempool.space) are fully keyless. *** ## Supported Chains | Chain | Source | Notes | | ----- | ------ | ----- | | **Stacks** | Hiro API | Full mempool: stats, per-address pending txs, per-tx stuck diagnosis | | **Bitcoin** | mempool.space | Full mempool: stats, per-address pending txs, per-tx stuck diagnosis (incl. CPFP & RBF) | | **EVM** (Ethereum, Base, Arbitrum, Optimism, Polygon, BSC, Avalanche) | Alchemy RPC | Gas/fee snapshot, per-address pending **count** + nonce gap, per-tx stuck diagnosis | > [!NOTE] > **Solana is not covered.** Solana has no mempool — transactions go straight to the block leader, so there is nothing pending to inspect. *** ## The Three Modes You pick the mode by what you pass: | Mode | What you pass | What you get | | ---- | ------------- | ------------ | | **Stats** | *(nothing)* | A live congestion snapshot — how busy the network is and what fee gets you in right now | | **Address** | an `address` | That address's pending (unconfirmed) transactions | | **Transaction** | a `tx_id` / txid / tx hash | A **"stuck" diagnosis** for one transaction | On **EVM** you can also set `chain` (default `ethereum`; accepts `base`, `arbitrum`, `optimism`, `polygon`, `bsc`, `avalanche`, and aliases like `eth` / `arb` / `op` / `matic` / `bnb` / `avax`). *** ### Stats — "how congested is it right now?" Run it with no address or transaction to get a network-wide snapshot. - **Stacks** — total pending count, a breakdown by transaction type (token transfer / contract call / contract deploy), the **fee percentiles in STX** (p25/p50/p75/p95) needed to get in per type, and **how long** pending txs of each type have been waiting. - **Bitcoin** — pending count, total backlog in vMB, **projected blocks to clear**, a congestion level, the current **recommended fee rates in sat/vB** (next block / 30 min / 1 hour / economy), and the fee histogram. - **EVM** — current and **next-block base fee**, **priority-fee percentiles** (p10/p50/p90), suggested **low / medium / high** all-in gas prices in gwei, and the pending block's transaction count. On EVM, the suggested gas price = next-block base fee + a priority-fee percentile. The pending-block tx count is the node's view of the **next block**, not the entire mempool — public RPCs don't expose the full pending pool. ### Address — "do I have pending transactions?" Pass an address to see what's unconfirmed for it. - **Stacks** — outgoing and incoming pending txs with fee, nonce, type, and age. - **Bitcoin** — pending txs touching the address, each with fee, vsize, sat/vB rate, and net value direction (incoming / outgoing). - **EVM** — the **count** of pending transactions plus a **nonce-gap** read (confirmed vs pending nonce). Public RPCs don't expose the individual pending txs, so this is a count, not a listing. ### Transaction — "why is my tx stuck?" Pass a transaction id/hash for a stuck diagnosis. - **Stacks** — the tx's fee vs live mempool fee percentiles for its type (**underpriced / below median / competitive**) and a sender **nonce-gap** check — the most common reason a tx won't confirm regardless of fee. - **Bitcoin** — the tx's sat/vB rate, the **effective** rate including any **CPFP** child, a verdict vs current recommended tiers (competitive / low / underpriced), and whether **RBF** is signaled (so you know if you can bump it). - **EVM** — whether the tx is still pending, its max/effective gas price vs the current base fee and median priority, and a sender **nonce-gap** check (is it stuck behind an earlier-nonce tx?). A **nonce gap** means an earlier transaction from the same sender hasn't confirmed yet — everything behind it is blocked **regardless of fee** until that one confirms or is replaced. The Inspector flags this on Stacks and EVM. *** ## Example Prompts > "How congested is the Bitcoin mempool right now, and what sat/vB do I need for the next block?" > "What gas price do I need on Base at the moment?" > "Why is my Stacks transaction stuck? `0x…`" > "Do I have any pending transactions? `SP…`" > "Is this Bitcoin tx going to confirm or is the fee too low? ``" > "Check this Ethereum tx — is it stuck behind an earlier nonce? `0x…`" *** ## Using It From an Agent (x402 / MCP) The per-chain tools are on the public Tools Platform as `stacks-mempool-inspector`, `bitcoin-mempool-inspector`, and `evm-mempool-inspector` (REST + MCP, **free**). Agents can use them to **time a broadcast** (wait for low fees), **right-size a fee** before signing, or **detect and recover a stuck transaction** (bump via RBF/CPFP on Bitcoin, or replace-by-nonce on Stacks/EVM). --- id: legal/nova-privacy title: "Privacy Policy" description: "Last updated: October 22, 2026" product: nova canonical: https://zeroauthoritydao.ai/docs/legal/nova-privacy related: [legal] tokens: 3515 --- # Privacy Policy Privacy Policy for the Nova AI assistant, last updated October 22, 2026: what Nova collects, how long each community feature keeps it, third parties, no AI training on your messages, and your choices. Nova ("Nova", "the bot", "we") is an AI blockchain and community assistant operated by Zero Authority DAO — covering Bitcoin, Stacks, Ordinals, 60+ EVM chains, and Solana, alongside community engagement features for the servers and groups it serves. Nova is available on Discord, Telegram, and as an embeddable web widget. This policy explains what data Nova collects, how it is used, and the choices you have. > [!NOTE] > **TL;DR** — By default Nova only reads and responds to messages directed at it (DMs, @mentions, or replies to Nova). When the admins of a server or group turn on a community feature (scam protection, language rules, the moderator copilot, XP, the daily recap, linking its Discord and Telegram chats), Nova also processes the messages posted in **that** community to run that feature, as described below. Conversation history and message buffers are kept briefly, then automatically deleted. We never sell your data, and your messages are **never** used to train AI models. ## Data We Collect | Data | When | Why | |------|------|-----| | Platform user ID and username (Discord/Telegram) | When you interact with Nova | Identify your account, apply rate limits, link premium status | | Message content | When you DM Nova, @mention it, or reply to one of its messages | Generate a response to your request | | Messages posted in a community | Only in a server/group whose admins turned on a community feature, and only while it is on | Run that feature: scam screening (Guardian), per-channel language rules (Language Moderation), unanswered-question alerts and the moderator brief (Pulse), XP and leaderboards (Community Games), welcomes (Harbor), the recap for members, kept as one live pinned message or posted daily (Relay), showing each message of the linked Discord channel and Telegram group on the other platform, with its author's display name and, from Telegram, profile photo (Warp) | | Conversation history | During active conversations with Nova | Short-term context so follow-up questions make sense | | Server/channel IDs | When Nova is used in a server | Deliver responses and alerts to the right place, per-server rate limits | | Server roles (read-only) | When you use role-gated features (premium, quests, bounties) | Verify eligibility and assign/remove reward roles | | Wallet addresses, alert preferences | Only when you explicitly register them (e.g. wallet tracker, swap alerts) | Deliver the alerts you asked for | | Wallets you verified for roles, the date you joined the server, your level and the days you were active | Only in a Discord server whose admins set up Community Roles | Decide which roles you have earned there, and give or remove them | | Community activity metadata (message timestamps, lengths, reaction counts) | Only in the ZADAO community server/group | Power opt-in community engagement stats and leaderboards | Nova does **not** collect presence/online status or voice data. It does not read messages that are not directed at it, except in a community whose admins turned on one of the community features above (and for the ZADAO community stats described below). It never reads your DMs with other people. ## How Long We Keep It - **Conversation memory** is tiered and expires automatically: recent context is kept for ~6 hours, extended context for ~48 hours, and compressed conversation summaries for up to 30 days. After that it is deleted. - **Community features** (only where a community's admins turned them on): - **Guardian and Language Moderation** check each message as it is posted and do not keep it. A message that is flagged is the exception: up to 1,000 characters of it, with its author's ID and name, are kept as a moderation record for that community's moderators for up to 180 days, then deleted automatically (or sooner on request). - **Pulse** keeps recent messages (text and username) for up to 72 hours to find unanswered questions and write the moderators' daily brief, and join events for up to 30 days. - **Relay** keeps messages from **public channels only** (the ones every member of the community can already see) for as long as the period the recap covers plus 6 hours: up to 30 hours by default, and up to 7 days and 6 hours when the community's admins choose a 48-hour or 7-day recap. They are kept **without usernames**, only to write the recap. Private and staff channels are never read. The buffer is deleted at once when Relay is turned off (a live recap message is taken down too), and a message deleted in the chat is removed from it. The recaps themselves, which name nobody, are kept for up to 90 days. - **Warp** copies a message of the linked Discord channel or Telegram group to the community's other platform as it is posted, with the author's display name. A Telegram member's copies on Discord also show their Telegram profile photo: Nova reads it from Telegram when Discord asks for it and keeps it in memory for a few hours, never in the database; members who hide their photo get a plain avatar. A Discord member's copies on Telegram show an emoji picked for them in that server: Nova keeps which emoji belongs to which Discord member (ids only) and removes it after 90 days without a message. It stores no message text and no names: only which message became which copy, for up to 48 hours, so that an edit or a deletion follows it. The text of recent copies is held in memory for about an hour for the same reason, and never written to the database. A copy stays on the other platform like any message there, and is deleted when its original is deleted. If you asked Nova not to copy your messages, that choice is kept until you change it or delete your data. - **Community Games** keeps XP, levels and message counts per member, with no message text, while the feature is in use. The list of who entered a giveaway is deleted 90 days after it closes, and the giveaway with its winners after one year. - **Community Roles** keeps, per Discord server, the wallets you verified there, the roles Nova gave you, and the date it first saw your wallet hold what a role asks for (used to count how long you have held it). The date you joined the server is read from Discord when your roles are checked and is not stored. All of it is deleted when you leave the server or delete your data. - **Knowledge base**: what a community's admins add to it, including a question and the moderator's answer that resolved it, is kept until an admin removes the entry. - **Community Settings dashboard**: a log of which team member changed which setting is kept for up to two years. - **Harbor** keeps join and leave dates and the time of a newcomer's first message for about 180 days. - **Usage allowance**: how much of your AI allowance you have used is kept as a running total per 15 minutes, linked to your account and with no message content, and deleted after 8 days. - **Nova Chat (web app)** keeps the full transcript of each of your threads so you can reopen it, until you delete the thread. - **ZADAO community stats**: message *metadata* (author ID, timestamp, length — no text) is kept up to 365 days to compute weekly engagement stats. Message *text* in the ZADAO community is stored transiently for up to 14 days to power quality-based contribution scoring, then permanently deleted; only content-free scores and counts are kept. - **Alert subscriptions and registered wallet addresses** are kept until you remove them or stop using Nova. - **Account records** (user ID, premium status) are kept while you use Nova. - **Payment and security records** (community plan payments, and the log of wallet operations made by the Nova team) are kept as long as accounting and security require, the latter for up to two years. ## Where Data Is Stored Data is stored in a PostgreSQL database hosted on Amazon Web Services (AWS), encrypted in transit and at rest, with access restricted to the Nova operations team. ## Third Parties - **Anthropic (Claude API)** — messages you send to Nova are processed by Anthropic's Claude models to generate responses. Where a community feature is on, messages posted in that community may also be processed by Claude to run it (for example to classify a suspected scam or to write the daily recap, which is sent without usernames). This is inference only: per Anthropic's commercial API terms, this data is **not used to train AI models**. - **Blockchain data providers** (e.g. Hiro, mempool.space, market data APIs) — Nova queries these for on-chain and market data. Your personal data is not shared with them; only the addresses/tokens you ask about are queried. - **AWS** — infrastructure hosting, as described above. - **Discord and Telegram** — Nova receives your messages and profile data through their APIs and delivers its responses back through them. Where a community turned on Warp, a message posted in its linked chat is also delivered, with your display name, to the community's chat on the other platform. The platforms process your data independently under their own privacy policies ([Discord](https://discord.com/privacy), [Telegram](https://telegram.org/privacy)). We do not sell, rent, license, or share your personal data with advertisers, data brokers, or any other monetization service. Ever. We disclose personal data only to the service providers above, when required by law, or when you expressly direct us to. ## AI and Machine Learning Nova uses large language models (Anthropic Claude) to understand and answer your messages, and to run the community features a community's admins turned on. Your message content is used **only for inference** (generating the response, the moderation verdict or the recap). Neither we nor our model provider use your messages to train or fine-tune machine learning models. ## Your Choices - **Don't want Nova reading your messages?** Don't DM, @mention, or reply to it. Nova ignores all other messages, unless the admins of the server or group you are in turned on a community feature: ask them which ones are on. - **Community features:** admins can turn any of them off at any time, and can leave channels out of the Relay recap. To keep your own messages from being copied to a community's other platform by Warp, tell Nova _"don't warp my messages"_ (anywhere, DMs included). You can ask the community's admins or our team to delete what a feature stored about you. - **Community stats (ZADAO server only):** server admins can exclude channels from tracking, and you can ask a ZADAO admin or our team to exclude your account or delete your activity data. - **Delete your data yourself, at any time:** tell Nova _"delete my data"_ on Discord or Telegram (in a DM, or by mentioning it). Nova shows what will be deleted and asks you to type a confirmation phrase; once you do, it deletes your conversations and its memory of you, your alerts and trackers, your XP and activity records in every community, your verified wallets and your account with every identity linked to it. This is immediate and cannot be undone. Two things are kept: payment records, which we must keep for accounting and which are no longer linked to an identity, and content a community published as its own (for example a knowledge base entry), with your ID removed from it. Discord roles Nova gave you for tokens you hold are removed as part of it. If you own a community on Nova, hand it over or delete it first. - **Get a copy of your data:** sign in at [nova.zeroauthoritydao.com](https://nova.zeroauthoritydao.com) with the same Discord, Telegram, Google or wallet identity, open the Dashboard and use **Your data > Download a copy**. You get a file with everything stored about your account and the identities linked to it. The same card has **Delete my data**. - **Delete a community's data:** the owner of a community can delete everything Nova stores for it (every feature's settings and records in its server and group, and the community itself) from the [Community Settings dashboard](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md), under **Delete community data**. - **Correct your data, or ask us to do any of this for you:** ask in the ZADAO Discord ([discord.gg/zeroauthority](https://discord.gg/zeroauthority)) or contact the team. - **Remove Nova:** server admins can remove the bot at any time; per-server data is no longer collected from that point, and previously stored data expires per the retention schedule above. To remove it at once, the community's owner uses **Delete community data** before removing the bot. ## Your Rights Depending on where you live (e.g. GDPR, UK GDPR, CCPA/CPRA, LGPD), you may have the right to **access** the personal data we hold about you, have it **corrected**, have it **deleted**, **object to or restrict** its processing, and receive a **copy** of it. Access, a copy and deletion are built in: see "Your Choices" above. To exercise any other right, contact us through the channels below — we honor these requests for all users regardless of location, and we will never discriminate against you for exercising them. We also delete API data when it is no longer needed for Nova's stated functionality, when Nova is removed from a server, or when Discord or you request it, in line with the Discord Developer Terms of Service. ## Security & Breach Notification Data is encrypted in transit and at rest, and access is restricted to the Nova operations team. If a security incident results in unauthorized access to your personal data, we will notify affected users and the relevant platforms/authorities as required by applicable law. ## Children Nova is not directed at children under 13 (or the minimum age required by Discord/Telegram in your country), and we do not knowingly collect data from them. ## Changes We will update this page when our data practices change and update the "Last updated" date above. ## Contact Questions or data requests: reach the team in the [ZADAO Discord](https://discord.gg/zeroauthority) or via [zeroauthoritydao.com](https://zeroauthoritydao.com). --- id: legal/nova-terms title: "Terms of Service" description: "Last updated: October 12, 2026" product: nova canonical: https://zeroauthoritydao.ai/docs/legal/nova-terms related: [legal] tokens: 1839 --- # Terms of Service Terms of Service for the Nova AI assistant on Discord, Telegram and the web widget, last updated October 12, 2026: eligibility (13+), not financial advice, blockchain transactions, acceptable use and Premium. Welcome to Nova ("Nova", "the bot", "the service", "we"). Nova is an AI blockchain and community assistant operated by Zero Authority DAO — covering Bitcoin, Stacks, Ordinals, 60+ EVM chains, and Solana, alongside community engagement features. Nova is available on Discord, Telegram, and as an embeddable web widget. By adding Nova to your server or group, messaging it, or using any of its features, you agree to these Terms of Service. > [!NOTE] > **TL;DR** — Nova is an informational AI assistant, **not a financial advisor**. Blockchain data and AI answers can be wrong; always do your own research before acting on them. Don't abuse the bot, and remember that on-chain transactions are irreversible. If you don't agree with these terms, simply don't use Nova. ## 1. The Service Nova provides: - AI-powered answers about blockchain networks, tokens, wallets, NFTs, and market data - Configurable alerts and notifications (price, swaps, NFTs, wallets, whales, smart alerts) - Community engagement features (stats, leaderboards, quests, daily snacks) in participating servers - Optional premium features with higher limits Nova is provided "as is" and may change, gain, or lose features at any time without notice. ## 2. Eligibility You must be at least 13 years old (or the minimum age required by Discord or Telegram in your country) to use Nova. By using Nova you confirm you meet this requirement and that you also comply with the [Discord Terms of Service](https://discord.com/terms) and [Telegram Terms of Service](https://telegram.org/tos) where applicable. ## 3. Not Financial Advice > [!WARNING] > **Nothing Nova says is financial, investment, legal, or tax advice.** - Prices, market data, token analytics, and on-chain information are provided **for informational purposes only** and may be delayed, incomplete, or incorrect. - AI-generated responses can contain errors or "hallucinations." Always verify important information independently. - Cryptocurrency markets are volatile and risky. Any decision to buy, sell, swap, or hold digital assets is **yours alone**, and you bear full responsibility for it. ## 4. Blockchain Transactions Some Nova features interact with public blockchains (e.g. premium payments, transaction-related tools): - **Blockchain transactions are irreversible.** Neither Nova nor Zero Authority DAO can cancel, reverse, or refund a confirmed on-chain transaction. - You are solely responsible for verifying addresses, amounts, and transaction details before signing or sending anything. - Network fees, congestion, and failures of underlying blockchains are outside our control. - You are responsible for the security of your own wallets, keys, and funds at all times. ## 5. Acceptable Use You agree **not** to: - Use Nova for anything unlawful, including fraud, market manipulation, money laundering, or evading sanctions - Attempt to bypass rate limits, abuse free-tier limits with multiple accounts, or disrupt the service (spam, flooding, denial of service) - Attempt to extract Nova's system prompts, exploit the AI to produce harmful content, or probe/attack our infrastructure - Resell or rebrand Nova's responses or data feeds as your own service without permission - Use Nova to harass, scam, or harm other users - Use Nova in a way that violates the [Discord Terms of Service](https://discord.com/terms), [Discord Community Guidelines](https://discord.com/guidelines), or [Telegram Terms of Service](https://telegram.org/tos) We may rate-limit, restrict, or block users, servers, or groups that violate these terms, at our sole discretion. ## 6. Premium - Premium is billed as a **one-time on-chain payment** (in USDh, STX, or sBTC) for a fixed duration (monthly or yearly). It does not auto-renew. - Because payments are on-chain, **completed payments are non-refundable**, except where required by law. If something goes wrong with a payment (e.g. paid but premium did not activate), contact the team and we will make it right. - Premium limits and features may evolve over time; material reductions will be communicated in our community channels. ## 7. Privacy Our handling of your data is described in the [Privacy Policy](https://zeroauthoritydao.ai/docs/legal/nova-privacy.md). In short: Nova only reads messages directed at it, plus the messages of a community whose admins turned on a community feature, keeps conversation context briefly, and never sells your data or uses it to train AI models. ## 8. Third-Party Services & Platform Terms Nova relies on third-party platforms and data providers (Discord, Telegram, Anthropic, blockchain APIs, market data providers). We are not responsible for their availability, accuracy, or actions. Your use of those platforms is governed by their own terms. - These terms are an agreement **solely between you and Zero Authority DAO**. Discord, Telegram, and Anthropic are not parties to these terms and bear no responsibility for Nova. - Nothing in these terms supersedes, modifies, or overrides the [Discord Terms of Service](https://discord.com/terms) or [Telegram Terms of Service](https://telegram.org/tos). If anything here conflicts with a platform's terms, the platform's terms prevail with respect to your use of that platform. - Nova is an independent third-party application. It is **not affiliated with, endorsed by, or sponsored by** Discord Inc., Telegram, or Anthropic. ## 9. Intellectual Property Nova's name, branding, code, and documentation belong to Zero Authority DAO. You may use Nova's responses for your own personal or community purposes. Public blockchain data remains public. ## 10. Availability We aim to keep Nova online but do not guarantee uninterrupted service. Nova may be unavailable due to maintenance, upstream outages, platform issues, or other causes. Alerts and notifications are delivered on a best-effort basis — **do not rely on Nova as your only safeguard for time-sensitive or financially critical events.** ## 11. Disclaimer of Warranties The service is provided **"as is" and "as available"**, without warranties of any kind, express or implied, including fitness for a particular purpose, accuracy, or non-infringement. ## 12. Limitation of Liability To the maximum extent permitted by law, Zero Authority DAO and the Nova team shall not be liable for any indirect, incidental, consequential, or special damages — including lost profits, lost funds, lost data, or trading losses — arising from your use of (or inability to use) Nova, even if advised of the possibility of such damages. Our total aggregate liability for any claim relating to the service shall not exceed the amount you paid us for premium in the 12 months preceding the claim. ## 13. Termination You can stop using Nova at any time — remove the bot from your server or simply stop messaging it. We may suspend or terminate access for users or servers that violate these terms. Sections 3, 4, 11, 12, and 14 survive termination. ## 14. Changes to These Terms We may update these terms from time to time. The "Last updated" date above reflects the latest revision. Continued use of Nova after changes take effect constitutes acceptance of the updated terms. ## 15. Contact Questions about these terms: reach the team in the [ZADAO Discord](https://discord.gg/zeroauthority) or via [zeroauthoritydao.com](https://zeroauthoritydao.com). --- id: work/bounties title: "Bounty Onchain" description: "Overview of a bounty and templates" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties related: [work, work/bounties/create, work/bounties/nft-rewards, work/bounties/mint-a-badge, work/bounties/contribution-markets, work/bounties/analytics, work/bounties/redeem-funds, work/bounties/create-v1, work/bounties/sandbox-winners, work/bounties/select-winners, work/bounties/community-engagement] tokens: 1190 --- # Bounty Onchain A bounty pays a reward for a specific task, with funds locked in a smart contract and paid to the winner. Includes six bounty templates and the basic steps to create one. ## What is a Bounty? A bounty is a reward offered to individuals or teams for completing a specific task or project. Bounties are commonly used in open-source communities and software development to incentivize contributions and improvements. ## Why Onchain Bounties? advantages: 1. **Transparency:** All transactions and activities related to the bounty are recorded on the blockchain, providing a transparent and immutable history. This ensures that all participants can trust the process and verify outcomes. 2. **Security:** Smart contracts automate the distribution of rewards once the conditions are met, reducing the risk of fraud and ensuring that contributors receive their compensation promptly. 3. **Decentralization:** Onchain bounties remove the need for intermediaries, allowing for direct interaction between project owners and contributors. This enhances the efficiency and reduces costs associated with traditional bounty programs. ## Bounty Templates These templates provide a framework for users to define the scope, requirements, and rewards of their bounties, helping them attract suitable contributors. #### Bounty Templates 1. **Bug Fixing** * **Description**: Identify and fix bugs in existing software to enhance functionality and user experience. Contributors are expected to provide detailed documentation of the bug and the steps taken to resolve it. 2. **Create a Meme or Graphic** * **Description**: Create engaging visual content, such as memes, logos, or marketing materials, to enhance brand identity and communication. Designs should align with the brand’s style guidelines and target audience. 3. **Content Writing** * **Description**: Produce high-quality written content, including blog posts, articles, or website copy, to inform, engage, and attract readers. Content should be well-researched, original, and aligned with the brand’s voice and messaging. 4. **Social Media Management** * **Description**: Develop and implement social media strategies to increase brand awareness and engagement. Responsibilities include content creation, scheduling posts, interacting with the audience, and analyzing performance metrics. 5. **Security Audit** * **Description**: Conduct a comprehensive security audit of a codebase or system to identify vulnerabilities and recommend improvements. The audit should include detailed reports and actionable suggestions for enhancing security measures. 6. **Video Content** * **Description**: Create compelling video content that aligns with the brand’s objectives, whether for marketing, education, or entertainment. Videos should be well-scripted, professionally edited, and tailored to resonate with the target audience. Include storyboarding, filming, and post-production as necessary to produce high-quality video assets. ## Getting Started Welcome to the bounty platform! Here, anyone who has connected their wallet and authenticated can create a bounty to harness the power of decentralized collaboration. Follow the steps below to get started with creating your bounty: ![getting started on zeroauthority.xyz](https://zeroauthoritydao.ai/docs/img/994c1131e0b1.webp) *getting started on zeroauthority.xyz* #### Step 1: Connect Your Wallet Ensure your wallet is connected and authenticated to gain access to the bounty creation features. This step secures your transactions and interactions with the platform. #### Step 2: Create a Bounty Once authenticated, you can create a bounty by following these simple steps: 1. **Add a Title and Description:** * Give your bounty a clear and descriptive title. * Provide detailed information about the task or project you want contributors to complete. The more specific you are, the better your chances of attracting suitable contributors. 2. **Set the Total Reward Amount:** * Decide the total amount of cryptocurrency or tokens you wish to offer as a reward. This amount will be locked in a smart contract to ensure security and trust. 3. **Select an End Date:** * Determine the deadline for submissions. The bounty will be open for contributions until this date. 4. **Select a Winner:** * Before the end date, review submissions and select a winner. The smart contract will automatically send the funds to the winning contributor, ensuring a seamless and transparent reward distribution. #### Step 3: Notifications To stay informed about your bounty's progress: * **Enter Your Email:** * Provide your email address to receive notifications when your submission is posted onchain and when a winner is selected. #### Step 4: Engage with Contributors Interact with potential contributors, answer questions, and provide feedback to ensure your bounty is successful and completed to your satisfaction. --- id: work/bounties/create title: "Create a bounty on V2 beta" description: "A client posts a bounty for creators to participate onchain" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/create related: [work/bounties] tokens: 426 --- # Create a bounty on V2 beta Create a bounty on v2: pick or create a bounty hub, choose the bounty type, add details and post it onchain so the contract locks the funds. Select Winner later releases them. ![](https://zeroauthoritydao.ai/docs/img/490a310c895e.webp) ## ***Start the process*** ![](https://zeroauthoritydao.ai/docs/img/672a8400b089.webp) 1 Create or select the bounty hub where you want the bounty to be categorized 2 If you don't have a hub set up, create a new hub 3 To post a bounty, select the type of bounty 4 Post a bounty with all the relevant details (ideas) 5 Review and confirm details before you post bounty 6 Post bounty onchain to verify trustless & permissionless 7 Once bounty posted, all clients and creators can view and participate 8 To select a winner, go to the bounty and "Select Winner" button 9 Select the user who won the reward and the smart contract will release funds *** ## Walk through with screenshots 1 Create or select the bounty hub where you want the bounty to be categorized ![](https://zeroauthoritydao.ai/docs/img/760fc6cca41a.webp) 2 If you don't have a hub set up, create a new hub ![](https://zeroauthoritydao.ai/docs/img/2715866a6181.webp) 3 To post a bounty, select the type of bounty ![](https://zeroauthoritydao.ai/docs/img/5f2a61538841.webp) 4 Post a bounty with all the relevant details (ideas) ![](https://zeroauthoritydao.ai/docs/img/30e163334753.webp) 5 Review and confirm details before you post bounty ![](https://zeroauthoritydao.ai/docs/img/d9bb7d602c5a.webp) 6 Post bounty onchain to verify trustless & permissionless and the smart contract will lock up funds ![](https://zeroauthoritydao.ai/docs/img/9da9c4857251.webp) 7 Once bounty posted, all clients and creators can view and participate ![](https://zeroauthoritydao.ai/docs/img/42ee520f9126.webp) 8 To select a winner, go to the bounty and "Select Winner" button ![](https://zeroauthoritydao.ai/docs/img/2a14a275e25a.webp) 9 Select the user who won the reward and the smart contract will release funds ![](https://zeroauthoritydao.ai/docs/img/2b096bb5e6c9.webp) --- id: work/bounties/nft-rewards title: "NFT as a Bounty Reward" description: "A client posts a bounty for creators to participate onchain" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/nft-rewards related: [work/bounties] tokens: 232 --- # NFT as a Bounty Reward Offer an NFT instead of tokens as the prize: create a Single Winner bounty, choose NFT Reward and the NFT, set the end date, then Select Winner to send it. Zero Authority DAO ### Platform 1. Navigate to **Bounties** and click **Create Bounty**. 2. If your organization doesn’t already have a **Bounty Hub**:\ • Follow the prompt to **Create Bounty Hub**\ • Add your group or company name, branding, and details\ • Save to continue 3. Return to **Create Bounty**:\ • Add bounty title, description, and requirements\ • Select **Single Winner** as the bounty type 4. Scroll to the bottom of the reward section and select **NFT Reward**. 5. Choose the NFT you want to issue as the prize.\ • If needed, upload or select from your organization's hosted NFTs 6. Set the **End Date** for the bounty. 7. Once the bounty deadline passes, review submissions and **Select Winner** to automatically issue the NFT to them. ### Screenshots Post a bounty :: Type ![](https://zeroauthoritydao.ai/docs/img/709d9964b764.webp) Post a bounty :: NFT reward ![](https://zeroauthoritydao.ai/docs/img/1d002738ccdf.webp) --- id: work/bounties/mint-a-badge title: "Bounty + Mint A Badge" description: "Add a landing page for your bounty" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/mint-a-badge related: [work/bounties] tokens: 333 --- # Bounty + Mint A Badge Add a landing page to a new or existing bounty and upload a custom badge that the creator and participants can mint. Without a custom badge, default images are used. ### Procedure: Bounty + Badge #### 1. Go to the Bounty Landing Page * Navigate to the landing page for the individual bounty you are managing or participating in. #### 2. Upload a Badge (Optional) * On the landing page, you can upload a **custom badge** for participants to mint. * If you do not upload a custom badge, the platform will automatically use the **default images** for both desktop and mobile landing pages. #### 3. Minting a Badge You can mint a badge in two ways: * **When creating a bounty** → As the bounty creator, you may mint a badge during bounty setup. * **When participating in a bounty** → As a participant, you may mint a badge linked to your contribution. #### 4. Adding a Landing Page to an Existing Bounty * Go to the bounty you already created. * Select the **“Add Landing Page”** button. * Enter the following details: * **Heading** (main title for the page) * **Subheading** (supporting line) * **Description** (details about the bounty and context) #### 5. Confirm & Publish * Review the bounty details and associated badge. * Save and publish to make the badge available for minting by all relevant participants. *** #### Adding a Landing Page to a New Bounty ![](https://zeroauthoritydao.ai/docs/img/300dc11f3762.webp) #### Adding a Landing Page to an Existing Bounty ![](https://zeroauthoritydao.ai/docs/img/374776ce4eaa.webp) --- id: work/bounties/contribution-markets title: "Contribution Markets" description: "Structuring effort, attention, and reward in Zero Authority Bounties" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/contribution-markets related: [work/bounties] tokens: 1544 --- # Contribution Markets Bounties come in three levels by impact: Signal (up to 50 STX), Contribution (up to 200 STX) and Commitment (up to 500 STX). Pick the level that matches the effort and reach you want. **Zero Authority Bounties** are a decentralized system for coordinating attention, effort, and contribution without centralized enforcement. Rather than relying on permissions or hierarchy, the system uses transparent economic incentives to shape behavior and surface meaningful work. By analyzing historical STX bounty activity and formalizing observed patterns, Zero Authority Bounties are classified into three clear levels based on **Impact**, not subjective importance. This classification aligns incentives with expected effort, review load, and impact, allowing creators and contributors to self-coordinate with minimal friction. The three levels—**Signal**, **Contribution**, and **Commitment**—act as economic primitives. They provide predictable outcomes for creators, clear expectations for contributors, and a shared mental model across the ecosystem. *** ### Bounty Classification Table | Level | Level Name | Reward Cap (STX or Equivalent Community Tokens) | Expected Submissions | Typical Impact | | ----: | ---------------- | ----------------------------------------------- | -------------------- | --------------------------------------------------- | | L1 | **Signal** | **≤ 50 STX** | Low | Awareness, reach, narrative amplification | | L2 | **Contribution** | **≤ 200 STX** | Medium | Thoughtful work, experiments, partial builds | | L3 | **Commitment** | **≤ 500 STX** | High | Flagship work, core development, high-signal output | *Reward caps may be denominated in STX or equivalent value in approved community tokens.* *** ### Benefits of This Model This classification reduces ambiguity for bounty creators by directly linking reward size to expected participation and effort. It improves planning, sets realistic review expectations, and leads to more consistent outcomes across campaigns. For contributors, the system is legible and permissionless. Participants understand what level of effort is expected before engaging, which improves signal quality and reduces wasted work. For the broader ecosystem, incentives become standardized without being enforced. Behavior clusters naturally, guided by economics rather than rules. *** ### Level Summaries #### Signal (L1) Signal bounties are designed to maximize visibility and momentum. They reward quick, low-friction actions such as social posts, memes, or lightweight engagement. These bounties are best suited for announcements, launches, and narrative propagation, delivering strong reach relative to cost. *** #### Contribution (L2) Contribution bounties invite focused, intentional effort. Participants invest time and attention to produce thoughtful responses, designs, experiments, or partial implementations. This level balances reach and substance and is well suited for ideation, early development, and exploratory work. *** #### Commitment (L3) Commitment bounties signal seriousness. Rewards at this level imply clear scope, higher expectations, and more rigorous evaluation. These bounties surface high-signal contributors and are best used for core development, flagship initiatives, and work with long-term or reputational impact. *** ### Conclusion By formalizing **Signal**, **Contribution**, and **Commitment** as first-class bounty levels, Zero Authority turns incentives into infrastructure. Rewards do more than compensate work—they coordinate attention, filter effort, and build trust over time. The result is a system that remains decentralized, legible, and adaptive, while quietly guiding behavior toward higher-quality outcomes without relying on authority, permissions, or centralized control. *** ### 5 Examples of Bounty Creator Goals & Classification Bounty creators are not just buying work—they are shaping attention. The same system can support very different goals depending on which bounty level is chosen. Below are five common creator goals and how they naturally map to the **Signal / Contribution / Commitment** framework. **1. Increase Awareness or Narrative Reach**\ Goal: Get a message seen, repeated, and remembered.\ Best Fit: **Signal (L1)**\ Signal bounties excel here because low rewards encourage fast, high-volume participation. The creator optimizes for breadth rather than depth, accepting lightweight output in exchange for reach and momentum. **2. Collect Ideas, Feedback, or Early Experiments**\ Goal: Explore a problem space before committing resources.\ Best Fit: **Contribution (L2)**\ Contribution bounties attract participants willing to think, test, and articulate ideas. The reward level filters out low-effort noise while still encouraging diverse approaches and creative risk-taking. **3. Validate a Concept or Prototype**\ Goal: Pressure-test something real without full commitment.\ Best Fit: **Contribution (L2)**\ At this level, contributors are incentivized to engage seriously but not exhaustively. The creator gains meaningful signal—designs, proofs of concept, experiments—without the overhead of managing a full build. **4. Deliver Core or Production-Grade Work**\ Goal: Ship something that matters.\ Best Fit: **Commitment (L3)**\ Commitment bounties communicate seriousness through economics. The higher reward attracts fewer but more capable contributors, aligns expectations around scope and quality, and justifies deeper review and coordination. **5. Identify and Signal Trusted Contributors**\ Goal: Surface long-term collaborators and high-signal builders.\ Best Fit: **Commitment (L3)**\ Beyond output, these bounties function as reputation filters. Completing a Commitment bounty credibly signals reliability, skill, and alignment, creating durable trust without centralized vetting. Across all five goals, the key insight remains the same: **reward size is a coordination signal**. By choosing the correct bounty level, creators implicitly set expectations, shape behavior, and achieve their objective without needing rules, permissions, or authority. --- id: work/bounties/analytics title: "Bounty Analytics" description: "Retrieve and Analyze Bounty Stats" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/analytics related: [work/bounties] tokens: 503 --- # Bounty Analytics Get live stats for one bounty: take its ID from the bounty URL, run GET /bounties/{id} in the API docs, and paste the request URL into Claude or GPT with a prompt to summarize engagement. ### Objective To fetch live bounty data from the Zero Authority API and generate overall engagement and performance statistics using an AI model (Claude or GPT). *** ### Steps #### 1. Open the Bounty Page Navigate to the specific bounty you want to analyze: **URL:** [Zero Authority Bounty Page](https://www.zeroauthoritydao.com/bounty/7056755e-0ef4-4b49-8154-692039785e6c) #### 2. Get the Bounty ID Copy the unique bounty identifier from the URL. **Example:** ``` 7056755e-0ef4-4b49-8154-692039785e6c ``` #### 3. Access the API Documentation Go to the API documentation page: **URL:** #### 4. Use the GET Endpoint Under **GET /bounties/{id} – Get bounty by ID**, paste your bounty ID into the parameter field, then click **Execute** to run the request. #### 5. Copy the Request URL Once executed, copy the generated request URL. It will look like this: ``` https://zeroauthoritydao.com/api/bounties/7056755e-0ef4-4b49-8154-692039785e6c ``` #### 6. Run the Request in an AI Model Paste the full API URL into an AI model (Claude or GPT) and include a prompt for analysis. **Example Prompt:** ``` Fetch data from this API endpoint: https://zeroauthoritydao.com/api/bounties/7056755e-0ef4-4b49-8154-692039785e6c Analyze and summarize the overall stats — include engagement metrics such as number of submissions, unique participants, total rewards distributed, completion rate, and any notable activity trends. ``` #### 7. Review the Output The AI will generate a synthesized summary of the bounty's engagement and performance data based on the API response. *** ### Result You will obtain a structured overview of the bounty’s real-time metrics — ideal for inclusion in community updates, dashboard analytics, or marketing summaries. *** **Notes:** * Ensure your API endpoint is accessible publicly or with an API key if required. * Use consistent IDs when analyzing multiple bounties for comparative reporting. --- id: work/bounties/redeem-funds title: "Bounty Redeem Funds" description: "Procedure for Redeeming Funds from a Bounty Contract" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/redeem-funds related: [work/bounties] tokens: 420 --- # Bounty Redeem Funds Get funds back from a bounty contract by calling redeem-funds on ZADAO-V2-MultiW-Bounty in the Stacks Explorer Sandbox, with the bounty ID and token from the original transaction. **Step 1: Locate the Bounty Contract** * Go to the Stacks Explorer and find the specific bounty contract you used. Example:\ [ZADAO-V2-MultiW-Bounty Contract](https://explorer.hiro.so/txid/SP2GW18TVQR75W1VT53HYGBRGKFRV5BFYNAF5SS5J.ZADAO-V2-MultiW-Bounty?chain=mainnet) **Step 2: Open the Sandbox** * Navigate to the Stacks Sandbox:\ [Stacks Sandbox - Deploy](https://explorer.hiro.so/sandbox/deploy?chain=mainnet) **Step 3: Use the Contract ID** * In the Sandbox, use the Contract ID from the example or your own:\ `SP2GW18TVQR75W1VT53HYGBRGKFRV5BFYNAF5SS5J.ZADAO-V2-MultiW-Bounty` **Step 4: Go to 'Call a Contract'** * Select the option **Call a contract** in the Sandbox interface. **Step 5: Retrieve Contract Functions** * Click **Get contract** to load all available functions in the smart contract. **Step 6: Use the 'redeem-funds' Function** * From the list of functions, locate and select **redeem-funds**. * You’ll need to provide two pieces of information: 1. **Bounty ID** – found in the original transaction. 2. **Token used** – also visible in the original transaction details. **Example Reference:**\ [Transaction Reference](https://explorer.hiro.so/txid/SP2GW18TVQR75W1VT53HYGBRGKFRV5BFYNAF5SS5J.ZADAO-V2-MultiW-Bounty?chain=mainnet) **Step 7: Enable Allow Mode** * Before confirming the transaction, toggle **Allow Mode** to authorize contract interactions. **Step 8: Execute Transaction** * Once parameters are filled and Allow Mode is enabled, execute the function to redeem your funds successfully. *** This process ensures correct retrieval and interaction with the bounty contract using the Stacks Sandbox environment on mainnet. --- id: work/bounties/create-v1 title: "How to create a bounty V1" description: "Procedure for Creating and Posting a Bounty on Zero Authority" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/create-v1 related: [work/bounties] tokens: 580 --- # How to create a bounty V1 Older version: create a bounty with name, description, dates and STX amount, set up its profile page, post it, then select the winner and accept onchain to release the funds. > [!NOTE] > This is the older v1 flow. For the current one, see [Create a bounty on V2 beta](https://zeroauthoritydao.ai/docs/work/bounties/create.md). ![](https://zeroauthoritydao.ai/docs/img/93359bc89803.webp) ### **Step 1: Access the Bounty Creation Page** * **Go to** page. *** ### **Step 2: Start Creating the Bounty** * **Click on** "Create Bounty" to begin the process. *** ![step 3](https://zeroauthoritydao.ai/docs/img/bdebb3443e72.webp) *step 3* ### **Step 3: Enter Bounty Details (First Page)** * **Name** * Enter the name of the bounty (e.g., "Educational Content"). * **Description** * Write a brief description of the bounty. Example: "Develop a series of educational content. Tag us on Twitter and in the submission. Be prepared to add the URL of your tweet." * **Start Date** * Set the start date for when you are ready to begin the bounty. * **End Date** * Set the end date, typically 2-4 weeks after the start date. * **Amount** * Enter the amount to be awarded for completing the bounty, in $STX. *** ![step 4](https://zeroauthoritydao.ai/docs/img/99cbd48e4436.webp) *step 4* ### **Step 4: Set Up the Bounty Profile Page (Second Page)** * **Bounty Profile Page** * Enter a one-word identifier for your bounty profile page (no spaces). * **Organization URL** * Provide the full URL of your organization (e.g., ""). * **Organization Description** * Write a description of your organization. * **Logo or Image** * Upload an image or logo to represent your organization on the bounty profile page. #### **Final Steps of Step 4 Posting Bounty** * **Review** all the information entered for accuracy. * **Submit** the bounty for posting on Zero Authority. ### **Last Step: Select Winner !** * **Review** all the information for all of the bounties posted * Write a message to the winner * Click on "accept" and complete transaction onchain * The smart contract will release the funds to the winner * done! ![](https://zeroauthoritydao.ai/docs/img/77d24d705507.webp) ![](https://zeroauthoritydao.ai/docs/img/15aca6d7284a.webp) Coming soon at the time of v1: all participants and the creator of the bounty earn reputation represented with an NFT badge, and v2 adds more types of bounties to launch and participate in. Thank you * email notification will go to winner and all participants * you have activated & engaged your community. * please leave us feedback on twitter DM or email our community manager --- id: work/bounties/sandbox-winners title: "Bounty Winners In Sandbox" description: "Manual Winner Selection via Stacks Explorer Sandbox" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/sandbox-winners related: [work/bounties] tokens: 1111 --- # Bounty Winners In Sandbox If the platform transaction that pays bounty winners fails, call the contract from the Stacks Explorer Sandbox with the bounty ID, token and winner addresses from the failed accept-submissions transaction. ### Overview This procedure outlines the steps to manually select bounty winners when the automated platform transaction fails on the blockchain. The process uses the Stacks Explorer Sandbox to directly call smart contract functions. *** ### Prerequisites Before beginning this procedure, ensure you have: * Access to Stacks Explorer (explorer.hiro.so) * Administrative access to the bounty smart contract * The failed transaction details and winner addresses * STX wallet connected with sufficient gas fees *** ### Step-by-Step Procedure #### Step 1: Access Stacks Explorer Sandbox 1. Navigate to **Stacks Explorer Sandbox** `ZADAO-V2-MultiW-Bounty` 2. **Log in** to your account with administrative privileges 3. Ensure your STX wallet is connected and has sufficient balance for transaction fees [Open the contract call in the Stacks Explorer Sandbox](https://explorer.hiro.so/sandbox/contract-call/SP2GW18TVQR75W1VT53HYGBRGKFRV5BFYNAF5SS5J.ZADAO-V2-MultiW-Bounty/accept-submissions?chain=mainnet) #### Step 2: Locate Failed Transaction Details 1. Navigate to the failed transaction: * Transaction ID: `0xba6cf…a9cb6` 2. **Extract the following information** from the failed `accept-submissions` transaction: * `bounty_id` * `used_token` * `winners` (list of STX addresses) #### Step 3: Prepare Winner Addresses From the failed transaction, the following addresses have been identified as winners: ``` SP30DPQTSZ1R3XVFJ0Z02CJZ66N8467R04BKMMGZ1 SP3KF338F5A6KNCVBFANM08AKNVNV4ZZKT12HEBXH SP3BRCBNKKRJTECH2ETCTW5HQ86P1S77MDHCM6VG0 SPK9J5DD22NTTMK6FMF07CANX81FQW8WE63SAM2Q SP3E1BE5M5SS5SD2Y0T6VWMSX3KJZ09GFCSRHJ144 SP23BQZ3RNTHM7GZZVT2EB5WTRM81JB5N4KJGDKMX SP258T581PRDFM9M0MHQWTCE9RMD6JQQ74HEWC46P SP31ZNSNSJK0R8Z8CRVKXFPWPC5A610SEA4XPBTQ7 SP2B9397JT7396J6BJF2DZ6HA6Q298C4938K0S2PB SP3FTV5B6F5P2B1YHW7SZDDE3VBRJCBZ72420V62M ``` [View the failed transaction in the Stacks Explorer](https://explorer.hiro.so/txid/0xba6cf02bce9222de41f6df906cf18f1b842e96979800ca41f61ad658db4a9cb6?chain=mainnet) #### Step 4: Execute Smart Contract Function in the Sandbox 1. In the **Sandbox interface**, locate the bounty smart contract 2. Find the **winner selection function** (likely `select-winners` or `distribute-bounty`) 3. **Input the required parameters**: * **Bounty ID**: Enter the `bounty_id` from the failed transaction * **Token**: Specify the `used_token` value * **Winners**: Enter each winner address individually in the provided input fields #### Step 5: Submit Transaction 1. **Review all entered data** for accuracy 2. **Check gas fee estimation** and ensure sufficient STX balance 3. **Submit the transaction** through the sandbox interface 4. **Wait for confirmation** on the blockchain (typically 1-10 minutes) #### Step 6: Verification 1. **Monitor the transaction status** in the Stacks Explorer 2. **Verify successful execution** by checking: * Transaction status shows as "Success" * Winner addresses received their bounty tokens * Bounty status updated to "Completed" 3. **Document the successful transaction hash** for record-keeping *** ### Troubleshooting #### Common Issues and Solutions **Transaction Fails Again**: * Check gas fee allocation * Verify all addresses are valid STX addresses * Ensure bounty contract has sufficient token balance **Input Field Limitations**: * If sandbox limits winner count, submit multiple smaller transactions * Process winners in batches if necessary **Access Issues**: * Verify administrative privileges on the smart contract * Ensure wallet connection is stable *** ### Post-Completion Actions 1. **Notify all winners** of successful token distribution 2. **Update internal records** with the new transaction hash 3. **Archive documentation** of the manual intervention 4. **Review platform code** to prevent similar failures in future bounties 5. **Monitor winner wallets** to confirm token receipt *** ### Security Notes * Always verify addresses before submitting transactions * Double-check bounty ID and token parameters * Use testnet for testing if available * Keep transaction records for audit purposes * Only authorized personnel should execute these procedures *** ### Screenshot * To get the bounty\_id and token, go back to the `accept-submissions` transaction * Add list item, and add all of the wallet addresses from `accept-submissions` * Then call function ![](https://zeroauthoritydao.ai/docs/img/640cbf33a714.webp) --- id: work/bounties/select-winners title: "Selecting Winner the Bounty" description: "There is no official deadline for selecting a winner at the bounty’s end date" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/select-winners related: [work/bounties] tokens: 424 --- # Selecting Winner the Bounty Submissions close at 11:59 PM UTC on the end date. There is no deadline to pick a winner after that, but do it promptly from My Bounties with Select Winner. Once the end date originally set by the bounty creator is triggered—**officially at 11:59 PM UTC**—the Clarity smart contract will automatically **prevent any further submissions**. At this point, no new participants can enter, and the selection process begins. There is no official or systematic deadline for selecting a winner once the bounty’s end date has passed. While the system does not enforce a strict timeline, it’s best to **review submissions and choose a winner promptly** to maintain engagement and trust within the community. Prompt selection ensures that participants feel valued for their contributions and keeps the momentum going for future bounties. **Delays can lead to frustration, discourage participation in future bounties, and create uncertainty among contributors.** While there is flexibility, timely action is strongly encouraged to uphold the credibility of the bounty system and maintain a positive user experience. **Procedure** ![](https://zeroauthoritydao.ai/docs/img/d06605b41c98.webp) **1. Access the Bounty Page** * Go to website. **2. Navigate to "My Bounties"** * Click on **"My Bounties"** to view the bounties you have created. **3. Identify Bounties That Have Ended** * Check for bounties where the **end date has passed**. **4. Select a Winner** * Review the submissions and choose the best entry. * Click **"Select Winner"** and confirm your choice. **5. Notify the Winner & Community** * Announce the winner to keep participants engaged. * Share the results on social media or Discord if applicable. **6. No Hard Deadline – Act Fast!** * There’s no strict deadline after the end date, but select a winner **as soon as possible** to keep the community happy. 🚀 --- id: work/bounties/community-engagement title: "Community Engagement" description: "Recognizing and Rewarding Community Members" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/bounties/community-engagement related: [work/bounties] tokens: 338 --- # Community Engagement Ideas for bounties that engage your community, mostly memes about Web3 and crypto work plus Twitter Space proof of attendance. ![where memes meet markets, a new paradigm emerges.](https://zeroauthoritydao.ai/docs/img/02d97fa9881d.webp) *where memes meet markets, a new paradigm emerges.* ### Engaging your community Engaging your community effectively is essential for creating a vibrant and supportive environment. Start by establishing clear communication channels across multiple platforms, encouraging open dialogue among members. Share valuable content, such as tutorials and success stories, to foster learning and recognition. *** ### Ideas for bounties to engage community Twitter Space proof of attendance Create a meme of Web3 vs. Web2 office life. Meme your reaction when you earn your first cryptocurrency. The moment you realize DAOs > 9-to-5 jobs. Meme the future of work powered by decentralized finance. When your boss discovers onchain reputation. Web3: Because Mondays should be optional. Meme getting paid in crypto vs. fiat. When you onboard your friends to Web3. Meme your Web3 learning curve with cryptocurrency. Waking up to new tokens in your wallet. Meme Life before and after discovering crypto. When crypto becomes your side hustle. Meme your excitement for decentralization. When the job pays in memes and crypto. Meme The power of community bounties. Meme Watching your crypto grow your reputation. When crypto is the new office currency. --- id: work/quests title: "Quests Onchain" description: "Overview of a quests and templates" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/quests related: [work, work/quests/get-started, work/quests/more-ideas, work/quests/how-to-win, work/quests/screenshots, work/quests/ideas] tokens: 918 --- # Quests Onchain A quest is an onchain mission that coordinates contributions toward a shared goal, with transparent records and smart contract rewards. Includes eight quest templates. ### What is a Quest? A Quest is a structured, onchain task or mission designed to coordinate real contributions toward shared goals. Unlike simple tasks, quests align purpose, incentives, and execution into a unified flow — allowing individuals, teams, and agents to collaborate in a decentralized system of value creation. Quests transform participation into progress, turning community energy into measurable outcomes. ### Why Onchain Quests? #### Advantages: **Transparency:** All quest activity, submissions, and reward flows are recorded onchain, creating a verifiable, immutable history of contribution and impact. Trust becomes systemic, not social. **Security:** Smart contracts automate verification, reward distribution, and access control — eliminating counterparty risk and ensuring contributors are compensated according to predefined rules. **Decentralization:** Quests remove centralized gatekeepers. Anyone can create, join, execute, or complete a quest without intermediaries, enabling permissionless coordination at scale. **Composability:** Quests can link together — outputs of one quest become inputs for another — forming modular systems of work, governance, and growth. *** ### Quest Templates These templates provide a structured framework for defining scope, requirements, rewards, and outcomes — helping creators attract aligned contributors and execute efficiently. #### Bug Fixing Quest **Description:** Identify and fix bugs in existing software systems to improve performance, reliability, and user experience. Contributors must document the issue, root cause, and resolution process with verifiable proof of completion. #### Create a Meme or Graphic Quest **Description:** Design engaging visual content such as memes, graphics, brand assets, or UI elements. Outputs must align with brand identity, visual language, and communication goals. #### Content Creation Quest **Description:** Produce high-quality written content including articles, research pieces, documentation, or educational material. Content should be original, well-researched, structured, and aligned with ecosystem narratives. #### Social Distribution Quest **Description:** Execute coordinated content distribution across social platforms to drive awareness, growth, and engagement. Includes content creation, publishing, amplification strategies, and performance tracking. #### Security Review Quest **Description:** Perform a structured security review or audit of systems, contracts, or infrastructure. Deliverables include risk analysis, vulnerability mapping, and actionable remediation strategies. #### Video Production Quest **Description:** Create strategic video content for education, marketing, or storytelling. Includes scripting, storyboarding, filming, editing, and post-production for high-quality narrative delivery. #### Research Quest **Description:** Conduct structured research on markets, ecosystems, technologies, or protocols. Outputs include synthesized reports, data models, insight maps, and strategic summaries. #### Growth Experiment Quest **Description:** Design and execute measurable growth experiments across onboarding, activation, engagement, or retention. Focus on data-driven learning and repeatable growth loops. *** ### Quests as Infrastructure Quests are not tasks. They are coordination primitives — programmable missions that convert intention into execution, community into capacity, and vision into reality. In Zero Authority, quests form the operating system of decentralized progress. No managers. No bottlenecks. No gatekeepers. Just aligned intent, autonomous execution, and onchain truth. --- id: work/quests/more-ideas title: "Specific Quest Ideas" description: "A Quest Protocol Standard — a shared operating standard" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/quests/more-ideas related: [work/quests] tokens: 1411 --- # Specific Quest Ideas Quest ideas by sector (DeFi, lending, NFT, wallets, learning, media, community, conferences), two themes each, built from a social share, a community join and asset ownership. ## 🧠 DeFi Quest Protocol ### Theme 1: **Yield Signal** > Social Share\ > • Users share yield strategies, dashboards, or protocol insights.\ > • End goal: Spread high-signal DeFi intelligence across networks. > Community Join\ > • Users enter DeFi strategy hubs and signal rooms.\ > • End goal: Build coordinated liquidity communities. > NFT or Asset Ownership\ > • Hold governance or LP NFTs/tokens.\ > • End goal: Onchain proof of aligned capital participation. ### Theme 2: **Liquidity Flow** > Social Share\ > • Share pool performance, TVL growth, and ecosystem metrics.\ > • End goal: Visibility for capital movement. > Community Join\ > • Join liquidity coordination groups.\ > • End goal: Collective liquidity orchestration. > NFT or Asset Ownership\ > • Hold LP tokens or protocol assets.\ > • End goal: Identity = liquidity contributor. *** ## 💸 Lending Quest Protocol ### Theme 1: **Credit Graph** > Social Share\ > • Share trust, reputation, and lending insights.\ > • End goal: Public trust signaling. > Community Join\ > • Join borrower/lender circles.\ > • End goal: Build social credit networks. > NFT or Asset Ownership\ > • Hold credit NFTs or lending tokens.\ > • End goal: Onchain credit identity. ### Theme 2: **Risk Shield** > Social Share\ > • Share risk education and protection strategies.\ > • End goal: Risk-aware culture. > Community Join\ > • Join risk monitoring communities.\ > • End goal: Collective defense systems. > NFT or Asset Ownership\ > • Hold collateral or insurance assets.\ > • End goal: Proof of responsible participation. *** ## 🖼 NFT Quest Protocol ### Theme 1: **Culture Engine** > Social Share\ > • Share art, collections, and cultural narratives.\ > • End goal: Cultural diffusion. > Community Join\ > • Join creator and collector circles.\ > • End goal: Cultural networks. > NFT or Asset Ownership\ > • Hold culture NFTs.\ > • End goal: Identity through culture. ### Theme 2: **Creator Graph** > Social Share\ > • Share creator stories and drops.\ > • End goal: Creator visibility. > Community Join\ > • Join creator guilds.\ > • End goal: Collaborative ecosystems. > NFT or Asset Ownership\ > • Hold creator NFTs.\ > • End goal: Patron identity layer. *** ## 👛 Wallet Quest Protocol ### Theme 1: **Self-Sovereignty** > Social Share\ > • Share wallet education and self-custody narratives.\ > • End goal: Sovereignty culture. > Community Join\ > • Join wallet user communities.\ > • End goal: Peer support networks. > NFT or Asset Ownership\ > • Hold wallet identity NFTs.\ > • End goal: Onchain digital identity. ### Theme 2: **Multi-Chain Navigator** > Social Share\ > • Share cross-chain experiences.\ > • End goal: Multi-chain literacy. > Community Join\ > • Join chain explorer groups.\ > • End goal: Network bridging. > NFT or Asset Ownership\ > • Hold multi-chain assets.\ > • End goal: Interoperable identity. *** ## 🎓 Learning Quest Protocol ### Theme 1: **Proof of Learning** > Social Share\ > • Share learning progress and insights.\ > • End goal: Knowledge propagation. > Community Join\ > • Join learning cohorts.\ > • End goal: Collective intelligence. > NFT or Asset Ownership\ > • Hold learning NFTs.\ > • End goal: Credentialized identity. ### Theme 2: **Mentor Graph** > Social Share\ > • Share teaching content.\ > • End goal: Knowledge visibility. > Community Join\ > • Join mentor networks.\ > • End goal: Knowledge transfer systems. > NFT or Asset Ownership\ > • Hold mentor badges/NFTs.\ > • End goal: Authority signaling. *** ## 📰 Media Quest Protocol ### Theme 1: **Signal Network** > Social Share\ > • Share verified news and narratives.\ > • End goal: Signal amplification. > Community Join\ > • Join media curation groups.\ > • End goal: Collective filtering. > NFT or Asset Ownership\ > • Hold media NFTs.\ > • End goal: Source credibility identity. ### Theme 2: **Citizen Intelligence** > Social Share\ > • Share field reporting.\ > • End goal: Decentralized journalism. > Community Join\ > • Join reporting networks.\ > • End goal: Distributed truth systems. > NFT or Asset Ownership\ > • Hold reporter NFTs.\ > • End goal: Proof-of-source identity. *** ## 🌱 Community Quest Protocol ### Theme 1: **Social Fabric** > Social Share\ > • Share community stories.\ > • End goal: Cultural bonding. > Community Join\ > • Join community hubs.\ > • End goal: Network density. > NFT or Asset Ownership\ > • Hold community NFTs.\ > • End goal: Belonging identity. ### Theme 2: **Reputation Mesh** > Social Share\ > • Share contributions and impact.\ > • End goal: Reputation signaling. > Community Join\ > • Join reputation circles.\ > • End goal: Trust formation. > NFT or Asset Ownership\ > • Hold reputation tokens.\ > • End goal: Trust anchoring. *** ## 🎤 Conference Quest Protocol ### Theme 1: **Human Graph** > Social Share\ > • Share connections and moments.\ > • End goal: Social visibility. > Community Join\ > • Join event communities.\ > • End goal: Network formation. > NFT or Asset Ownership\ > • Hold event NFTs.\ > • End goal: Attendance identity. ### Theme 2: **Knowledge Flow** > Social Share\ > • Share insights and learnings.\ > • End goal: Knowledge diffusion. > Community Join\ > • Join session groups.\ > • End goal: Collective memory. > NFT or Asset Ownership\ > • Hold session NFTs.\ > • End goal: Proof-of-participation identity. *** ### 🧬 Protocol Reality Layer Every quest — regardless of vertical — runs the same pipeline: **Participation → Identity Signal → Reputation Weight → Treasury Flow → NOVA AI Scoring → Reward Distribution → Compounding Trust** --- id: work/quests/how-to-win title: "How do I win?" description: "Zero Authority Quest Reward Procedure" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/quests/how-to-win related: [work/quests] tokens: 807 --- # How do I win? Quests have no single winner. The quest fee goes to a treasury governed by NOVA AI, which grants rewards to wallets based on activity, contribution and reputation. ![](https://zeroauthoritydao.ai/docs/img/53c6c87438ac.webp) ### Winning a Quest (Non-Bounty Model) In Zero Authority, quests do not operate on winner-takes-all bounty mechanics. There are no single winners, no subjective selection, and no centralized approvals. Rewards emerge from participation, contribution, reputation, and sustained alignment. This system is designed to reward **behavior**, not submissions — and **coordination**, not competition. *** ### Core Principles * Quests are participation-based, not contest-based * Rewards are probabilistic and reputation-weighted * Contribution compounds over time * Alignment > visibility * Activity > performance theater *** ### Quest Flow Procedure #### 1. Quest Creation A creator launches a new quest. * The quest defines purpose, objectives, and contribution pathways * The creator sets a **reward fee** (not a prize pool) * This fee is automatically deposited into the **Treasury Contract** The treasury becomes the reward engine — not the creator. *** #### 2. Participation Phase Participants join the quest. * Users contribute through actions, tasks, coordination, content, development, research, or execution * All actions are recorded onchain * Participation builds **activity score** and **reputation weight** There is no “submission” model — only verifiable contribution. *** #### 3. Reputation Accumulation Each participant builds a living reputation profile: * Consistency of participation * Quality signals * Verification history * Cross-quest contribution * Long-term alignment patterns Reputation is cumulative, portable, and composable across quests. *** #### 4. Treasury Control Layer (NOVA AI) The **Treasury Contract** is governed by NOVA AI. NOVA AI: * Monitors participation data * Tracks activity levels * Evaluates reputation weight * Analyzes contribution patterns * Models long-term alignment This creates a dynamic contribution graph rather than static scoring. *** #### 5. Reward Distribution Logic Rewards are not claimed — they are **granted**. NOVA AI selects wallets for reward distribution based on: * Activity intensity * Contribution consistency * Reputation weight * Cross-quest engagement * Ecosystem alignment This selection is: * Non-deterministic (not predictable) * Non-gameable (anti-sybil + reputation weighting) * Continuous (not event-based) * Probabilistic (likelihood-based, not ranking-based) *** #### 6. Distribution Execution * NOVA AI triggers treasury distributions * Smart contracts execute transfers * Rewards flow directly to selected wallets * All distributions are transparent and onchain There is no announcement of winners — only proof of contribution and receipt. *** ### System Outcome Quests produce: * Long-term contributors, not short-term hunters * Ecosystem builders, not task mercenaries * Compounding reputation, not disposable wallets * Coordination networks, not leaderboard economies *** ### Philosophy In Zero Authority, you don’t “win” a quest. You **become** valuable to the system. Rewards follow gravity. Reputation is mass. Participation bends the treasury. And alignment determines flow. This is not a marketplace. It’s an economy of trust, coordination, and emergence. --- id: work/quests/ideas title: "General Quest Ideas" description: "A Quest Protocol Standard — a shared operating standard" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/quests/ideas related: [work/quests] tokens: 1189 --- # General Quest Ideas Ten example quests, five virtual and five in real life, each built from the same three activities: a social share, joining a community and holding an NFT. ## 🌐 Virtual Quests (Fun, Engaging, Interactive) ### 1. The Clip Storm Quest **Theme:** Viral remix culture > **Social Share**\ > • Description: Share short clips remixed from long-form content across social platforms.\ > • End User Goal: Become a signal node — not a viewer, a distributor of culture. > **Community Join**\ > • Description: Join the remix/creator community hub.\ > • End User Goal: Enter the creative loop and co-create attention cycles. > **NFT or Asset Ownership**\ > • Description: Hold a Remix Pass NFT.\ > • End User Goal: Identity as a recognized cultural amplifier. *** ### 2. The Signal Relay Quest **Theme:** Network effect game > **Social Share**\ > • Description: Cross-post curated signal threads across networks.\ > • End User Goal: Build reputation as a trusted signal carrier. > **Community Join**\ > • Description: Join the Signal Relay coordination channel.\ > • End User Goal: Access high-signal intelligence flows. > **NFT or Asset Ownership**\ > • Description: Hold a Signal Node NFT.\ > • End User Goal: Identity as part of the information graph. *** ### 3. The Community Jam Quest **Theme:** Digital block party energy > **Social Share**\ > • Description: Share highlights, moments, and community energy.\ > • End User Goal: Spread social gravity around the community. > **Community Join**\ > • Description: Join the live community hub.\ > • End User Goal: Become part of the social core. > **NFT or Asset Ownership**\ > • Description: Hold a Jam Badge NFT.\ > • End User Goal: Visible proof of belonging. *** ### 4. The Creator Collab Quest **Theme:** Co-creation loops > **Social Share**\ > • Description: Share collaborative content drops.\ > • End User Goal: Build creator-network reputation. > **Community Join**\ > • Description: Join the creator coordination group.\ > • End User Goal: Access collaboration pipelines. > **NFT or Asset Ownership**\ > • Description: Hold a Creator Pass NFT.\ > • End User Goal: Identity as a verified collaborator. *** ### 5. The Mystery Drop Quest **Theme:** Curiosity engine > **Social Share**\ > • Description: Share decoded clues and discoveries.\ > • End User Goal: Become part of the discovery narrative. > **Community Join**\ > • Description: Join the puzzle-solving group.\ > • End User Goal: Collective intelligence participation. > **NFT or Asset Ownership**\ > • Description: Hold a Mystery Key NFT.\ > • End User Goal: Access hidden layers of the system. *** ## 🌍 Real-Life Quests (Fun, Engaging, Interactive) ### 1. The City Signal Quest **Theme:** Local discovery engine > **Social Share**\ > • Description: Share city discoveries publicly.\ > • End User Goal: Become a local signal beacon. > **Community Join**\ > • Description: Join the city coordination group.\ > • End User Goal: Access real-world social graphs. > **NFT or Asset Ownership**\ > • Description: Hold a City Node NFT.\ > • End User Goal: Identity as a local network anchor. *** ### 2. The IRL Flash Meet Quest **Theme:** Spontaneous coordination > **Social Share**\ > • Description: Share meetup moments and highlights.\ > • End User Goal: Create social gravity around gatherings. > **Community Join**\ > • Description: Join the flash coordination channel.\ > • End User Goal: Access spontaneous meetups. > **NFT or Asset Ownership**\ > • Description: Hold a Flash Pass NFT.\ > • End User Goal: Verified access to pop-up events. *** ### 3. The Culture Capture Quest **Theme:** Living documentary > **Social Share**\ > • Description: Share cultural moments and stories.\ > • End User Goal: Become a culture archivist. > **Community Join**\ > • Description: Join the culture documentation group.\ > • End User Goal: Collective storytelling participation. > **NFT or Asset Ownership**\ > • Description: Hold a Culture Archive NFT.\ > • End User Goal: Identity as a cultural recorder. *** ### 4. The Human Graph Quest **Theme:** Social mapping > **Social Share**\ > • Description: Share social connections and introductions.\ > • End User Goal: Expand social capital. > **Community Join**\ > • Description: Join the social graph circle.\ > • End User Goal: Build relational networks. > **NFT or Asset Ownership**\ > • Description: Hold a Graph Node NFT.\ > • End User Goal: Identity as a connector. *** ### 5. The Collective Game Quest **Theme:** Real-world team play > **Social Share**\ > • Description: Share team highlights and wins.\ > • End User Goal: Build group narrative momentum. > **Community Join**\ > • Description: Join the team coordination group.\ > • End User Goal: Belong to a living team structure. > **NFT or Asset Ownership**\ > • Description: Hold a Team Crest NFT.\ > • End User Goal: Proof of team identity. *** --- id: work/gigs title: "Gigs Onchain" description: "Overview of a gigs onchain and templates" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/gigs related: [work, work/gigs/v2, work/gigs/offer-and-accept, work/gigs/milestones, work/gigs/redeem-funds] tokens: 405 --- # Gigs Onchain Gigs are fixed contracts between a client and a creator, secured by smart contracts, with options to confirm completion and a modular event flow from offer to completion. ## Introduction Problem Addressed The ZeroAuthority Gig Marketplace tackles the challenge of establishing transparent and secure fixed contracts for Web3 projects. By addressing trust issues and enabling smart contract-based interactions, it creates a peer-to-peer trustless network for hiring individuals in the Web3 space. #### Key Features * **Completion Confirmation Options:** Clients can confirm gig completion with multiple options, ensuring flexibility and fairness in the resolution process. * **Talent Discovery:** BNS ID and Reputation integration with trajanapp (coming later) facilitate the discovery of talent for projects. * **Modular Events:** The platform supports a modular event system, covering the entire workflow from gig offers to completion. * **Governance Token Integration:** The $Zero governance SIP-010 token is relaunched to provide emissions to both clients and creators. ### Getting Started #### Account Setup To get started, users need to create profiles highlighting their skills, experience, and setting their pay rates. This section guides you through the account setup process. #### Navigating the Cerulean Marketplace Learn how to navigate the Cerulean Marketplace, explore available gigs, and understand the platform's layout and features. ### Gig Procedures #### Completion Confirmation Options Understand the options available for clients to confirm gig completion, including percentage-based agreements and dispute resolution. #### Modular Events Explore the modular event system that defines the lifecycle of a gig, from initial offer to dispute resolution. --- id: work/gigs/v2 title: "Gigs on v2 beta" description: "How a client and creator will work onchain" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/gigs/v2 related: [work/gigs] tokens: 537 --- # Gigs on v2 beta The v2 gig flow: the client offers a gig and creates it onchain, the creator accepts and submits deliverables, then the client reviews, releases funds and rates the gig. ![](https://zeroauthoritydao.ai/docs/img/a96c5135a6be.webp) ## ***Start the process*** ![](https://zeroauthoritydao.ai/docs/img/ae80197cb285.webp) ***Client starts the process*** 1 Offering a gig (send a gig request to a creator) 2 Write your gig details 3 Review your gig details 4 Create gig onchain 5 Share your feedback ### ***Creator has to accept gig*** 6 Go to received gigs 7 Accept offer (or Decline offer) 8 Accept gig onchain ### ***Creator has to submit deliverables*** 9 Go to received gigs 10 Submit deliverables 11 To submit deliverables, provide a link and add a comment ### ***Client has to review deliverables to release funds*** 12 Go to sent gigs 13 Review submssion 14 To mark review submssion complete, confirm release of funds from the smart contract, and provide a comment 15 Rate gig onchain 16 All is complete *** ## Walk through with screenshots ### 1 Offering a gig ![](https://zeroauthoritydao.ai/docs/img/8f2b962f5a19.webp) 2 Write your gig details 3 Review your gig details ![](https://zeroauthoritydao.ai/docs/img/eeeb4de723fb.webp) ### 4 Create gig onchain ![](https://zeroauthoritydao.ai/docs/img/c76e3a19e43c.webp) 5 Share your feedback ![](https://zeroauthoritydao.ai/docs/img/78d84f50a9f6.webp) *** ***Creator has to accept gig (person wants to fulfill project deliverables)*** 6 Go to received gigs ![](https://zeroauthoritydao.ai/docs/img/5753b4704033.webp) ### 7 Accept offer (or Decline offer) ![](https://zeroauthoritydao.ai/docs/img/086654173c2e.webp) 8 Accept gig onchain ![](https://zeroauthoritydao.ai/docs/img/340d7f113bec.webp) *** ***Creator has to submit deliverables*** 9 Go to received gigs ![](https://zeroauthoritydao.ai/docs/img/4ead00da943f.webp) ### 10 Submit deliverables 11 To submit deliverables, provide link and comment ![](https://zeroauthoritydao.ai/docs/img/aaef86394cf6.webp) *** ***Client has to review deliverables to release funds*** 12 Go to sent gigs ![](https://zeroauthoritydao.ai/docs/img/0455fd132b4e.webp) ### 13 Review submssion ![](https://zeroauthoritydao.ai/docs/img/cde2ae09a528.webp) 14 To mark review submssion complete, confirm release of funds from the smart contract, and provide a comment ![](https://zeroauthoritydao.ai/docs/img/e7772023cb4e.webp) 15 Rate gig onchain ![](https://zeroauthoritydao.ai/docs/img/ee7cd66ba319.webp) 16 All is complete --- id: work/gigs/offer-and-accept title: "How To Offer or Accept Gig Onchain" description: "Gig Request, Gig Accept, & Gig Complete" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/gigs/offer-and-accept related: [work/gigs] tokens: 212 --- # How To Offer or Accept Gig Onchain Send a gig offer (Fixed or Milestone) from a creator's profile, accept offers sent to you, and check pending requests you sent. Each action needs a connected wallet and a signed transaction. ## Procedure Step 1 - Connect Wallet. Step 2 - Sign Transaction. ![](https://zeroauthoritydao.ai/docs/img/5860e51ae198.webp) Connecting your wallet and signing works as described in [Access to the Platform](https://zeroauthoritydao.ai/docs/profile/access.md), which also covers troubleshooting. **Making a Gig Request Offer:** * Follow Steps 1 and 2 to make an offer to someone for a gig. Go to website and click offer or navigate to a profile page and click "offer" * Select Fixed or Milestone **Accepting a Gig Request:** * Pending offers submitted to you to collaborate * Follow Steps 1 and 2 to accept a gig request from someone else. * Go to website to view the offer and accept offer **Waiting for someone to accept your gig request or mark gig complete?** * **Pending work requests you sent to collaborate** * Follow Steps 1 and 2. * Go to website and view the pending request you sent --- id: work/gigs/milestones title: "Milestone Gigs Onchain" description: "Overview of a milestone gig and templates" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/gigs/milestones related: [work/gigs] tokens: 330 --- # Milestone Gigs Onchain A milestone gig splits payment into up to 5 milestones, each released when the client marks it complete. If the client does not, funds can be redeemed by the client, then the creator, after the end date. 1. **Initiating a Milestone Contract:** * Begin by creating a milestone contract on the platform. * The start date is initiated at the time of the transaction block confirmation on the blockchain. 2. **Setting Milestone Details:** * Specify an end date for the milestone contract. * Note that up to 5 milestones can be created for a single contract. 3. **Payment for Milestone Delivery:** * When ready to pay for the delivery of a milestone, select the "complete" option. * The clarity contract will automatically release funds specifically for the completed milestone. 4. **Automatic Redemption for Inactivity:** * If the client takes no action or forgets to mark milestones as complete, 5 days after the end date, the client can choose to redeem funds. * This action triggers the clarity contract to release funds. 5. **Creator's Redemption Opportunity:** * If the end date is triggered and the client hasn't redeemed funds within 5 days, the creator has the option to trigger fund redemption. 6. **Remaining Funds for Creator:** * Upon redemption, the creator receives any remaining funds for the completed work. 7. **Reputation Badges:** * Clients earn a reputation badge for initiating a service request. * Creators earn a reputation badge for delivering the requested service. --- id: work/gigs/redeem-funds title: "Redeem Funds" description: "How to Redeem Funds From a Gig Contract" product: zadao canonical: https://zeroauthoritydao.ai/docs/work/gigs/redeem-funds related: [work/gigs] tokens: 547 --- # Redeem Funds Get your coins back from a gig contract after its 14-day lock: call redeem-back on ZADAO-V2a-gigs in the Stacks Sandbox with the gig id and payment token, from the wallet that created it. It is important to note, once the gig’s 14-day lock period has passed, you can use the redeem funds to get the coins back. Unfortunately, this function before 14 days, in Bitcoin blocks, will not work. **1. Open the gig page**\ Go to the gig you created:\ **2. Get the Stacks transaction**\ On the gig page, copy the **Stacks transaction** associated with the gig creation. **3. Open the transaction in the explorer**\ Paste that transaction into:\ [https://explorer.hiro.so](https://explorer.hiro.so/)\ (or use the direct link if you already have one)\ Example:\ **4. Get the contract ID**\ On the explorer page, locate the gig contract.\ It should look like:\ **SP2GW18TVQR75W1VT53HYGBRGKFRV5BFYNAF5SS5J.ZADAO-V2a-gigs** **5. Open Stacks Sandbox**\ Go to the Stacks Sandbox. **6. Connect your Stacks wallet**\ Make sure you are connecting **with the same wallet that originally created the gig**.\ If you use a different wallet, you won’t be able to redeem funds. **7. Under “Call a contract”**\ Paste the gig contract ID:\ **SP2GW18TVQR75W1VT53HYGBRGKFRV5BFYNAF5SS5J.ZADAO-V2a-gigs** **8. Click “Get contract”** **9. Choose the function**\ Select the public function **`redeem-back`**. **10. Enable Allow Mode**\ Turn on "Allow Mode" so the contract can move tokens. **11. Enter the inputs**\ You need two things:\ • **gig id**\ • **pay on** (the token ID used for payment) How to find them: **Finding the gig id:**\ On the explorer page for the original transaction, open the **Events** tab.\ Look for the event where the gig was created and copy the **gig id**. **Finding the “pay on” token ID:**\ In the same **Events** tab, look for the **currency** field.\ Example:\ `currency: 'SP32AEEF6WW5Y0NMJ1S8SBSZDAY8R5J32NBZFPKKZ.wstx'`\ This is the token contract ID you must enter for **pay on**. **12. Submit the transaction**\ After submitting, your funds will automatically return to you **once the gig’s 14-day lock period has passed**. *** --- id: about/stakeholder-updates title: "Stakeholders Updates" description: "Zero Authority DAO Updates" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/stakeholder-updates related: [about, about/stakeholder-updates/december-2025, about/stakeholder-updates/november-2025, about/stakeholder-updates/october-2025, about/stakeholder-updates/q3-2025, about/stakeholder-updates/q2-2025, about/stakeholder-updates/q4-2024] tokens: 186 --- # Stakeholders Updates Explains what Zero Authority DAO stakeholder updates cover (traffic, bounty participation, social reach) and links each update from Q4 2024 to December 2025. A Stakeholders Update for **Zero Authority DAO** brings together the most important insights on our progress, performance, and direction. It highlights growth metrics such as platform traffic, community participation in bounties, and overall social reach. See our latest Community highlights driving engagement and reputation building cross our ecosystem. - [December 2025](https://zeroauthoritydao.ai/docs/about/stakeholder-updates/december-2025.md) - [November 2025](https://zeroauthoritydao.ai/docs/about/stakeholder-updates/november-2025.md) - [October 2025](https://zeroauthoritydao.ai/docs/about/stakeholder-updates/october-2025.md) - [Q3 2025](https://zeroauthoritydao.ai/docs/about/stakeholder-updates/q3-2025.md) - [Q2 2025](https://zeroauthoritydao.ai/docs/about/stakeholder-updates/q2-2025.md) - [Q4 2024](https://zeroauthoritydao.ai/docs/about/stakeholder-updates/q4-2024.md) ![](https://zeroauthoritydao.ai/docs/img/7858c3714d3f.webp) --- id: about/stakeholder-updates/december-2025 title: "December 2025" description: "Board Meeting Summary" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/stakeholder-updates/december-2025 related: [about/stakeholder-updates] tokens: 1618 --- # December 2025 Summarizes the December 14, 2025 board meeting on V3, multi-chain and revenue plans, and a Jan 2025 to Jan 2026 analysis of social, community, web, bounty and gig activity, with 149,453 STX distributed. #### 📅 Summary The Zero Authority Board meeting on December 14, 2025, centered on transforming the platform into a self-governing, AI-powered, multi-chain protocol for the decentralized "future of work." The core strategy is to integrate AI agents for autonomous operations, diversify revenue streams beyond current grants, and establish a firm financial and competitive footing for a potential bear market. *** #### Points on the Future of Zero Authority and Solutions * AI-Powered Autonomous Protocol: The future involves a major V3 upgrade integrating AI agents to create a largely self-governing, autonomous organization that manages tasks, requests, payments, and even contributor hiring on-chain. * Multi-Chain Ecosystem Bridge: The platform will expand to become a chain-agnostic bridge between Web2 and Web3, enabling multi-chain onboarding (Stacks, Base, Solana, BTC L2, ETH L2) with embedded wallets, and providing foundational tooling for HR, governance, and operations in decentralized environments. * Revenue Diversification through AI Monetization: A key solution for financial sustainability is to monetize AI tools and agent services via API calls (X402) and develop an independent, cross-chain jobs board to attract users from multiple blockchain ecosystems. * Targeted Growth in High-Engagement Verticals: User growth will be driven by focusing on high-engagement sectors, specifically gaming and esports, and offering premium bundled services tailored to these markets for predictable income streams. *** ### CommunityFI & ReputationFI — Systems Analysis **Coverage Period:** Jan 2025 – Jan 2026 *** ### 1. System Overview This analysis evaluates Zero Authority as a **coordination system**, not a social brand. The objective is to measure how effectively attention is converted into participation, and participation into economically meaningful contribution. The system is composed of five interlocking layers: * Social distribution * Community infrastructure * Owned attention * CommunityFI incentives * ReputationFI incentives Each layer is measured independently and then evaluated as part of a unified flow. *** ### 2. Social Distribution Layer **Primary Surface:** X (formerly Twitter) **Metrics** * Impressions: **782,400** * Engagement rate: **8.3%** * Total engagements: **65,000** * Likes: **23,600** * Reposts: **5,900** * Replies: **5,700** * Profile visits: **7,000** * Followers: **\~4,500** * Verified followers: **742** **Analysis**\ Engagement significantly exceeds platform norms, with strong reply and repost activity indicating discourse rather than passive consumption. Profile visit volume suggests content drives intent, not just visibility. **Function**\ Discovery and narrative propagation. Social surfaces feed downstream systems rather than acting as terminal endpoints. *** ### 3. Community Infrastructure Layer **Coordination Infrastructure:** Nova Bot (Discord + Telegram) **Observed Reach (rolling windows)** * Discord: **7,840 – 11,179 members** * Across **13–17 servers** * Telegram: **428 – 523 members** * Across **5 chats** * Direct message reach: **6 users (controlled)** **Analysis**\ Discord functions as the primary coordination and discussion layer. Telegram provides broadcast redundancy. Direct messaging is intentionally constrained to preserve trust and prevent spam dynamics. **Function**\ Real-time synchronization between attention and action. This layer acts as the system’s nervous system. *** ### 4. Owned Attention Layer **Analytics Source:** Fathom\ **Period:** Last 365 days **Aggregate Metrics** * People: **32,200** * Views: **213,000** * Avg time on site: **1:17** * Bounce rate: **35%** * Event completions: **6,700** **By Property** * **zeroauthoritydao.com** * 27.5K people * 201.8K views * 30% bounce * All tracked events * **zeroauthority.xyz** * Lower traffic, higher bounce (49%) * **docs.zeroauthority.xyz** * Longest dwell (1:45), highest bounce (83%) **Analysis**\ The primary site demonstrates strong intent and conversion behavior. Documentation traffic aligns with expected usage patterns: deep, task-oriented visits with minimal retention. **Function**\ Conversion and context layer. Bridges off-platform attention into participation. *** ### 5. CommunityFI Layer — Bounties **Dataset** * Total bounties: **329** * Multi-token payouts enabled * STX payouts included alongside ecosystem tokens #### Token Distribution via Bounties **STX** * **7,083.8001 STX** **Non-STX Tokens** * **LEO** — 32,796,000 * **WELSH** — 1,981,200 **Analysis**\ Bounties prioritize scale and accessibility. Non-STX tokens optimize for experimentation, onboarding, and broad participation. STX bounties represent a smaller share of volume but carry higher trust and reputational weight. **Function**\ Entry point for contributors and primary participation funnel. *** ### 6. ReputationFI Layer — Gigs **Dataset** * Total gigs: **213** #### STX Distribution via Gigs * **142,369.601 STX** **Analysis**\ Gigs account for the majority of native economic value distributed. They represent scoped work with clear delivery expectations and higher trust thresholds. **Function**\ Reputation amplification and economic alignment. This is the system’s credibility layer. *** ### 7. Combined Economic Output (STX) **Total STX Distributed** * **149,453.4011 STX** **Distribution Breakdown** * Bounties: **\~4.7%** * Gigs: **\~95.3%** **Analysis**\ The distribution ratio indicates a healthy separation of concerns: bounties for discovery, gigs for value concentration. *** ### 8. System-Level Findings 1. Attention is consistently converted into coordinated participation. 2. CommunityFI and ReputationFI functions are cleanly separated. 3. Native asset (STX) settlement anchors trust and reputation. 4. Infrastructure components are operational and interdependent. This system operates as a **coordination economy**, not a marketing funnel. *** ### 9. Strategic Implications * Reputation already exists; it is not yet fully surfaced. * Gig-based contributors should carry materially higher REP weighting. * Public contribution metrics would immediately influence behavior. * Multi-surface architecture reduces dependency on any single platform. *** ### 10. Conclusion Zero Authority has closed the loop most communities fail to close:\ **attention → participation → economic contribution**. ![](https://zeroauthoritydao.ai/docs/img/cb3f65c9954b.webp) --- id: about/stakeholder-updates/november-2025 title: "November 2025" description: "The Bitcoin L2 Economy is Exploding!" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/stakeholder-updates/november-2025 related: [about/stakeholder-updates] tokens: 364 --- # November 2025 Zero Authority community metrics from May to November 2025: 21,300 people, 308 bounties and 190 gigs completed, Nova AI activity, and the STX, sBTC and other tokens exchanged. The growth of the Zero Authority community is a testament to the daily dedication of businesses, builders, and creators showing up on the leading Bitcoin L2. Since May, the community has seen remarkable engagement and output, proving that the value created together is far bigger than any single metric: * Total People: 21,300 * Total Views: 156,700 * Total Actions: 5,400 #### 🛠️ Building & Exchange Metrics (May → Nov) The sheer volume of work completed and value exchanged highlights a rapidly maturing onchain economy: | **Metric** | **Figure** | | ----------------------- | ------------------------ | | Bounties Completed | 308 | | Gigs Completed | 190 | | NovaAI Activity (Daily) | Nearly 9,900 engagements | #### 💰 Community Value Exchanged The transactional value flowing through the ecosystem showcases a vibrant, multi-asset economy: | **Asset** | **Amount Exchanged** | | --------- | -------------------- | | STX | 80,000 | | sBTC | 0.1096 | | LEO | 26,000,000 | | ROO | 64,000 | | FLAT | 2,700,000 | | DIKO | 16,000 | The numbers don't lie: The Zero Authority community is driving explosive growth, making the onchain economy on the Bitcoin L2 bigger and stronger than ever. *** --- id: about/stakeholder-updates/october-2025 title: "October 2025" description: "Protocol Summary" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/stakeholder-updates/october-2025 related: [about/stakeholder-updates] tokens: 770 --- # October 2025 Zero Authority metrics for October 2025 across the website, X, the Nova AI bot on Discord and Telegram, and the blog, followed by reported results from organizations using the protocol. ### Zero Authority DAO ![](https://zeroauthoritydao.ai/docs/img/be7b3e3d6b26.webp) October showed consistent ecosystem growth across all channels: web, social, bot, and blog. Zero Authority DAO recorded 3.1K unique visitors and 23.6K page views on its main site (zeroauthoritydao.com) with a 1:09 average time on site, a 27% bounce rate, and 700 total event completions. The /bounty and /profile pages led engagement, supported primarily by direct traffic and wallet-integrated referrals via portfolio.xverse.app, confirming repeat users and strong community presence. On X (Twitter), the account achieved 53K impressions with an 8.2% engagement rate, totaling 4.4K engagements, 1.7K likes, and 380 reposts. Despite a 22% dip in impressions, engagement remained high, showing content resonance with an active core audience. Engagement peaks aligned with bounty launches and meme-driven initiatives. Nova AI Bot expanded its footprint, reaching 6,613 Discord members across 11 servers and 1,324 Telegram members across 6 chats, solidifying its role as a multi-network coordination tool for DAO notifications and governance updates. The blog (blog.zeroauthority.xyz) grew to 145 subscribers (+2.1%) with 1.71K views over 90 days (+88%). The latest post, “Bitcoin Yields with Stacks Dual Stack”, achieved a 24% open rate, continuing the blog's trend of steady audience growth and reader engagement around technical and thought-leadership content. In summary, October marked steady ecosystem momentum. Website engagement reflected returning users, X maintained high interaction quality, Nova AI bot scaled multi-platform reach, and the blog nearly doubled its readership. Zero Authority DAO continues maturing into a cohesive digital ecosystem integrating governance, coordination, and community growth. ### Supercharge Communities with Zero Authority Protocol In a world where attention is the new currency, companies and organizations are discovering that the **Zero Authority Protocol** delivers a new level of audience engagement. Unlike traditional social platforms, where algorithms gate visibility and community reach, Zero Authority enables **direct, decentralized engagement** with your audience through incentives, transparency, and authentic participation. **Results from organizations using Zero Authority Protocol:** * **10x audience participation** compared to traditional social channels. * **5x increase in community-driven content creation** through bounty systems and incentives. * **3x faster feedback loops** for new products, campaigns, or features. * **Higher trust and retention**, driven by verifiable contribution and transparent governance. The protocol makes Web3 communities come alive—where engagement isn’t just clicks and likes, but a living, evolving ecosystem of collaboration and shared value. Organizations using Zero Authority aren’t just building audiences; they’re building **networks of aligned contributors** who co-create the future of their brand. The next generation of engagement is here. It’s **open, decentralized, and powered by Zero Authority.** --- id: about/stakeholder-updates/q3-2025 title: "Q3 2025" description: "May to September 2025" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/stakeholder-updates/q3-2025 related: [about/stakeholder-updates] tokens: 769 --- # Q3 2025 Zero Authority metrics for May to September 2025: 18,000 website users, X engagement, about 12,000 Nova bot members, largest bounty payouts and partners, insights and recommendations for Q4 2025. The **Community Summary Dashboard** provides a concise view of Zero Authority DAO’s ecosystem health, highlighting **user growth, community engagement, platform activity, and protocol distribution of value**. This data-driven snapshot demonstrates ongoing traction and scalability for the DAO’s ecosystem. ### **1. Website & Platform Performance** * **Visitors:** **18,000 Users** (133,000 total views) * **Top Countries:** USA🇺🇸, UK🇬🇧, Indonesia🇮🇩, Nepal🇳🇵, Nigeria🇳🇬, France🇫🇷, Austrila🇦🇺 *** ### **2. Social Media (X)** * **Impressions:** **242,000** (+30%) * **Engagement Rate:** **8.5%** (+7.7%) — very strong for Web3 * **Total Engagements:** 20.6K (+41%) * **Trend:** July spike (\~60K impressions/week), followed by steady baseline. *** ### **3. Community & Nova AI Bot** * **Telegram/Discord:** \~12,000 members reached across chats & servers * **Takeaway:** Nova Bot is driving **community-led engagement at scale**, with Discord as the strongest channel. *** ### **4. Bounty Ecosystem** * **Activity:** Dozens of bounties completed across memes, design, tutorials, giveaways, and marketing. * **Largest Payouts:** * Meme & Marketing: multiple **1,000,000 LEO** distributions * Multi-winner contest: **25,000,000 MEME** tokens (UAP x LEO x MEME) * Design: **1,000 STX** (largest single payout recorded) * FlatEarth & Welsh campaigns: 230K+ tokens each * **Key Partners:** Dawgpool, $ROO MOB, Stacks AI Guild, Welsh Community, Happy Feline Friday, Leo Bounty Hub, FlatEarth, POS Army HQ * **Impact:** **Multi-winner bounties** = higher participation + sustained creator output. *** ### **5. Insights** * **Mobile-first:** 78%+ of visitors are on phones → mobile optimization is essential. * **Regional strength:** Nigeria, with growth potential in Indonesia & Nepal. * **X/Twitter correlation:** Directly tied to traffic and July’s activity spikes. * **Retention:** Solid time on site and low bounce rate = strong fit for active contributors. * **Growth engine:** Community (Discord + Twitter + Bounties) is the key driver. *** ### **6. Strategic Recommendations (Q4 2025)** 1. **Optimize Mobile UX** — build a Progressive Web App for bounty browsing & submissions. 2. **Regional Growth Playbook** — deepen presence in Nigeria, then scale campaigns to Indonesia & Nepal. 3. **X + Discord Integration** — automate winner announcements, live bounty updates, and social sharing loops. 4. **Gamify Reputation** — link Nova bot to on-chain reputation badges for higher repeat engagement. 5. **Creator Partnerships** — elevate top meme/marketing bounty participants into “community influencers.” 6. **Data-Driven Growth** — replicate July’s high-engagement playbook with targeted campaigns. *** ⚡ **Summary** Zero Authority DAO is building momentum with strong website growth, a vibrant community, and a thriving bounty ecosystem. Mobile-first users, regional traction, and social-driven discovery are proving the model. The next step is to **scale through mobile optimization, regional campaigns, and gamified engagement**. *** --- id: about/stakeholder-updates/q2-2025 title: "Q2 2025" description: "May 1 to July 30, 2025" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/stakeholder-updates/q2-2025 related: [about/stakeholder-updates] tokens: 452 --- # Q2 2025 Zero Authority community dashboard for May 1 to July 30, 2025: 4.4k users, about 11,000 Discord and Telegram members, July bounty token distributions, X impressions and blog subscribers. The **Community Summary Dashboard** provides a concise view of Zero Authority DAO’s ecosystem health, highlighting **user growth, community engagement, platform activity, and protocol distribution of value**. This data-driven snapshot demonstrates ongoing traction and scalability for the DAO’s ecosystem. *** #### **Key Highlights** 1. **Platform Growth** * **4.4k Users** * **30.4k Views** * **1.2k Event Completions** * *Key Insight: Steady month-over-month increases demonstrate growing adoption and community participation.* 2. **Community & Network Reach** * **Discord/Telegram:** \~11,000 members active chats & servers * *Key Insight: Expanding community presence across key platforms reflects increasing user engagement and visibility.* 3. **Bounty & Incentive Distribution (July)** * LEO: 2,500,000 * WELSH: 200,000 * STX: 435 * FlatEarth: 268,600 * $ROO: 14,500 * *Key Insight: Regular bounty distributions incentivize participation, drive network effects, and strengthen the DAO ecosystem.* 4. **Social Media Momentum** * **X/Twitter Impressions:** 105,000 * **Engagement Rate:** 8.3% * *Key Insight: Organic reach is growing rapidly, positioning the DAO for increased brand awareness and contributor inflow.* 5. **Content & Knowledge Hub Performance** * **141 Subscribers** * *Key Insight: Content continues to attract and retain a highly engaged audience.* *** ## **State of the Creators in Web3** The data signals **consistent growth, strong community engagement, and effective incentive programs**—all key indicators of long-term network value and adoption. As the DAO scales, these metrics illustrate a **healthy ecosystem**, positioning Zero Authority as a leader in decentralized community governance and reputation systems. *** --- id: about/stakeholder-updates/q4-2024 title: "Q4 2024" description: "July to December 2024" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/stakeholder-updates/q4-2024 related: [about/stakeholder-updates] tokens: 1154 --- # Q4 2024 Zero Authority's 2024 year-end recap: 130 gigs and 100 bounties, 42,874 STX exchanged, the other tokens and NFTs distributed, and the focus on onchain reputation and blockchain names for 2025. ![](https://zeroauthoritydao.ai/docs/img/d6120258fa47.webp) As 2024 comes to a close, Zero Authority DAO celebrates a remarkable year of empowering individuals and communities in the decentralized space. Our gig and bounty marketplace onchain has seen incredible activity, facilitating 130 gigs and 100 bounties 🚀. Over 41,639 STX were exchanged in gigs, along with 1,235 STX and a wide range of tokens through bounties 💎. These included 20,502 DOG, 146,000 LEO, 100,000 MEME, 578,444 PEPE, 480,000 PNUT, and 271,200 WELSH. To top it off, we distributed amazing NFT rewards like 2 Invader NFTs, 2 LEO NFTs, 1 MegaPont NFT, 3 CrashPunk NFTs, and 2 MOJO NFTs 🖼️🔥. These milestones highlight the energy and diversity of our ecosystem, creating countless opportunities for people worldwide. 🌍✨ The tokens exchanged include 20,502 DOG, 146,000 LEO, 100,000 MEME, 1,000,000 MemeGoat, 578,444 PEPE, 480,000 PNUT, 5,625 ROO, 271,200 WELSH, and 50,000 WEN. These numbers reflect the platform’s diverse and growing ecosystem, where users can earn and engage with a range of digital assets beyond just STX. With these token exchanges, Zero Authority continues to demonstrate the depth of its decentralized marketplace and the value it creates for participants. ***The Foundation of Zero Authority’s Protocol*** STX served as the lifeblood of the Zero Authority protocol in 2024, with a total of 42,874 STX exchanged through gigs and bounties. This strong reliance on STX showcases its significance as a currency of trust within the ecosystem. By integrating seamlessly with other tokens and assets, STX enables transparent, secure, and decentralized transactions, reinforcing its role as a cornerstone of the gig and bounty marketplace. 🚀✨ ***People Will Earn Their First Bitcoin And Crypto Via Gig Marketplace Onchain 💼💸***\ Zero Authority’s gig marketplace is the perfect place to earn your first Bitcoin or crypto! 🌟 By completing tasks directly onchain, users skip middlemen and dive straight into trustless and transparent opportunities. It’s simple, fair, and accessible for anyone with skills to share. Whether you're earning STX, BTC, or experimenting with other tokens, Zero Authority is the gateway to financial freedom and the world of crypto. 🚀💡 ***Continued Growth Of Communities With Bounties Onchain 🤝🎯***\ Bounties onchain are the ultimate way to unite communities and ignite collaboration! 💥 Organizations and DAOs can post bounties, rewarding contributors instantly with tokens and NFTs. This creates real value while strengthening connections among community members. From small tasks to big milestones, bounties drive engagement and help communities grow stronger together. 🌱💎 ***Reputation Onchain Is The New CV 🌐📜***\ In the decentralized world, your reputation onchain is your new CV! ✅✨ Forget resumes—what matters now is your history of contributions, endorsements, and completed tasks. Zero Authority’s reputation system tracks your impact, making it easy for others to trust and work with you. Your onchain activity speaks louder than traditional credentials, showing the world who you really are. 🌟🛠️ ***Names On The Blockchain As Social Verification (.Btc .Sol .Eth)🌌🔗*** The adoption of blockchain namespaces is expanding, with Ethereum Name Service (ENS) surpassing 2.9 million domains in 2023 ([ENS Stats](https://dune.com/sixdegree/ens-domain-registration-renewal-and-churned)), Solana Name Service (SNS) registering over 650,000 domains ([Solana Stats](https://docs.sns.id/collection/solana-name-service/register)), and .BTC domains gaining traction through ecosystems like Stacks ([BNS One](https://bns.one/)). Verification just got a Web3 upgrade! 🚀 Using your BTC, SOL, or ETH name shows the world your blockchain identity. 🌐 These names are more than just cool—they’re secure, decentralized, and instantly recognizable across platforms. At Zero Authority, we make it easy to leverage these identities, creating trust and unlocking opportunities everywhere you go. 🛡️💡 ***The Mission of Zero Authority In 2025 Is More Important 🌟🤝*** As we step into 2025, Zero Authority’s mission becomes more important than ever. 🛠️ In a world shifting to decentralization, trust and reputation are the foundation of progress. Our work to build a reputation layer for Web3 ensures that people and organizations can collaborate securely and transparently. By empowering individuals through gigs, bounties, and endorsements, we’re shaping a future where everyone has access to decentralized opportunities. 🌍🚀 Here’s to an even bigger and better 2025! Let’s keep building together. 💪✨🎉 --- id: govern/grants/endowment title: "Endowment Grants" description: "Last update June 1, 2026" product: zadao canonical: https://zeroauthoritydao.ai/docs/govern/grants/endowment related: [govern/grants] tokens: 351 --- # Endowment Grants Screenshots of the Endowment Grants flow: the grantee submits each milestone, a steward approves it, then the admin approves it. Grantee Role: ![](https://zeroauthoritydao.ai/docs/img/e6c236cda34b.webp) ![](https://zeroauthoritydao.ai/docs/img/47fd940936c4.webp) After submission: ![](https://zeroauthoritydao.ai/docs/img/8224991c3daf.webp) Steward/Reviewer sees this UI to review: ![](https://zeroauthoritydao.ai/docs/img/0103932f7f51.webp) After Reviewer/Steward Approve then the main admin sees this UI: ![](https://zeroauthoritydao.ai/docs/img/a415f933d819.webp) After the admin approves the submission the first milestone completes, and this UI is displayed: ![](https://zeroauthoritydao.ai/docs/img/fa663aa0ff3e.webp) ![](https://zeroauthoritydao.ai/docs/img/d6788ecb1544.webp) Again, the Grantee can see the Submit Button for new milestone: ![](https://zeroauthoritydao.ai/docs/img/1ffe19f33a30.webp) ![](https://zeroauthoritydao.ai/docs/img/d1d9beea7c4c.webp) After second milestone submission the grantee sees: ![](https://zeroauthoritydao.ai/docs/img/37f7e5f56c58.webp) Now, the steward can see the approve button after the grantee submission to approve. ![](https://zeroauthoritydao.ai/docs/img/66e4377dfcce.webp) When approved, the admin can see: ![](https://zeroauthoritydao.ai/docs/img/816e60672e1d.webp) After, Second milestone approved the UI looks like: ![](https://zeroauthoritydao.ai/docs/img/2e2348d053b7.webp) ![](https://zeroauthoritydao.ai/docs/img/409902a2f31a.webp) Again, the grantee sees the submit button for the next milestone: ![](https://zeroauthoritydao.ai/docs/img/246abe28523e.webp) ![](https://zeroauthoritydao.ai/docs/img/561c85bb5cc5.webp) When submitted, again the steward can see the same approve buttons:(Note, the admin can also do the steward approve if the steward is sick) Super Admin you can see new Link on side panel Role Management and this is the UI: ![](https://zeroauthoritydao.ai/docs/img/8ae0b09a995d.webp) --- id: govern/grants/degrants-3 title: "DeGrants 3" description: "January 2, 2026, New Grantee Onboarding" product: zadao canonical: https://zeroauthoritydao.ai/docs/govern/grants/degrants-3 related: [govern/grants] tokens: 814 --- # DeGrants 3 Onboarding for DeGrants 3 grantees: apply, pass steward review and complete your Zero Authority profile before funding. Also how admins pay a grantee with a Retroactive Gig. Welcome to **DeGrants 3**! 🎉\ This guide will walk you through the process of applying, setting up your profile, receiving funding, and shipping your project. *** ### 1. Submit Your Application * Go to [DeGrants](https://degrants.xyz/). * Select the **track** that best matches your project. * Provide clear details about your proposal, including goals and expected outcomes. *** ### 2. Steward Review * Community stewards will review your application. * They may reach out with questions or requests for clarification. * If approved, you’ll move on to the funding stage. *** ### 3. Create Your Zero Authority DAO Profile (Required Before Funding) Before receiving funding, you must create and complete your profile on [Zero Authority DAO](https://www.zeroauthoritydao.com/). **Steps:** 1. **Connect Your Wallet** * Open the Zero Authority DAO website. * Connect your wallet (Xverse, Hiro, Leather, etc.). 2. **Sign the Transaction** * Sign the transaction prompt to confirm your action. 3. **Edit & Complete Your Profile** * Once confirmed, you’ll be able to edit your profile. * In the **Services** section, be sure to select **“DeGrants.”** * Fill out the following: * ✅ Project name, team details, and relevant links * ✅ Your **X (Twitter) account** * ✅ Your **Telegram account** * ✅ A **profile picture (PFP)** * ✅ (Optional but recommended) A **BNS name** via [bns.one](https://bns.one/) for easier identity recognition 💡 **Tip:** Selecting **DeGrants** under Services ensures your profile is correctly associated with your grant. *** ### 4. Receive Funding * Once selected, you’ll receive starter funding (if applicable) or milestone-based payments. * Keep track of your milestones and ensure updates are delivered on time. *** ### 5. Ship Your Project 🚀 * Build and share your progress with the community. * Post updates regularly to keep everyone informed. * Launch your project into the wild and make an impact! *** ## Pay a Grantee This guide will walk you through the process of **funding milestones** for DeGrants. Once a milestone is completed and verified by the **Steward** and **DeGrants Administrators**, the Grantee becomes eligible for on-chain payment. 👉 Payments are **verifiable** on the Grantee’s profile:\ `https://www.zeroauthoritydao.com/profile/{STX-wallet-address}` *** ### Steps to Pay a Grantee #### 1. Find the Creator * Go to: [Zero Authority DAO – Creators](https://www.zeroauthoritydao.com/creators) * Search for the Grantee’s profile (by name, wallet, or BNS). *** #### 2. Offer a Gig * On the creator’s profile, select **Offer Gig**. *** #### 3. Choose Retroactive Gig * Select **Retroactive Gig** so the payment is processed as a **one-time milestone payout**. *** #### 4. Fill In Gig Details * Add a **Name** (e.g., “Milestone 1 Payment – Project X”). * Add a **Description** (e.g., “Payment for successful completion of milestone 1 as verified by steward”). *** #### 5. Confirm & Submit * Review all details. * Confirm the transaction. * Submit on-chain — payment will be publicly visible on the Grantee’s profile. *** 💡 **Tip:** Always double-check the wallet address and milestone details before confirming the transaction. --- id: about/roadmap title: "The Roadmap" description: "The Zero Authority Roadmap refers to the strategic transition of a decentralized project (often in the blockchain or Web3 space) from a centralized founding team to a fully communit" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap related: [about, about/roadmap/v3, about/roadmap/decentralizing-future-of-work, about/roadmap/overview, about/roadmap/veritas-omnia-vincit, about/roadmap/product, about/roadmap/detailed, about/roadmap/smarttrail, about/roadmap/bounty, about/roadmap/gigs] tokens: 200 --- # The Roadmap Describes the Zero Authority Roadmap: Trajan Corporation's plan to move the Web3 gig economy from a centralized platform to an onchain ecosystem on Stacks, ending with the protocol governed entirely by its community. Trajan Corporation is pioneering the Zero Authority Roadmap to transition the Web3 gig economy from a centralized platform model to a sovereign, onchain ecosystem powered by reputation and Bitcoin-backed smart contracts. By systematically decentralizing governance through the Zero Authority DAO and automating trust via the Stacks blockchain, Zero Authority is building a "permissionless marketplace" where creators, companies, agents, and autonomous organizations own their professional data and execution is secured by code rather than corporate oversight. This roadmap outlines a deliberate shift from Trajan’s initial role as a foundational architect to a final state of "Zero Authority," where the protocol becomes a public good governed entirely by its community of builders and contributors. --- id: about/roadmap/v3 title: "Zero Authority V3" description: "July 1, 2026 - An AI-Native Platform for Communities to Coordinate, Build, and Ship Together" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap/v3 related: [about/roadmap] tokens: 996 --- # Zero Authority V3 Announces Zero Authority V3 (July 1, 2026): what Stacks Endowment grant Milestones 1 and 2 delivered, including the launch of zadao.ai and mintable AI agents, and the next onchain agent integrations. ![](https://zeroauthoritydao.ai/docs/img/9b072a9a1d10.webp) ## FOR IMMEDIATE RELEASE ## Zero Authority Unveils V3: An AI-Native Platform for Communities to Coordinate, Build, and Ship Together **Zero Authority V3**, is the next evolution of its open collaboration platform, introducing AI agents, bounties, quests, gigs, events, and on-chain reputation into a single unified experience. As a recipient of the **Stacks Endowment Grant Program**, Zero Authority has been building toward an agent-first future where AI becomes the primary interface for discovering opportunities, coordinating work, and contributing across decentralized communities. The launch of **zadao.ai** marks the successful completion of **Milestone 2: Agentic UX Deployment and Platform Integration**. Built for builders, DAOs, startups, and open-source communities, Zero Authority V3 enables contributors to discover opportunities, launch specialized AI agents, earn on-chain Reputation (REP), and coordinate meaningful work from one platform. Users can instantly deploy purpose-built AI agents, including **Mint Ecosystem Scout, Mint SIP Legend, Mint Bounty Hunter, Mint Bitflow Trader, Mint Zest Lender,** and **Mint Market Analyst**, allowing communities to automate research, governance, ecosystem discovery, and collaboration in minutes. > *"Communities shouldn't have to stitch together dozens of disconnected tools. Zero Authority V3 brings collaboration, funding, reputation, and AI into one coordinated workspace where both people and agents can contribute."* ### Milestone 1 & 2 Highlights Through support from the **Stacks Endowment Grant Program**, Zero Authority has delivered major advancements across both project milestones. #### Milestone 1 – Foundation & Community Infrastructure Milestone 1 established the foundation for the Zero Authority ecosystem by delivering the core infrastructure needed for decentralized collaboration. **Delivered:** * Grants, Bounties, Gigs, Quests, Events, and SIP Tracker * On-chain Reputation (REP) and contributor identity * Unified community workspace for collaboration and funding * Modular platform architecture designed for AI integration * Open infrastructure built for the Bitcoin ecosystem #### Milestone 2 – Agentic UX Deployment & Platform Integration Milestone 2 transformed Zero Authority into an AI-native platform where users interact through natural conversation instead of traditional workflows. **Delivered:** * Launch of **zadao.ai** * Conversational AI for creating gigs, bounties, quests, and other opportunities * AI-assisted navigation and contextual recommendations across the platform * Specialized AI agents that collaborate to brainstorm ideas, evaluate proposals, and assist communities * Unified integration across Grants, SIP Tracker, Bounties, Quests, Events, and Gigs * Foundation for autonomous on-chain agents and wallet-enabled AI Rather than adding AI as another feature, Zero Authority rebuilt the user experience around intelligent agents that help users discover opportunities, coordinate work, and complete tasks faster. ### Looking Ahead With Milestone 2 complete, development now shifts toward enabling agents to securely interact on-chain. Integrations include: * **MCP** native embedded functionality for deeper cross-chain integrations * **AIBTC** for autonomous AI coordination * **STXPay** for embedded wallet functionality * Permissioned agent wallets capable of executing transactions on a user's behalf * Multi-agent collaboration for governance, funding, and ecosystem participation These capabilities move Zero Authority closer to a future where communities coordinate through intelligent agents while maintaining user ownership, transparency, and decentralized control. Zero Authority V3 represents a major step toward an agentic internet—one where AI doesn't replace communities, but empowers them to build, coordinate, and grow together. **Explore Zero Authority V3:** [https://zadao.ai](https://zadao.ai/) --- id: about/roadmap/overview title: "Road Map Overview" description: "\"the onchain economy is powered by reputation\"" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap/overview related: [about/roadmap] tokens: 956 --- # Road Map Overview Lists the four roadmap phases of the Zero Authority DAO Cerulean marketplace: foundation, expansion, Web3 integration with multi-chain support via Chainlink CCIP, and evolution into a Web3 infrastructure hub. ## **Road Map Overview: Decentralized Work's Future Unleashed** ### **Phase 1: Foundation** * *Zero Authority DAO:* Establish a robust governance structure, empowering users in decision-making. * *Smart Contracts:* Integrate smart contracts for efficiency and lower transaction costs. * *Tokenized Reputation:* Launch an immutable system showcasing user skills transparently. * *Self-Sovereign Identity:* Implement user-centric identity solutions for privacy. ### **Phase 2: Expansion** * *Community Engagement:* Foster an engaged, global community through outreach and inclusivity. * *Global Accessibility:* Break geographical barriers, creating an inclusive marketplace. * *Lowering Entry Barriers:* Streamline onboarding to attract diverse users. ### **Phase 3: Web3 Integration** * *Decentralized Autonomous Rewards:* Implement transparent smart contracts for fair rewards. * *Blockchain Agnosticism:* Position Zero Authority DAO | Cerulean Mkpl as a pioneer in blockchain agnosticism, ensuring compatibility with various blockchain networks. This strategic move allows the platform to adapt and thrive across different blockchain environments, maximizing accessibility and inclusivity for users. * *Expansion to Top 10 Layer 1 Chains:* Propel the platform's growth by expanding its presence to the top 10 layer 1 blockchain networks. This expansion ensures that users can leverage the benefits of Zero Authority DAO | Cerulean Mkpl across a diverse range of blockchain ecosystems, promoting widespread adoption and user engagement. * *Utilizing Chainlink's CCIP:* Implement Chainlink's Cross-Chain Interoperability Protocol (CCIP) to achieve seamless cross-chain compatibility. By integrating Chainlink's robust infrastructure, the platform ensures that users can interact and transact across different blockchain networks effortlessly, fostering a truly interconnected and decentralized marketplace. * *Web3 Version Optimization:* Enhance the Web3 version of the platform to fully leverage the benefits of blockchain agnosticism and cross-chain compatibility, providing users with a unified and streamlined experience regardless of the blockchain they choose. ### **Phase 4: Evolution and Sustainability (and Beyond)** * *Web3 Infrastructure Hub:* Evolve into the go-to Web3 infrastructure gig marketplace, offering a versatile platform where freelancers from Web3 or Web2 networks can utilize Zero Authority as both infrastructure and front-end for their communities. * *Access Control via Tokens:* Introduce a system allowing freelancers to gate access to their communities using either fungible or non-fungible tokens, providing a flexible and secure means of managing memberships. * *Collaborative Integration:* Encourage seamless collaboration by facilitating the integration of diverse freelancing networks, fostering an interconnected ecosystem where users can easily navigate and engage across different communities. * *Smart Contract Customization:* Enable freelancers to customize smart contracts according to their specific community needs, ensuring flexibility and adaptability for a wide range of projects within the Web3 and Web2 space. * *Decentralized Governance Features:* Implement advanced decentralized governance features, empowering freelancers to actively participate in shaping the rules and regulations governing their communities, further enhancing the democratic nature of the Zero Authority platform. ### **Thoughts on the Zero Authority:** The journey ahead for the Zero Authority DAO | Cerulean Mkpl is marked by decentralization, empowerment, and innovation. As we navigate, we invite our community to remember why they started – to be part of a transformative movement reshaping decentralized work. Together, we pave the way for a more equitable decentralized marketplace. --- id: about/roadmap/veritas-omnia-vincit title: "Veritas Omnia Vincit" description: "This is the spirit behind Zero Authority V2 Beta." product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap/veritas-omnia-vincit related: [about/roadmap] tokens: 520 --- # Veritas Omnia Vincit Explains why Zero Authority V2 Beta was built around onchain transparency, and lists its tools: gigs, bounties and endorsements onchain, plus NOVA AI agents and bots. *"Truth Conquers All."* ### Why Zero Authority V2? Traditional systems of governance and coordination rely on opaque decision-making and permissioned gatekeepers. Even in Web3, too many protocols fall short when it comes to **verifiable transparency**. Zero Authority V2 is our answer — a platform designed to bring a **new level of transparency to trustless, permissionless protocols**. Every action, interaction, and contribution is recorded onchain, where communities can verify, audit, and engage without reliance on hidden processes or closed systems. ### What Are the Benefits? * **Onchain accountability** — every gig, bounty, endorsement, or bot action is traceable and verifiable. * **No centralized gatekeepers** — you don’t need permission to contribute, create, or build reputation. * **Trust by design** — protocols and communities can coordinate without needing to trust individuals. * **Real-time transparency** — see how decisions are made, how funds flow, and how contributors participate. ### What Are the Solutions? Zero Authority V2 provides **modular, onchain tools** that enable decentralized communities and protocols to operate with confidence: #### 💼 Gigs Onchain Create, accept, and complete task-based work entirely onchain. Payments, deliverables, and reputation all happen transparently. #### 🏹 Bounties Onchain Launch and fulfill bounties directly onchain — no intermediaries, no off-chain tracking, just direct proof of contribution. #### 🌟 Endorsements Onchain Enable community members to endorse each other’s work and contributions with permanent, verifiable records. Build your reputation where it matters: on the blockchain. #### 🤖 NOVA AI + Bots Onchain Deploy **NOVA**, our AI-powered agents and bots, to assist in governance, moderation, coordination, and transparency — all operating visibly and trustlessly onchain. *** This is just the beginning. Zero Authority V2 Beta invites builders, creators, and communities to join us in proving that **trust starts with transparency** — and transparency starts onchain. *** --- id: about/roadmap/product title: "Product Roadmap" description: "This page provides a detailed roadmap of the product development plan for ZeroAuthority. It outlines the major milestones and goals for the product, including features, updates, and releases." product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap/product related: [about/roadmap] tokens: 1727 --- # Product Roadmap Lists Zero Authority product releases from V1.0.0 Balaji (summer 2023) to V2.2.0 SmartTrail: Hiro Wallet profiles, Web3 profiles, reputation on chain, V2 Novum Initium and the Projects Module. ## V1.0.0 Balaji release Summer 2023 Own your profile data. Own your work data. Marketplace matches people who provide a service and people looking for a service. Connecting Hiro Wallet allows you to own your profile and work data on the marketplace. The marketplace is designed to match people who provide a service with people who are looking for a service. By owning your data, you have greater control over your personal information and can ensure that it is secure and protected. With Hiro Wallet, you can securely store your profile and work data on the blockchain, which provides an immutable and transparent record of your information. This allows you to maintain greater control over your data and ensures that it cannot be tampered with or modified without your consent. The marketplace matches service providers with customers based on their needs and preferences, creating a more efficient and effective system for connecting people with the services they need. By using a decentralized marketplace, users can benefit from greater transparency, lower fees, and more direct access to service providers. Overall, by connecting Hiro Wallet to the marketplace, users can own their data, control their online identity, and participate in a more transparent and efficient system for accessing and providing services. ## V1.1.0 release Web3 Profiles Own your profile data. Add details about yourself and your favorite NFT as PFP. Decentralized profiles provide information to connect with the community and empower creators. Web3 profiles are decentralized profiles that allow users to own their profile data and share information about themselves in a secure and transparent manner. With a web3 profile, users can add details about themselves and their favorite NFTs as their profile picture. By owning their profile data, users can control their online identity and ensure that their personal information is kept secure and private. Web3 profiles also enable users to connect with the community in a more direct and decentralized manner, empowering creators to build and engage with their audiences in new and innovative ways. Web3 profiles can be particularly useful for creators, who can use their profiles to showcase their work and connect with potential collaborators and clients. By providing information about their skills, experience, and favorite NFTs, creators can build a more authentic and transparent online presence, which can help them to attract new followers and grow their audience. Overall, web3 profiles offer a decentralized and transparent approach to online identity and community building, providing users with greater control over their personal information and empowering creators to connect and engage with their audiences in new and innovative ways. ## V1.2.0 release Reputation On Chain Own your data. a decentralized reputation system built on blockchain technology has the potential to provide greater transparency, security, and trust A reputation on chain is a decentralized reputation system that uses blockchain technology to provide greater transparency, security, and trust in online interactions. By leveraging the immutability and transparency of the blockchain, a reputation on chain can provide users with greater control over their personal data and online identity. With a reputation on chain, users can own and control their data, allowing them to manage their online reputation in a more secure and transparent manner. Users can also be incentivized to contribute to the reputation system, helping to maintain its accuracy and reliability. A reputation on chain can be particularly useful in e-commerce, peer-to-peer marketplaces, and other online communities where trust is essential. By providing a decentralized and transparent reputation system, users can have greater confidence in the reliability and integrity of their online interactions, leading to greater trust and improved overall user experiences. ## V2.0.0 Novum Initium release A New Beginning The V2.0.0 Novum Initium release marks a new beginning for the platform, introducing a range of new features and improvements that enhance the user experience and provide a competitive advantage. ## V2.1.0 release Projects Module - release date tbd The Projects Module provides a flexible and scalable approach to project management, enabling users to leverage specialized skills, reduce overhead costs, and achieve quick turnaround times. By offering a range of tools and features designed specifically for project management, the module provides a centralized platform for users to collaborate and manage their projects. This allows for greater visibility and control over project timelines, deliverables, and resources. The module also offers flexibility in terms of project scope and scale, allowing users to easily scale their projects up or down as needed. This ensures that projects can be completed on time and within budget, while also enabling users to adapt to changing business needs and priorities. Additionally, the module facilitates the leveraging of specialized skills and expertise, enabling users to easily identify and engage with the right talent for their projects. This results in improved project outcomes and reduced costs, as users can more efficiently allocate resources and leverage specialized expertise. Overall, the Projects Module offers a powerful set of tools and features for project management, providing users with greater flexibility, scalability, and cost-effectiveness. This module is particularly useful for businesses and organizations that need to manage complex projects with multiple stakeholders and resources. ## V2.2.0 SmartTrail release Web3 Security Module. See [SmartTrail](https://zeroauthoritydao.ai/docs/about/roadmap/smarttrail.md). A security module is a software component designed to enhance the security of a system or application. It typically includes a range of features and tools that help to detect and mitigate security vulnerabilities. Some common functions of a security module include: * Vulnerability detection: A security module can scan for vulnerabilities in an application or system, such as outdated software or misconfigured settings. * Secure software development: A security module can provide tools and guidelines for secure software development practices, such as secure coding standards and testing procedures. * Code review: A security module can analyze source code for potential security issues and provide feedback to developers on how to address them. * Compliance auditing: A security module can help ensure that a system or application complies with industry standards and regulations, such as HIPAA or PCI-DSS. Client can improve the overall security of their systems and applications, reduce the risk of data breaches or other security incidents, and demonstrate a commitment to security best practices. --- id: about/roadmap/detailed title: "Roadmap Detailed" description: "Digital wallets and data ownership have the potential to reshape online interactions and empower individuals, to build a user-friendly and robust Web3 ecosystem." product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap/detailed related: [about/roadmap] tokens: 1547 --- # Roadmap Detailed Lists planned Zero Authority frontend items (universal profiles, reputation on-chain, Expertia, global front end) and backend items (wallet connect, notifications, gig and challenge contracts, SIPs, DAO contract). ## Frontend Development: Bringing Web3 to Life We want to craft beautiful, user-friendly interfaces for websites and web applications. It's the magic you see, the pixels that dance on your screen, the buttons you click, and the forms you fill. Think of it as the paintbrush that brings the digital canvas to life. * Responsive Design: In today's multi-device world, websites and applications need to adapt seamlessly to different screen sizes and resolutions. Frontend developers employ responsive design techniques to ensure users have a consistent experience across desktops, tablets, and mobile devices. * Performance Optimization: Nobody enjoys a slow website. Frontend developers optimize code and leverage caching techniques to ensure fast loading times and smooth interactions. * Accessibility: Making the web accessible to everyone is crucial. Frontend developers implement best practices to ensure websites are usable by users with disabilities, including those using screen readers or assistive technologies. * Open-source software development kits (SDKs) and application programming interfaces (APIs) are powerful tools that accelerate and simplify frontend development. 1\. Universal Profiles: * Description: Create a universal profile system that aggregates and displays a user's activity and contributions across various Web3 platforms. Think of it as a decentralized LinkedIn for the pseudonymous economy. * Benefits: * Enhances reputation and trust within the DAO. * Allows users to showcase their skills and expertise. * Facilitates collaboration and project discovery. 2\. Reputation On-Chain: * Description: Integrate reputation metrics directly onto the blockchain, providing a transparent and verifiable record of user contributions. * Benefits: * Increases trust and accountability within the DAO. * Enables reputation-based rewards and incentives. * Creates a more meritocratic system of governance. 3\. Expertia Release: * Description: Launch a platform for experts to offer their services and knowledge to the DAO community. This could include consulting, mentorship, and project-specific expertise. * Benefits: * Provides valuable resources for DAO projects. * Generates income for experts within the community. * Fosters collaboration and knowledge sharing. 4\. Global Front End: * Description: Develop localized versions of the DAO platform to reach a wider global audience. Allow projects, protocols, teams, and any entity to implement the frontend and give their community a place to earn rewards and reputation and connect to the global network. * Benefits: * Expands the DAO's reach and influence. * Makes the platform accessible to diverse communities. * Promotes cultural exchange and collaboration. ## Backend Development: The Invisible Engine of Web Experiences Backend development is the magic behind the curtain, the unsung hero of the web. It's the intricate machinery that powers the interactive experiences you enjoy online, from streaming movies to shopping for clothes to collaborating with colleagues. While front-end development focuses on the user interface and what you see, backend development handles everything that happens in the background, making it all tick. * Powering the Digital World: Backend development forms the foundation for countless online experiences, from e-commerce platforms to online education tools to social media. * High-Demand Skills: Backend developers are in high demand across various industries, making it a lucrative career path. * Problem-Solving and Creativity: Backend development requires logical thinking, problem-solving skills, and creativity to design efficient and secure systems. * Continuous Learning: The tech landscape constantly evolves, and backend developers must stay up-to-date with new technologies and trends to remain relevant. 1\. Connect Wallet: * Description: Implement seamless integration with various Web3 wallets to facilitate easy access to DAO functionalities. * Benefits: * Improves user experience and accessibility. * Increases participation and engagement within the DAO. * Enables secure and transparent transactions. 2\. Notification Systems: * Description: Develop a comprehensive notification system to inform users about relevant DAO events, proposals, and updates. * Benefits: * Enhances community engagement and participation. * Ensures transparency and accountability within the DAO. * Improves overall user experience. 3\. Upgrade Gig Contracts: * Description: Enhance the functionality and flexibility of Gig Contracts, the DAO's system for freelance work and project collaboration. * Benefits: * Attracts more talent and projects to the DAO. * Enables more complex and nuanced work arrangements. * Streamlines the project development process. 4\. Challenge Contract: * Description: Introduce a new contract type for incentivized challenges and competitions to drive innovation and community engagement within the DAO. * Benefits: * Fosters creativity and problem-solving within the community. * Discovers new talent and ideas for DAO projects. * Creates a fun and engaging way to contribute. 5\. New SIP Stacks Improvement Proposals: * Description: Continuously improve the functionality and security of the Stacks blockchain through ongoing SIPs. * Benefits: * Ensures the stability and scalability of the DAO platform. * Opens up new possibilities for development and innovation. * Maintains the DAO's position at the forefront of Web3 technology. 6\. DAO Contract: * Description: Continuously update and optimize the core DAO contract to ensure efficient governance, transparency, and security. * Benefits: * Maintains the integrity and effectiveness of the DAO's decision-making process. * Protects the DAO's funds and resources. * Enables the DAO to adapt and evolve over time. By implementing these ambitious roadmap items, Zero Authority DAO aims to create a robust, transparent, and globally accessible ecosystem for Web3 collaboration and innovation. Remember, this roadmap is a living document and may evolve over time based on community feedback and changing needs. --- id: about/roadmap/smarttrail title: "SmartTrail" description: "Includes a range of features and tools that help to detect and mitigate security vulnerabilities." product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap/smarttrail related: [about/roadmap] tokens: 800 --- # SmartTrail Describes SmartTrail, a Web3 security tool whose intelligent agents and human reviewers detect smart contract threats, and how creators use its reports to plan and apply remediation. ![](https://zeroauthoritydao.ai/docs/img/5e72eb199444.webp) SmartTrail is a web3 security solution that uses intelligent agents to protect web3 environments from smart contract attacks. By utilizing machine learning and analytics, SmartTrail's agents can detect potential threats and respond quickly to prevent harm. As an intelligent agent, SmartTrail can perceive its environment and take autonomous actions to achieve its security goals. It continuously learns and improves its performance by analyzing data from the blockchain network. SmartTrail is a cutting-edge web3 security solution that uses intelligent agents to identify and mitigate potential threats before they cause damage to the network. The system also employs human reviewers to verify and investigate any suspicious activities detected by the agents. This human oversight ensures maximum protection against attacks and minimizes the occurrence of false positives. With the combination of human expertise and machine intelligence, SmartTrail provides comprehensive and reliable protection against smart contract attacks. How SmartTrail is a cutting-edge web3 security solution that uses intelligent agents to identify and mitigate potential threats in web3 smart contracts: * SmartTrail employs advanced machine learning and analytics techniques to analyze and monitor blockchain networks in real-time. * Its intelligent agents are constantly learning and improving their performance by acquiring knowledge from the blockchain network. * SmartTrail's intelligent agents can quickly detect any potential threats in web3 smart contracts and take immediate action to prevent them from causing harm. * The system uses a combination of human reviewers and intelligent agents to ensure that any suspicious activities are thoroughly investigated and verified. * SmartTrail provides a comprehensive and robust web3 security solution that combines the best of human expertise and machine intelligence to protect against smart contract attacks. * By detecting and mitigating potential threats before they cause significant harm to the network, SmartTrail helps to ensure the stability and security of the web3 environment. How creators can leverage SmartTrail to perform remediation from the tool identifying potential threats and vulnerabilities: * Once SmartTrail identifies potential threats and vulnerabilities in your web3 smart contracts, it will provide detailed reports on the issues found. * Review the reports provided by SmartTrail carefully to understand the nature of the threats and vulnerabilities. * Work with SmartTrail to develop a remediation plan based on the findings. SmartTrail's team of experts can assist you in this process. * Implement the remediation plan to address the identified threats and vulnerabilities. * Regularly monitor your smart contracts using SmartTrail to ensure that any new threats or vulnerabilities are identified and addressed promptly. * Consider leveraging SmartTrail's intelligent agents and human reviewers to continually improve your web3 security posture. * Collaborate with SmartTrail in the Cerulean Marketplace to ensure that your web3 smart contracts are secure and protected from potential attacks. --- id: about/roadmap/bounty title: "Bounty" description: "Welcome to our Bounties on zero authority!" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap/bounty related: [about/roadmap] tokens: 189 --- # Bounty Adds details to the bounty docs: bounties have a start date, and the $STX reward is locked in a Clarity smart contract until the client picks a winner, then released automatically. ## Bounties Overview The bounties system connects clients with people ready to take on specific tasks and projects: clients post bounties, manage submissions, and reward the best work with $STX, the native cryptocurrency of the Stacks blockchain. What a bounty is, why it runs onchain and how to create one are covered in [Bounty Onchain](https://zeroauthoritydao.ai/docs/work/bounties.md). Details this page adds: * **Start Date**: besides the end date, a bounty has a start date, when it opens for submissions. * **Reward in a Clarity contract**: the $STX reward is locked in a Clarity smart contract until the client selects a winner, then released to the winner automatically. * **Transparency**: all transactions and contract interactions are recorded on the Stacks blockchain. --- id: about/roadmap/gigs title: "Gigs" description: "Zero Authority DAO | Gig Mkpl vs. Traditional Platforms: P2P Networks in the Web3 Era" product: zadao canonical: https://zeroauthoritydao.ai/docs/about/roadmap/gigs related: [about/roadmap] tokens: 922 --- # Gigs Compares the Zero Authority DAO Cerulean gig marketplace with Upwork, LinkedIn and Gumroad: decentralization, smart contracts, tokenized reputation, self-sovereign identity, lower fees and its Web3 version. The Zero Authority DAO | Gig "Cerulean" Marketplace is changing the traditional P2P networks in the Web3 space by prioritizing decentralization, ownership, and a tokenized reputation system, distinguishing itself from platforms like Upwork, LinkedIn, and Gumroad and paving the way for a more equitable and empowering decentralized marketplace. In the dynamic landscape of decentralized ecosystems, the Zero Authority DAO | Gig Mkpl emerges as a groundbreaking platform, redefining the way we perceive and engage in peer-to-peer (P2P) networks. By drawing comparisons with traditional platforms such as Upwork, LinkedIn, and Gumroad, the Gig Mkpl showcases a myriad of key features and benefits that set it apart in the Web3 space. ## Key Features: * Decentralization: Unlike Upwork and LinkedIn, which operate with centralized authority, the Gig Mkpl leverages decentralized autonomous organization (DAO) principles. This ensures a trustless and transparent environment where users have greater control over their data and transactions. * Smart Contracts: The use of smart contracts on the Gig Mkpl automates and secures transactions. This eliminates the need for intermediaries, reducing costs and increasing efficiency compared to traditional platforms like Gumroad. * Tokenized Reputation: Gig Mkpl introduces a tokenized reputation system on the blockchain. This ensures that user ratings and reviews are immutable, fostering a more genuine representation of an individual's skills and reliability compared to the subjective nature of reputation on Upwork or LinkedIn. * Self-Sovereign Identity: Users on the Cerulean Mkpl have control over their identity and personal information. This contrasts with LinkedIn, where user data is centralized, and privacy concerns may arise. ## Benefits: * Ownership of Data: Cerulean Mkpl users have true ownership of their data. This departure from the data-hungry models of LinkedIn and Upwork ensures that individuals retain control over their professional information and are not subject to third-party exploitation. * Lower Fees: With the elimination of intermediaries and the use of smart contracts, Cerulean Mkpl significantly reduces transaction fees compared to traditional platforms like Gumroad, enabling creators and freelancers to maximize their earnings. * Global Accessibility: The decentralized nature of Cerulean Mkpl ensures that users from any corner of the world can participate without restrictions, fostering a more inclusive global marketplace compared to region-specific limitations on Upwork and Gumroad. #### Web3 Version: Unlocking Rewards and Reputation Cultivation The Gig Mkpl's transition to a Web3 version is a pivotal evolution. By embracing blockchain technology, users can now cultivate their reputation on the platform through verifiable and transparent interactions. Smart contracts ensure that rewards are directly tied to one's contribution, creating a merit-based system that is free from centralized biases. In the Web3 version, users experience a gamified ecosystem where active participation and positive contributions lead to tangible rewards. This shift from a passive reputation model to an active one not only incentivizes quality work but also fosters a sense of community and collaboration. The Zero Authority DAO | Gig Mkpl stands as a beacon of innovation in the Web3 space, challenging the conventions of traditional P2P networks. By prioritizing decentralization, ownership, and a tokenized reputation system, it not only sets itself apart from Upwork, LinkedIn, and Gumroad but also paves the way for a more equitable and empowering future in the realm of decentralized marketplaces. --- id: legal/terms title: "Terms of Service" description: "Effective Date: January 1, 2026" product: zadao canonical: https://zeroauthoritydao.ai/docs/legal/terms related: [legal] tokens: 1860 --- # Terms of Service Zero Authority D/B/A Trajan Terms of Service, effective January 1, 2026: eligibility (18+), permitted use, blockchain and DAO disclosures, no financial advice, liability limits and Washington State law. **Zero Authority D/B/A Trajan**\ **Website:** [https://www.zeroauthoritydao.com](https://www.zeroauthoritydao.com/) These Terms of Service (“Terms”) govern your access to and use of the website, applications, platforms, tools, and services provided by **Zero Authority D/B/A Trajan** (“Zero Authority,” “Trajan,” “we,” “us,” or “our”), including but not limited to [https://www.zeroauthoritydao.com](https://www.zeroauthoritydao.com/) (collectively, the “Platform”). By accessing or using the Platform, you agree to be legally bound by these Terms. If you do not agree, you may not access or use the Platform. *** ### 1. Legal Structure and Nature of the Platform Zero Authority operates as a decentralized ecosystem and digital coordination platform. Some components of the Platform may involve decentralized governance mechanisms, blockchain infrastructure, community coordination tools, and autonomous systems. You acknowledge that: * The Platform may involve decentralized technologies. * Some services may be community-driven or algorithmically mediated. * Certain interactions may not be controlled by a single centralized authority. * Blockchain transactions are irreversible and publicly visible. Use of the Platform is at your own risk. *** ### 2. Eligibility You must: * Be at least 18 years old (or legal age in your jurisdiction). * Have legal capacity to enter into binding agreements. * Not be prohibited from using digital services under applicable laws. By using the Platform, you represent and warrant that you meet these requirements. *** ### 3. Account Registration and Access Some features require account creation. You agree to: * Provide accurate and truthful information * Maintain the security of your credentials * Be responsible for all activity under your account * Immediately notify us of unauthorized use We reserve the right to suspend or terminate accounts for violations of these Terms. *** ### 4. Permitted Use You agree not to: * Use the Platform for illegal purposes * Engage in fraud, manipulation, deception, or misrepresentation * Interfere with system integrity or security * Attempt unauthorized access to systems or data * Abuse, harass, or harm other users * Scrape, extract, or harvest data without permission * Reverse-engineer platform systems *** ### 5. Intellectual Property All content, systems, branding, interfaces, designs, software, documentation, and trademarks are owned by or licensed to Zero Authority D/B/A Trajan unless otherwise stated. You are granted a limited, non-exclusive, non-transferable, revocable license to use the Platform for its intended purpose. No ownership rights are transferred. *** ### 6. Blockchain and Crypto Disclosures You acknowledge and agree: * Blockchain transactions are irreversible. * Digital assets may be volatile in value. * Smart contracts may contain bugs or vulnerabilities. * On-chain data is public and permanent. * Wallet interactions are user-controlled. * We do not control external blockchains, protocols, or networks. * We are not responsible for network failures, congestion, forks, or exploits. Use of blockchain systems is at your own risk. *** ### 7. Data Collection and Use #### 7.1 Data We May Collect We may collect and process: * Account information (email, identifiers, metadata) * Technical data (IP address, device type, browser, OS, logs) * Usage data (features used, interactions, session activity) * Analytics data * Wallet addresses and on-chain interaction data * Communication data (messages, support requests, submissions) * Community activity data * Platform performance metrics *** ### 8. Data Usage Purposes Your data may be used for: * Platform operation and maintenance * Security and fraud prevention * Analytics and system improvement * Governance analytics * Community coordination * Feature optimization * Service delivery * Compliance with legal obligations * Platform research and development *** ### 9. Data Sharing We may share data with: * Infrastructure providers * Analytics services * Security services * Legal authorities (when required by law) * Compliance partners * Platform integrators We do **not** sell personal data as a business model. *** ### 10. On-Chain Data Disclaimer Any data written to a blockchain is: * Public * Permanent * Immutable * Outside our control You are solely responsible for what data you publish on-chain. *** ### 11. User Content If you submit content (text, code, proposals, data, media, feedback, or contributions), you grant Zero Authority a **non-exclusive, global, royalty-free license** to use, store, display, distribute, and process that content for platform operations, governance, analytics, and ecosystem development. You retain ownership of your content. *** ### 12. DAO, Governance, and Community Systems Some platform features may include: * Governance mechanisms * Voting systems * Proposals * Bounties * Quests * Endorsements * Reputation systems * Community-driven decision processes These systems may be: * Automated * Community-governed * Algorithmically mediated * Non-binding in legal jurisdictions Participation does not create employment, partnership, fiduciary duty, or agency relationships. *** ### 13. No Financial, Legal, or Investment Advice Nothing on the Platform constitutes: * Financial advice * Investment advice * Legal advice * Tax advice * Securities offerings * Guarantees of profit or return You are responsible for your own decisions and risk assessment. *** ### 14. Disclaimers The Platform is provided **“AS IS”** and **“AS AVAILABLE.”**\ We make no warranties regarding: * Availability * Reliability * Accuracy * Security * Fitness for purpose * Error-free operation * Data integrity *** ### 15. Limitation of Liability To the maximum extent permitted by law, Zero Authority D/B/A Trajan shall not be liable for: * Loss of funds * Loss of data * Loss of profits * Business interruption * Security breaches * Smart contract failures * Blockchain failures * Governance outcomes * DAO decisions * Community actions * Protocol exploits * Network failures Total liability shall not exceed the amount paid by you (if any) to use the Platform in the prior 12 months. *** ### 16. Indemnification You agree to indemnify and hold harmless Zero Authority D/B/A Trajan from any claims, damages, losses, liabilities, and expenses arising from: * Your use of the Platform * Your content * Your actions * Your violations of these Terms * Your violation of applicable laws *** ### 17. Termination We may suspend or terminate access: * Without notice * For violations * For security risks * For legal compliance * For platform integrity * For operational necessity *** ### 18. Governing Law These Terms are governed by the laws of the **State of Washington, United States**, without regard to conflict of law principles. *** ### 19. Severability If any provision is found unenforceable, the remaining provisions remain in full force and effect. *** ### 20. Entire Agreement These Terms constitute the entire agreement between you and Zero Authority D/B/A Trajan regarding use of the Platform. *** ### 21. Contact **Zero Authority D/B/A Trajan**\ Website: [https://www.zeroauthoritydao.com](https://www.zeroauthoritydao.com/)\ Email: Address: 611 South DuPont Highway Suite 102, City of Dover, DE 19901 *** --- id: legal/privacy title: "Privacy Policy" description: "Effective Date: January 1, 2026" product: zadao canonical: https://zeroauthoritydao.ai/docs/legal/privacy related: [legal] tokens: 1286 --- # Privacy Policy Zero Authority D/B/A Trajan Privacy Policy, effective January 1, 2026: what personal, technical, usage and blockchain data the platform collects, how it is used, shared and retained, and your rights. **Zero Authority D/B/A Trajan**\ **Website:** [https://www.zeroauthoritydao.com](https://www.zeroauthoritydao.com/) This Privacy Policy explains how **Zero Authority D/B/A Trajan** (“Zero Authority,” “Trajan,” “we,” “us,” or “our”) collects, uses, stores, shares, and protects your personal data when you access or use our platform, services, and website (collectively, the “Platform”). We believe privacy is not a feature — it’s infrastructure. By using the Platform, you consent to the practices described in this Policy. *** ### 1. Scope This Policy applies to: * Website visitors * Platform users * Contributors * Community members * DAO participants * Developers * Governance participants * Ecosystem partners It covers both off-chain and on-chain interactions. *** ### 2. Core Privacy Principles We follow these principles: * **Data minimization** — collect only what we need * **Purpose limitation** — use data only for defined purposes * **Transparency** — clear use and disclosure * **Security** — protect systems and access * **User control** — respect user rights * **Decentralization-aware** — acknowledge on-chain realities *** ### 3. Data We Collect #### A. Personal Data May include: * Email address * Account identifiers * Username or profile data * Support communications * Contact details (if provided) #### B. Technical Data May include: * IP address * Device type * Browser type * Operating system * Log files * Session metadata * Access timestamps #### C. Usage Data May include: * Feature interactions * Navigation paths * Governance interactions * Community participation * Platform engagement metrics #### D. Blockchain Data May include: * Wallet addresses * Transaction hashes * On-chain activity * Public ledger data Note: On-chain data is public, permanent, and not controlled by us. *** ### 4. Lawful Basis for Processing (GDPR-Lite) We process data based on: * **Consent** — when you provide data voluntarily * **Contractual necessity** — to deliver platform services * **Legitimate interest** — platform security, improvement, analytics * **Legal obligation** — compliance with applicable laws *** ### 5. How We Use Data We use data to: * Operate the Platform * Provide services * Manage accounts * Enable governance systems * Support DAO coordination * Improve performance * Monitor security * Prevent fraud * Analyze usage * Maintain infrastructure * Communicate with users * Provide support * Develop new features *** ### 6. Data Sharing We may share data with: * Infrastructure providers * Hosting services * Analytics services * Security providers * Compliance partners * Legal authorities (if required by law) We do **not** sell personal data. *** ### 7. International Data Transfers Data may be processed in multiple jurisdictions depending on infrastructure providers and decentralized services. We apply reasonable safeguards to protect user data across borders. *** ### 8. Data Retention We retain personal data only as long as necessary to: * Provide services * Meet legal obligations * Resolve disputes * Enforce agreements * Maintain platform integrity On-chain data is permanent by design and cannot be deleted. *** ### 9. User Rights (GDPR-Lite) You have the right to: * Access your data * Correct inaccurate data * Request deletion (where legally and technically possible) * Restrict processing * Object to processing * Request data portability * Withdraw consent Some rights may be limited due to: * Legal obligations * Security requirements * Blockchain immutability * Platform integrity needs *** ### 10. Cookies and Analytics We may use cookies and similar technologies to: * Improve functionality * Analyze traffic * Enhance user experience * Monitor performance * Secure sessions You may control cookies through your browser settings. *** ### 11. Security We implement reasonable technical and organizational measures to protect data, including: * Access controls * Encryption where appropriate * Secure infrastructure * Monitoring systems * Internal data governance controls No system is perfectly secure. Use of the Platform is at your own risk. *** ### 12. Children’s Data The Platform is not intended for individuals under 18. We do not knowingly collect data from minors. *** ### 13. Decentralized Systems Disclaimer Some platform components use decentralized technologies. This means: * Data may be distributed * Data may be immutable * Data may be publicly accessible * Data may not be fully erasable * Data may be processed by third-party networks Users are responsible for what they publish on-chain. *** ### 14. Changes to This Policy We may update this Policy periodically. Changes will be reflected by updating the “Effective Date.” Continued use of the Platform means acceptance of the updated Policy. *** ### 15. Contact **Zero Authority D/B/A Trajan**\ Website: [https://www.zeroauthoritydao.com](https://www.zeroauthoritydao.com/)\ Email: \ Support: \ Business Address: 611 South DuPont Highway Suite 102, City of Dover, DE 19901 *** --- id: govern/sips title: "SIP Tracker" description: "Last update May 1, 2026" product: zadao canonical: https://zeroauthoritydao.ai/docs/govern/sips related: [govern, govern/sips/bot, govern/sips/guide, govern/sips/cab-admin, govern/sips/notifications, govern/sips/cab-voting] tokens: 282 --- # SIP Tracker The SIP Tracker, a Stacks and Zero Authority partnership, lets the community follow SIPs and protocol changes as they happen and give feedback at every stage. **Stacks and Zero Authority are joining forces to advance how decentralized networks evolve.**\ Together, they connect the structured governance of Stacks Improvement Proposals (SIPs) with a real-time coordination layer—turning ideas into shipped upgrades faster, without sacrificing transparency or decentralization. Through this partnership, the community can: * Track SIPs and protocol changes as they happen * Contribute feedback during every stage of a proposal * Coordinate contributors, builders, and stakeholders in one place * Surface key signals—activity, sentiment, and progress—in real time * Accelerate the path from discussion → alignment → implementation ![](https://zeroauthoritydao.ai/docs/img/61c2f063dca1.webp) [New Stacks governance tool: SIP Tracker (Stacks forum)](https://forum.stacks.org/t/new-stacks-governance-tool-sip-tracker/18645) [Announcement on X](https://x.com/clairemgadd/status/2016954790916636751) By aligning governance with execution, Stacks and Zero Authority enable a more responsive, community-led development cycle—where participation is open, coordination is seamless, and innovation compounds onchain. --- id: govern/sips/guide title: "SIP Tracker Guide" description: "Last update May 1, 2026" product: zadao canonical: https://zeroauthoritydao.ai/docs/govern/sips/guide related: [govern/sips] tokens: 872 --- # SIP Tracker Guide How to use the SIP Tracker by role: learn about SIPs, build with ratified SIPs, vote as a CAB member, or run votes as a CAB admin. Welcome to the SIP (Stacks Improvement Proposal) Tracker. This guide helps you understand, use, and participate in governance based on your role. *** ### 🔍 What is a SIP? A **SIP (Stacks Improvement Proposal)** is a formal proposal that defines changes, upgrades, or new features for the ecosystem. SIPs move through a lifecycle: * Draft → Review → Voting → Ratified → Implemented Start exploring here:\ 👉 *** ## 👤 User Guides by Role *** ### 👤 Person A — Learn About SIPs **Goal:** Understand how governance works #### Steps: 1. Visit the SIP dashboard\ 👉 2. Review the introduction section\ 👉 3. Browse available SIPs\ 👉 4. Open an example SIP\ 👉 5. Learn the lifecycle stages: * Draft * Voting * Ratified **Outcome:** You understand how ideas become protocol decisions. *** ### ⚙️ Person B — Use or Build with a SIP **Goal:** Integrate or contribute to SIPs #### Steps: 1. Browse or search SIPs\ 👉 2. Filter for approved SIPs\ 👉 3. Open a SIP\ 👉 4. Review: * Technical specifications * Implementation details * Linked resources 5. Take action: * Build using approved SIPs * Provide feedback on drafts **Outcome:** You can build on top of SIPs or contribute improvements. *** ### 🗳️ Person C — CAB Member (Voting) **Goal:** Review and vote on proposals #### Steps: 1. Access SIP Tracker\ 👉 2. Connect your wallet 3. View active voting SIPs\ 👉 4. Open a SIP\ 👉 5. Review proposal details: * Summary * Risks * Community discussion 6. Cast your vote: * Approve * Reject * Abstain 7. Confirm your vote 8. Track results\ 👉 **Outcome:** You participate directly in governance decisions. *** ### 🏛️ Person D — CAB Admin **Goal:** Manage and facilitate voting #### Steps: 1. Access CAB Admin dashboard\ 👉 2. Prepare SIP for voting: * Finalize proposal * Set voting window * Confirm eligible voters 3. Activate voting 4. Notify CAB members 5. Share SIP voting link\ 👉 6. Monitor participation\ 👉 7. Support voters: * Wallet connection * Proposal clarification 8. Close voting and finalize results 9. Update SIP status: * Ratified * Rejected **Outcome:** Governance is executed transparently and efficiently. *** ## 🔗 Quick Links * SIP Dashboard\ 👉 * Voting SIPs\ 👉 * Ratified SIPs\ 👉 * Example SIP\ 👉 * CAB Admin\ 👉 *** ## 💡 Tips * Use filters to quickly find relevant SIPs * Always review full proposal details before voting * Follow discussions for deeper context * Check SIP status before building or integrating --- id: govern/sips/cab-admin title: "CAB Administration Guide" description: "Last update May 1, 2026" product: zadao canonical: https://zeroauthoritydao.ai/docs/govern/sips/cab-admin related: [govern/sips] tokens: 370 --- # CAB Administration Guide CAB admins create groups and manage members. Super Admins open and close voting on a SIP, and results are tallied into CSV and Markdown files. ![](https://zeroauthoritydao.ai/docs/img/29cec47c2027.webp) *** ### CAB Administration Guide #### Creating a Group If you are a **CAB Admin**, you have permission to create a new group. * Click **“+ New Group”** * Define the group’s purpose (e.g., Technical, Ethics, Economics) * Add initial members and assign roles *** ### Roles within the CAB Structure #### 1. CAB Super Admin * Oversees the entire CAB system * Can initiate voting on any SIP * Can close voting once complete * Responsible for final output (CSV + Markdown) #### 2. CAB Group Admin * Manages a specific CAB group * Adds/removes members * Organizes group participation * Ensures members are ready for voting #### 3. CAB Group Member * Participates in SIP review * Casts votes when voting is active * Receives notifications and updates *** ### SIP Voting Process 1. **SIP Ready for Review** * A SIP reaches the CAB voting stage 2. **Vote Initiated** * A **Super Admin** initiates voting from the SIP ID page 3. **Notifications Sent** * Members are notified via **NOVA AI** (if configured) * Includes direct link to the SIP ID page 4. **Voting** * Members cast votes directly on the SIP page 5. **Vote Completion** * Once all members have voted, a **Super Admin** closes voting 6. **Results Generated** * Votes are automatically tallied * Two files are created: * CSV (raw data) * Markdown (formatted summary) 7. **Publishing** * Files can be uploaded to GitHub or attached to the SIP --- id: govern/sips/notifications title: "SIP Tracker Notifications" description: "Last update May 1, 2026" product: zadao canonical: https://zeroauthoritydao.ai/docs/govern/sips/notifications related: [govern/sips] tokens: 220 --- # SIP Tracker Notifications Get SIP Tracker alerts in Telegram or Discord for new SIPs, status changes, voting windows and outcomes by connecting the Zero Authority AI bot. Zero Authority AI notifications extend the SIP Tracker experience by delivering real-time, AI-powered updates directly into Telegram or Discord. By connecting the bot and selecting governance-specific triggers—such as new SIPs, status changes (Draft → Voting → Ratified), voting windows opening, or final outcomes—you can stay continuously informed without needing to monitor the dashboard. Once configured, the system tracks SIP activity in real time and sends tailored alerts based on your preferences, enabling contributors, builders, CAB members, and admins to act quickly and stay aligned with governance as it evolves. Turn on notifications here: - [Nova for CAB Groups & Governance Participants](https://zeroauthoritydao.ai/docs/nova/cab-groups.md) Zero Authority AI notifications () Monitor the dashboard at --- id: nova/community/flares title: "Nova Quasar: Flares" product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/flares related: [nova/community] tokens: 1144 --- # Nova Quasar: Flares Flares post automatically in your channel when something real happens: a member or XP milestone, a new leaderboard leader, an anniversary, or on PRO a holder milestone or SIP result. Never about price. **Flares** are posts that fire on their own when something real happens in your community: you turn a rule on once ("post when we pass each 500 members") and from then on Nova writes the post and publishes it in your own Discord channel or Telegram group. Flares are the first feature of **Nova Quasar**, Nova's community marketing and reach features. *** ## What a flare looks like > **2,000 members** > > 🎉 ZADAO just passed 2,000 members. Thank you to everyone who showed up and stuck around. > > _That is two thousand people who decided this was worth their time._ The title and first paragraph come from a template, so a flare never needs AI to post. The last line is the optional **AI-written line**: one short sentence about the event, added while your weekly allowance lasts. On Discord a flare is a card in your accent color; on Telegram it is a formatted message. If your community runs its own bot ([Nova Soul](https://zeroauthoritydao.ai/docs/nova/community/soul.md)), flares post as that bot. A flare has no calendar and no per-post approval. Every one is tied to an event, and each event posts once. *** ## What you can announce | Trigger | Fires when | You set | | --- | --- | --- | | **Member milestone** | The server or group passes every N members | N (for example 500) | | **Community XP milestone** | The XP earned by the whole community passes every N | N | | **Member level milestone** | A member reaches level 10, 20, 30... | Every how many levels | | **New leaderboard leader** | Someone new takes first place on the all-time XP leaderboard | Nothing | | **Community anniversary** | Once a year on the community's birthday | The date (optional on Discord, where the server's creation date is used) | | **Token holder milestone** *(PRO)* | Your token passes every N holders (Stacks, Solana, EVM) | Chain, token address, N | | **Stacks governance result** *(PRO)* | A SIP changes status, or an advisory-board vote on one closes | Optionally one SIP | The XP, level and leaderboard triggers need [Ascend](https://zeroauthoritydao.ai/docs/nova/community/community-games.md) turned on. A new rule starts from the current numbers: one created at 1,530 members with "every 500" first posts at 2,000, not for the 1,500 it missed. > [!WARNING] > **No price posts.** There is no price trigger, and a flare never states or implies token price movement, returns or urgency to buy. Nova checks every post, including your own templates and the AI line, and blocks text that does. A holder milestone talks about people, not value. *** ## Free vs Community PRO | | Free | Community PRO | | --- | --- | --- | | Active rules | 3 | 20 | | Template flares | Unlimited | Unlimited | | AI-written lines | 10 / week | 150 / week | | Voice of the AI line | Nova's | Your [Nova Soul](https://zeroauthoritydao.ai/docs/nova/community/soul.md) persona | | Community triggers (members, XP, levels, leaderboard, anniversary) | ✓ | ✓ | | Token holder and governance triggers | — | ✓ | | Your own template per rule | ✓ | ✓ | When the weekly AI allowance or your plan's AI budget is spent, flares keep posting with the template alone. **Keeping it quiet.** A community posts at most **4 flares a day** by default (you can set 1 to 12), on both tiers. A flare over the limit is skipped, not queued, so yesterday's news never shows up late. Each rule can also have a cooldown between two posts. *** ## Set it up 1. As an admin, in the channel (Discord) or topic (Telegram forum) where flares should appear, tell Nova what to announce: > _"@Nova post here when we pass each 500 members"_ 2. Add more rules the same way, or point one at another channel (Discord only): > _"@Nova announce in #wins when someone reaches level 20"_ 3. Check it: _"@Nova test the flare"_ posts a labelled sample with example numbers. 4. See what you have with `/flares`, or ask _"@Nova what flares do we have?"_ To change one: _"@Nova pause flare #3"_, _"@Nova make the member flare every 1,000"_. 5. Optional: write your own text for a rule (_"@Nova use this text for the member flare: We are {milestone} strong, {community}!"_), turn the AI line off, set a card color, or add a footer note such as a risk warning. The same settings are on the **Nova Quasar** card of the [Community Settings dashboard](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md). > [!NOTE] > **Permissions.** Discord: Nova needs *View Channel*, *Send Messages* and *Embed Links* in the flares channel. Telegram: Nova needs to be able to post in the group (and in the topic, for forum groups). If a rule cannot post, `/flares` shows the problem next to it, and the flare goes out once the channel is fixed. --- id: nova/community/harbor title: "Nova Harbor" product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/harbor related: [nova/community] tokens: 1248 --- # Nova Harbor Harbor welcomes every new member with your template or an AI-personal message, link buttons and raid protection. Community PRO adds first-message welcomes, DM follow-ups, auto-roles, goodbyes and milestones. **Nova Harbor** welcomes every new member of your Discord server or Telegram group automatically — with your own message or an AI-personal one, link buttons, and (on Community PRO) a full onboarding flow: first-message welcomes, DM series, auto-roles, role buttons, goodbyes, optional ban-hammer messages and milestone celebrations. *** ## What a welcome looks like You write the template; Nova fills it in for each newcomer: > 👋 Welcome to **{community}**, {user}! Start in #introductions and grab your roles below — you're member #{member_count}. | Placeholder | Becomes | | --- | --- | | `{user}` | A mention of the new member (a ping on Discord, a tappable name on Telegram) | | `{name}` | Their name, without a ping | | `{community}` | Your server / group name | | `{member_count}` | Current member count | | `{date}` | Today's date | If your template never names the member, Nova adds the mention in front. On Discord the welcome can be a **rich card** (their avatar, your accent color, "Member #1,234"); on Telegram it's a formatted message (`**bold**`, `__italic__`, `[links](https://…)`). Link buttons (rules, website, start-here) sit underneath. **Opportunities button.** Turn on "Find opportunities for me" and the welcome gets a button that opens the member's own [Nova Scout](https://zeroauthoritydao.ai/docs/nova/scout.md) setup: bounties, grants and hackathons matching their skills, sent to their DMs. If your community runs its own bot, the button sends them to the main Nova bot. **AI-personal welcomes.** Turn them on and Nova rewrites your template into a fresh, warm welcome for each newcomer while keeping its key info. When the daily AI allowance or your plan's AI budget runs out, Nova simply posts your template — nobody is ever left un-welcomed. *** ## Built for busy rooms | Situation | What Harbor does | | --- | --- | | Several people join within a few seconds | **One** combined welcome ("Welcome Ann, Bo and Cy!") — the window is adjustable | | A join raid (dozens of accounts per minute) | Welcomes **pause for 10 minutes**; no roles or DMs go to raid accounts | | Someone leaves and rejoins | Not re-welcomed within the cooldown you pick (default 30 days) | | A channel full of old welcomes | **Auto-delete** after N minutes, or **keep only the latest** | | Telegram "X joined / X left" clutter | Optionally deleted automatically | | Discord Rules Screening | The welcome waits until the member accepts your rules | *** ## Free vs Community PRO | | Free | Community PRO | | --- | --- | --- | | Welcome templates | 1 | Up to 10, rotated, with per-template stats | | Link buttons | 2 | 6 | | "Find opportunities for me" button | ✓ | ✓ | | AI-personal welcomes | 10 / day | 300 / day + your style instructions | | Welcome language | Same as your template | The member's own language (auto) or a fixed one | | When to welcome | On join | On join **or** at their first message | | DM welcome + up to 3 follow-up DMs | — | ✓ | | Auto-roles + self-assign role buttons (Discord) | — | ✓ (up to 5 each) | | Goodbye messages | — | ✓ up to 10 rotating lines, for members who leave on their own | | Ban messages ("the ban hammer has spoken") | — | ✓ optional, up to 10 rotating lines or Nova's built-in jokes | | Member milestones ("we just hit 1,000!") | — | ✓ (when a [Flares](https://zeroauthoritydao.ai/docs/nova/community/flares.md) member rule is on, Flares posts the milestone instead, once) | | Stats | Joins, welcomed | + activation rate (members who post within 7 days), A/B per template, DM delivery | **First-message mode** (PRO) waits until a newcomer first speaks and replies to that message — ideal for large groups where most joiners never talk. *** ## Set it up 1. As an admin, in the channel (Discord) or topic (Telegram forum) where welcomes should appear, say: > _"@Nova turn on welcomes"_ 2. Customize by talking to Nova — e.g. _"@Nova set the welcome message to: Welcome {user}! Read #rules first 🚀"_ — or from the **Nova Harbor** card in the [Community Settings dashboard](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md), which shows a **live preview** as you type. 3. Check it: _"@Nova test the welcome"_ posts a labelled test that deletes itself after ~2 minutes and lists anything that's misconfigured (missing permissions, a role above Nova's, etc.). 4. See how it's going: _"@Nova how many people joined this month?"_ > [!WARNING] > **Permissions.** Discord: Nova needs *Send Messages* + *Embed Links* in the welcome channel, and *Manage Roles* (with its role **above** the ones it assigns) for auto-roles and role buttons. Telegram: make Nova an **admin** — large groups hide "joined" messages from bots, so admin rights are what make join detection reliable (add *Delete messages* if you want notices cleaned up). > [!NOTE] > **Telegram DMs.** Telegram only lets a bot message people who have started it, or who asked to join through a **join-request** invite link — those requesters get your DM welcome before they're even approved. On Discord, members with closed DMs are skipped. --- id: nova/community/relay title: "Nova Relay" description: "Relay keeps your members up to date on what happened while they were away." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/relay related: [nova/community] tokens: 1575 --- # Nova Relay Relay keeps one pinned live message, or a daily post, summing up what the team announced and what people discussed across your Discord and Telegram public channels. Community PRO. **Relay** keeps your members up to date on what happened while they were away. Nova reads your community's public channels, on Discord and Telegram together, and writes a few short lines: what the team announced and what people talked about. Relay is a **Community PRO** feature. You choose how it shows up: | Mode | What members see | | --- | --- | | **Live message** *(default)* | **One** pinned message that Nova edits in place every few hours, like a small dashboard of what's happening. Nothing new is posted, so nobody gets pinged by it. | | **Daily post** | A new recap once a day, pinned in place of yesterday's. | *** ## What it looks like > **While you were away** > > **📣 From the team**\ > • Season 2 starts Monday, and your Season 1 points carry over. `#announcements` > > **💬 What people talked about**\ > • The new leaderboard was the talk of the day; a few people want a weekly view too. `#general`\ > • Wallet sign-in on mobile tripped a few people up; opening the page in the wallet's own browser fixed it. _on Telegram_ > > _Last 24h: 48 people · 312 messages · busiest in #general · Updated 2 hours ago · next in 4 hours_ Each line says what happened, not just that something did, and points to the channel or topic where it happened, so members can tap through. The same topic discussed in several channels, or on both platforms, is one line. If your community runs its own bot ([Nova Soul](https://zeroauthoritydao.ai/docs/nova/community/soul.md)), Relay posts as that bot. **Live message.** Nova rewrites the lines only when enough new was said since the last update. Otherwise it keeps them and refreshes the counts and the "updated" time. A quiet stretch costs nothing. Lines older than the period the message covers are taken off. If someone deletes the message, Nova posts a new one at the next update. **Daily post.** On a quiet day nothing is posted and the last recap stays pinned. *** ## Make it yours Every setting can be changed by asking Nova or on the **Relay** card in the [Community Settings dashboard](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md). In live mode, a change shows on the message right away. | Setting | Choices | | --- | --- | | **Updates every** *(live)* | 1, 2, 3, 4, 6 *(default)*, 12 or 24 hours, starting from the time you pick | | **Covers the last** *(live)* | 12 hours, 24 hours *(default)*, 48 hours or 7 days | | **Where** | Up to 3 places. Discord: text or announcement channels, threads, or a forum (live only: Nova opens one post there and keeps it updated). Telegram: the group or forum topics | | **Voice** | Friendly *(default)*, short and plain, or neutral reporter | | **Lines** | 3 to 8 *(default 5)* | | **Unanswered questions** | Left out *(default)*, in their own "Can you help?" section, or mixed in | | **Layout** | Sections *(default)*, one list, or headlines (a short bold topic before each line) | | **Title** | "While you were away" *(default)*, "What's new in *your community*", "📡 Relay", or your own | | **Emoji** | One per section *(default)*, one per line, or none | | **Where it happened** | A tappable channel or topic next to each line *(default)*, or hidden | | **Footer** | People first *(default)*, the classic stats line, or none | | **Discord format** | Card *(default)*, embed, or plain message | | **Telegram** | Lines shown *(default)*, or collapsed behind a tap to keep the pinned message short | | **Accent stripe** *(Discord)* | Any color, or none | | **Language** | The language most messages use *(default)*, or one you pick | _"@Nova make the recap update every 3 hours and cover the last 48h"_ · _"@Nova make the recap shorter and write it in Italian"_ · _"@Nova put the live recap in the #news forum"_ · _"@Nova switch Relay to a daily post at 18:00 Rome time"_ *** ## What Relay reads, and what it never does | | | | --- | --- | | **Reads** | Every channel, thread and forum topic that **all members can already see** | | **Never reads** | Private and staff channels, private threads, age-restricted channels, DMs, other communities | | **Never writes** | Member names, mentions, links, price predictions or calls to buy | | **Leaves out** | Messages deleted by a moderator, by [Guardian](https://zeroauthoritydao.ai/docs/nova/community/guardian.md) or by their author, and any channel you exclude | Only a message from an admin or moderator can become team news, so a member posting a fake giveaway does not end up pinned as an announcement. > [!NOTE] > **Servers where members need a role to see channels.** If `@everyone` sees nothing in your Discord server, tell Nova which role every member has: _"@Nova the member role for the recap is @Verified"_. Relay then reads the channels that role can see. A role with moderation or admin permissions is refused, so staff channels stay out. *** ## Set it up 1. As an admin, in the channel (Discord) or topic (Telegram forum) where the message should live: > _"@Nova keep a live recap of the community pinned here"_ The live message goes up right away with a short "nothing yet" note, and fills in at the first update with enough to say. Relay starts reading when you turn it on. 2. Post it in more places, or leave a channel out: > _"@Nova also keep the recap in #general"_ · _"@Nova don't read #off-topic for the recap"_ 3. Have both platforms? Turn Relay on in your Discord server **and** your Telegram group. Both show the same recap, covering both. To keep one platform to itself: _"@Nova don't merge the recap with Telegram"_. 4. Need it now: _"@Nova update the recap now"_ (2 a day). In live mode, an update that finds nothing new enough to rewrite does not use one. 5. Check on it any time with _"@Nova is Relay on?"_: it lists the mode, what is read, where it posts, a link to the live message, and anything to fix. Turning Relay off deletes what it was holding and takes the live message down. > [!NOTE] > **Permissions.** Discord: Nova needs *View Channel*, *Send Messages* (*Send Messages in Threads* for a thread, *Create Posts* for a forum) and *Pin Messages* (*Manage Messages* on older servers); *Embed Links* for the embed format. Telegram: make Nova an admin with the *Pin messages* right. Without the pin permission the message still posts, and Nova tells you it could not pin it. Nova never pins a forum post: a forum has one pinned post, and it is yours. --- id: nova/community/warp title: "Nova Warp" description: "Warp turns your Discord channel and your Telegram group into one chat: what a member posts on one side appears on the other within seconds, under their name. Warp is a Community PRO feature." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/community/warp related: [nova/community] tokens: 1464 --- # Nova Warp Warp links one Discord channel and one Telegram group or topic into a single live chat: messages, replies, edits and deletions cross within seconds under the member's name, with no cross-pinging. Community PRO. ## What members see > 🦊 **Alice** · Discord\ > gm everyone, the AMA starts in 10 minutes\ > _🌀 Warped from Discord_ On Telegram, a message from Discord shows the author's emoji, their name and where it came from. Each Discord member gets their own emoji in your server and keeps it, so regulars are easy to spot. On Discord, a message from Telegram shows the member's name and Telegram profile photo. A member without a visible photo gets a plain avatar in one of Telegram's colors. Every copied message ends with a small _🌀 Warped from Telegram_ line (or _from Discord_ on Telegram), so nobody mistakes a copy for the member's own account. Replies show who they answer and the start of that message, an edited message is edited on the other side, and a deleted one is deleted there too. **Talking to Nova works on both sides.** A message to Nova crosses like any other (the @mention just doesn't work on the other side), and Nova's answer appears in both chats, as a reply to the question. Members on either side can reply to Nova's answer to keep the conversation going. A reply to one of Nova's alerts crosses too, with a short quote of the alert. When a chat moves faster than the platforms allow a bot to post, the waiting messages arrive together as one message instead of being lost. Italic, underline, strikethrough, code and spoilers cross both ways, and a spoiler stays hidden. Bold text crosses as plain text, so nobody can make their message look like another member's name line. A reply to an older message carries a short quote of it, a Telegram album arrives as one message, a forwarded message is marked as forwarded (never with who it came from), and a very long message is cut with a link to the original. | | | | --- | --- | | **Crosses** | Members' messages in the linked channel (Discord) and the linked chat or topic (Telegram), messages to Nova and Nova's answers to them, replies, edits and deletions | | **Crosses as a file** | One image, GIF or video per message, up to 8 MB | | **Crosses as a note** | Bigger files, albums, media under a spoiler and other files show as a short note such as _[🖼️ image]_; a poll shows its question and options, a sticker its emoji | | **Never crosses** | Nova's alerts and other posts (each side has its own), other bots' messages, commands, other channels and topics, threads inside the linked Discord channel, messages of members who opted out (and Nova's answers to them), and staff messages when **Keep staff messages on this side** is on | | **Never happens** | Nobody is pinged across, links never open a preview, and a link cannot hide behind other text | A message deleted by a moderator or by [Guardian](https://zeroauthoritydao.ai/docs/nova/community/guardian.md) is removed on the other side too, and one removed within a second or two never crosses. A purge or a raid cleanup is removed in one go. Deleting a copy only removes the copy: each side's moderators moderate their own side. A mention of a channel most members cannot see shows as _#private-channel_ on Telegram. If the link stops on its own (Community PRO ended, the linked Discord channel was deleted or made private), both chats are told Warp is paused, and told again when it is back. > [!NOTE] > **Members choose.** When the link opens, both chats get a notice saying they are linked. A member who doesn't want their messages copied tells Nova _"don't warp my messages"_ (in the chat or in a DM), and _"warp my messages again"_ to undo it. *** ## Set it up 1. In your Discord server, as an admin, in the channel to link (one every member can read): > _"@Nova link this channel with our Telegram group"_ 2. In your Telegram group, as an admin, in the main chat or in the forum topic to link: > _"@Nova link this chat with our Discord"_ 3. The link opens as soon as both sides are on, and Nova posts the notice in both chats. 4. Check on it any time with _"@Nova is Warp on?"_: it says what is linked and anything to fix. To move it: _"@Nova warp #general instead"_. To stop: _"@Nova stop the bridge"_ (both chats are told). The Discord server and the Telegram group must belong to the same community on Nova (link the second one with an activation code from the [Community Settings dashboard](https://zeroauthoritydao.ai/docs/nova/community/settings-dashboard.md)). The **Warp** card under Nova Orbit there shows whether the two chats are linked, lets you pick the channel (only channels every member can read are offered) and lists anything to fix. Moving the link to another channel or topic tells the old one it was unlinked. > [!NOTE] > **Permissions.** Discord: Nova needs *View Channel*, *Send Messages* and *Manage Webhooks* in the linked channel, and *Manage Messages* is recommended (it removes many copies at once and copies whose webhook a moderator deleted). Without *Manage Webhooks* Telegram messages still arrive, posted by Nova with the member's name on top. Telegram: make Nova an admin so it sees every message. **A general chat behind a member role.** If @everyone sees nothing until members get a role (like @Member or @Verified), name that role when you turn Warp on: _"@Nova link this channel with our Telegram group, the member role is @Member"_. Nova accepts a role only when most of the server has it, and never a role with moderation or admin permissions, so a staff channel can never be linked. **Options** (per side, in chat or on the Warp card): * **Who can manage Warp in chat** (Discord): server admins only (default), or admins and moderators (members who can manage messages, time out, kick or ban). Only an admin can change it. On Telegram every group admin can already manage Warp. Your dashboard team manages it from the Warp card either way. * **Keep staff messages on this side**: messages from moderators and admins (Telegram: group admins) are not copied to the other platform. Members' messages still cross. --- id: nova/scout title: "Nova Scout" description: "Nova Scout goes through open bounties, grants and hackathons across several platforms and sends you the few that fit your skills, by direct message." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/scout related: [nova] tokens: 795 --- # Nova Scout Nova Scout sends you, by direct message, the few open bounties, grants and hackathons that match your skills, from Superteam Earn, Zero Authority DAO, Karma and Cantina. Set it up with /scout; free for everyone. It covers Superteam Earn (Solana), Zero Authority DAO (Stacks), the Karma grants registry (many ecosystems) and Cantina bug bounties. Jobs and ambassador programs are not covered yet. *** ## Set it up 1. Run `/scout` (on Telegram, in your private chat with Nova; on Discord, anywhere). 2. Pick what you are looking for, your skills and your ecosystems. Leaving a list empty means "any". 3. Optionally set a minimum reward, your timezone, send time and country. 4. Press **Start**. Your first picks arrive right away. You can also just tell Nova: > _"I'm a designer into Solana and Stacks. Send me bounties over $200 every Monday at 9am Rome time."_ > [!NOTE] > Picks arrive as a direct message. On Discord, allow direct messages from the server you share with Nova. On Telegram, start a private chat with Nova first. *** ## What you receive | Message | When | | ------- | ---- | | **Digest** | Weekly or daily at your local time. At most 5 listings, never one you have already seen. A period with no match sends nothing. | | **Instant alert** | A strong new match, as soon as it is listed. At most 2 a day, daytime only. On by default; turn it off in `/scout`. | | **Reminder** | 24 hours before a listing you saved closes, after Nova checks it is still open. | Every listing shows the same things in the same order: the reward (with a dollar value when the token is not a stablecoin), the deadline in your own timezone, one line on what the work is, who is offering it and who can enter, and why it matched you. *** ## Buttons on a listing | Button | What it does | | ------ | ------------ | | **Open listing** | Opens the original listing on its own platform. You always apply there. | | **Save** | Keeps it in your saved list and reminds you 24 hours before it closes. | | **Remind me** | Saves it and adds an earlier reminder, 3 days before. | | **Not for me** | Hides it. Nova shows you fewer listings from that sponsor and of that kind. | *** ## Search without subscribing Anyone can ask, with no setup: > _"Any design bounties over $500 on Solana closing this week?"_ Nova answers from the same open listings and links each one. *** ## Good to know * **Region-locked listings.** Many listings are open to one country only. Set your country and Nova hides the ones you cannot enter. Without it, they are shown with an "only" label. * **Rolling and missing values.** A grant with no deadline says "rolling". A listing with no stated reward says so. Nova does not fill gaps. * **Bug bounties** appear only if security is one of your skills. The figure is the program's maximum payout; most need identity verification and some charge a submission fee, both shown on the listing. * **One profile per person.** Link your Discord and Telegram on the [dashboard](https://zeroauthoritydao.ai/docs/nova/alerts/manage.md) and both share one profile. You can also pause or delete it there. > [!WARNING] > Nova links listings; it does not vouch for sponsors. A listing marked "sponsor not verified" has not been checked by its platform. Never run code sent to you as a "test task" on a computer that holds a wallet. *** ## Limits Nova Scout is included for everyone, Free and Premium alike. --- id: nova/spaghettipunk-club title: "SpaghettiPunk Club" description: "Nova reads the SpaghettiPunk Club straight from its contracts on Stacks: your Membership Cards, your SPoint, the SPoint market, and alerts for all of it." product: nova canonical: https://zeroauthoritydao.ai/docs/nova/spaghettipunk-club related: [nova] tokens: 572 --- # SpaghettiPunk Club Nova reads the SpaghettiPunk Club contracts on Stacks: SPoint on your Membership Cards, the SPoint market and Club stats, with alerts for fills, collectable SPoint and unsubscribed NFTs. It only reads; trading happens in the Club dapp. > [!NOTE] > SPoint are the Club's loyalty points. They are held by a Membership Card (a SpaghettiPunk Club NFT), not by your wallet, so they do not appear in a normal wallet lookup. Nova only reads: collecting, subscribing, buying and selling happen in the [Club's dapp](https://spaghettipunk-dapp.vercel.app). *** ## Ask about the Club | You want | Example prompt | | --- | --- | | SPoint on a card, and the room left on it | _"How many SPoint are on card 333?"_ | | Your cards, SPoint ready to collect, and NFTs you hold that are not subscribed | _"Show my SpaghettiPunk wallet SP..."_ | | The open sell orders on the SPoint market | _"Show the SPoint market"_ | | Club totals: SPoint collected and spent, cards minted, NFTs subscribed | _"SpaghettiPunk Club stats"_ | If your Stacks wallet is linked to Nova, you can leave the address out. *** ## Get alerts Tell Nova what to watch. In a DM the alerts are yours; in a server or group, an admin sets them up and they post in that channel. > _"Alert me when my SPoint order sells and when I have SPoint to collect, wallet SP..."_ | Alert | When it arrives | | --- | --- | | Your SPoint sell order was filled | Within about 15 minutes | | SPoint were sent to one of your cards | Within about 15 minutes | | Someone minted with your referral code | Within about 15 minutes | | A new SPoint sell order, optionally at or below a price you pick | Within about 15 minutes | | You have SPoint ready to collect (you pick how many) | Checked a few times a day | | An eligible NFT you hold is not subscribed under your wallet | Checked once a day | | Club feed: market fills, mints paid in SPoint, referral mints | Within about 15 minutes | | Club milestones: cards minted, NFTs subscribed, SPoint collected | Checked a few times a day | The feed and the milestones are made for a community channel (Discord or Telegram): > _"Post SpaghettiPunk Club activity and milestones in this channel"_ > [!WARNING] > An NFT you bought keeps earning SPoint for its previous owner until you subscribe it from your own wallet. The "not subscribed" alert tells you which ones. These are regular [Smart Alerts](https://zeroauthoritydao.ai/docs/nova/smart-alerts.md): snooze, do-not-disturb, history and the dashboard work the same way, and each subscription counts as one alert.