[ANN] [V] Version - Rare Desirable NO PREMINE Store of Value -->> v0.8.9.9 FIX

[mindfox]

And I really can't do much of anything if I'm not on my developer workstation, where I can debug the code. And the problem is that I won't be able to get to it before a couple of hours...

I can read that the checksum is different that it was supposed to be, but I can't verify the cause without debugging it.
I'm raising hands and waiting for the developer.

Staycrypto, if there's anything I can do to help, pm me.

[staycrypto]

The hardcoded stake modifier checkpoints need to be updated.  I am doing that now.

[wickedsick]

mindfox can you please post your V address? ill send some coins for the help

[mindfox]

mindfox can you please post your V address? ill send some coins for the help

It's VLfAgKgvNBWc9KWVkx7GnQodDYGRUMzcuh
But don't send anything. It's my pleasure to help. Our team in v.zeuspool.com always try to actively help the community , the coin and the dev team).

[wickedsick]

what can i say more...thank you again for helping and supporting V!!

[baddw]

But other coins don't stop block generation when they hit those checkpoints, requiring everybody to download new wallets/daemons in order for the blockchain to continue.

You still got it wrong. It's not the checkpoints that made it stop working. Even if it was due to that fact, the wallet should have start working since there are users (like zeuspool or other wallets) that have updated.
We should be able to go beyond that, but we're not.
The problem is elsewhere. Please let's give some space to the developer to fix this issue.

Ok, so it's not the checkpoint per se, but the block number which corresponds with the checkpoint.  Please excuse my lack of understanding of the distinction.  I am glad that you and staycrypto are on it.  I'm merely here in the peanut gallery.

[mindfox]

But other coins don't stop block generation when they hit those checkpoints, requiring everybody to download new wallets/daemons in order for the blockchain to continue.

You still got it wrong. It's not the checkpoints that made it stop working. Even if it was due to that fact, the wallet should have start working since there are users (like zeuspool or other wallets) that have updated.
We should be able to go beyond that, but we're not.
The problem is elsewhere. Please let's give some space to the developer to fix this issue.

Ok, so it's not the checkpoint per se, but the block number which corresponds with the checkpoint.  Please excuse my lack of understanding of the distinction.  I am glad that you and staycrypto are on it.  I'm merely here in the peanut gallery.

You misunderstood me. I was not being aggressive towards you. I was just trying to explain the developer's view so nobody thinks he made wrong decisions.
I was just in a hurry to dig up the cause of the problem.

I apologize (geez, I do that a lot lately) if I came strong on you.

[bitkokos]

block reward is 4 V
why sometimes it gives more than 4?
here it's 2004  http://revchain.versioncoin.com/block/0000000000015ed9e4b2cee099a7954c7e6eb62f0d60dccf93717e89cf5d385e


edit: I got it. there must be withdrawals, coins sent etc. right?

[ClutchThese]

block reward is 4 V
why sometimes it gives more than 4?
here it's 2004  http://revchain.versioncoin.com/block/0000000000015ed9e4b2cee099a7954c7e6eb62f0d60dccf93717e89cf5d385e


edit: I got it. there must be withdrawals, coins sent etc. right?

block was worth 4. the 2000 was transfered to other addresses as a transaction.

[mindfox]

block reward is 4 V
why sometimes it gives more than 4?
here it's 2004  http://revchain.versioncoin.com/block/0000000000015ed9e4b2cee099a7954c7e6eb62f0d60dccf93717e89cf5d385e

It doesn't. What you see is the total coins transfered with that block. It includes block generation transaction and all the transactions the mining wallet accepted till the time of generation.
When you move coins from your wallet to a destination, these transactions are inserted to the next mined block, if it gets accepted by the mining wallet.
That's what confirmations are. How many blocks generated after your transaction has been accepted by the next mined block.

I hope you get any of this, as English is not my native... (no, I won't apologize again, it's getting really boring )

[baddw]

But other coins don't stop block generation when they hit those checkpoints, requiring everybody to download new wallets/daemons in order for the blockchain to continue.

You still got it wrong. It's not the checkpoints that made it stop working. Even if it was due to that fact, the wallet should have start working since there are users (like zeuspool or other wallets) that have updated.
We should be able to go beyond that, but we're not.
The problem is elsewhere. Please let's give some space to the developer to fix this issue.

Ok, so it's not the checkpoint per se, but the block number which corresponds with the checkpoint.  Please excuse my lack of understanding of the distinction.  I am glad that you and staycrypto are on it.  I'm merely here in the peanut gallery.

You misunderstood me. I was not being aggressive towards you. I was just trying to explain the developer's view so nobody thinks he made wrong decisions.
I was just in a hurry to dig up the cause of the problem.

I apologize (geez, I do that a lot lately) if I came strong on you.

No problem, I understand, and I appreciate both your ability to help the dev as well as to explain things to those of us who don't really understand PoS coins.

[staycrypto]

I've pushed an update to github, if you would like to test it.  I put the hard checkpoint checksum on block 19079, so it will test it at startup.  Will run and package the Windows client build now.

[mindfox]

I'm afraid this doesn't fix the issue.
Block 19079 has already passed the test and since there isn't any rpc command to recheck everything, it will still try to check 19080 block.
I am re-downloading the blockchain to re-test, but I'm afraid this is not a solution.

I'll keep you posted.

[staycrypto]

I'm afraid this doesn't fix the issue.
Block 19079 has already passed the test and since there isn't any rpc command to recheck everything, it will still try to check 19080 block.
I am re-downloading the blockchain to re-test, but I'm afraid this is not a solution.

I'll keep you posted.

Let me know... it shouldn't fail 19080 as there is no hard checkpoint for that block.

I need to update the seed nodes.  Should have that done shortly.

[mindfox]

I'm afraid this doesn't fix the issue.
Block 19079 has already passed the test and since there isn't any rpc command to recheck everything, it will still try to check 19080 block.
I am re-downloading the blockchain to re-test, but I'm afraid this is not a solution.

I'll keep you posted.

Let me know... it shouldn't fail 19080 as there is no hard checkpoint for that block.

I need to update the seed nodes.  Should have that done shortly.

The download of the chain goes very slow now. I'm still at 18040...

[mindfox]

For some reason it's very slow... I'm still at 18119

[staycrypto]

Updated Windows build v0.8.2:

https://mega.co.nz/#!BUtS0DDD!t5-BSGZIDSX8nnMIPN_KwV4ia6i5ttN48rHonuuv6GU

[mindfox]

I forgot to say that I stopped the stratum to our pool while I'm doing this update so we won't have any "accident" and create any fork to the chain.

Users of v.zeuspool.com don't switch pools. We're alive but it's a required action till we make sure that the coin is fixed.

Of course the same should apply to all pools (I hope).

[bitkokos]

updated to 0.8.2 but it's still on 19079
I have the wallet open for 10 minutes.

Anyways, good luck guys.
It's past midnight here. I gotta go sleep

see ya

[staycrypto]

updated to 0.8.2 but it's still on 19079
I have the wallet open for 10 minutes.

Anyways, good luck guys.
It's past midnight here. I gotta go sleep

see ya

Yes, the client won't show network movement until mining resumes, which will hopefully be soon.

I must apologize for missing this pretty trivial bug, I tried to be extremely thorough with the lead up to the V launch, checking and triple checking everything I could think of, and this was a dumb oversight.  Hopefully no more issues following this and we can resume building awareness in the community.