[URGENT] Delegates Please Upgrade to v0.4.26!

[liondani]

looks like svk gives the right data...
http://bitsharesblocks.com/home

[bytemaster]

Code Select Expand


"blockchain_head_block_num": 1247140,
  "blockchain_head_block_age": "3 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T19:17:50",
  "blockchain_average_delegate_participation": "41.06 %"

[bytemaster]

Code Select Expand


  "blockchain_head_block_num": 1247131,
  "blockchain_head_block_age": "5 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T19:15:50",
  "blockchain_average_delegate_participation": "37.27 %"

[kokojie]

Upgraded to 0.4.26

[bytemaster]

Code Select Expand

  "blockchain_head_block_num": 1247102,
  "blockchain_head_block_age": "15 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T19:03:50",
  "blockchain_average_delegate_participation": "33.01 %",


[emski]

when we reach 51% participation I think I open a champaign  :P

  "blockchain_head_block_num": 1247086,
  "blockchain_head_block_age": "4 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T18:58:10",
  "blockchain_average_delegate_participation": "30.15 %",
  "client_version": "v0.4.26",

PS: I think I have something better that I was longing to open for a long time...

[abit]

v0.4.26 has been released with a checkpoint to address the blockchain fork: https://bitsharestalk.org/index.php?topic=7067.msg161432#msg161432

Delegates and seed nodes should upgrade ASAP.

Unable to download the linux binary. Working now.

The windows binary works.

[liondani]

"blockchain_head_block_num": 1247075,
  "blockchain_head_block_age": "42 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T18:52:50",
  "blockchain_average_delegate_participation": "28.29 %",
"client_version": "v0.4.26",

when we reach 51% participation I think I open a champaign  :P

[fluxer555]

Is there any way devs could implement 'naming' of the forks? Something more recognizable than a hash, and something that stays consistent for majority forks. Once a minority fork pops up, it gets a new name.

We could use the names that ElasticSearch uses for naming its run instances:

https://github.com/elasticsearch/elasticsearch/blob/master/src/main/resources/config/names.txt

[emski]

 "blockchain_head_block_num": 1247075,
  "blockchain_head_block_age": "42 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T18:52:50",
  "blockchain_average_delegate_participation": "28.29 %",
"client_version": "v0.4.26",

[liondani]

  "blockchain_head_block_num": 1247043,
  "blockchain_head_block_age": "2 minutes old",
  "blockchain_head_block_timestamp": "2014-12-12T18:38:20",
  "blockchain_average_delegate_participation": "23.11 %"

very helpful to have updates like this every 15 minutes for example to avoid confusion about which chain is the right one.

[emski]

I've upgraded delegates to 0.4.26 (resync blockchain).
I've updated the seed to 0.4.26 (reindexed).
Everything seems OK.

[abit]

My (standby) delegate a.delegate.abit running on v0.4.25-RC1 now..

blockchain_average_delegate_participation 16.64%

is it okay?

Ya. People are slowly switching over.

riverhead-del-server-1 is v0.4.25?

[vikram]

v0.4.26 has been released with a checkpoint to address the blockchain fork: https://bitsharestalk.org/index.php?topic=7067.msg161432#msg161432

Delegates and seed nodes should upgrade ASAP.

[Fox]

Currently building v0.4.26 @ 43%
Currently producing with v0.4.25-RC-2