Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 359. (Read 782375 times)

I seem to be syncing ok without.

need some add nodes. i not connecting to anyone with a full sync

I'm getting the same hash & block as the MN Info page.
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

getblockhash 259354
eec3af574e7f12628ebd1866b8d92f7f8aa4964c33ef32c28043394a7d41ccb1

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.   

this right? i lagging behind on blocks...


02:29:34

getblockhash 259206


02:29:34

94dc5a94f7908b68b592817cda25836b4a1d7dd5c302c2d3765c626bc70ba4f2

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. 

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

Same here for one wallet, the other crashed... same chain?

getblockhash 259234

401290011c0d187b6b1e2c153509cd8c763315f1d44ee5829a1bcac1954ba69f

Wallet is synced, masternode started successfully and blocks are moving along.  Currently on 259229.

So far so good. 

Ahh. Good to know. I'll use that next time i need to sync quickly. 

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.

Actually, you do not need any addnodes in the conf file as stated by s3v3nh4cks instructions above. But coin-server.com is fine.

addnode=coin-server.com

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

Yes, it's done like that intentionally until the new fix goes live later on today.

still stuck @bloc 259200 under 2.1.1 ..
is it "normal" .. ?!

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.

yep.. been downloading and synching over and over again, it was quite annoyed, i guess patience will payoff huh!

Yup. You are absolutely right it sure has been a mess. We are looking forward to moving past this when things start moving again tonight. We are so grateful to the community for bearing with us through all of the hassle this past week has presented us. I think that the folks in here are some of the best in crypto, and we are so glad to have you guys here with us.

We knew there would be a few roadbumps, but never expected to encounter the level of hassle that we did. There is clearly a reason all other PoS coins just stick with the old Bitcoin codebase, but if we want PoS in general to remain competitive things must advance. Most of the issues we have encountered along the way were only evident once there were a large number of people stress testing the system, we could not have done it without you guys. We are so grateful to you all.

Thank you for that. Again, I would also like to apologize on behalf of the team for having missed your request in the first place. But, your apology means a lot to us, it is not something that can be expected from most folks involved in crypto. No one here usually likes to admit mistakes, those who are willing to do so are few and far between. I am glad you see it as a mistake, we want to help in any way we can, but don't always see every post, especially in trying times such as we have been going through the past week or so.

I just want to emphasize for everyone the slack and skype contact methods. There are fewer people in slack, skype seems to be really active all of the time, but either one of those places will get you a quicker response more often than not. Links are in the OP, stop in and say hi.

Yes, they could have surrended after the second or third failure, but they has been /will keep working until find the solution. This made me very comfortable about  having a nice amount of this coin.