BitShares 2 Release Coordination Thread

[emski]

I've upgraded mine. You can vote it in if needed.

unlocked >>> get_witness emski
get_witness emski
{
  "id": "1.6.36",
  "witness_account": "1.2.5568",
  "last_aslot": 0,
  "signing_key": "BTS5XJa9t218xhUHQNNicGtxix461Ps9mfvHA6kLMoPr95WrfV1zF",
  "vote_id": "1:46",
  "total_votes": "111395992725",
  "url": "",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

[maqifrnswa]

witness maqifrnswa is up to date

[mindphlux]

Witness mindphlux.witness has been updated to the lastest branch and replayed the blockchain.

However, for some reason I have been voted out today suddenly and I do not know the reason why. Please vote me in again @bytemaster so I can continue my contributions and services for the community.

Thanks.

[clayop]

delegate-clayop is updated and replayed the blockchain

[puppies]

updated --replayed switched production to that node and producing blocks

[ElMato]

elmato updated to latest branch "bitshares" and replayed.
(everything works fine)

[dichalcog3nid3]

I need all witnesses to update to the latest *bitshares* branch and replay the blockchain.   Post here after you have done so.

Witness b33lz38v8 has updated and replayed blockchain. I will notify others!

[Thom]

I'm on it, but what for? PM me if necessary.

[bytemaster]

I need all witnesses to update to the latest *bitshares* branch and replay the blockchain.   Post here after you have done so.

[clayop]

If all you were interested in was crash and fork protection you could just load two keys into one config.ini.  Set those as your two public keys in config.py and only run a single witness node with the script.  At this point I wouldn't recommend that.  The script may not work as intended.  I plan on testing it on a single box testnet once I can get some sleep.

I'm interested in this part, fort protection, since last night I have experienced forks two times. What I need is that if fork is detected (witness participation is below a certain level), then terminate witness node and replay the blockchain with the same signing key. I will wait for your newer version. Thanks

[puppies]

@puppies where can I find your failover script?

His script is in a pull request to xeroc's and it is here - https://github.com/xeroc/python-graphenelib/pull/8

Thanks. Do I have to put multiple public/private witness signing keys in config.ini?

You can but thats not really how I envisioned it. 

I have 3 different witness nodes all running a different public private key in their config.ini.  I have the script running on one of those nodes and on a home pc.  If the witness with the active signing key misses a block the script automatically switches to the next signing key, thus switching to the next node.  I am working on improving that with automatic --replay-blockchain after a crash or when witness participation gets to 50%. 

If all you were interested in was crash and fork protection you could just load two keys into one config.ini.  Set those as your two public keys in config.py and only run a single witness node with the script.  At this point I wouldn't recommend that.  The script may not work as intended.  I plan on testing it on a single box testnet once I can get some sleep.

If anyone is running any failover script and has multiple witness nodes ready to produce blocks if their key is set to the signing key, be very very careful.  There is the potential that you could end up producing blocks on 2 forks at the same time.  That would be very bad and could get you fired.  At this early stage in the game there is no replacement for diligence. 

[clayop]

@puppies where can I find your failover script?

His script is in a pull request to xeroc's and it is here - https://github.com/xeroc/python-graphenelib/pull/8

Thanks. Do I have to put multiple public/private witness signing keys in config.ini?

[twitter]

@bytemaster . I checked my witness_node ("id": "1.6.25",)and it is running but for some reason it was out for producing blocks since this morning . am i in another forked chain.....

Code Select Expand

get_witness bue
{
    "id": "1.6.25",
  "witness_account": "1.2.18513",
  "last_aslot": 59851,
  "signing_key": "BTS6pDEnP5iUioSfGECyE84LTM4Z1tN6ySpQhuKroixj5zA8igbxt",
  "pay_vb": "1.13.50",
  "vote_id": "1:35",
  "total_votes": "1340207605570",
  "url": "http://bue.com",
  "total_missed": 26,
  "last_confirmed_block_num": 56354
}

[cube]

@puppies where can I find your failover script?

His script is in a pull request to xeroc's and it is here - https://github.com/xeroc/python-graphenelib/pull/8

[ffwong]

Witness "dragonball" ready to serve the net.    :)
Please give dragonball some votes. Thanks.

get_witness dragonball
{
  "id": "1.6.46",
  "witness_account": "1.2.95289",
  "last_aslot": 0,
  "signing_key": "BTS6R58dMYBsz2WxfFXoq659kTjowRjQRwkDyMwU6QTmRFpBg5Bo3",
  "vote_id": "1:57",
  "total_votes": 0,
  "url": "http://www.dragonball",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}