You are viewing a single comment's thread from:
RE: testing new payout reward time
These are the results of the test. I did not upvote myeslf immediately.
Payout time was 12 hours. Then I upvoted (with 1%!!!) and payout time changed to 24 hours.
These are the results of the test. I did not upvote myeslf immediately.
Payout time was 12 hours. Then I upvoted (with 1%!!!) and payout time changed to 24 hours.
Good or bad news depending upon your point of view. We were planning on changing it to 24 hours at next hardfork (due to much demand), but delayed. Looks like part of the change escaped review.
"escaped review"? No integration testing? Regression testing? SQA? Surely the deployment/webops team would've caught it? No? Gasps!
let's see what it will give
Is this some unintended side effect of the latest fork?
Yes. Appears so.
Why did the time double when you vote it? o_0
OK so does this mean payout timing changes according to voting?
always has.
OK I never noticed that. So there is no change?
@thecryptofiend The next Hard Fork's was intentionally going to change the voting payout time back to 24 hours from 12. The intentional issue is that somehow in HF 13 which was just rolled out today, the voting payout time starts at 12 hours but was just bumped to 24 hours with an upvote.
Really depending on how you look at it this is either a good or bad thing like @dantheman said. Some people will want their 12 hour payout's but may now have to wait 24 hours, and others will be able to bump the time to a 24 hour payout if they're looking for a larger more immediate payout. The schedule used to be one payout at 12 hours, and one at 30 days but if you check the pay out timer on the post right now it says next payout is in 22 hours.
Regardless, the ability to bump the payout time from 12 to 24 hours was not supposed to work in this fashion and is unintended which is why this test post exists.
@complexring If you could give us an update after the payout cycle ends so we know how it's currently working as of right now, it would be much appreciated. :-)
@alifton OK thanks for the explanation mate! Just realised there was a hard fork when my miner stopped working and had to update it to get it running again. I should probably keep a closer eye on github!