|
StakeBox
|
 |
August 17, 2016, 04:04:02 PM |
|
While I have a bit of time to kill waiting for things to get going I figured I would talk for a minute about the PoS rewards for anyone who was wondering. If you either haven't been here for long, or haven't been keeping up with everything, you may have noticed that the rewards for staking don't seem to match up with what you may have expected. So here is a breakdown of what is going on, I posted this in slack when asked, so will just copy and paste it here with a bit of editing and a few additions.
Masternodes will be paid a portion of the block rewards. Refer to the OP of the ANN thread for the block rewards for any given block number. We have implemented a "seesaw" reward mechanism that is used to determine the split between the masternode and the staker of the block. Right now the value of each block is 50 DNET. 10% of that is reserved for the budget, which is voted on by the owners of masternodes, anyone can submit a proposal to be voted on. So, we are left with 45 DNET to be shared between the winning masternode and the staker
Here is the actual code that is used to determine the split.
else if(nHeight > LAST_POW_BLOCK)
{
int64_t nMoneySupply = chainActive.Tip()->nMoneySupply;
int64_t mNodeCoins = mnodeman.size() * 10000 * COIN;
if(fDebug)
LogPrintf("GetMasternodePayment(): moneysupply=%s, nodecoins=%s \n", FormatMoney(nMoneySupply).c_str(),
FormatMoney(mNodeCoins).c_str());
if (mNodeCoins <= (nMoneySupply * .05) && mNodeCoins > 0) {
ret = blockValue * .85;
}
else if (mNodeCoins <= (nMoneySupply * .1) && mNodeCoins >= (nMoneySupply * .05)) {
ret = blockValue * .8;
}
else if (mNodeCoins <= (nMoneySupply * .15) && mNodeCoins >= (nMoneySupply * .1)) {
ret = blockValue * .75;
}
else if (mNodeCoins <= (nMoneySupply * .2) && mNodeCoins >= (nMoneySupply * .15)) {
ret = blockValue * .7;
}
else if (mNodeCoins <= (nMoneySupply * .25) && mNodeCoins >= (nMoneySupply * .2)) {
ret = blockValue * .65;
}
else if (mNodeCoins <= (nMoneySupply * .3) && mNodeCoins >= (nMoneySupply * .25)) {
ret = blockValue * .6;
}
else if (mNodeCoins <= (nMoneySupply * .35) && mNodeCoins >= (nMoneySupply * .3)) {
ret = blockValue * .55;
}
else if (mNodeCoins <= (nMoneySupply * .4) && mNodeCoins >= (nMoneySupply * .35)) {
ret = blockValue * .5;
}
else if (mNodeCoins <= (nMoneySupply * .45) && mNodeCoins >= (nMoneySupply * .4)) {
ret = blockValue * .45;
}
else if (mNodeCoins <= (nMoneySupply * .5) && mNodeCoins >= (nMoneySupply * .45)) {
ret = blockValue * .4;
}
else if (mNodeCoins <= (nMoneySupply * .55) && mNodeCoins >= (nMoneySupply * .5)) {
ret = blockValue * .35;
}
else if (mNodeCoins <= (nMoneySupply * .6) && mNodeCoins >= (nMoneySupply * .55)) {
ret = blockValue * .3;
}
else if (mNodeCoins <= (nMoneySupply * .65) && mNodeCoins >= (nMoneySupply * .6)) {
ret = blockValue * .25;
}
else if (mNodeCoins <= (nMoneySupply * .7) && mNodeCoins >= (nMoneySupply * .65)) {
ret = blockValue * .2;
}
else if (mNodeCoins <= (nMoneySupply * .75) && mNodeCoins >= (nMoneySupply * .7)) {
ret = blockValue * .15;
}
else{
ret = blockValue * .1;
}
}
So, basically, when the number of coins locked in masternodes is between 0 and 5 percent of of all available coins the winning masternode gets 85% of the block reward. using that as a reference you can go through the code to see that if the number of coins in masternodes is more than 75% of all available coins the winning masternode will get 10% of the block reward.
There are 16 steps to the seesaw right now, over time we will tweak the seesaw as we get a better feel for how the various aspects of the network perform. We started with the idea that about 1/3 of coins being in masternodes is an ideal split. That makes for a strong masternode network, which is responsible for the Obfuscation transactions as well as the SwiftTX transactions. It should also leave enough coins in the wild to support the needed level of staking to promote blockchain security, and have a good number of coins on the exchange to provide sufficient liquidity.
A more user friendly breakdown of the steps of the seesaw is as follows.
If number of coins in masternodes is between 0 and 5 percent of coin supply masternodes will receive 85% of the block rewards.
If number of coins in masternodes is between 5 and 10 percent of coin supply masternodes will receive 80% of the block rewards.
If number of coins in masternodes is between 10 and 15 percent of coin supply masternodes will receive 75% of the block rewards.
If number of coins in masternodes is between 15 and 20 percent of coin supply masternodes will receive 70% of the block rewards.
If number of coins in masternodes is between 20 and 25 percent of coin supply masternodes will receive 65% of the block rewards.
If number of coins in masternodes is between 25 and 30 percent of coin supply masternodes will receive 60% of the block rewards.
If number of coins in masternodes is between 30 and 35 percent of coin supply masternodes will receive 55% of the block rewards.
If number of coins in masternodes is between 35 and 40 percent of coin supply masternodes will receive 50% of the block rewards.
If number of coins in masternodes is between 40 and 45 percent of coin supply masternodes will receive 45% of the block rewards.
If number of coins in masternodes is between 45 and 50 percent of coin supply masternodes will receive 40% of the block rewards.
If number of coins in masternodes is between 50 and 55 percent of coin supply masternodes will receive 35% of the block rewards.
If number of coins in masternodes is between 55 and 60 percent of coin supply masternodes will receive 30% of the block rewards.
If number of coins in masternodes is between 60 and 65 percent of coin supply masternodes will receive 25% of the block rewards.
If number of coins in masternodes is between 65 and 70 percent of coin supply masternodes will receive 20% of the block rewards.
If number of coins in masternodes is between 70 and 75 percent of coin supply masternodes will receive 15% of the block rewards.
If number of coins in masternodes is more than 75 percent of coin supply masternodes will receive 10% of the block rewards.
This is a bit more rudimentary than we initially anticipated, but should work well enough for the time being until we get a good idea of the profitability of staking vs masternode ownership. We will be revisiting the seesaw once we have more data to base the numbers on.
The primary goal behind the seesaw is to ensure that it is always more profitable to have a masternode than it would be to just stake those 10k coins. The reason for that is the costs, hassles, and risks associated with upkeep of a masternode are greater than those of staking alone. But we also need to ensure that there are enough coins not in masternodes for the reasons presented above.
|
|
|
|
|
|
|
|
|
|
|
If you see garbage posts (off-topic, trolling, spam, no point, etc.), use the "report to moderator" links. All reports are investigated, though you will rarely be contacted about your reports.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
xtrembash
|
|
August 17, 2016, 04:32:36 PM |
|
still stuck @bloc 259200 under 2.1.1 ..
is it "normal" .. ?!
|
|
|
|
|
Haunebu81
|
|
August 17, 2016, 04:36:25 PM |
|
still stuck @bloc 259200 under 2.1.1 ..
is it "normal" .. ?!
Yes, it's done like that intentionally until the new fix goes live later on today. Ok Everyone, We are pretty confident this is the one..  Fair Release for Staking tomorrow at 9PM EST Instructions, -Remove addnodes from conf file -Delete all your files except the wallet.dat, and the (2) .conf files -Sync from Scratch, Wallet will stop at 259200 until 9PM EST Then everyone can start to stake.. Thank You for your Patience.. Wallets are uploaded and ready, Links in the OP are updated as well. |
|
|
|
|
|
EcoChavCrypto
|
|
August 17, 2016, 06:14:32 PM |
|
Are we all still using the below addnodes in v2.1.1.0?
addnode=104.218.120.208
addnode=185.69.52.224
addnode=188.60.65.97
addnode=130.255.12.2
addnode=185.129.62.63
|
|
|
|
|
jk9694
|
|
August 17, 2016, 06:25:43 PM |
|
Are we all still using the below addnodes in v2.1.1.0?
addnode=104.218.120.208
addnode=185.69.52.224
addnode=188.60.65.97
addnode=130.255.12.2
addnode=185.129.62.63
addnode=coin-server.com |
|
|
|
|
jakiman
Legendary
 Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
August 17, 2016, 07:09:22 PM |
|
Are we all still using the below addnodes in v2.1.1.0?
addnode=104.218.120.208
addnode=185.69.52.224
addnode=188.60.65.97
addnode=130.255.12.2
addnode=185.129.62.63
addnode=coin-server.com Actually, you do not need any addnodes in the conf file as stated by s3v3nh4cks instructions above. But coin-server.com is fine. |
|
|
|
|
jk9694
|
|
August 17, 2016, 07:48:22 PM |
|
Are we all still using the below addnodes in v2.1.1.0?
addnode=104.218.120.208
addnode=185.69.52.224
addnode=188.60.65.97
addnode=130.255.12.2
addnode=185.129.62.63
addnode=coin-server.com Actually, you do not need any addnodes in the conf file as stated by s3v3nh4cks instructions above. But coin-server.com is fine. When we ran the "test" last night, coin-server.com was handling 598 connections. Made for a very very quick sync as that is on a 1 GB fiber connection with no bandwidth limitations. |
|
|
|
|
jakiman
Legendary
Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
August 17, 2016, 08:42:15 PM |
|
Ahh. Good to know. I'll use that next time i need to sync quickly. |
|
|
|
|
EcoChavCrypto
|
|
August 18, 2016, 01:06:37 AM |
|
Wallet is synced, masternode started successfully and blocks are moving along. Currently on 259229. So far so good. |
|
|
|
B1tUnl0ck3r
Sr. Member
Offline
Activity: 854
Merit: 277
liife threw a tempest at you? be a coconut !
|
|
August 18, 2016, 01:09:11 AM |
|
Same here for one wallet, the other crashed... same chain?
getblockhash 259234
401290011c0d187b6b1e2c153509cd8c763315f1d44ee5829a1bcac1954ba69f
|
When the people of the world will get that covid was intentionally released to frame china, steal the election from trump, assure massive bail outs and foster the forced vaccination agendas...they will forget, like 911, wmds in irak, uss liberty or pedogate.
|
|
|
|
EcoChavCrypto
|
|
August 18, 2016, 01:13:54 AM |
|
Same here for one wallet, the other crashed... same chain?
getblockhash 259234
401290011c0d187b6b1e2c153509cd8c763315f1d44ee5829a1bcac1954ba69f
I am a bit behind but yes 02:11:41  Block height out of range (code -8) 02:12:51  getblockhash 259234 02:12:51  401290011c0d187b6b1e2c153509cd8c763315f1d44ee5829a1bcac1954ba69f |
|
|
|
|
EcoChavCrypto
|
|
August 18, 2016, 01:15:23 AM |
|
Just got an MN payout. Status: 18 confirmations Date: 18/08/2016 02:08 Credit: 38.25000884 DNET Net amount: +38.25000884 DNET EDIT: And another. |
|
|
|
|
borris123
|
|
August 18, 2016, 01:30:14 AM |
|
this right? i lagging behind on blocks...
02:29:34

getblockhash 259206
02:29:34

94dc5a94f7908b68b592817cda25836b4a1d7dd5c302c2d3765c626bc70ba4f2
|
|
|
|
|
|
EcoChavCrypto
|
|
August 18, 2016, 01:35:18 AM |
|
I just got stuck at 308 had a wallet crash and block data corruption. I removed coin-server addnode from both confs and tried to stop ./darknet-cli in the node which failed. ./darknetd restarted without issue.
I'll re-sync the desktop wallet and let you guys know how it goes.
|
|
|
|
|
|
|
borris123
|
|
August 18, 2016, 01:40:22 AM |
|
need some add nodes. i not connecting to anyone with a full sync
|
|
|
|
|
|
EcoChavCrypto
|
|
August 18, 2016, 01:41:13 AM |
|
need some add nodes. i not connecting to anyone with a full sync
I seem to be syncing ok without. |
|
|
|
|
borris123
|
|
August 18, 2016, 01:45:47 AM |
|
masternode_payments_stats gone down
|
|
|
|
|
jakiman
Legendary
Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
August 18, 2016, 01:47:19 AM |
|
My wallet keeps crashing and chain gets corrupt. Done it twice now.  Lucky I made a backup of the chain at 259200. But yeah, this is new. |
|
|
|
|
borris123
|
|
August 18, 2016, 01:47:53 AM |
|
My wallet keeps crashing and chain gets corrupt. Done it twice now. think windows wallet fucked |
|
|
|
|
|
Poll
