> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/basics/the-render-spl-token.md). # The RENDER SPL Token Information about the RENDER SPL token In [RNP-001](https://github.com/rendernetwork/RNPs/blob/main/RNP-001.md), the Render Network community approved the transition to the Burn Mint Equilibrium (BME) where artists burn RENDER tokens in exchange for an equivalent USD valued Render Credits, that are non-fungible work credits. For nodes fulfilling the GPU work, RENDER tokens are distributed as network emissions, which are outlined in [RNP-006](https://github.com/rendernetwork/RNPs/blob/main/RNP-006.md) and updated in [RNP-013](https://github.com/rendernetwork/RNPs/blob/main/RNP-013.md). The Burn Mint Equilibrium has been implemented on the Solana Blockchain, with the legacy ERC-20 RNDR token being upgraded to RENDER SPL tokens in the operation of the BME. Complete upgrade information for the RENDER SPL token can be found [here](https://renderfoundation.com/upgrade). \ \ **Using RENDER Tokens**\ GPU computing work on the Render Network is done by burning RENDER SPL Tokens in exchange for an equivalent amount of Render Credits. These Render Credits provide the corresponding USD value of the burned RENDER Tokens and are used to submit work the network. Once artists burn the required amount of base token (RENDER), a set of non-transferrable, non-fungible **Coupon Tokens** (Render Credits) are issued to requesters to complete jobs. \ *Example: A Render Network creator burns $5 worth of RENDER to produce 5 Render Credits, which are non-fungible and non-transferrable* --- # 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://know.rendernetwork.com/basics/the-render-spl-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.