Author Topic: [URGENT] Delegates Please Upgrade to v0.4.26!  (Read 17769 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

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
Downgraded spartako,spartako1,spartako2 to v0.4.25-RC2

Code: [Select]
default (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 1246950,
  "blockchain_head_block_age": "50 seconds old",
  "blockchain_head_block_timestamp": "2014-12-12T17:36:00",
  "blockchain_average_delegate_participation": "5.96 %",
  "blockchain_confirmation_requirement": 303,
  "blockchain_share_supply": "2,498,307,571.05240 BTS",
  "blockchain_blocks_left_in_round": 97,
  "blockchain_next_round_time": "at least 16 minutes in the future",
  "blockchain_next_round_timestamp": "2014-12-12T17:53:00",
  "blockchain_random_seed": "a393f9536da50480dd66e66fe04fe44cdcc1a572",
  "client_data_dir": "/home/spartako/.BitShares",
  "client_version": "v0.4.25-RC2",
  "network_num_connections": 17,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2014-12-12T17:36:50",
  "ntp_time_error": 0.001722,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "17 weeks in the future",
  "wallet_unlocked_until_timestamp": "2015-04-07T11:16:55",
  "wallet_last_scanned_block_timestamp": "2014-07-24T09:23:30",
  "wallet_scan_progress": "? %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "80 seconds in the future",
  "wallet_next_block_production_timestamp": "2014-12-12T17:38:10"
}


Code: [Select]
default (unlocked) >>> get_block 1246470
{
  "previous": "68b7e003ca08d50843faaddcf696cfff1954ede3",
...}

default (unlocked) >>> get_block 1246901
{
  "previous": "b5214c1bc914ea5da6c1bb8f774d07f12b85dbe2",
...}
wallet_account_set_approval spartako

Offline theoretical

is their  an easy way to tell if you are on the right chain/fork?

You can check block hashes like this:

Code: [Select]
>>> get_block 1246470
{
  "previous": "68b7e003ca08d50843faaddcf696cfff1954ede3",

Code: [Select]
>>> get_block 1246901
{
  "previous": "b5214c1bc914ea5da6c1bb8f774d07f12b85dbe2",
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Please lock delegates still on 0.4.25 to help people switch forks faster
Done. I was all happy having made it through the morning's chaos without missing a single block, bye bye 100% reliability!

lol
have you ever seen a top soldier without scars ?


Offline Riverhead

Please lock delegates still on 0.4.25 to help people switch forks faster
Done. I was all happy having made it through the morning's chaos without missing a single block, bye bye 100% reliability!

There wont be a single 100% reliability delegate left now

It'll be like a badge. "Oh, you have 100% reliability? Well, you weren't here for forkfest 2014 noob"

Offline svk

Please lock delegates still on 0.4.25 to help people switch forks faster
Done. I was all happy having made it through the morning's chaos without missing a single block, bye bye 100% reliability!

There wont be a single 100% reliability delegate left now
For sure, I was the only one left on the v25 chain though, haha.
Worker: dev.bitsharesblocks

Offline Riverhead

Please lock delegates still on 0.4.25 to help people switch forks faster
Done. I was all happy having made it through the morning's chaos without missing a single block, bye bye 100% reliability!

You can't tell war stories without a few scars :).

Offline monsterer

Please lock delegates still on 0.4.25 to help people switch forks faster
Done. I was all happy having made it through the morning's chaos without missing a single block, bye bye 100% reliability!

There wont be a single 100% reliability delegate left now
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Please lock delegates still on 0.4.25 to help people switch forks faster

roger

Offline svk

Please lock delegates still on 0.4.25 to help people switch forks faster
Done. I was all happy having made it through the morning's chaos without missing a single block, bye bye 100% reliability!
Worker: dev.bitsharesblocks

Offline GaltReport

I keep getting this repeated (with slightly different numbers):

--- syncing with p2p network, 325689 blocks left to fetch
--- in sync with p2p network

--- syncing with p2p network, 111 blocks left to fetch
--- in sync with p2p network

Is the fork resolution having a bad time?
I am also getting similar....

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
...downgrading to v0.4.25-RC2
it will take a while...

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Please lock delegates still on 0.4.25 to help people switch forks faster
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline monsterer

I keep getting this repeated (with slightly different numbers):

--- syncing with p2p network, 325689 blocks left to fetch
--- in sync with p2p network

--- syncing with p2p network, 111 blocks left to fetch
--- in sync with p2p network

Is the fork resolution having a bad time?

My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline GaltReport

is their  an easy way to tell if you are on the right chain/fork?