> For the complete documentation index, see [llms.txt](https://docs.nectarliquid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nectarliquid.com/community.md). # Community Stay up to date with Nectar Liquid news and connect with the community across the channels listed below. #### Official Channels The following channels carry verified announcements and updates directly from the Nectar Liquid team. * Telegram Announcements for general updates and platform news * Telegram Technical Announcements for real time core network alerts and smart contract updates * Discord for community discussions and governance updates * X (formerly Twitter) for public updates and ecosystem highlights * Substack for deep dive monthly reviews and governance proposals * Telegram (English) for open global discussion * GitHub for open source smart contract repositories and official documentation files #### Community Groups The following spaces are dedicated to active discussions and peer to peer support. * Telegram (Regional and Localized Markets) for discussions surrounding regional fiat tokens like the CNGN pair * Telegram (Developer Support) for engineers integrating platform APIs * Telegram Trading Chat for market analysis and leaderboard performance reviews #### Environment Specific Technical Support To support developers and traders across both operational networks, our community channels provide dedicated triage sections depending on your active deployment. * Mainnet Support Channels * Core Focus: Monitoring production trading activity, real asset API integrations, and live network performance on Asset Chain Mainnet. * Target Audience: Production traders, institutional liquidity providers, and live integration partners. * Beta Testnet Support Channels * Core Focus: Simulating arbitrage strategies, troubleshooting testnet faucet distributions, and validating REST API performance on Asset Chain Testnet. * Target Audience: Smart contract developers, alpha testers, and AI agent engineers configuring autonomous trading plugins. #### Media Kit The Nectar Liquid assets repository contains official brand materials. This includes high resolution logos for the Nectar Liquid exchange, the NECTAR token, and Nectarliquid pools in SVG and PNG formats for press and community use. Media kits include independent assets matching the visual design themes of both the Mainnet and Beta Testnet applications. #### Courses and Education The Nectar Liquid developer portal and ecosystem guides cover protocol mechanics, token pricing, fees, and advanced trading features. These educational resources are designed for both traders and developers building on the network, and they are sponsored by the Nectar Liquid DAO and Asset Chain. The educational documentation is divided into two distinct configurations: * Mainnet Integration Guides: Structured instructions for executing live programmatic trades, tracking real time protocol yield, and interacting with production contracts. * Testnet Sandbox Tutorials: Step by step documentation for building autonomous AI agent trading skills, interacting with testnet endpoints, and deploying strategy bots without risking real capital. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nectarliquid.com/community.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.