> For the complete documentation index, see [llms.txt](https://docs.pulselend.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulselend.com/about-pulselend/plend-token.md). # PLEND Token The utility of the PulseLend protocol extends into its native token, PLEND. Here's an outline of the main functions and features of the PLEND token within the PulseLend ecosystem: #### 1. Governance PLEND serves as the primary token for governance within the PulseLend protocol. Owners of PLEND have the ability to participate in shaping the future of the protocol. This empowers users by giving them a say in the decision-making processes of the platform, thus truly decentralizing authority. #### 2. Protocol Support Staking PLEND tokens in the PulseLend Safety Cave offers additional support to the protocol. This safety measure is designed to protect the platform during potential shortfall events, thereby ensuring the robustness and reliability of the system in uncertain times. #### 3. Delegation Capabilities PLEND can also be delegated to a PRC-20 address. This functionality further encourages active participation within the PulseLend ecosystem by allowing users to entrust their voting rights to delegates who they believe can make well-informed decisions on their behalf. #### 4. Incentives and Rewards An additional feature of PulseLend's protocol is its rewards system. Users can earn PLEND emissions and a portion of the fees generated by the protocol, exclusively when they stake their PLEND tokens. This incentive structure rewards active participation and investment in the platform, fostering a vibrant and engaged community. In summary, PLEND's multiple functionalities, including governance, support, delegation, and incentives, serve to enhance the PulseLend protocol's usability and efficiency, fostering a resilient and inclusive DeFi ecosystem. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pulselend.com/about-pulselend/plend-token.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.