[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN

[Haunebu81]

Is the new vultr MN script out yet?

[1714092637]

1714092637

[q327K091]

collecting like an aggressive landlord collects rents

missing a transaction though.. anyone knows if we have block explorer ? thanks

never mind ,nothing is missing, network is operating great, spinning yet another master node as per indication (slack) things will move big time in months to come, I call it a "sleeper" in the crypto world

[Haunebu81]

collecting like an aggressive landlord collects rents

missing a transaction though.. anyone knows if we have block explorer ? thanks

Yep, right here: http://lmgtfy.com/?q=darknet+block+explorer

[StakeBox]

Running masternode start via the debug console yields the following error:

Not capable masternode: can't detect external address. Please use the masternodeaddr configuration option. Nothing is mentioned in the initial post about having to do this, only using the default 127 / local loop address at least for a single master node.

It is not usually needed. I should just have s3v3n modify the instructions to include it, and, upon further review, I see that the start command is incorrect there, which is why you were entering it like that. I will let him know to fix that as well.

To use the masternodeaddr configuration option add masternodeaddr=<your external IP address> in darknet.conf.

[tomahawkeer]

Running masternode start via the debug console yields the following error:

Not capable masternode: can't detect external address. Please use the masternodeaddr configuration option. Nothing is mentioned in the initial post about having to do this, only using the default 127 / local loop address at least for a single master node.

It is not usually needed. I should just have s3v3n modify the instructions to include it, and, upon further review, I see that the start command is incorrect there, which is why you were entering it like that. I will let him know to fix that as well.

To use the masternodeaddr configuration option add masternodeaddr=<your external IP address> in darknet.conf.

edit: appears to be working. It didnt like using the nat address apparently.

[q327K091]

collecting like an aggressive landlord collects rents

missing a transaction though.. anyone knows if we have block explorer ? thanks

Yep, right here: http://lmgtfy.com/?q=darknet+block+explorer

pretty funny, .. great block explorer btw.., ok.. span off and activated 68th master node , thanks all and God speed

[tomahawkeer]

how often do masternodes get payments

[StakeBox]

how often do masternodes get payments

Right now it takes around 48 hours to begin receiving masternode payments. Once you start getting them you can calculate the number of expected payments per day with the following formula.

number of blocks per day/number of masternodes=number of daily payments per masternode

So, right now you can expect 1440/974~1.47 payments per day. With the current number of masternodes on the network masternode payments are 29.25 DNET, so you are looking at about 43 DNET per day per masternode, on average.

These numbers reflect as things stand right now, and could change daily, or even hourly, if the number of masternodes changes.

[Haunebu81]

how often do masternodes get payments

60 Second block time = 1440 blocks per day.
973 Masternodes online.

1440 / 973 = 1.48 times per day on average.

That would make the current average daily revenue per each masternode, about $0.18, or $5.47 per month.

[tomahawkeer]

That isn't too bad. How good is the staking  or is that included in the MN calculations?

[StakeBox]

That isn't too bad. How good is the staking  or is that included in the MN calculations?

The reward structure is set up so that as long as 1/3 or less of the total coin supply is locked up in masternodes it will be more profitable to have 10k in a masternode than to be staking 10k. The block rewards are fixed, the reward for staking is not a percentage of the staking input as with most other PoS coins. Here is a bit to help you better understand how things work.

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.

[NotMyFarm]

Mac Wallet still disconnecting (while staking) somewhere between the 24 h
have to restart once a day

My Transactions are all messed up
in overview it only shows very old once
 

[jakiman]

DEV UPDATE

Mandatory v2.1.2.2 wallet update has been released today by Stakebox that has fixed some core bugs and include many frontend improvements.

https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.1.2.2

Change Log
- Incorrect math for the max budget, the block rewards, and the seesaw mechanism were corrected.
- Issue with masternode payment enforcement has been addressed.
- Unconfirmed staking and masternode rewards will no longer be shown in coin control.
- Masternode rewards will be marked as such in the transactions tab, and will no longer show as confirmed prematurely.
- Staking and masternode rewards will also show in the immature row on the main overview page of the wallet.
- Transactions sent using Obfuscation were showing as Darksent in the transactions page before, they will show as Obfuscated now.
- 2 new RPC calls created. setstakesplitthreshold & getstakesplitthreshold. This will allow people to experiment with stake split sizes.
- Few other minor changes to the Qt

As with any wallet upgrades, please backup first then test with 1 or few of your wallets and masternodes first before upgrading all wallets.

[DRPD]

DEV UPDATE

Mandatory v2.1.2.2 wallet update has been released today by Stakebox that has fixed some core bugs and include many frontend improvements.

https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.1.2.2

Change Log
- Incorrect math for the max budget, the block rewards, and the seesaw mechanism were corrected.
- Issue with masternode payment enforcement has been addressed.
- Unconfirmed staking and masternode rewards will no longer be shown in coin control.
- Masternode rewards will be marked as such in the transactions tab, and will no longer show as confirmed prematurely.
- Staking and masternode rewards will also show in the immature row on the main overview page of the wallet.
- Transactions sent using Obfuscation were showing as Darksent in the transactions page before, they will show as Obfuscated now.
- 2 new RPC calls created. setstakesplitthreshold & getstakesplitthreshold. This will allow people to experiment with stake split sizes.
- Few other minor changes to the Qt

As with any wallet upgrades, please backup first then test with 1 or few of your wallets and masternodes first before upgrading all wallets.

ok updating 5 nodes for test
is there a block or timeframe until the update must be done

[NotMyFarm]

Mac Wallet updated
works like a charm
back to staking 

[borris123]

Does this fix masternode start-missing?

[mikegi]

DEV UPDATE

Mandatory v2.1.2.2 wallet update has been released today by Stakebox that has fixed some core bugs and include many frontend improvements.

https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.1.2.2

Change Log
- Incorrect math for the max budget, the block rewards, and the seesaw mechanism were corrected.
- Issue with masternode payment enforcement has been addressed.
- Unconfirmed staking and masternode rewards will no longer be shown in coin control.
- Masternode rewards will be marked as such in the transactions tab, and will no longer show as confirmed prematurely.
- Staking and masternode rewards will also show in the immature row on the main overview page of the wallet.
- Transactions sent using Obfuscation were showing as Darksent in the transactions page before, they will show as Obfuscated now.
- 2 new RPC calls created. setstakesplitthreshold & getstakesplitthreshold. This will allow people to experiment with stake split sizes.
- Few other minor changes to the Qt

As with any wallet upgrades, please backup first then test with 1 or few of your wallets and masternodes first before upgrading all wallets.

Nice update, this has the kind of information I like to see.

Building now.. testing soon...

[jakiman]

Does this fix masternode start-missing?

We'll have to wait for StakeBox or s3v3nh4cks to answer that one. But it wasn't specifically mentioned.

ok updating 5 nodes for test
is there a block or timeframe until the update must be done

Not sure if there is a timeframe as the chain isn't being touched. But hopefully the devs can answer this also.

[NotMyFarm]

question

lets say i have 50k Dnet

i can run 5 MN's
can the 5 MN Wallets stake parallel ?
(be Masternodes and Stake at the same time)
 

is there more payments for the 5 MN's
or 50k Wallet staking ?

[borris123]

question

lets say i have 50k Dnet

i can run 5 MN's
can the 5 MN Wallets stake parallel ?
(be Masternodes and Stake at the same time)
 

is there more payments for the 5 MN's
or 50k Wallet staking ?

You earn more for masternodes and the coins earned from them can stake in the controller. The 10k will not stake and is locked.