How EVOnode get its Rewards, How earnings distributed from Platform CreditPool?

CoinRider

CoinRider

New member
How EVOnode get its Rewards,
How earnings are distributed?

Please help to understand how EVOnodes rewards are calculated and distributed.

So we get, 60% of new block - goes to masternodes...

From that 60%
62.5% goes to Masternode/EVOnode - 0.89 DASH
37.7% goes to Credit Pool for distribution to EVOnodes only. -0.51 DASH
At the end of EPOH creditpool distributed for EVOnodes, but how....


How exactly Credit Poll are distributed to Platform balances of Active EVOnodes?
what it depends on ( Total EVOnodes, .... .... .... )


I started my EVONode in middle of 7 EPOH and received:
in 7 EPOH - 8.5 DASH on platform balance (nof full epoh running)
in 8 EPOH - 12.6 DASH on platform balance + 2x0.89 DASH from CORE.
in 9 EPOH - 11.4 DASH on platform balance + 2x0.89 DASH from CORE.
in 10 EPOH - 8.64 DASH on platform balance + 2x0.89 DASH from CORE.

+Fees on average was 0.001 for EPOH.

And for 10 EPOH, i did check some other EVOnodes recived 11.77 DASH, 11.01 DASH.
Why my EVOnode received only 8.64 DASH, less than another EVOnode's from same EPOH, that was running same.
It was online all time and has no POSban Score, and updated to new ver., and update was made when it wasn't in quorum.

How is CreditPool distributed what's a distribution algorithm inside platform from CreditPool?
can't find any info about it.
 
The Platform credits are distributed among Evonodes at the end of each epoch (9.125 days / 40 epochs per year). The distribution is through Gaussian distribution. I will let ChatGPT explain what this is :

The Gaussian principle, in the context of distributions, refers to the Gaussian distribution, also known as the normal distribution. This is a fundamental statistical concept representing how values in a dataset tend to cluster around a mean (average) with a characteristic "bell-shaped curve."

Key Properties of Gaussian Distribution:​

  1. Bell-shaped curve:
    • Most values cluster around the mean.
    • As you move further from the mean, the frequency of values decreases symmetrically on both sides.
  2. Symmetry:
    • The curve is symmetric about the mean (μ\muμ).
    • Equal probability of values occurring above or below the mean.
  3. Defined by two parameters:
    • μ\muμ (mean): the central value where the peak of the curve occurs.
    • σ2\sigma^2σ2 (variance): the spread of the data. The square root of variance, σ\sigmaσ (standard deviation), determines the width of the curve.
  4. 68-95-99.7 Rule(Empirical Rule):
    • 68% of values lie within 1 standard deviation (μ±σ\mu \pm \sigmaμ±σ).
    • 95% of values lie within 2 standard deviations (μ±2σ\mu \pm 2\sigmaμ±2σ).
    • 99.7% of values lie within 3 standard deviations (μ±3σ\mu \pm 3\sigmaμ±3σ).

Relevance to Platform Credits Distribution in Tenderdash:​

If Tenderdash uses a Gaussian distribution for allocating Platform credits among Evonodes:

  1. Fairness: The majority of Evonodes would receive a credit amount close to the mean (μ\muμ), ensuring equitable distribution.
  2. Probability of outliers: A few Evonodes might receive significantly higher or lower credits than the mean, but these instances would be rare and statistically predictable.
  3. Optimization: Gaussian distribution minimizes extremes and centralizes credit distribution, likely promoting system stability and reducing bias in resource allocation.
This approach leverages the predictability of the Gaussian model to balance rewards effectively while ensuring that the allocation process is not skewed heavily toward any extremes.
Click to expand...
So your Evonode can perform really well one epoch, and considerably less the next epoch. But looking at this long term and with regards to the median of received Platform credits, this should work out in the long run. Also to clarify : Tenderdash is a fork from Tendermint.

Just be aware the more Evonodes are setup and become operational on the Dash network, the lower the annual APY of Evonodes will get and the less Platform credits per epoch your Evonode / all Evonodes will receive.

You can calculate the annual / monthly / per epoch APY estimate for Evonodes with this tool : https://www.dash.org/forum/index.ph...masternode-and-evonode-apy.55273/#post-239445 You just need to provide it with :

Number of Enabled Masternodes (Dash Core wallet, Information)
Number of Enabled Evonodes on latest Platform (v1.5.x & v1.6.x) --> https://mnowatch.org/evonodes/
Number of Enabled Evonodes (Dash Core wallet, Information)

Also be informed that in a future Platform version the leftover fees from registering a contested username (0.2 dash per username), will be distributed among Evonodes as well at the end of each epoch. This could be in Platform v1.7.0 (when it activate two epochs after release), but i am not totally sure it will be in that specific Platform version. Could be in a later Platform version.

What we really need though are dApps on Platform, that utilize Platform and start a fees market for Evonodes. Maybe provide additional revenue streams for Evonodes too. We currently have one dApp : the DashPay wallet dApp. It is only on Android, only for 64 bit devices and has some bugs right now that devs are working on fixing. I am not even sure we can even call it a dApp right now, it is more like a Semi-dApp.
 
Last edited:
peter said:
And what happens to the 0.2 Dash today? Burned?
Click to expand...
All i know is that each contested username has its own bucket where that fee goes into. That bucket pays for masternodes and evonodes voting on contested usernames. If mno's (masternode and evonode operators) vote multiple times on a contested username (by changing their vote for example), then that bucket will get even lower. Any leftover of those buckets will at some point be distributed among Evonodes in a future Platform update at the end of each epoch.
 
Last edited:
at first it seemed that there was a dependence on the offered blocks and it seemed that there were somewhere 0.6 dashes for 1 block... but now there are much more blocks (it is also not clear why) but there are fewer dash coins
 
tfoto said:
at first it seemed that there was a dependence on the offered blocks and it seemed that there were somewhere 0.6 dashes for 1 block... but now there are much more blocks (it is also not clear why) but there are fewer dash coins
Click to expand...
mno's voting on contested usernames create state transitions --> faster blocks
more Evonodes operational on the Dash network --> lower APY for Evonodes --> less Platform credits per Evonode each epoch.
 
qwizzie said:
That bucket pays for masternodes and evonodes voting
Click to expand...
Does it mean, that the node, that votes, gets a part of the bucket, or is it burned? Or something else?

qwizzie said:
Any leftover of those buckets will at some point be distributed among Evonodes in a future Platform update at the end of each epoch.
Click to expand...
Does it mean, that today the leftover of those buckets are accumulated and saved somewhere, and distributed later in a future version?
 
peter said:
Does it mean, that the node, that votes, gets a part of the bucket, or is it burned? Or something else?


Does it mean, that today the leftover of those buckets are accumulated and saved somewhere, and distributed later in a future version?
Click to expand...
I suspect it will get burned, not totally sure how it works.
Yes today / at present the leftover of those buckets are accumulated and saved somewhere, and distributed later in a future version. Or they will just stay as leftover in their buckets and distributed later in a future version (i think it is the last).
 
CoinRider said:
I started my EVONode in middle of 7 EPOH and received:
in 7 EPOH - 8.5 DASH on platform balance (nof full epoh running)
in 8 EPOH - 12.6 DASH on platform balance + 2x0.89 DASH from CORE.
in 9 EPOH - 11.4 DASH on platform balance + 2x0.89 DASH from CORE.
in 10 EPOH - 8.64 DASH on platform balance + 2x0.89 DASH from CORE.
Click to expand...


You ran 3 complete Epochs and got total Dash (12.6+11.4+8.64)+3*2*0.89=37.98 DASH. Annualised that's 37.98/3*40=506.4 Dash. As a percentage of 4000 Dash, 506/4000*100=12.66% According to MNOwatch, evonodes page, the APY is






Evonodes apy.png



So yo beat the average and still complain? Am I confused?
 
You must log in or register to reply here.
Back
Top