Too many missed and forked blocks due to new wallet

[Markus]

Restarting my client didn't help. I am slowly dropping though, 39 % now.

[gamey]

So the fork I was on that had 87% initially is steadily dropping.  We're at 56.11 % now.  It would seem the fork resolution code is fubared.  I hope they have enough traces etc to figure out what happened. :(

edit - actually now it is 58%.  I'm looking at it too often and the random noise keeps me from being able to see if it is increasing/decreasing.

[svk]

but how is it possible to be on a 44% paricipation fork and the same time svk is on a chain with 94% participation?   :-\ :-\ :-\

I'm assuming you have stale data from svk.

Exactly.

The upgrade has finished now, I'm currently reindexing blocks to make sure I get the correct missed blocks etc, it'll be back up shortly.

[ripplexiaoshan]

It's getting scary for sure!

"blockchain_average_delegate_participation": "55.49 %",

are some devs watching?

This is actually kind of cool. Seeing what happens at the limits of DPOS. As long as it remains greater than 50%, then in theory the system should work fine (assuming you wait at most 16 minutes to ensure your transaction is in the right fork of the chain). And if it goes below that, you should in theory have enough evidence within 16 minutes to know that your transaction isn't considered valid and you should act as if the network is down (or you are on the minority fork). Of course, I don't know if the client UIs are properly designed to signal this to the user.

In this situation, actually the whole network can be considered as "down", because the exchanges have stopped their fund transferring. And most of the people are too scared to do anything.

[chsln]

Every delegate that didn't upgrade the client yet should do so

https://bitsharestalk.org/index.php?topic=12194.0

[cube]

57+42 = close to 100%.  So the smaller fork is starting to win over delegates?

All exchanges should freeze transactions until the fork issue is resolved.

[gamey]

but how is it possible to be on a 44% paricipation fork and the same time svk is on a chain with 94% participation?   :-\ :-\ :-\

I'm assuming you have stale data from svk.

[chsln]

but how is it possible to be on a 44% paricipation fork and the same time svk is on a chain with 94% participation?   :-\ :-\ :-\

Bitsharesblock is down for upgrade

[liondani]

but how is it possible to be on a 44% paricipation fork and the same time svk is on a chain with 94% participation?   :-\ :-\ :-\

[gamey]

57+42 = close to 100%.  So the smaller fork is starting to win over delegates? 

[liondani]

"blockchain_average_delegate_participation": "42.80 %",
running 25 RC2

should we start panicking?

I assume we are on a fork!
restart your client

http://bitsharesblocks.com/home

[monsterer]

I'm totally unclear on what the correct course of action is.

I'm reporting 0 missed blocks on my v0.4.24.1 build, no crashes, everything *looks* fine. Am I causing forks here, or what?

[gamey]

The wallet I'm using for development (VPS) was at 87% and is now at 57% participation.

[chsln]

I'm running 4GB on v0.4.24.1 and its been fine.

How can I tell if I'm producing forks?

what is your participation rate when you type "info" ?

"blockchain_average_delegate_participation": "45.09 %"

That's the overall average for the entire network, though isn't it?

  "blockchain_average_delegate_participation": "44.10 %",
i think it is the main chain  :-[

I don't tink it is.

My 0.4.25 istance i saying so:

"participation_rate": 57.06214689265537

[liondani]

I am obvious on a fork? Right?