Hi presstab,
I think I found a display issue with the Staking: I bought & withdrew HYP 11.7. 6:22h UTC (time when the transaction was done, which is the time used for display in the wallet). So they appear ripe now, and the wallet is displaying that it would stake any second now for about a day, incl. displaying a weight in coin control.
However, on 11.7. and 12.7., blocks were slooooow and the transactions were only included in a block on 12.7. in the afternoon.
Since blocks are again slow right now as consequence of being slow 9 days ago, I would have expected them to already stake.
So, now I assume that for staking itself, the timestamp of the block will be used, not the timestamp of the transaction.
In a way this is good, because the transaction timestamp might be faked, but perhaps the GUI should take this into consideration and not suggest them being ripe already?
Kind regards
Mike
It actually does use the transaction time rather than the block time. The question I have and am not exactly sure at the moment is whether the transaction time defaults as the block time.
Here is the timeweight code:
int64 nTimeWeight = min((int64)nTimeTx - txPrev.nTime, (int64)nStakeMaxAge) - nStakeMinAge;
CBigNum bnCoinDayWeight = CBigNum(nValueIn) * nTimeWeight / COIN / (24 * 60 * 60);
Be mindful that there is still a factor of luck involved in the process. You are trying to create a hash that is larger than the kernel hash, and the more coin weight you have the more likely it will be to solve the problem in a timely manner. Just yesterday a member had a block of 7 stake after 20 days.