Author Topic: [URGENT] Delegates Please Upgrade to v0.4.26!  (Read 17763 times)

0 Members and 1 Guest are viewing this topic.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani

Offline bytemaster

Code: [Select]
"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 %"
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

Code: [Select]
  "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 %"
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline kokojie

  • Sr. Member
  • ****
  • Posts: 286
    • View Profile

Offline bytemaster

Code: [Select]
  "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 %",
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
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...

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
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.
BitShares committee member: abit
BitShares witness: in.abit

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: 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

Offline fluxer555

  • Hero Member
  • *****
  • Posts: 749
    • View Profile
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

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
 "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",

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: 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.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I've upgraded delegates to 0.4.26 (resync blockchain).
I've updated the seed to 0.4.26 (reindexed).
Everything seems OK.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
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?
BitShares committee member: abit
BitShares witness: in.abit

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

Offline Fox

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