Are all of them on a fork or just other failure?
oho...
delegate (locked) >>> blockchain_get_security_state
{
"alert_level": "yellow",
"estimated_confirmation_seconds": 10,
"participation_rate": 76.515151515151516
}
not cool
Quote from: xeroc on August 28, 2014, 09:15:00 AM
delegate (locked) >>> blockchain_get_security_state
{
"alert_level": "yellow",
"estimated_confirmation_seconds": 10,
"participation_rate": 76.515151515151516
}
not cool
I'd actually not noticed that command before, thanks for pointing it out! I've added the information there to my website, it will update in real time once per minute. You can find it on the delegates page here:
http://bitsharesblocks.com/#/delegates
Quote from: xeroc on August 28, 2014, 09:15:00 AM
delegate (locked) >>> blockchain_get_security_state
{
"alert_level": "yellow",
"estimated_confirmation_seconds": 10,
"participation_rate": 76.515151515151516
}
not cool
Not surprising just after a fork. Everyone is trying to sync to sync still. Curiously my node server is syncing super fast (30 blocks/sec) but the GUI is quite slow.
Quote from: xeroc on August 28, 2014, 09:15:00 AM
delegate (locked) >>> blockchain_get_security_state
{
"alert_level": "yellow",
"estimated_confirmation_seconds": 10,
"participation_rate": 76.515151515151516
}
not cool
Seems to get better once sync'd.
blockchain_get_security_state
{
"alert_level": "green",
"estimated_confirmation_seconds": 10,
"participation_rate": 94.392523364485982
}