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

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I am at Austin Airport an just realize that I cannot connect to any other port than 80 and 443 .. my machines are still compiling and redownloading the chain .. though I have no chance to switch over to 0.4.26 from 0.4.25-RC2 for quite some hours ...

I hope I will have access to my ssh sessions in LA ..
Anyone can offer a temporary port 80 proxy ssh machine?

0.4.25-RC2 should be fine assuming it is properly connected.
it seems so as I am on the main chain (AFAIK) produce block and have the same participation rate as you have posted earlier .. gonna update to 26 though .. once I am in LA ... hope they have port 22 open via WIFI
yhea .. found an at&t hotstpot that let me connect through 22 .. opened up 80 for ssh and am now again working on the upgrade to 0.4.26 ..
delegate is currently running 26 .. will move it back to the VPS when synced .. backup delegate upgrading atm ..

btw.

Code: [Select]
{
  "blockchain_head_block_num": 1247883,
  "blockchain_head_block_age": "6 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T22:29:10",
  "blockchain_average_delegate_participation": "75.37 %",
  "blockchain_confirmation_requirement": 162,

Offline monsterer

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.

Really? The third update in 24 hours?
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline wackou

However, when I run
Code: [Select]
blockchain_get_delegate_slot_records wackou-delegate it shows that my last block was from 2014-12-12T13:38:10
Sorry, my bad, that's because the default values are
Code: [Select]
blockchain_get_delegate_slot_records wackou-delegate -1000 10and as there were lots of missed blocks, -1000 went way past beyond the usual 10 blocks per delegate to show blocks until "now", so running
Code: [Select]
blockchain_get_delegate_slot_records wackou-delegate -1000 100does the trick. Sorry for the noise  :-[
Please vote for witness wackou! More info at http://digitalgaia.io

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
I am at Austin Airport an just realize that I cannot connect to any other port than 80 and 443 .. my machines are still compiling and redownloading the chain .. though I have no chance to switch over to 0.4.26 from 0.4.25-RC2 for quite some hours ...

I hope I will have access to my ssh sessions in LA ..
Anyone can offer a temporary port 80 proxy ssh machine?

I can give you a ssh connection on 443 port, if send in PM your a ssh public key I give you the details how to connect.
wallet_account_set_approval spartako

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I am at Austin Airport an just realize that I cannot connect to any other port than 80 and 443 .. my machines are still compiling and redownloading the chain .. though I have no chance to switch over to 0.4.26 from 0.4.25-RC2 for quite some hours ...

I hope I will have access to my ssh sessions in LA ..
Anyone can offer a temporary port 80 proxy ssh machine?

0.4.25-RC2 should be fine assuming it is properly connected.
it seems so as I am on the main chain (AFAIK) produce block and have the same participation rate as you have posted earlier .. gonna update to 26 though .. once I am in LA ... hope they have port 22 open via WIFI

Offline bytemaster

I am at Austin Airport an just realize that I cannot connect to any other port than 80 and 443 .. my machines are still compiling and redownloading the chain .. though I have no chance to switch over to 0.4.26 from 0.4.25-RC2 for quite some hours ...

I hope I will have access to my ssh sessions in LA ..
Anyone can offer a temporary port 80 proxy ssh machine?

0.4.25-RC2 should be fine assuming it is properly connected.
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 xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I am at Austin Airport an just realize that I cannot connect to any other port than 80 and 443 .. my machines are still compiling and redownloading the chain .. though I have no chance to switch over to 0.4.26 from 0.4.25-RC2 for quite some hours ...

I hope I will have access to my ssh sessions in LA ..
Anyone can offer a temporary port 80 proxy ssh machine?

Offline wackou

upgraded seed node and delegate to 0.4.26, and producing blocks. There is something weird, though:
I am pretty sure I just produced a block with wackou-delegate, it even came up on bitsharesblocks: http://bitsharesblocks.com/blocks/block?id=1247596

However, when I run
Code: [Select]
blockchain_get_delegate_slot_records wackou-delegate it shows that my last block was from 2014-12-12T13:38:10

What's even weirder, is that this list keeps being updated, but seems to lag ~8h behind the current time. I would have thought that this is a sync issue, or some background indexing, however both my delegate node and my seed node show the exact same list, and they are on different machines. I did follow the same upgrade pattern for both though (0.4.25-RC1 -> 0.4.25 -> 0.4.25-RC2 (resync blockchain) -> 0.4.26), so maybe that's the cause? I'm a bit confused as to what this could be given that my delegate is signing blocks correctly now...  ???
Please vote for witness wackou! More info at http://digitalgaia.io

Offline Fox

Now producing blocks with v0.4.26
Witness: fox

Offline Riverhead

Code: [Select]
{
  "blockchain_head_block_num": 1247432,
  "blockchain_head_block_age": "7 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T20:45:20",
[b]  "blockchain_average_delegate_participation": "70.63 %",
[/b]

It is pleasing to see how fast delegates act in order to restore the network security, isn't it ?
+1

Offline bytemaster

Code: [Select]
{
  "blockchain_head_block_num": 1247432,
  "blockchain_head_block_age": "7 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T20:45:20",
[b]  "blockchain_average_delegate_participation": "70.63 %",
[/b]

It is pleasing to see how fast delegates act in order to restore the network security, isn't it ?

Much more responsive than miners.

Especially true for 100% pay delegates which are losing pay every minute the network is down.
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": 1247432,
  "blockchain_head_block_age": "7 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T20:45:20",
[b]  "blockchain_average_delegate_participation": "70.63 %",
[/b]

It is pleasing to see how fast delegates act in order to restore the network security, isn't it ?

Much more responsive than miners.   
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
Code: [Select]
{
  "blockchain_head_block_num": 1247432,
  "blockchain_head_block_age": "7 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T20:45:20",
[b]  "blockchain_average_delegate_participation": "70.63 %",
[/b]

It is pleasing to see how fast delegates act in order to restore the network security, isn't it ?

Offline bytemaster

Code: [Select]
{
  "blockchain_head_block_num": 1247432,
  "blockchain_head_block_age": "7 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T20:45:20",
[b]  "blockchain_average_delegate_participation": "70.63 %",
[/b]
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 GaltReport

Delegates Upgraded to  0.4.26:

delegate1-galt
delegate1.john-galt