Quote from: mumbly on July 22, 2014, 02:40:23 PM

Quote from: asdf55 on July 21, 2014, 03:27:39 PM

http://hvcstats.com/getnextrewardwhenstr
Returns an estimate of how long until the block reward votes will be tallied (human readable). -Says block change in 19.9 Hours

Not correct. As I mentioned in posts before, block reward will change at block 97200 because last block reward change was at block 93600. That is in ~ 80minutes... So your count is wrong and also wallet count is wrong...

Hey asdf55,

Apologies, I think I missed the meaning of your earlier posts.

Just to let you know, I'm not one of the coin devs but if we identify a legit issue with the wallet I can make sure they take a look at it.

http://hvcstats.com = basically a hosted version of the HVC wallet to expose the API, so if the problem exists with the wallet it'll show up there also.

Could you try explaining the problem and how you have found the potential fault? Just pure maths from the block time, or is there a third party reference we should be looking at?

I took a quick look at these two calls:
http://hvcstats.com/getnextrewardwhensec
http://hvcstats.com/getnextrewardwhenstr

The seconds that the first call returns seem to agree with the second call, so I don't believe that there is a problem converting the seconds to a human readable format.

But also (and I haven't check this in detail) when I looked at http://hvcstats.com/getnextrewardwhensec twice over five minutes it *seemed* like it gained 1000 seconds - not verified, just something I think I noticed.

Does anyone else have an opinion, or otherwise think they can see an issue? If we can identify that there is a problem and how exactly to see it I know it will save the devs a bunch of time debugging the code.

Cheers,
M

EDIT: try this:
- open http://hvcstats.com/getnextrewardwhensec
- wait five minutes, then refresh - it seems like it does add 1000 seconds - is there an explanation or is there a fault here?

http://hvcstats.com/getnextrewardwhensec
http://hvcstats.com/getnextrewardwhenstr

those are not correct, it displays block reward change in about 3hrs from now, but it will not change in 3hrs, because block change was yesterday.

Let me try to explain on this example:

We are now at block ~97860
Block reward changed yestarday at block 97200 (next block reward change is at block 97200+3600=100800)
So instead avereged 3524 should stand avereged 660 (97860-97200)
Insead of When: 3,0 hours should stand When:4,08 days (3600blocks-660blocks=>2940blocks *2minperblock=>5880min /60minper hour=>98hours/24hperday=>4,08days)