# RENDER Emissions and RNDR Metrics (Legacy) Summary

## RENDER Token Information – Historical Reference <a href="#h.frizjo6eos6c" id="h.frizjo6eos6c"></a>

**Note on historical context:** The Render Network has migrated to a new Burn Mint Equilibrium (BME) model passed by Render Network governance in [RNP-001](https://github.com/rendernetwork/RNPs/blob/main/RNP-001.md). Updates to Burn Mint Equilibrium (BME) emissions have been made in [RNP-006](https://github.com/rendernetwork/RNPs/blob/main/RNP-006.md), [RNP-013](https://github.com/rendernetwork/RNPs/blob/main/RNP-013.md), and [RNP-015](https://github.com/rendernetwork/RNPs/blob/main/RNP-015.md). **Refer to those documents for more up-to-date information.** Legacy RNDR ERC-20 token information is summarized below for historical reference. Much of the information below is no longer up to date.

## **Background on RNDR Token Sales & Bonus** <a href="#h.yjui8xrxxjhh" id="h.yjui8xrxxjhh"></a>

The sale took place in two phases. The project kicked off with a public sale on the Ethereum blockchain followed by a private sale phase in the months after. All tokens sold have been issued on the old Ethereum contract.

**Public Sale:** Oct 2017

* **Public Sale Price:** 1 RNDR = $0.25 USD equivalent of token\*
* **Public Sale Bonus:** 20% Genesis Bonus (Dec 5, 2018)
* **Public Sale Vesting**: none

\*The ETH/RNDR exchange rate was 1150 RNDR per 1 ETH for the token sale. This was decided by taking a 30-day weighted average of the price of ETH when the sale started.

**Private Sale:** Jan 2018 — May 2018

* **Private Sale Price:** 1 RNDR = $0.25 USD equivalent of token\*
* **Private Sale Bonus:** 2.5% to 30% Bonus
* **Private Sale Vesting:** none

\*Converted to ETH at time of purchase

RNDR Token’s migration updates the ERC-20 tokens distributed to token holders to include additional escrow smart-contract functionality. [In March 2018, we announced that the total minted tokens in the RNDR ecosystem would be 536,870,912 RNDR](https://medium.com/render-token/rndr-token-migration-instructions-7db3ee8941a), (or 2^29). This number was derived from our analysis on the supply/demand for rendering over the next 10–12 years.

* **Migration ratio:** 1 RNDR old => 1 RNDR new
* **New contract:** [0x6de037ef9ad2725eb40118bb1702ebb27e4aeb24](https://etherscan.io/address/0x6de037ef9ad2725eb40118bb1702ebb27e4aeb24)
* **Currently migrated:** 504.8m RNDR
* **Migration end:** Migration stays open indefinitely
* **Migration supply limit:** 536,870,912 RNDR\*

\* The oversupply on the old contract of 1,610,612,736 (1.61bn) RNDR will be burned by July 2020. More on how this process will occur will be announced before the actual burn date.

## **RNDR Purchasing Plan (March 2020)** <a href="#h.qjjo7ne1ss88" id="h.qjjo7ne1ss88"></a>

[As announced on March 16th, the RNDR network planned to purchase up to 4.5 million RNDR tokens on the Probit exchange.](https://medium.com/render-token/rndr-token-migration-instructions-7db3ee8941ahttps://etherscan.io/token/0x6de037ef9ad2725eb40118bb1702ebb27e4aeb24https:/medium.com/render-token/update-rndr-purchasing-plan-87ac2688ef4e) These tokens will flow back to creators and new users on the RNDR ecosystem in order to provide an easier way to get started using RNDR, ultimately helping scale the network for both creators and node operators. Although the initial timeline for token purchasing has completed, we will continue to purchase tokens on the open market as needed for user growth + user acquisition efforts.

We have since made an [ETH address to track these tokens](https://etherscan.io/address/0x0e54147eecbc7ebc945b3a59aee7124ff70c6c95).

There is a limit on how much we can withdraw on ProBit on a daily basis, and we will continue to flow tokens into the address. The plan is to continue to transfer previously purchased RNDR to this address and use this wallet as a way to increase user acquisition over the coming months.

To date, we have acquired 3.2m tokens from ProBit at an average price of about $0.042. We will continue to purchase tokens from time to time in order to support faster network growth and initiatives like the RNDR Credit system.

The RNDR token information is available from [Coinmarketcap](https://coinmarketcap.com/currencies/render-token/) and [CoinGecko](https://www.coingecko.com/en/coins/render-token).

Coinbase recently announced that they are exploring the addition of a range of new assets. [RNDR was listed as one of the 18 projects](https://blog.coinbase.com/coinbase-continues-to-explore-support-for-new-digital-assets-2c5b84813fcf?gi=78647faa804f).

The RNDR team is constantly exploring ways to make a more sustainable ecosystem for users, including working with partners who align with RNDR’s mission to provide easy and secure access to the network for all node operators and creators. Due to the current nature of exchange news and listings, we can only announce developments when confirmed by our exchange partners. Please turn on Telegram/Twitter notifications, as well as Medium reminders in order to stay up to date on any updates that may occur over the coming weeks and months.

The network also introduced [RNDR Credits](https://know.rendernetwork.com/basics/broken-reference), an easy creator friendly way to purchase rendering power on the network using [PayPal](https://www.paypal.com/us/home) and [Stripe](https://stripe.com/). These Credits are non-exchangeable and only usable on the network. The RNDR Network uses tokens purchased on the open market to support this RNDR Credit system. As new payment options are created we will release information on the [RNDR Medium channel](https://medium.com/render-token).

**— The RNDR Team**


---

# Agent Instructions: 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:

```
GET https://know.rendernetwork.com/basics/token-metrics-summary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.