I am in the same boat as cgt99. win7-64 same error message. I tried sync from scratch, no improvement.

my masternode.conf is empty (only the example), I didn't need to configure it with previous dnet version. If I switch back to the previous version, the masternode works perfectly.

However staking is working, it's specifically the masternode, the little lock icon never appears (tried to create new masternode too without success).

What should I do? any advices?

tx for the "yell" at s3v3n
as well how do i run 2nd wallet on 1 computer (1 testnet - 1 real)

if you have an (idiot proved) mac guide for this
i consider  

That issue was never mentioned as fixed. So I assume it can still happen.

But in saying that, I haven't had that hang issue for the last 100+ start-alias commands.
I just make sure I run start-alias at least 5 seconds after running the walletpassphrase.

Turns out that the 10000 DNET was used to pay a 40 DNET fee in the same block.... perhaps to do with having obfuscation enabled.

So what have I learned...

Transactions shown by "darknet-cli listlockunspent" might already be spent or might not even exist
(Try putting a fictional txid into masternode.conf )

Transactions listed in masternode.conf will be locked when starting the node.

"darknet-cli masternode list-conf" does exactly what it says... Print's the contents of masternode.com at the time dartknetd was rund in JSON format  as well as printing the status of the node.

I selected everything using coin control, still cant even move <1000 coins.
Will try again tonight

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

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.

how often do masternodes get payments

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.

This is a local master node, Windows server 2008 R2, yes this is the QT wallet 64 bit. The darknet-cli is the command line, and not the debug window, however issuing the command via the debug window gives a similar error message. (same code, less verbose). As far as the masternode address is concerned, that is part of the directions in the initial post for creating a new master node..

Staking on Mac
(payments coming  )

my wallet dropps of Network once a day (need wallet restart)
is that a setting mistake by computer (i tripple checked that 'never fall asleep')
or in the wallet ?
(bummer as i would love to have this run without checking - specially when on the road )

I am trying to create a masternode, and I have followed the directions in the initial thread post, however trying to run darknet-cli master node start I get the following:

error: {code":-32601, "message": method not found"}

I have already created the masternode address and funded it with the 10k coins (exactly). If I try to run the master node start command before the wallet has started I get a different address. Is starting the master node like this even necessary ?

I am brand new to the coin so this is my first experience(s) with it.

tx guys
 

Edit:
how do i fix this ?
"The transaction was rejected! This might happen ... coins already spent ...
If u use a copy of wallet.dat and coins were spend in copy but not marked as spend but here"

why isnt it updated - i do not understand 

i am on the newest wallet v2.1.2.1 / Mac
downloaded and updated (blockchain ) everything fresh
am staking since 3+ hours (all green and unlocked) but ZERO payments ?!?

what am i doing wrong ?

Where are we on this issue of votes? Is Github financed by us already? And about jakiman communication operations? Would be nice to use those coins... who controls them in the meantime?

Hello, It's not clear to me what you mean by having many smaller inputs. Is it to have a wallet.dat with different addresses with each one 2k-5k? Or one single address with everything on it? I think it's the first one. However I don't understand the logic behind it. Could you please explain a little bit more on that?