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

staycrypto

member

Activity: 70

Merit: 10

Crypto Craftsman

Quote from: filipe3x on March 05, 2014, 05:53:46 PM

I'm on 0.8.2

Quote

"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue."

The network just started moving again. Give it a few minutes to sync, and then close and relaunch the Vault and you should be good.

filipe3x

hero member

Activity: 1008

Merit: 500

I'm on 0.8.2

Quote

"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue."

staycrypto

member

Activity: 70

Merit: 10

Crypto Craftsman

Quote from: bitkokos on March 05, 2014, 05:41:27 PM

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.

bitkokos

hero member

Activity: 490

Merit: 500

0_0

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

mindfox

sr. member

Activity: 280

Merit: 250

Donate to put a smile on my face :)

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).

staycrypto

member

Activity: 70

Merit: 10

Crypto Craftsman

Updated Windows build v0.8.2:

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

mindfox

sr. member

Activity: 280

Merit: 250

Donate to put a smile on my face :)

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

mindfox

sr. member

Activity: 280

Merit: 250

Donate to put a smile on my face :)

Quote from: staycrypto on March 05, 2014, 04:51:54 PM

Quote from: mindfox on March 05, 2014, 04:48:14 PM

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...

staycrypto

member

Activity: 70

Merit: 10

Crypto Craftsman

Quote from: mindfox on March 05, 2014, 04:48:14 PM

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

sr. member

Activity: 280

Merit: 250

Donate to put a smile on my face :)

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

member

Activity: 70

Merit: 10

Crypto Craftsman

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.

baddw

hero member

Activity: 700

Merit: 500

Quote from: mindfox on March 05, 2014, 04:25:09 PM

Quote from: baddw on March 05, 2014, 04:22:13 PM

Quote from: mindfox on March 05, 2014, 03:41:28 PM

Quote from: baddw on March 05, 2014, 03:36:26 PM

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.

mindfox

sr. member

Activity: 280

Merit: 250

Donate to put a smile on my face :)

Quote from: bitkokos on March 05, 2014, 04:28:46 PM

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 Cheesy

)

ClutchThese

sr. member

Activity: 448

Merit: 250

Quote from: bitkokos on March 05, 2014, 04:28:46 PM

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.

bitkokos

hero member

Activity: 490

Merit: 500

0_0

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?

mindfox

sr. member

Activity: 280

Merit: 250

Donate to put a smile on my face :)

Quote from: baddw on March 05, 2014, 04:22:13 PM

Quote from: mindfox on March 05, 2014, 03:41:28 PM

Quote from: baddw on March 05, 2014, 03:36:26 PM

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.

baddw

hero member

Activity: 700

Merit: 500

Quote from: mindfox on March 05, 2014, 03:41:28 PM

Quote from: baddw on March 05, 2014, 03:36:26 PM

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.

wickedsick

sr. member

Activity: 467

Merit: 250

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

mindfox

sr. member

Activity: 280

Merit: 250

Donate to put a smile on my face :)

Quote from: wickedsick on March 05, 2014, 04:11:26 PM

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 Wink

, the coin and the dev team).

wickedsick

sr. member

Activity: 467

Merit: 250

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

Topic: [ANN] [V] Version - Rare Desirable NO PREMINE Store of Value -->> v0.8.9.9 FIX - page 32. (Read 71651 times)