> 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/tokenomics/nectar-token.md). # NECTAR Token NECTAR is the platform utility and governance token. Staking NECTAR earns you a share of protocol fees. 27 percent of fees from leverage trading, liquidations, borrowing fees, and swaps are used to buyback NECTAR. Distribution of bought back NECTAR is determined by the protocol. See Staking for details. For more on fee distribution, see Fees. NECTAR also grants voting power in protocol governance. Escrowed NECTAR or esNECTAR has historically been distributed as a staking and referral incentive. Learn more about esNECTAR on the Rewards page. #### Token addresses * Asset Chain Mainnet: *To be announced prior to the official DAO Token Generation Event (TGE).* * Asset Chain Testnet: Distributed through community testnet incentive distributions and reward epochs. NECTAR can be bridged between supported networks using authorized bridge protocols. #### Buying NECTAR You can buy NECTAR on the Buy page once live liquidity pools are opened following the governance launch. #### Staking Staking NECTAR earns you a share of protocol fee buybacks. 27 percent of protocol fees are used to buyback NECTAR on the open market through a mechanism approved by the DAO vote. Note: Bought back NECTAR accumulates in the Treasury and will be distributed to stakers when NECTAR reaches specific target milestones. Your share is based on staking power, which accrues continuously based on the amount staked and the duration of staking. You can stake NECTAR on the Earn page. For programmatic access to staking power data, use the `fetchStakingPower` method in the SDK or the Nectar Liquid API endpoint. #### Staked NECTAR token addresses After staking NECTAR, you receive a Staked NECTAR token. The balance of this token reflects your total staked amount, including any esNECTAR tokens. * Asset Chain: Deployed in conjunction with the Staking Pool contracts on Asset Chain. #### Treasury The Nectar Liquid treasury is funded by: * Fees from the NECTAR protocol owned liquidity * A designated percentage of V2 fees allocated to the treasury and keeper costs The treasury assets are governed under multi-signature security: * DAO Treasury: Multi-sig controlled treasury address (governed by NECTAR DAO). * POL Multisig: Protocol Owned Liquidity multi-signature management. * Governance Committee: Community-elected protocol oversight committee. The Nectar Liquid DAO owns protocol owned liquidity. If required, the treasury may be used to pay for issues submitted through the bug bounty. #### Token supply The supply of NECTAR can be viewed on the Dashboard. The increase in circulating supply varies depending on the number of tokens that are vested. The forecasted max supply is 13.25 million NECTAR tokens. Minting beyond this cap requires a governance vote approved by NECTAR token holders. #### Supply allocation * 6 million NECTAR: Community reserves and early adopters. * 2 million NECTAR: Paired with designated assets for liquidity. * 2 million NECTAR: Reserved for vesting of escrowed NECTAR tokens. * 2 million NECTAR: For the treasury. * 1 million NECTAR: For integration incentives and community developers. * 250,000 NECTAR: Distributed to contributors linearly over two years. #### Network Bridging NECTAR tokens can be bridged between Asset Chain and other networks using supported bridge protocols. Bridging outward may have a waiting period during which you do not have access to your tokens. All Nectar Liquid features operate natively on Asset Chain. #### Next steps * Rewards: Learn about esNECTAR, vesting, and managing rewards. * Voting power: Participate in protocol governance. * Fees: Understand how trading fees are generated and distributed. * Earn page: Start staking NECTAR. --- # 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/tokenomics/nectar-token.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.