Dash Evonodes are a new type of Masternode introduced to Dash in mid-2023 for the purpose of running Dash Platform, aka Evolution or Evo for short. These Masternodes are collateralised with 4000 Dash and upon activation will run additional services as well as the standard ones in the 'dashd'.
Below is some information about these new node types.
The above chart shows the count of Evonodes since the launch. Collateralised means there is 4000 Dash 'locked' in that Masternode, while Enabled means it is also running and thus eligible to earn rewards.
The above chart shows the current APY for Evonodes and Regular Masternodes, note that it does not include any of the fees earned, so the numbers shown above are the lowest estimate for the APY. The APY is calculated looking forward one year, that is what you should earn if you run the node for a year and the network was static over that time. Platform was formally activated in block 2128896 which started loading the credit pool, however platform has not yet started creating blocks.
The above chart is the Evonodes speculative APY chart, it shows the annualised rate of return in Dash for an Evonode and a regular Masternode had Platform been forked and running since the start. This is a historical chart that shows the what the APY was expected to be prior to launch.
The above chart shows the amount of Dash held in Evonodes as percentage of Dash held in all Masternodes.
The above chart shows the Platform Rewards (Fees) earned per each Epoch. The API to get this data goes back to Epoch 35. The total fees paid in each Epoch are made up of the following components, processing + distributedStorage + coreBlockRewards.
The above chart shows the amount of Dash held in the Credit Pool (Asset Lock) on the L1 (POW) blockchain in escrow for the Platform (POS) chain. The amount should exactly balance what is reported by Platform. For every block that is produced a portion of the Masternode reward is added to this pool to be later paid out to the Evonodes as their reward, these payouts happen once every Epoch, which is every 9 nine days or so. When a Evonode operator redeems their Platform credits for Dash, the amount redeemed decreases the Credit Pool shown here and is liberated as Dash. When a Platform user decides to top-up their Identity the Credit Pool will also increase as the Dash they top-up is placed into the Credit Pool and new Platform Credits are minted for their Identity. A similar process happens in reverse.
The above number is the balance of the credits currently held on Platform, it is an integer that is 100,000,000,000 larger than a Dash, so to convert the above number to Dash, you divide it by 10^11. It is expected that the credit pool and the platform balance always agree, in case they do not agree it may indicate some kind of bug, eg drain of credits from platform. One Sat aka Duff gives you 1000 credits.
The Platform delta is the difference between the credit pool, those are assets locked on the payment chain and the Platform balance. This delta should never be positive, meaning more Dash is promised in Platform than what is currently locked in the Credit Pool. Factors that can make the number negative (more Dash in the Credit Pool than on Platform itself are: unclaimed Asset pool locks, pending Withdrawals, and accounting block to block where timing issues can lead to small discrepencies.
Time remaining to next Evonode payments: ???
| Created date | Updated date | Protx hash | Tx Seq | Amount | Address | Status |
|---|---|---|---|---|---|---|
| Loading... | ||||||
The above table shows the withdrawal queue for Platform, withdrawlas are run daily, if the size of the credit pool is over 10k Dash, then a cap of 2,000 Dash per day is impossed globally on withdrawals, below 10k Dash, the maximum withdrawals amount is set at 10% of size of the credit pool, eg if there is 4567 Dash in the credit pool, then the withdrawals for that day will be capped at 456.7 Dash. In case the sum of withdrawals exceeds this amount, then they remain in the queue until the next day.
The above is your unique and secure Dash Platform Node-id and Node-key. From the first line, the 'id' portion of the above can be entered in the protx register_prepare_evo part of the Evonode setup in argument 9 labelled 'platformNodeID'. Copying the block above will give you the private key for your node_key.json file which goes in your tenderdash configuration. In case you are setting up an Evonode now and intend to later setup the server running tenderdash etc, just copy the entire block above and save it in a password manager or similar until you need it.
The table below lists details about every registered evonode on the network, the data is refreshed every 15 mins. Another helpful resource is the Platform Explorer Validators page.
| Protx hash | Collateral address | IP | Status | Active (YNU) | Protocol version | User agent | NodeID | Platform Balance | Platform Proposed Blocks | Platform ChainID | Platform protocol version | DAPI version | Drive version | Tenderdash version | Platform height | Platform epoch | Platform HTTP Port | Platform P2P Port | Country | Votes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Loading... | ||||||||||||||||||||
Table row count: ???