Are the devs aware that the split threshold is set to 50% of the coins total supply?
This high split threshold is also why the coin is seeing only 100 or so blocks/day versus the 1440/day it should be.
I would suggest either lowering the threshold to 500 or implementing the custom threshold code from other coins like hyperstake.
This high split threshold is also why the coin is seeing only 100 or so blocks/day versus the 1440/day it should be.
I would suggest either lowering the threshold to 500 or implementing the custom threshold code from other coins like hyperstake.
Rdyoung, thanks for voicing your concerns about the network. Would you mind dropping a referencing the portion of code where you are think there might be an issue? Ill take a look and review but first Im trying to determine what "split threshold" you're talking about exactly. If there is a problem and it needs to be fixed I can easily add an update to the next wallet release along with some other minor changes being made like 8_bit said.
When you integrated POSv from reddcoin you left the reddcoin code untouched for the split, the split threshold is the size at which the code will split 1 output into 2 when staking. The issue here is that there is only 4.xmillion coin in circulation but the threshold was left at 2million which worked for RDDs billions.
In short the network doesn't have enough inputs trying to stake, therefore there will be times when no inputs are mature enough to stake and no blocks can be staked. It also doesn't matter if someone manually splits up their balance into a bunch of smaller inputs in attempt to push the network, eventually those inputs will get combined into 1 larger block.
Here is the relevant code in wallet.cpp
// we split the coinstake output in two to avoid concentrating
// too many coins in one output. currently almost always split.
unsigned int nStakeSplitAge = 45 * 24 * 60 * 60; // 45 days
// avoid concentrated transactions. on average, each block contains:
// generated interest ~= 27b * 5% / 365 / 1440 ~= 2.5k
// corresponding stake ~= 27b / 365 / 1440 ~= 50k
// optimally each output stakes once every week so 50k * 52 = 2.6m
// but only a fraction of the total money supply is staked on the network
int64 nStakeCombineThreshold = 2000000 * COIN;
I was looking above at the nStakeSplitAge thinking this is what you were referring to... I now see exactly what you're talking about in regards to the math here on the combine threshold. This is something we will for sure fix in the next release, I knew there was a good reason to give us a window to collective user feedback and pull requests from the community before pushing our next wallet. The next changes going in were minor so this gives us an opportunity to do some refactoring and fix some genuine issues in network. Good find, kudos to you Rd.
Glad I could be of help. To be honest though this isn't skill that found this, POTcoin is dealing with the same issue but the devs refuse to release an updated wallet to address it. It took me and a couple of others building out "mega wallets" with a ton of individual addresses to get the network up to speed. Even now if I pull my wallet offline for a day or so the network ends up short on the expected # of blocks.
Listen to this guy he's an official stoner, they will tell you what's up haha! 
