Topic: 💸  DigiCube  🔷  NOW ON RAWX (NEW MCXNOW)  💸  EARN 50K CUBE/WEEK WITH TWITTER! - page 70. (Read 460478 times)

Then it is good.

Depends on stake rate. If you get a 500% rate, you need a lot less time than if you were going to hit a 1%

It's impossible to predict what you will receive until time of stake. Therefore, it might be best to just use one giant input if that amount can make you stake higher than the maximum reward per block

The idea sound good but how will that bring new investors.?

So how long do I need to keep the wallet locked with 2.2M blocks?

Basically, you need to stake above the maximum reward possible to get a positive stake, which will be squished to the maximum reward. This system is designed to reward large or long holders and punish those trying to stake fast and sell

Needing a much higher coinage than expected. I did not explain it clearly earlier

What are people complaining about?

That said.. changing to a straight coinage-styled system is not hard to do, but please do not take this decision lightly as it requires a LOT of time and work to get all sites and wallets updated and a lot fewer coins will be burned

Correct, I gave a bad explanation of the system. I should have gone in-depth earlier

Hmm.   Reblocked my coins yesterday at 15:10 into 2.2million blocks and turned off staking.   Just got in, turned on staking (it's 17:00 here)  and BOOOM two blocks staked instantly for -229167, and -229149 cube!   Staking is turned back off as I've lost almost 1/2 million already.   Why did this negative stake with blocks of 2.2million?

Ok, I need to do some clarifying here. We are going to break down a few lines from this function so I can explain it as clearly as possible




The part that matters is this:




Follow nMinReward back, so we know the value needed to not hit this section:


Original:

Last fork:

This fork:


So now, nMinReward is (nHeight * .11), meaning that in order to stake for a positive amount, the actual stake reward must be higher than 11% of the block number in order to receive a positive stake. The number needed to maintain this amount will be different, based on that input's stake rate. This means that stakes will be hitting the maximum reward

If this system proves to not be as easy to use as intended, we can fork to make it a bit easier later and use a straight coinage-dependent formula. The way this is now designed is made to burn coins as much as possible (at least for a little while so supply gets to a more manageable amount), while still providing incentive (or a chance for incentive). If there is a large percentage of people that prefer a straight coinage-style formula, we can update to that if we have to. However, changing now means inflation will continue, although not as extreme as before

Sorry for the confusion, I could have explained this a little better earlier. It may have been an oversight on my part not to switch formulas right away and keep the new formula based on the old stake rate, but it is what it is. We have a lot of wallets and nodes that need updating if we decide to switch, so please do not take this decision opportunity lightly because it is a lot of work getting everyone everywhere to update

Is it just me or the system is very slow right now? 2 of 6 confirmations in 2 hours

To avoid getting minus stake make sure you have your blocks higher than :

what about this one sir?
Transaction ID: Payment to self that is still unconfirmed for 1 day. Using the address that I posted..
719acc9136c202ebfcc99c1ba49661584cedcc95facf94f1c5905785a82c0b28

It appears to me that the coinage is calculated after minimum stake age is deducted.
so those coins were only 4'36" old

but I cant work out how to get your particular outcome

 int dayWeight = (min((GetAdjustedTime() - nTime) + timeOffset, (int64)STAKE_MAX_AGE) - nStakeMinAge) / 86400;

 uint64 coinAge = max(txOut.nValue * nDayWeight / COIN, (int64)0);

I compile my own wallet, my stakes dont split unless they reach my predefined threshold.

Obviously the cube wallet doesnt like that and Ive dropped over a million even though I followed the staking guide.

Oh well, Im not into manually recombining and I'll have to wear that one. Expensive lesson though. So be it.

it helps to see the minting tab, as it shows how the inputs were split after the stake with their transaction IDs.

Have not moved anything yet, all I have done is lock my wallet so I dont lose more

Screenshotting the minting tab, which is a mess is no help to anyone..

look at the stake input column on this block: http://www.presstab.pw/phpexplorer/CUBE/block.php?height=1000047

2,500,000 exactly

Minted: -250,888.30, 10% of the input size

http://freestaking.com/qt2/

the number under "coin age required"

2M+

Min sum cubes for + stakes?