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

tertius993

hero member

Activity: 1029

Merit: 712

Quote from: staycrypto on March 16, 2014, 01:45:07 PM

One of the issues we are seeing is that there are a lot of chain reorganizations happening, until it smooths out and all of the blocks are reprocessed it causes a lot of resource contention with the bdb database. Creating a file named DB_CONFIG in the version data dir with these contents alleviated the issue on the seed nodes:

Code:

set_lk_max_locks 537000
set_lk_max_objects 537000
set_lg_dir database

I am still looking into improving the performance of RPC calls for the pools and we are contemplating another update to boost the difficulty up faster as it seems to be ramping up but very very slowly.

I appreciate everybody's considerable patience in getting this chain back on the right track.

Thanks for the update.

I think it would help if you could confirm:

a) is it safe for people to continue to use the latest version of the wallet already released?
b) is it OK to continue mining?

cheers

staycrypto

member

Activity: 70

Merit: 10

Crypto Craftsman

One of the issues we are seeing is that there are a lot of chain reorganizations happening, until it smooths out and all of the blocks are reprocessed it causes a lot of resource contention with the bdb database. Creating a file named DB_CONFIG in the version data dir with these contents alleviated the issue on the seed nodes:

Code:

set_lk_max_locks 537000
set_lk_max_objects 537000
set_lg_dir database

I am still looking into improving the performance of RPC calls for the pools and we are contemplating another update to boost the difficulty up faster as it seems to be ramping up but very very slowly.

I appreciate everybody's considerable patience in getting this chain back on the right track.

tertius993

hero member

Activity: 1029

Merit: 712

Quote from: BitcoinFX on March 16, 2014, 12:59:38 PM

Looks like there may need to be another updated wallet release soon ?

v0.8.9.9 appears to of caused a wallet compatibility issue.

I suspect you are correct. I have not upgraded my wallet yet, nor have I opened my wallet since the problems arose a few days ago.

At the moment I am going to hold fire until we know exactly the position.

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Quote from: ralexvalex on March 16, 2014, 01:05:17 PM

Guys, which chain is correct? I got 70200 now.

I have that chain on both of the nodes I posted with around 20 connections on each.

ralexvalex

sr. member

Activity: 256

Merit: 250

Guys, which chain is correct? I got 70200 now.

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Looks like there may need to be another updated wallet release soon ?

v0.8.9.9 appears to of caused a wallet compatibility issue.

damiano

legendary

Activity: 1246

Merit: 1000

103 days, 21 hours and 10 minutes.

Downloaded updated wallet and edited new conf

No luck Angry

No sync

sin242

sr. member

Activity: 280

Merit: 250

Everything i had mined last night is gone. Not sure if i was somehow off on my own fork and it re-corrected or what may have happened
there. Deleted and redownloaded the blocks just in case

Keep in mind in not bitching, just sharing info.

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Quote from: staycrypto on March 16, 2014, 11:48:55 AM

Quote from: BitcoinFX on March 16, 2014, 09:03:49 AM

Its a real shame that Version has had such a problematic start. It has real potential as a great store of value crypto.

It has been very frustrating. Version was intended to be my prized coin. I didn't sleep for many days and I lost my day job because of it.

Quote from: BitcoinFX

Looks as if the blocks are being harvested intentionally again.

Going to have to take a close look at the distribution to continue with this.

Anyone want to try a mod. of p2pool for Version and I'll run it on the nodes I posted above ?

It is not that they are being harvested intentionally, but we have to wait it out for the difficulty to come up to par again.

There were several nested issues as a result of the KGW algorithm:

1. When proof of stake kicked in and PoS blocks started to join the blockchain, the KGW function was not differentiating between PoW and PoS. This was causing the moving average to get dragged down close to the minimum difficulty and the chain to look like it was "kicking over" into min diff repeatedly.

2. Once we solved that, the other issue is that KGW doesn't handle chain stops and starts. What you wind up with is a very long time difference between the last block and the block before it, and it drags the difficulty down as well, like a time warp attack with a very long time warp.

So, I put in a switch to get us out of KGW and onto the "normal" calculation. Its a simple formula with exponential adjustment, but it will take some time for the difficulty to ramp up to match the hashpower on the network. In the short run it means orphans and the behavior you typically see with a brand new coin lanch, but in the long run it should result in a more stable chain for us.

Indeed. Sorry to hear that you lost your job!

I'll keep my nodes up and watch the chain. Not sure that everything is 100% though, however the network does seem to be becoming more stable. Had to re-sync / restart a couple of times.

bittymymitty

newbie

Activity: 55

Merit: 0

Quote from: staycrypto on March 16, 2014, 11:48:55 AM

Quote from: BitcoinFX on March 16, 2014, 09:03:49 AM

Its a real shame that Version has had such a problematic start. It has real potential as a great store of value crypto.

It has been very frustrating. Version was intended to be my prized coin. I didn't sleep for many days and I lost my day job because of it.

Quote from: BitcoinFX

Looks as if the blocks are being harvested intentionally again.

Going to have to take a close look at the distribution to continue with this.

Anyone want to try a mod. of p2pool for Version and I'll run it on the nodes I posted above ?

It is not that they are being harvested intentionally, but we have to wait it out for the difficulty to come up to par again.

There were several nested issues as a result of the KGW algorithm:

1. When proof of stake kicked in and PoS blocks started to join the blockchain, the KGW function was not differentiating between PoW and PoS. This was causing the moving average to get dragged down close to the minimum difficulty and the chain to look like it was "kicking over" into min diff repeatedly.

2. Once we solved that, the other issue is that KGW doesn't handle chain stops and starts. What you wind up with is a very long time difference between the last block and the block before it, and it drags the difficulty down as well, like a time warp attack with a very long time warp.

So, I put in a switch to get us out of KGW and onto the "normal" calculation. Its a simple formula with exponential adjustment, but it will take some time for the difficulty to ramp up to match the hashpower on the network. In the short run it means orphans and the behavior you typically see with a brand new coin lanch, but in the long run it should result in a more stable chain for us.

Sorry about your day job, hope things work out in the end. This coin has great potential but seems to be plagued with issues, anyway to pull in dev resources from another PoS coin as a reference to get this guy back on track?

ralexvalex

sr. member

Activity: 256

Merit: 250

So are these blocks we found till now real? Thanks

mindfox

sr. member

Activity: 280

Merit: 250

Donate to put a smile on my face :)

Quote from: staycrypto on March 16, 2014, 11:48:55 AM

Quote from: BitcoinFX on March 16, 2014, 09:03:49 AM

Its a real shame that Version has had such a problematic start. It has real potential as a great store of value crypto.

It has been very frustrating. Version was intended to be my prized coin. I didn't sleep for many days and I lost my day job because of it.

Quote from: BitcoinFX

Looks as if the blocks are being harvested intentionally again.

Going to have to take a close look at the distribution to continue with this.

Anyone want to try a mod. of p2pool for Version and I'll run it on the nodes I posted above ?

It is not that they are being harvested intentionally, but we have to wait it out for the difficulty to come up to par again.

There were several nested issues as a result of the KGW algorithm:

1. When proof of stake kicked in and PoS blocks started to join the blockchain, the KGW function was not differentiating between PoW and PoS. This was causing the moving average to get dragged down close to the minimum difficulty and the chain to look like it was "kicking over" into min diff repeatedly.

2. Once we solved that, the other issue is that KGW doesn't handle chain stops and starts. What you wind up with is a very long time difference between the last block and the block before it, and it drags the difficulty down as well, like a time warp attack with a very long time warp.

So, I put in a switch to get us out of KGW and onto the "normal" calculation. Its a simple formula with exponential adjustment, but it will take some time for the difficulty to ramp up to match the hashpower on the network. In the short run it means orphans and the behavior you typically see with a brand new coin lanch, but in the long run it should result in a more stable chain for us.

True, but there are other issues as well.
Get online so we can talk

staycrypto

member

Activity: 70

Merit: 10

Crypto Craftsman

Quote from: BitcoinFX on March 16, 2014, 09:03:49 AM

Its a real shame that Version has had such a problematic start. It has real potential as a great store of value crypto.

It has been very frustrating. Version was intended to be my prized coin. I didn't sleep for many days and I lost my day job because of it.

Quote from: BitcoinFX

Looks as if the blocks are being harvested intentionally again.

Going to have to take a close look at the distribution to continue with this.

Anyone want to try a mod. of p2pool for Version and I'll run it on the nodes I posted above ?

It is not that they are being harvested intentionally, but we have to wait it out for the difficulty to come up to par again.

There were several nested issues as a result of the KGW algorithm:

1. When proof of stake kicked in and PoS blocks started to join the blockchain, the KGW function was not differentiating between PoW and PoS. This was causing the moving average to get dragged down close to the minimum difficulty and the chain to look like it was "kicking over" into min diff repeatedly.

2. Once we solved that, the other issue is that KGW doesn't handle chain stops and starts. What you wind up with is a very long time difference between the last block and the block before it, and it drags the difficulty down as well, like a time warp attack with a very long time warp.

So, I put in a switch to get us out of KGW and onto the "normal" calculation. Its a simple formula with exponential adjustment, but it will take some time for the difficulty to ramp up to match the hashpower on the network. In the short run it means orphans and the behavior you typically see with a brand new coin lanch, but in the long run it should result in a more stable chain for us.

sx1234

member

Activity: 98

Merit: 10

Quote from: Tigggger on March 16, 2014, 09:43:36 AM

Quote from: sin242 on March 16, 2014, 03:16:55 AM

Quote from: mindfox on March 16, 2014, 03:09:25 AM

Quote from: sin242 on March 16, 2014, 02:45:19 AM

So all my coins went to stake right about the time this for happened. They're no longer in the wallet and didn't come back when i re-opened for minting, are they gone for good?

If those coins were coming from blocks with height number higher than the one that we restarted ( a few hours after the incident happened ), then yes, they are lost, as they were never meant to be created in the manner they did.

No, my original coins which were mined at launch, are gone.

Edit: For clarity, i mined 19 blocks at launch. This was the last one

Have the exact same issue,

Had 1,804 mined from pools well before the problems started. My balance is now showing 0 following the update.

All of them are still in my ledger

Not done downloading the chain yet, but looking at the wallet looks the same.. EXCEPT, it appears it's giving me credit for Stake.. But NONE of the mined coins are showing...

Tigggger

legendary

Activity: 1098

Merit: 1000

Quote from: sin242 on March 16, 2014, 03:16:55 AM

Quote from: mindfox on March 16, 2014, 03:09:25 AM

Quote from: sin242 on March 16, 2014, 02:45:19 AM

So all my coins went to stake right about the time this for happened. They're no longer in the wallet and didn't come back when i re-opened for minting, are they gone for good?

If those coins were coming from blocks with height number higher than the one that we restarted ( a few hours after the incident happened ), then yes, they are lost, as they were never meant to be created in the manner they did.

No, my original coins which were mined at launch, are gone.

Edit: For clarity, i mined 19 blocks at launch. This was the last one

Have the exact same issue,

Had 1,804 mined from pools well before the problems started. My balance is now showing 0 following the update.

All of them are still in my ledger

ralexvalex

sr. member

Activity: 256

Merit: 250

Quote from: Nthused on March 16, 2014, 09:30:33 AM

Actually I think I just jumped onto a Different Chain, Diff 0 (91.4kh/s)

Accepting so many I have my doubts its real....All Orphans...

Happened to me 3 times today. They just disappear and current block goes back to 53k.

Nthused

legendary

Activity: 1554

Merit: 1001

Actually I think I just jumped onto a Different Chain, Diff 0 (91.4kh/s)

Accepting so many I have my doubts its real....All Orphans...

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Quote from: Nthused on March 16, 2014, 09:23:50 AM

No you just have to wait it out with your wallet, Patience....

I had to wait till my Mint by Stake Finally Confirmed aswell.

Yes. It looks like it might of been trying to sync up with the 'old' chain, before the newer consensus kicked in.

-banscore= Threshold for disconnecting misbehaving peers (default: 100)
-bantime= Number of seconds to keep misbehaving peers from reconnecting (default: 86400)

Cool

sx1234

member

Activity: 98

Merit: 10

Guess Zeuspool attempting to fix? Says:

Notice: Undefined offset: 1 in /var/zpanel/hostdata/zadmin/public_html/v_zeuspool_com/include/jsonRPCClient.php on line 142 Notice: Undefined offset: 1 in /var/zpanel/hostdata/zadmin/public_html/v_zeuspool_com/include/jsonRPCClient.php on line 142 Notice: Undefined offset: 1 in /var/zpanel/hostdata/zadmin/public_html/v_zeuspool_com/include/jsonRPCClient.php on line 142

At top of screen now..

Nthused

legendary

Activity: 1554

Merit: 1001

No you just have to wait it out with your wallet, Patience....

I had to wait till my Mint by Stake Finally Confirmed aswell.

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