BitShares Forum

Main => General Discussion => Topic started by: bytemaster on October 13, 2015, 03:50:02 pm

Title: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 13, 2015, 03:50:02 pm: This thread is intended to for witnesses and individuals attempting to join the BitShares 2 network.

I have just tagged a pre-release of 2.x

https://github.com/bitshares/bitshares-2/releases/tag/v2.15.286

It has a bundled light wallet for the Mac. No faucets are up and running at this point in time, so this is for importing your keys only. Only advanced users should be joining the network at this point in time.
Title: Re: BitShares 2 Release Coordination Thread
Post by: xeroc on October 13, 2015, 03:53:58 pm: is the genesis block included?!?
//
Quote

Seed nodes and genesis file have been included in the source.
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 13, 2015, 03:54:20 pm: Are you planning to upload Linux binaries? Or we should build by ourselves? If so, any instruction needed?
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 13, 2015, 03:55:12 pm: At last, it is out!
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 13, 2015, 03:57:17 pm: Quote from: xeroc on October 13, 2015, 03:53:58 pm
is the genesis block included?!?
//
Quote

Seed nodes and genesis file have been included in the source.

Yes they are. genesis.json file.
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 13, 2015, 03:57:39 pm: compiling...
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 13, 2015, 03:59:48 pm: Very nice. VPS's already connected. Just waiting on my slow home pc to finish building and I will import balances
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 13, 2015, 04:08:38 pm: Quote from: puppies on October 13, 2015, 03:59:48 pm
Very nice. VPS's already connected. Just waiting on my slow home pc to finish building and I will import balances

Let me know when your witness is ready so I can start voting for them.
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 13, 2015, 04:10:40 pm: Witness bitcube is up. Please vote for bitcube. Thank you!

Code: [Select]
get_witness bitcube { "id": "1.6.12", "witness_account": "1.2.23725",
Title: Re: BitShares 2 Release Coordination Thread
Post by: roadscape on October 13, 2015, 04:14:07 pm: roadscape (1.6.13) is up!
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 13, 2015, 04:14:52 pm: Building...
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 13, 2015, 04:26:47 pm: ETA on windows wallet?
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 13, 2015, 04:28:43 pm: Seed node 128.199.131.4:1777 is up.
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 13, 2015, 04:34:08 pm: 1.6.14 dele-puppy is up and ready to produce blocks

seed node 104.236.144.84:1777 up as well
Title: Re: BitShares 2 Release Coordination Thread
Post by: xeroc on October 13, 2015, 04:38:35 pm: Quote from: puppies on October 13, 2015, 04:34:08 pm
1.6.14 dele-puppy is up and ready to produce blocks

seed node 104.236.144.84:1777 up as well
congratulations!!!! +5%
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 13, 2015, 04:41:36 pm: So far things are running very smoothly.
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 13, 2015, 04:42:27 pm: compiling for " bue "
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 13, 2015, 04:43:37 pm: Quote from: bytemaster on October 13, 2015, 04:41:36 pm
So far things are running very smoothly.

Yes indeed. :)

Is the webwallet still remain at https://graphene.bitshares.org ? It is showing a websocket error.
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 13, 2015, 04:48:52 pm: Alright witness set up on 3 nodes with 3 different keys. Failover script is running. I'm as ready as I can get.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Pheonike on October 13, 2015, 04:50:09 pm: Can the bitshares homepage be updating with a message saying the the transition in progress, please check back today for further instructions or something?
Title: Re: BitShares 2 Release Coordination Thread
Post by: Akado on October 13, 2015, 04:52:36 pm: Quote from: fav on October 13, 2015, 04:26:47 pm
ETA on windows wallet?

+5%
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 13, 2015, 04:57:02 pm: spartako (1.6.15) up ready for producing blocks

Code: [Select]
get_witness spartako { "id": "1.6.15", "witness_account": "1.2.333", "last_aslot": 0, "signing_key": "BTS7qFryjVpfkndAW4siraK1dV4f8gGxRsgnry7ErPFRjirdwVJEG", "vote_id": "1:25", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: Fox on October 13, 2015, 04:57:47 pm: I'm in with Witness ID 1.6.16

Please vote for fox.

EDIT:
Code: [Select]
get_witness fox { "id": "1.6.16", "witness_account": "1.2.167", "last_aslot": 0, "signing_key": "BTS6bcMW7N4dMCYXc8LM9evJ1J2jWCDUFYiW2L1RWHqVxHH3pq2U7", "vote_id": "1:26", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 13, 2015, 04:58:23 pm: Building ...
Title: Re: BitShares 2 Release Coordination Thread
Post by: twentythree on October 13, 2015, 04:59:41 pm: if i understand it correctly 2.0 is complete different ting. but we transfer amount and value of coins with the snapshot.
Title: Re: BitShares 2 Release Coordination Thread
Post by: triox on October 13, 2015, 05:01:00 pm: Seed node 52.28.180.40:35681 up on the production chain.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 13, 2015, 05:03:05 pm: bhuz ready on ID 1.6.17

Code: [Select]
"id": "1.6.17", "witness_account": "1.2.25010", "last_aslot": 0, "signing_key": "BTS6wV9VeA5RabRaQi1Dwn94BcpcYNxZ51XQmJ3NVAdpziZaxffZJ", "vote_id": "1:27", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 13, 2015, 05:06:21 pm: Quote from: triox on October 13, 2015, 05:01:00 pm
Seed node 52.28.180.40:35681 up on the production chain.

can't connect
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 13, 2015, 05:13:38 pm: My seed nodes are up:

23.95.43.126:50696

109.73.172.144:50696
Title: Re: BitShares 2 Release Coordination Thread
Post by: triox on October 13, 2015, 05:18:20 pm: Quote from: fav on October 13, 2015, 05:06:21 pm
Quote from: triox on October 13, 2015, 05:01:00 pm
Seed node 52.28.180.40:35681 up on the production chain.

can't connect

nc -vz 52.28.180.40 35681
Connection to 52.28.180.40 35681 port [tcp/*] succeeded!

weird
Title: Re: BitShares 2 Release Coordination Thread
Post by: mindphlux on October 13, 2015, 05:19:00 pm: Witness mindphlux.witness is ready to produce blocks on the BTS2 mainnet! Please vote.

get_witness mindphlux.witness
{
"id": "1.6.19",
"witness_account": "1.2.91689",
"last_aslot": 0,
"signing_key": "BTS6sAQ7hSXsP76MNyn1K51ATS9EL1ZyGKmcJX28xmZtMByzwz1uh",
"vote_id": "1:29",
"total_votes": 0,
"url": "",
"total_missed": 0,
"last_confirmed_block_num": 0
}

I was on testnet 4,5,6 as a witness with feeds.
Title: Re: BitShares 2 Release Coordination Thread
Post by: ElMato on October 13, 2015, 05:21:22 pm: elmato ready
get_witness elmato
{
"id": "1.6.20",
"witness_account": "1.2.31489",
"last_aslot": 0,
"signing_key": "BTS7TrF5cDX66egLWPLJ7YCnZD5vHeFTgNbPChV8MDQnVKMzDfPrK",
"vote_id": "1:30",
"total_votes": 0,
"url": "http://about:blank",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: wackou on October 13, 2015, 05:22:34 pm: Witness wackou now ready:

Code: [Select]
get_witness wackou { "id": "1.6.18", "witness_account": "1.2.277", "last_aslot": 0, "signing_key": "BTS8C1Cz3LDu732VT74bYvNE2G25NLghV96zcMnFwLd4Z6aXWup9i", "vote_id": "1:28", "total_votes": 0, "url": "http://digitalgaia.io", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 13, 2015, 05:23:34 pm: I just added the Mac OS X full node.
Title: Re: BitShares 2 Release Coordination Thread
Post by: pc on October 13, 2015, 05:29:21 pm: My witness is up and running. Please vote.

Code: [Select]
unlocked >>> get_witness cyrano get_witness cyrano { "id": "1.6.21", "witness_account": "1.2.28788", "last_aslot": 0, "signing_key": "BTS5ARpXg6yWZptHgik721dyXek57v53op6XT7rwTj7Kmb8CGwWEM", "vote_id": "1:31", "total_votes": 0, "url": "http://bts-witness.quisquis.de/", "total_missed": 0, "last_confirmed_block_num": 0 }
(I was on the testnet as "pmc".)
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 13, 2015, 05:36:49 pm: Let us know when we should try some feeds.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 13, 2015, 05:39:48 pm: Quote from: puppies on October 13, 2015, 05:36:49 pm
Let us know when we should try some feeds.

Should we set bter_trust_level = 0 ?
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 13, 2015, 05:42:31 pm: poloniex has managed to claim some of their BTS so that is a good sign :)
Title: Re: BitShares 2 Release Coordination Thread
Post by: Xeldal on October 13, 2015, 05:43:14 pm: Witness up and ready to produce

Code: [Select]
get_witness xeldal { "id": "1.6.22", "witness_account": "1.2.564",
Title: Re: BitShares 2 Release Coordination Thread
Post by: Ander on October 13, 2015, 05:43:32 pm: Quote from: bytemaster on October 13, 2015, 05:42:31 pm
poloniex has managed to claim some of their BTS so that is a good sign :)

Nice, good job guys.

Polo matters the most, and not just because its the one exchange I actually have some BTS on right now. :P
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 13, 2015, 05:44:43 pm: Publish feeds at will. They will not enable the assets until 7 witnesses are publishing.
Title: Re: BitShares 2 Release Coordination Thread
Post by: xeroc on October 13, 2015, 05:48:23 pm: Quote from: bytemaster on October 13, 2015, 05:44:43 pm
Publish feeds at will. They will not enable the assets until 7 witnesses are publishing.
Please MANUALLY CONFIRM CORRECTNESS of the prices derived!!!!!
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 13, 2015, 05:50:15 pm: Quote from: xeroc on October 13, 2015, 05:48:23 pm
Quote from: bytemaster on October 13, 2015, 05:44:43 pm
Publish feeds at will. They will not enable the assets until 7 witnesses are publishing.
Please MANUALLY CONFIRM CORRECTNESS of the prices derived!!!!!

Shouldn't we set bter_trust_level to 0 ? bter didn't honored bts 2
Title: Re: BitShares 2 Release Coordination Thread
Post by: cybermonetarist on October 13, 2015, 06:00:52 pm: Quote from: bytemaster on October 13, 2015, 05:23:34 pm
I just added the Mac OS X full node.
Works very fast.
Sync - works
Create new account - doesn't works
Import - doesn't works
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 13, 2015, 06:01:43 pm: Plese vote for spartako, I'm in the active witness list but I have 0 votes ???

I just voted for all witness that are here

Edit: Now I have votes, thanks!
Title: Re: BitShares 2 Release Coordination Thread
Post by: Ander on October 13, 2015, 06:02:11 pm: Quote from: Bhuz on October 13, 2015, 05:50:15 pm
Quote from: xeroc on October 13, 2015, 05:48:23 pm
Quote from: bytemaster on October 13, 2015, 05:44:43 pm
Publish feeds at will. They will not enable the assets until 7 witnesses are publishing.
Please MANUALLY CONFIRM CORRECTNESS of the prices derived!!!!!

Shouldn't we set bter_trust_level to 0 ? bter didn't honored bts 2

I dont think bter should be included at all in feeds. The bter price could hit zero easily and mess things up.
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 13, 2015, 06:07:04 pm: bue is up running .... +5%

Code: [Select]
get_witness bue { "id": "1.6.25", "witness_account": "1.2.18513", "last_aslot": 0, "signing_key": "BTS6pDEnP5iUioSfGECyE84LTM4Z1tN6ySpQhuKroixj5zA8igbxt", "vote_id": "1:35", "total_votes": 0, "url": "http://bue.com", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 13, 2015, 06:07:17 pm: Quote from: Ander on October 13, 2015, 06:02:11 pm
Quote from: Bhuz on October 13, 2015, 05:50:15 pm
Quote from: xeroc on October 13, 2015, 05:48:23 pm
Quote from: bytemaster on October 13, 2015, 05:44:43 pm
Publish feeds at will. They will not enable the assets until 7 witnesses are publishing.
Please MANUALLY CONFIRM CORRECTNESS of the prices derived!!!!!

Shouldn't we set bter_trust_level to 0 ? bter didn't honored bts 2

I dont think bter should be included at all in feeds. The bter price could hit zero easily and mess things up.

I think that setting bter_trust_level = 0, it will not be included.

@xeroc pls confirm
Title: Re: BitShares 2 Release Coordination Thread
Post by: jsidhu on October 13, 2015, 06:09:16 pm: i couldnt build graphene since i was on 14.04 trusty and i couldnt install gcc 4.9 in time, had to go to work. WIll get to it later.
Title: Re: BitShares 2 Release Coordination Thread
Post by: boombastic on October 13, 2015, 06:11:33 pm: witness mr.agsexplorer is ready, please vote

Code: [Select]
get_witness mr.agsexplorer { "id": "1.6.24", "witness_account": "1.2.10285", "last_aslot": 0, "signing_key": "BTS7yYqVQZ3BB31T2P3Cot4M2Eyxo59aMLhrAvKUi54YWBJcpzAdj", "vote_id": "1:34", "total_votes": 0, "url": "http://agsexplorer", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: Harvey on October 13, 2015, 06:20:19 pm: The witness node "harvey-xts" is up,
please kindly vote :)

Code: [Select]
unlocked >>> get_witness harvey-xts get_witness harvey-xts { "id": "1.6.23", "witness_account": "1.2.3284", "last_aslot": 0, "signing_key": "BTS7V2jfYZEToTjGFndctgTPipMuMcobqzwsd8RQv77c5Vzcexgt6", "vote_id": "1:33", "total_votes": 0, "url": "url-to-proposal", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: theoretical on October 13, 2015, 06:21:59 pm: Quote from: jsidhu on October 13, 2015, 06:09:16 pm
i couldnt build graphene since i was on 14.04 trusty and i couldnt install gcc 4.9 in time, had to go to work. WIll get to it later.

Ubuntu 14.04 is our best supported Linux platform, since that is what I use and I am the only core developer who uses Linux almost exclusively. The compiler I use is

Code: [Select]
$ g++ --version g++ (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4
Title: Re: BitShares 2 Release Coordination Thread
Post by: Ander on October 13, 2015, 06:25:49 pm: Is there a block explorer showing the new chain yet?

Bitsharesblocks looks like its on the old one, it has very low delegate participation.
Title: Re: BitShares 2 Release Coordination Thread
Post by: 21xhipster on October 13, 2015, 06:26:38 pm: I didn't catch how to claim balance from BTS 0.9?
Could somebody explain?
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 13, 2015, 06:27:39 pm: delegate-clayop (1.6.27) is up and running
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 13, 2015, 06:27:44 pm: Quote from: 21xhipster on October 13, 2015, 06:26:38 pm
I didn't catch how to claim balance from BTS 0.9?
Could somebody explain?

you can claim your balances after you imported your keys
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 13, 2015, 06:33:02 pm: witness up and ready

Code: [Select]
get_witness delegate.ihashfury { "id": "1.6.26", "witness_account": "1.2.23043", "last_aslot": 0, "signing_key": "BTS7zkx4GLMZHKHETwJpJHHUuSmbNJt43DhJbyWe5tVAMaDxbeZhd",
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 13, 2015, 06:37:36 pm: bitcube publishing feeds. Now waiting for seven.
Title: Re: BitShares 2 Release Coordination Thread
Post by: jakub on October 13, 2015, 06:40:32 pm: Quote from: 21xhipster on October 13, 2015, 06:26:38 pm
I didn't catch how to claim balance from BTS 0.9?
Could somebody explain?
http://docs.bitshares.eu/migration/index.html
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 13, 2015, 06:43:27 pm: Can someone update language translations?
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 13, 2015, 06:48:30 pm: I put bter_trust_level = 0, publishing feeds
Title: Re: BitShares 2 Release Coordination Thread
Post by: xeroc on October 13, 2015, 06:54:49 pm: Quote from: Bhuz on October 13, 2015, 06:48:30 pm
I put bter_trust_level = 0, publishing feeds
Sorry .. that is not enough to exclude bter .. you need to remove the line in the last thirs of the code that has fetch_from_bter and threading in it

Sorry i cant push a commit just now .. first thing to happen tomorrow
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 13, 2015, 06:56:00 pm: https://bitshares.openledger.info/
Title: Re: BitShares 2 Release Coordination Thread
Post by: maqifrnswa on October 13, 2015, 06:57:27 pm: The normal PPA is updated:

Code: [Select]
sudo apt-add-repository ppa:showard314/bitshares sudo apt-get update
the new package name is bitshares2-cli and will install cli_wallet and witness node. People can have both bitshares-cli and bitshares2-cli installed at the same time (for wallet transferring)

Code: [Select]
sudo apt-get install bitshares2-cli
It is only for vivid and wily, if your vps is trusty will will have to upgrade (too many dependencies for me to backport)

electron light client will be coming later today ("bitshares2")
Title: Re: BitShares 2 Release Coordination Thread
Post by: lafona on October 13, 2015, 06:58:10 pm: Sorry I'm late to the party but delegate-1.lafona is up and ready to be voted in. Thanks
Code: [Select]
get_witness delegate-1.lafona { "id": "1.6.28", "witness_account": "1.2.30889", "last_aslot": 0, "signing_key": "BTS4wFCDYZ1GFWU5aYEPnVnMFUAHHfMv8ysZngScxo5jKVg9EHW2C", "vote_id": "1:38", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0
Title: Re: BitShares 2 Release Coordination Thread
Post by: 21xhipster on October 13, 2015, 06:58:59 pm: Quote from: jakub on October 13, 2015, 06:40:32 pm
Quote from: 21xhipster on October 13, 2015, 06:26:38 pm
I didn't catch how to claim balance from BTS 0.9?
Could somebody explain?
http://docs.bitshares.eu/migration/index.html
Thanks! Import Keys, but not Restore Backup...
Title: Re: BitShares 2 Release Coordination Thread
Post by: boombastic on October 13, 2015, 07:01:54 pm: Quote from: bytemaster on October 13, 2015, 06:56:00 pm
https://bitshares.openledger.info/

Code: [Select]
Mixed Content: The page at 'https://bitshares.openledger.info/#/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://bitshares.openledger.info/ws'. This request has been blocked; this endpoint must be available over WSS.
They should enable wss to go along with https.
Title: Re: BitShares 2 Release Coordination Thread
Post by: mindphlux on October 13, 2015, 07:05:15 pm: Witness mindphlux.witness is publishing feeds with BTER patched out of pricefeeds.py
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 13, 2015, 07:25:37 pm: Quote from: mindphlux on October 13, 2015, 07:05:15 pm
Witness mindphlux.witness is publishing feeds with BTER patched out of pricefeeds.py

I think we should comment out bittrex and btcavg besides bter.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Tuck Fheman on October 13, 2015, 07:27:47 pm: (http://i.imgur.com/hxnv21T.gif)
Title: Re: BitShares 2 Release Coordination Thread
Post by: CalabiYau on October 13, 2015, 08:32:04 pm: Quote from: Tuck Fheman on October 13, 2015, 07:27:47 pm
(http://i.imgur.com/hxnv21T.gif)

8) COOL 8)
Title: Re: BitShares 2 Release Coordination Thread
Post by: twentythree on October 13, 2015, 08:35:34 pm: i found 27 active witnesses in list but i docent see myself there
Title: Re: BitShares 2 Release Coordination Thread
Post by: triox on October 13, 2015, 08:35:54 pm: Ready to serve the network.

Code: [Select]
get_witness triox-delegate { "id": "1.6.29", "witness_account": "1.2.32321", "last_aslot": 0, "signing_key": "BTS8R6yT22snMyVGXtJkvr9w6kb2uXSbYa3GJzrnHoZN4AmdYBrVD", "vote_id": "1:39", "total_votes": 0, "url": "love", "total_missed": 0, "last_confirmed_block_num": 0 }
Now preparing failover infrastructure.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Spectral on October 13, 2015, 09:14:00 pm: witness spectral is ready, please vote!

Code: [Select]
get_witness spectral { "id": "1.6.30", "witness_account": "1.2.32495", "last_aslot": 0, "signing_key": "BTS8ZWNd9K82gPqKVDbkK8etaYTBMQ3ME3MTQ6HqF586ZbMLrZ5DH", "vote_id": "1:40", "total_votes": "156572592133", "url": "bitspace.no", "total_missed": 0, "last_confirmed_block_num": 0 }
I'm also setting up a seed node which should be ready by tonight.
Title: Re: BitShares 2 Release Coordination Thread
Post by: svk on October 13, 2015, 09:26:40 pm: Quote from: Ander on October 13, 2015, 06:25:49 pm
Is there a block explorer showing the new chain yet?

Bitsharesblocks looks like its on the old one, it has very low delegate participation.
You can always the built-in one. I haven't really had time to upgrade bitsharesblocks so it's staying 0.9x for now.

Left and right arrows should allow you to navigate blocks but it seems to be a little inconsistent, I'll have to add some buttons..
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 13, 2015, 09:40:04 pm: witness bts-bitshares-argentina is ready

{
"id": "1.6.33",
"witness_account": "1.2.89292",
"last_aslot": 0,
"signing_key": "BTS7vyDvX1dxcPvXs63A4cctf8ZFRcb7a3QGWoQYdX6ckuKJonbyx",
"vote_id": "1:43",
"total_votes": 0,
"url": "",
"total_missed": 0,
"last_confirmed_block_num": 0
}

I think I'll change that name to witness.rnglab sometime soon. My other (funded) keys are still being imported. Using that account now because it was already lifetime member.

I had to find that I needed to add the prefix to the account name inside the json file =/
Title: Re: BitShares 2 Release Coordination Thread
Post by: darbon on October 13, 2015, 09:42:37 pm: holytransaction on ID 1.6.32 is up ready for producing blocks

get_witness holytransaction
{
"id": "1.6.32",
"witness_account": "1.2.31965",
"last_aslot": 0,
"signing_key": "BTS8Pr7paLBxGL84YUeA9GdnRHZij1XA1oBPDbvuMRYt12Yx3LTCU",
"vote_id": "1:42",
"total_votes": 0,
"url": "",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: wackou on October 13, 2015, 10:07:32 pm: Seed nodes

seed01.bitsharesnodes.com:1776
seed02.bitsharesnodes.com:1776
seed03.bitsharesnodes.com:1776

are now operational. Getting late for me now, will start publishing feeds tomorrow. Hope I'm going to be able to catch some sleep with all the excitement! :D
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 13, 2015, 10:31:07 pm: I would just like to say spectacular job Dan, and all other devs. Very nice product.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Ander on October 13, 2015, 10:32:29 pm: Quote from: puppies on October 13, 2015, 10:31:07 pm
I would just like to say spectacular job Dan, and all other devs. Very nice product.
+2.0%
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 13, 2015, 10:41:26 pm: Quote from: puppies on October 13, 2015, 10:31:07 pm
I would just like to say spectacular job Dan, and all other devs. Very nice product.
+5%

feeds are up
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 13, 2015, 10:48:41 pm: Quote from: Ander on October 13, 2015, 10:32:29 pm
Quote from: puppies on October 13, 2015, 10:31:07 pm
I would just like to say spectacular job Dan, and all other devs. Very nice product.
+2.0%

+100% (participation rate!)
my admiration for this project and its people is always growing.

dedicated seed node ready at 159.203.101.205:1777

witness producing blocks and feeds, bter excluded.

just my two CORE
Title: Re: BitShares 2 Release Coordination Thread
Post by: abit on October 13, 2015, 10:53:37 pm: in.abit is ready.
Code: [Select]
get_witness in.abit { "id": "1.6.35", "witness_account": "1.2.35248", "last_aslot": 0, "signing_key": "BTS83K3qNNZBRLWMa6pXcwnfMJqC9J46ZpMFEYDKUDCNy2BgNrWth", "vote_id": "1:45", "total_votes": 0, "url": "https://github.com/abitmore", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: alt on October 13, 2015, 11:27:16 pm: delegate.baozi is ready
Code: [Select]
get_witness delegate.baozi { "id": "1.6.37", "witness_account": "1.2.9952", "last_aslot": 0, "signing_key": "BTS7RrZ81Y91hnncYXUoffXaSYipqZHH2USh7mJpBPMNrMXZ5gVQb", "vote_id": "1:47", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: emski on October 13, 2015, 11:29:25 pm: 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": 0,
"url": "",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: CalabiYau on October 14, 2015, 05:25:16 am: Full node is running smoothly all night - really good job !

You guys deliver +5%
Title: Re: BitShares 2 Release Coordination Thread
Post by: mindphlux on October 14, 2015, 05:27:54 am: Witnesses, please post also if you were active on testnet. That will decide my vote. Thanks
Title: Re: BitShares 2 Release Coordination Thread
Post by: taoljj on October 14, 2015, 05:28:43 am: Ready to serve the network.

get_witness delegate.taolje
{
"id": "1.6.38",
"witness_account": "1.2.10091",
"last_aslot": 0,
"signing_key": "BTS6oRYTjcbQU8s9TAtEY4qZknY7Xaw3E29ore3L3xX611KxFE5Nr",
"vote_id": "1:48",
"total_votes": 0,
"url": "url-to-proposal",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 14, 2015, 07:05:34 am: transaction from Lifetime Member don't vest properly and are not paid back...
Title: Re: BitShares 2 Release Coordination Thread
Post by: keewee on October 14, 2015, 07:06:52 am: Quote from: bytemaster on October 13, 2015, 03:50:02 pm
... Only advanced users should be joining the network at this point in time ...

oops... However, the OSX light client is running really well. Connected to the network quickly and I was able to import my 0.9.3c wallet and claim my balance with no major issues
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 14, 2015, 07:08:48 am: Code: [Select]
[{ "id": "1.13.15", "owner": "1.2.1191", "balance": { "amount": 425034686, "asset_id": "1.3.0"looks about right to me fav

Heres fav
Code: [Select]
get_object 2.6.21106 [{ "id": "2.6.21106", "owner": "1.2.21106", "most_recent_op": "2.9.7070", "total_core_in_orders": 0, "lifetime_fees_paid": 12086327, "pending_fees": 0, "pending_vested_fees": 75975 } ] unlocked >>> get_object 1.13.47 get_object 1.13.47 [{ "id": "1.13.47", "owner": "1.2.21106", "balance": { "amount": 9669063, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 7776000, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "75186633888000", "coin_seconds_earned_last_update": "2015-10-14T07:00:00" } ] } ] unlocked >>>
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 14, 2015, 07:09:52 am: Quote from: puppies on October 14, 2015, 07:08:48 am
Code: [Select]
[{ "id": "1.13.15", "owner": "1.2.1191", "balance": { "amount": 425034686, "asset_id": "1.3.0"looks about right to me fav

mh?
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 14, 2015, 07:11:28 am: (http://i.imgur.com/a3ou7fU.png)

80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 14, 2015, 08:47:12 am: Quote from: fav on October 14, 2015, 07:11:28 am
(http://i.imgur.com/a3ou7fU.png)

80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav { ... "cashback_vb": "1.13.52" } get_object 1.13.52 [{ "id": "1.13.52", "owner": "1.2.21106", "balance": { "amount": 9729843, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 7776000, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "75659259168000", "coin_seconds_earned_last_update": "2015-10-14T08:00:00" } ] } ]
Title: Re: BitShares 2 Release Coordination Thread
Post by: noisy on October 14, 2015, 09:10:13 am: https://bitshares.openledger.info/ works ok, but for me https://bitshares.org/wallet/ is not loading at all.

(http://i.imgur.com/n1q90Wz.png)
Title: Re: BitShares 2 Release Coordination Thread
Post by: ncinic on October 14, 2015, 09:16:59 am: same here!
Title: Re: BitShares 2 Release Coordination Thread
Post by: betax on October 14, 2015, 09:53:36 am: I was travelling last night and ran out of battery, always happens :)
Witness ready and separate node on 40.127.190.171:1777

Code: [Select]
get_witness betaxtrade { "id": "1.6.39", "witness_account": "1.2.6956", "last_aslot": 0, "signing_key": "BTS6JhLDwYRKSa7FjEmfhy4VHHMn8SZySc8RJrbc5mWyCvERV3coy", "vote_id": "1:49", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 14, 2015, 11:53:18 am: Quote from: spartako on October 14, 2015, 08:47:12 am
Quote from: fav on October 14, 2015, 07:11:28 am
(http://i.imgur.com/a3ou7fU.png)

80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav { ... "cashback_vb": "1.13.52" } get_object 1.13.52 [{ "id": "1.13.52", "owner": "1.2.21106", "balance": { "amount": 9729843, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 7776000, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "75659259168000", "coin_seconds_earned_last_update": "2015-10-14T08:00:00" } ] } ]

But my balance does not update?
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 14, 2015, 12:32:24 pm: Quote from: fav on October 14, 2015, 11:53:18 am
Quote from: spartako on October 14, 2015, 08:47:12 am
Quote from: fav on October 14, 2015, 07:11:28 am
(http://i.imgur.com/a3ou7fU.png)

80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav { ... "cashback_vb": "1.13.52" } get_object 1.13.52 [{ "id": "1.13.52", "owner": "1.2.21106", "balance": { "amount": 9729843, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 7776000, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "75659259168000", "coin_seconds_earned_last_update": "2015-10-14T08:00:00" } ] } ]

But my balance does not update?

you should give this command:
Code: [Select]
withdraw_vesting "1.13.52" 97 BTS true
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 14, 2015, 01:52:38 pm: Quote from: spartako on October 14, 2015, 12:32:24 pm
Quote from: fav on October 14, 2015, 11:53:18 am
Quote from: spartako on October 14, 2015, 08:47:12 am
Quote from: fav on October 14, 2015, 07:11:28 am
(http://i.imgur.com/a3ou7fU.png)

80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav { ... "cashback_vb": "1.13.52" } get_object 1.13.52 [{ "id": "1.13.52", "owner": "1.2.21106", "balance": { "amount": 9729843, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 7776000, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "75659259168000", "coin_seconds_earned_last_update": "2015-10-14T08:00:00" } ] } ]

But my balance does not update?

you should give this command:
Code: [Select]
withdraw_vesting "1.13.52" 97 BTS true

Is that possible in the win lightwallet or OpenLedger?
Title: Re: BitShares 2 Release Coordination Thread
Post by: xeroc on October 14, 2015, 01:56:54 pm: theoretically it should be able to do so .. the corresponding calls are simply not yet exposed for "easy use" ..
Title: Re: BitShares 2 Release Coordination Thread
Post by: Troglodactyl on October 14, 2015, 02:00:24 pm: Quote from: fav on October 14, 2015, 01:52:38 pm
Quote from: spartako on October 14, 2015, 12:32:24 pm
Quote from: fav on October 14, 2015, 11:53:18 am
Quote from: spartako on October 14, 2015, 08:47:12 am
Quote from: fav on October 14, 2015, 07:11:28 am
(http://i.imgur.com/a3ou7fU.png)

80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav { ... "cashback_vb": "1.13.52" } get_object 1.13.52 [{ "id": "1.13.52", "owner": "1.2.21106", "balance": { "amount": 9729843, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 7776000, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "75659259168000", "coin_seconds_earned_last_update": "2015-10-14T08:00:00" } ] } ]

But my balance does not update?

you should give this command:
Code: [Select]
withdraw_vesting "1.13.52" 97 BTS true

Is that possible in the win lightwallet or OpenLedger?
Does it show up in wallet settings under balance claims?
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 14, 2015, 02:01:18 pm: Quote from: Troglodactyl on October 14, 2015, 02:00:24 pm
Quote from: fav on October 14, 2015, 01:52:38 pm
Quote from: spartako on October 14, 2015, 12:32:24 pm
Quote from: fav on October 14, 2015, 11:53:18 am
Quote from: spartako on October 14, 2015, 08:47:12 am
Quote from: fav on October 14, 2015, 07:11:28 am
(http://i.imgur.com/a3ou7fU.png)

80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav { ... "cashback_vb": "1.13.52" } get_object 1.13.52 [{ "id": "1.13.52", "owner": "1.2.21106", "balance": { "amount": 9729843, "asset_id": "1.3.0" }, "policy": [ 1,{ "vesting_seconds": 7776000, "start_claim": "1970-01-01T00:00:00", "coin_seconds_earned": "75659259168000", "coin_seconds_earned_last_update": "2015-10-14T08:00:00" } ] } ]

But my balance does not update?

you should give this command:
Code: [Select]
withdraw_vesting "1.13.52" 97 BTS true

Is that possible in the win lightwallet or OpenLedger?
Does it show up in wallet settings under balance claims?

No
Title: Re: BitShares 2 Release Coordination Thread
Post by: Spectral on October 14, 2015, 02:26:04 pm: Quote from: mindphlux on October 14, 2015, 05:27:54 am
Witnesses, please post also if you were active on testnet. That will decide my vote. Thanks
I was active towards the end of the testnet, and had a witness up with feeds the entire oct5 testnet.

witness spectral (1.6.30)
Title: Re: BitShares 2 Release Coordination Thread
Post by: betax on October 14, 2015, 02:29:34 pm: Quote from: betax on October 14, 2015, 09:53:36 am
I was travelling last night and ran out of battery, always happens :)
Witness ready and separate node on 40.127.190.171:1777

Code: [Select]
get_witness betaxtrade { "id": "1.6.39", "witness_account": "1.2.6956", "last_aslot": 0, "signing_key": "BTS6JhLDwYRKSa7FjEmfhy4VHHMn8SZySc8RJrbc5mWyCvERV3coy", "vote_id": "1:49", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0 }

^^^^ I was active throughout all the testnet :)
Title: Re: BitShares 2 Release Coordination Thread
Post by: Spectral on October 14, 2015, 03:46:42 pm: General question: Where should I post bugs/log files? Is there a "technical" thread after release?
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 14, 2015, 04:24:14 pm: is there a way to see my voting power (+proxies)?
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 14, 2015, 07:31:11 pm: All witnesses may need to replay the blockchain to get back in sync. There seems to be an issue that can cause things to get out of sync.
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 14, 2015, 07:32:13 pm: Quote from: bytemaster on October 14, 2015, 07:31:11 pm
All witnesses may need to replay the blockchain to get back in sync. There seems to be an issue that can cause things to get out of sync.

Is replay enough? or do we need to resync?
Title: Re: BitShares 2 Release Coordination Thread
Post by: Spectral on October 14, 2015, 08:14:21 pm: Quote from: bytemaster on October 14, 2015, 07:31:11 pm
All witnesses may need to replay the blockchain to get back in sync. There seems to be an issue that can cause things to get out of sync.

Done. Deleted folder object_database and config folder, and restarted. Now syncing nicely.

My witness also crashed earlier today (around 14:00 UTC) and I had to do the same thing. Here is a log (https://drive.google.com/open?id=0BzEEZBS7b6xPaHhkdGVzcVkzbGs)of the event in case it is useful.

Previously I didn't have to restart my seed node, but this time it was necessary. Please ask for more logs if needed.

witness spectral is synced again and ready (but needs votes! :) )
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 14, 2015, 08:15:38 pm: Quote from: Spectral on October 14, 2015, 08:14:21 pm
Quote from: bytemaster on October 14, 2015, 07:31:11 pm
All witnesses may need to replay the blockchain to get back in sync. There seems to be an issue that can cause things to get out of sync.

Done. Deleted folder object_database and config folder, and restarted. Now syncing nicely.

My witness also crashed earlier today (around 14:00 UTC) and I had to do the same thing. Here is a log (https://drive.google.com/open?id=0BzEEZBS7b6xPaHhkdGVzcVkzbGs)of the event in case it is useful.

Previously I didn't have to restart my seed node, but this time it was necessary. Please ask for more logs if needed.

witness spectral is synced again and ready (but needs votes! :) )

Voted!
Title: Re: BitShares 2 Release Coordination Thread
Post by: betax on October 14, 2015, 08:25:35 pm: Quote from: betax on October 14, 2015, 09:53:36 am
I was travelling last night and ran out of battery, always happens :)
Witness ready and separate node on 40.127.190.171:1777

Code: [Select]
get_witness betaxtrade { "id": "1.6.39", "witness_account": "1.2.6956", "last_aslot": 0, "signing_key": "BTS6JhLDwYRKSa7FjEmfhy4VHHMn8SZySc8RJrbc5mWyCvERV3coy", "vote_id": "1:49", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0 }

@bytemaster, needs some votes too...
Title: Re: BitShares 2 Release Coordination Thread
Post by: abit on October 14, 2015, 08:26:25 pm: looks like my witness in.abit is still in sync, haven't been voted in though, do I need to restart or replay?
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 14, 2015, 08:28:46 pm: Quote from: abit on October 14, 2015, 08:26:25 pm
looks like my witness in.abit is still in sync, haven't been voted in though, do I need to restart or replay?

If you are still in sync you should be ok.
Title: Re: BitShares 2 Release Coordination Thread
Post by: betax on October 14, 2015, 09:01:50 pm: Quote from: abit on October 14, 2015, 08:26:25 pm
looks like my witness in.abit is still in sync, haven't been voted in though, do I need to restart or replay?

you are in now
Title: Re: BitShares 2 Release Coordination Thread
Post by: maqifrnswa on October 14, 2015, 09:43:54 pm: my witness is up for as long as it is needed. I helped testing on testnet.
I was a little delayed getting it up, was checking and double checking the ubuntu linux builds. Both the light wallet and CLI is working well over there for the past day.

Code: [Select]
get_witness maqifrnswa { "id": "1.6.43", "witness_account": "1.2.6004", "last_aslot": 0, "signing_key": "BTS61sn4chv5XVwEEbkmU3V7atoHcfuRfdwKjaeTNEsaXSLQgNCcm", "vote_id": "1:54", "total_votes": 0, "url": "", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: Riverhead on October 14, 2015, 09:49:15 pm: Back in sync. I was worried about the --replay-blockchain but it replayed it in about 10 seconds. Wow.
Title: Re: BitShares 2 Release Coordination Thread
Post by: EkremH on October 14, 2015, 09:55:18 pm: You said: "Seed nodes and genesis file have been included in the source.". I found the genesis.json, but where to find the seed node? As in pre-releases to run witness_node we have to run ./witness_node -d oct5 --genesis-json oct5-genesis.json -s "104.236.51.238:2005", so we need a seed node. Or it works and if we just run ./witness_node ?
Title: Re: BitShares 2 Release Coordination Thread
Post by: lafona on October 14, 2015, 09:58:39 pm: Quote from: EkremH on October 14, 2015, 09:55:18 pm
You said: "Seed nodes and genesis file have been included in the source.". I found the genesis.json, but where to find the seed node? As in pre-releases to run witness_node we have to run ./witness_node -d oct5 --genesis-json oct5-genesis.json -s "104.236.51.238:2005", so we need a seed node. Or it works and if we just run ./witness_node ?

It should work if you just run ./witness_node. You don't have to include the arguments for seed nodes or genesis file. If you already tried running it with the old args, oct5 etc. You may need to run it with --resync-blockchain to get it to remove the files from the old chain.
Title: Re: BitShares 2 Release Coordination Thread
Post by: EkremH on October 14, 2015, 10:36:22 pm: No, oct 5 was just an example. I found at the source the genesis.json, but I could not find seed node ?
Title: Re: BitShares 2 Release Coordination Thread
Post by: dichalcog3nid3 on October 14, 2015, 10:42:39 pm: Guys! Top notch witness b33lz338v8 needs your votes! Many thanks! :D

(http://merkabahnk.io/img/bts/witnesswitness.jpg)
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 14, 2015, 10:56:04 pm: re-syn ing :'(......

DONE!!!

bue need some vote back for servicing network
Title: Re: BitShares 2 Release Coordination Thread
Post by: alt on October 14, 2015, 11:11:19 pm: delegate.baozi in sync, need some vote
Quote from: bytemaster on October 14, 2015, 07:31:11 pm
All witnesses may need to replay the blockchain to get back in sync. There seems to be an issue that can cause things to get out of sync.
Title: Re: BitShares 2 Release Coordination Thread
Post by: maqifrnswa on October 15, 2015, 12:34:54 am: Quote from: EkremH on October 14, 2015, 10:36:22 pm
No, oct 5 was just an example. I found at the source the genesis.json, but I could not find seed node ?

it should find the seed node and use the genesis with no arguments
Code: [Select]
./witness_node
Is supposed to just work, no genesis file or seeds are needed. This is different than the testnet where you had to give it seed nodes and genesis.json.

also, witness maqifrnswa needs votes
Title: Re: BitShares 2 Release Coordination Thread
Post by: taoljj on October 15, 2015, 12:58:44 am: Quote from: bytemaster on October 14, 2015, 07:31:11 pm
All witnesses may need to replay the blockchain to get back in sync. There seems to be an issue that can cause things to get out of sync.

delegate.taolje is syncing nicely now, need some vote for servicing network
Code: [Select]
get_witness delegate.taolje { "id": "1.6.38", "witness_account": "1.2.10091", "last_aslot": 0, "signing_key": "BTS6oRYTjcbQU8s9TAtEY4qZknY7Xaw3E29ore3L3xX611KxFE5Nr", "vote_id": "1:48", "total_votes": 0, "url": "url-to-proposal", "total_missed": 0, "last_confirmed_block_num": 0
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 15, 2015, 01:22:59 am: bue need some vote to be back for servicing network

Code: [Select]
get_witness bue { "id": "1.6.25", "witness_account": "1.2.18513", "last_aslot": 36341, "signing_key": "BTS6pDEnP5iUioSfGECyE84LTM4Z1tN6ySpQhuKroixj5zA8igbxt", "pay_vb": "1.13.50", "vote_id": "1:35", "total_votes": "864423218403", "url": "http://bue.com", "total_missed": 26, "last_confirmed_block_num": 33743 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 15, 2015, 02:38:57 am: witness "1.6.33" is back, sorry for the delay

Update: failover script based on update_witness didn't work because witness_node process died on both servers after the fork. Checking logs now
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 15, 2015, 11:03:42 am: Both witness nodes crashed around 10 minutes after the fork. Seednode also crashed a few minutes later. Each on a different VPS.

Code: [Select]
{"new_block":{"previous":"000084897bc808eea0f1911cac37901486b5f7c6","timestamp":"2015-10-14T19:36:06","witness":"1.6.19","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f162b264a288624d187a02dc21655a3d99add519670b6f094807e873a3c879bca61fb02066f730b8ecaba18ccf01c08e848e5a5f0617c125c6981c31e3c1dfbf3","transactions":[]}} th_a db_block.cpp:191 _push_block 2317366ms th_a fork_database.cpp:51 push_block ] Pushing block to fork database that failed to link: 0000848b0cb606ed5d3eb45e250db0169efe761e, 33931 2317366ms th_a fork_database.cpp:52 push_block ] Head: 33855, 0000843f85f188ee02afcd6bda5e224429c59d5d 2317367ms th_a application.cpp:477 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:72 _push_block {"new_block":{"previous":"0000848a85dd34c82612e01f4544b0ff2a93b00a","timestamp":"2015-10-14T19:36:12","witness":"1.6.1","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f74f7f59213b1a5309d9062f5d5885a0f6d0ab78993acdc3db79eafaa5c423e783e5239ebf0ac8f8f99670e2cdd1240d820ec7e85ee1fc779882612810ee1ad3f","transactions":[]}} th_a db_block.cpp:191 _push_block witness_node: /home/failover/bitshares-2/libraries/net/node.cpp:1605: void graphene::net::detail::node_impl::schedule_peer_for_deletion(const peer_connection_ptr&): Assertion `_closing_connections.find(peer_to_delete) == _closing_connections.end()' failed. Aborted (core dumped)
ulimit set to 0 by default, no core files were saved.
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 15, 2015, 12:35:47 pm: Quote from: rnglab on October 15, 2015, 02:38:57 am
witness "1.6.33" is back, sorry for the delay

Update: failover script based on update_witness didn't work because witness_node process died on both servers after the fork. Checking logs now

My newest version of failover script should restart witness_node and cli_wallet in case of crash, or witness production falling below 50%. Unlock the wallet, and switch signing keys if blocks are missed. The first 3 times it restarts it will attempt a --replay-blockchain to get back on a majority fork. If that doesn't work it will try a --resync-blockchain.

At least thats what I expect it to do. I still need to test it a bit more.
Title: Re: BitShares 2 Release Coordination Thread
Post by: betax on October 15, 2015, 01:03:49 pm: Quote from: puppies on October 15, 2015, 12:35:47 pm
Quote from: rnglab on October 15, 2015, 02:38:57 am
witness "1.6.33" is back, sorry for the delay

Update: failover script based on update_witness didn't work because witness_node process died on both servers after the fork. Checking logs now

My newest version of failover script should restart witness_node and cli_wallet in case of crash, or witness production falling below 50%. Unlock the wallet, and switch signing keys if blocks are missed. The first 3 times it restarts it will attempt a --replay-blockchain to get back on a majority fork. If that doesn't work it will try a --resync-blockchain.

At least thats what I expect it to do. I still need to test it a bit more.

Great ill test it now as I am not in yet ;)
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 15, 2015, 01:29:48 pm: Quote from: puppies on October 15, 2015, 12:35:47 pm
Quote from: rnglab on October 15, 2015, 02:38:57 am
witness "1.6.33" is back, sorry for the delay

Update: failover script based on update_witness didn't work because witness_node process died on both servers after the fork. Checking logs now

My newest version of failover script should restart witness_node and cli_wallet in case of crash, or witness production falling below 50%. Unlock the wallet, and switch signing keys if blocks are missed. The first 3 times it restarts it will attempt a --replay-blockchain to get back on a majority fork. If that doesn't work it will try a --resync-blockchain.

At least thats what I expect it to do. I still need to test it a bit more.

great puppies! that's what we need. I can help testing if you want.
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 15, 2015, 01:37:01 pm: I've switched witness account from "1.6.33" "bts-bitshares-argentina" to "1.6.45" "rnglab"

Please downvote bts-bitshares-argentina and vote for rnglab. Thanks

{
"id": "1.6.45",
"witness_account": "1.2.31810",
"last_aslot": 0,
"signing_key": "BTS6zwC6qHhk19WBkEBT5YWAvWXjALnSTyTRTBXvSAZujckX2JSaZ",
"vote_id": "1:56",
"total_votes": 0,
"url": "",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 15, 2015, 02:31:09 pm: Thanks betax and rng. Be careful. I forgot to mention the first thing it will do is kill any running witness_node on your box so that it can start a new one in a screen called witness. I would not suggest running it on your main production witness until it has been much more thoroughly tested.
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 15, 2015, 03:26:46 pm: Quote from: puppies on October 15, 2015, 02:31:09 pm
I would not suggest running it on your main production witness until it has been much more thoroughly tested.

Thanks for the great work and +5% for the responsible caution statement.
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 15, 2015, 03:35:11 pm: @bytemaster "bue " need your vote to back to service . Thanks

Code: [Select]
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 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 15, 2015, 03:52:48 pm: Quote from: puppies on October 15, 2015, 02:31:09 pm
Thanks betax and rng. Be careful. I forgot to mention the first thing it will do is kill any running witness_node on your box so that it can start a new one in a screen called witness. I would not suggest running it on your main production witness until it has been much more thoroughly tested.

Thanks puppies, I'll help testing. It seems that you also improved fork detection : )
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 15, 2015, 04:55:25 pm: @puppies where can I find your failover script?
Title: Re: BitShares 2 Release Coordination Thread
Post by: ffwong on October 15, 2015, 05:02:20 pm: Witness "dragonball" ready to serve the net. :)
Please give dragonball some votes. Thanks.

Quote
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
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 15, 2015, 05:05:47 pm: Quote from: clayop on October 15, 2015, 04:55:25 pm
@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
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 15, 2015, 05:20:15 pm: @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]
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 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 15, 2015, 05:39:47 pm: Quote from: cube on October 15, 2015, 05:05:47 pm
Quote from: clayop on October 15, 2015, 04:55:25 pm
@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?
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 15, 2015, 06:03:43 pm: Quote from: clayop on October 15, 2015, 05:39:47 pm
Quote from: cube on October 15, 2015, 05:05:47 pm
Quote from: clayop on October 15, 2015, 04:55:25 pm
@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.
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 15, 2015, 06:31:12 pm: Quote from: puppies on October 15, 2015, 06:03:43 pm
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
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 15, 2015, 06:45:20 pm: I need all witnesses to update to the latest *bitshares* branch and replay the blockchain. Post here after you have done so.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Thom on October 15, 2015, 06:47:38 pm: I'm on it, but what for? PM me if necessary.
Title: Re: BitShares 2 Release Coordination Thread
Post by: dichalcog3nid3 on October 15, 2015, 07:15:13 pm: Quote from: bytemaster on October 15, 2015, 06:45:20 pm
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!
Title: Re: BitShares 2 Release Coordination Thread
Post by: ElMato on October 15, 2015, 07:26:54 pm: elmato updated to latest branch "bitshares" and replayed.
(everything works fine)
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 15, 2015, 07:38:54 pm: updated --replayed switched production to that node and producing blocks
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 15, 2015, 07:51:02 pm: delegate-clayop is updated and replayed the blockchain
Title: Re: BitShares 2 Release Coordination Thread
Post by: mindphlux on October 15, 2015, 07:54:51 pm: 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.
Title: Re: BitShares 2 Release Coordination Thread
Post by: maqifrnswa on October 15, 2015, 07:55:33 pm: witness maqifrnswa is up to date
Title: Re: BitShares 2 Release Coordination Thread
Post by: emski on October 15, 2015, 08:01:52 pm: 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
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: abit on October 15, 2015, 08:03:46 pm: Quote from: bytemaster on October 15, 2015, 06:45:20 pm
I need all witnesses to update to the latest *bitshares* branch and replay the blockchain. Post here after you have done so.
~~compiling.~~ in.abit updated.
Why not make a new tag as "a new versioning system"?
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 15, 2015, 08:07:16 pm: Building
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 15, 2015, 08:10:04 pm: bitcube is updated to latest.
Title: Re: BitShares 2 Release Coordination Thread
Post by: roadscape on October 15, 2015, 08:10:48 pm: Quote from: bytemaster on October 15, 2015, 06:45:20 pm
I need all witnesses to update to the latest *bitshares* branch and replay the blockchain. Post here after you have done so.

roadscape (1.6.13) is updated but needs more votes!

I seem to have been voted out after the fork yesterday. Had no issues getting back on the main chain with a replay.
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 15, 2015, 08:16:40 pm: rnglab updated and synced

get_witness rnglab
{
"id": "1.6.45",
"witness_account": "1.2.31810",
"last_aslot": 0,
"signing_key": "BTS6zwC6qHhk19WBkEBT5YWAvWXjALnSTyTRTBXvSAZujckX2JSaZ",
"vote_id": "1:56",
"total_votes": 0,
"url": "",
"total_missed": 0,
"last_confirmed_block_num": 0
}

{
"id": "2.1.0",
"head_block_number": 62406,
"head_block_id": "0000f3c607dede3b4ca1015c0f93eb07f5fbf1fb",
"time": "2015-10-15T20:15:42",
"current_witness": "1.6.7",
"next_maintenance_time": "2015-10-15T21:00:00",
"witness_budget": 134850000,
"accounts_registered_this_interval": 3,
"recently_missed_count": 2,
"current_aslot": 66149,
"recent_slots_filled": "329648541687007327326095134548769636347",
"dynamic_flags": 0,
"last_irreversible_block_num": 62386
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 15, 2015, 08:19:12 pm: Quote from: bytemaster on October 15, 2015, 06:45:20 pm
I need all witnesses to update to the latest *bitshares* branch and replay the blockchain. Post here after you have done so.

bhuz updated, replayed and signing
Title: Re: BitShares 2 Release Coordination Thread
Post by: abit on October 15, 2015, 08:20:46 pm: Got an exception while replaying:
Code: [Select]
1152083ms th_a db_update.cpp:180 clear_expired_propos ] Failed to apply proposed transaction on its expirat[31/1873] ting it. {"id":"1.10.1","expiration_time":"2015-10-14T15:29:00","review_period_time":"2015-10-14T14:29:00","proposed_transaction":{"ref_block_n um":0,"ref_block_prefix":0,"expiration":"2015-10-14T15:29:00","operations":[[31,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"new_para meters":{"current_fees":{"parameters":[[0,{"fee":2000000,"price_per_kbyte":1000000}],[1,{"fee":500000}],[2,{"fee":0}],[3,{"fee":200000 0}],[4,{}],[5,{"basic_fee":500000,"premium_fee":200000000,"price_per_kbyte":100000}],[6,{"fee":2000000,"price_per_kbyte":100000}],[7,{ "fee":300000}],[8,{"membership_annual_fee":200000000,"membership_lifetime_fee":1000000000}],[9,{"fee":50000000}],[10,{"symbol3":"50000000000","symbol4":"30000000000","long_symbol":500000000,"price_per_kbyte":10}],[11,{"fee":50000000,"price_per_kbyte":10}],[12,{"fee":5 0000000}],[13,{"fee":50000000}],[14,{"fee":2000000,"price_per_kbyte":100000}],[15,{"fee":2000000}],[16,{"fee":100000}],[17,{"fee":1000 0000}],[18,{"fee":50000000}],[19,{"fee":100000}],[20,{"fee":500000000}],[21,{"fee":2000000}],[22,{"fee":2000000,"price_per_kbyte":10}],[23,{"fee":100000,"price_per_kbyte":10}],[24,{"fee":100000}],[25,{"fee":100000}],[26,{"fee":2000000}],[27,{"fee":0,"price_per_kbyte": 10}],[28,{"fee":500000000}],[29,{"fee":100000}],[30,{"fee":100000}],[31,{"fee":2000000}],[32,{"fee":500000000}],[33,{"fee":100000}],[34,{"fee":100000}],[35,{"fee":100000,"price_per_kbyte":10}],[36,{"fee":2000000}],[37,{}],[38,{"fee":500000,"price_per_kbyte":10}],[39,{ "fee":500000,"price_per_output":500000}]],"scale":10000},"block_interval":3,"maintenance_interval":3600,"maintenance_skip_slots":3,"committee_proposal_review_period":3600,"maximum_transaction_size":98304,"maximum_block_size":2097152,"maximum_time_until_expiration":864 00,"maximum_proposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_witness_co unt":1001,"maximum_committee_count":1001,"maximum_authority_membership":10,"reserve_percent_of_fee":2000,"network_percent_of_fee":2000 ,"lifetime_referrer_percent_of_fee":3000,"cashback_vesting_period_seconds":7776000,"cashback_vesting_threshold":10000000,"count_non_me mber_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":150000,"worker_budget_per_day":"50000000000","max_predica te_opcode":1,"fee_liquidation_threshold":10000000,"accounts_per_fee_scale":1000,"account_fee_scale_bitshifts":4,"max_authority_depth": 2,"extensions":[]}}]],"extensions":[]},"required_active_approvals":["1.2.0"],"available_active_approvals":["1.2.90743","1.2.90744","1. 2.90745","1.2.90746","1.2.90747","1.2.90748","1.2.90749","1.2.90750","1.2.90751","1.2.90752"],"required_owner_approvals":[],"available _owner_approvals":[],"available_key_approvals":[]} 10 assert_exception: Assert Exception itr->get_balance() >= -delta: Insufficient Balance: committee-account's balance of 0 BTS is less than required 20 BTS {"a":"committee-account","b":"0 BTS","r":"20 BTS"} th_a db_balance.cpp:70 adjust_balance {"account":"1.2.0","delta":{"amount":-2000000,"asset_id":"1.3.0"}} th_a db_balance.cpp:76 adjust_balanceAnyway it's up
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 15, 2015, 08:24:16 pm: Quote from: abit on October 15, 2015, 08:20:46 pm
Got an exception while replaying:
Code: [Select]
1152083ms th_a db_update.cpp:180 clear_expired_propos ] Failed to apply proposed transaction on its expirat[31/1873] ting it. {"id":"1.10.1","expiration_time":"2015-10-14T15:29:00","review_period_time":"2015-10-14T14:29:00","proposed_transaction":{"ref_block_n um":0,"ref_block_prefix":0,"expiration":"2015-10-14T15:29:00","operations":[[31,{"fee":{"amount":2000000,"asset_id":"1.3.0"},"new_para meters":{"current_fees":{"parameters":[[0,{"fee":2000000,"price_per_kbyte":1000000}],[1,{"fee":500000}],[2,{"fee":0}],[3,{"fee":200000 0}],[4,{}],[5,{"basic_fee":500000,"premium_fee":200000000,"price_per_kbyte":100000}],[6,{"fee":2000000,"price_per_kbyte":100000}],[7,{ "fee":300000}],[8,{"membership_annual_fee":200000000,"membership_lifetime_fee":1000000000}],[9,{"fee":50000000}],[10,{"symbol3":"50000000000","symbol4":"30000000000","long_symbol":500000000,"price_per_kbyte":10}],[11,{"fee":50000000,"price_per_kbyte":10}],[12,{"fee":5 0000000}],[13,{"fee":50000000}],[14,{"fee":2000000,"price_per_kbyte":100000}],[15,{"fee":2000000}],[16,{"fee":100000}],[17,{"fee":1000 0000}],[18,{"fee":50000000}],[19,{"fee":100000}],[20,{"fee":500000000}],[21,{"fee":2000000}],[22,{"fee":2000000,"price_per_kbyte":10}],[23,{"fee":100000,"price_per_kbyte":10}],[24,{"fee":100000}],[25,{"fee":100000}],[26,{"fee":2000000}],[27,{"fee":0,"price_per_kbyte": 10}],[28,{"fee":500000000}],[29,{"fee":100000}],[30,{"fee":100000}],[31,{"fee":2000000}],[32,{"fee":500000000}],[33,{"fee":100000}],[34,{"fee":100000}],[35,{"fee":100000,"price_per_kbyte":10}],[36,{"fee":2000000}],[37,{}],[38,{"fee":500000,"price_per_kbyte":10}],[39,{ "fee":500000,"price_per_output":500000}]],"scale":10000},"block_interval":3,"maintenance_interval":3600,"maintenance_skip_slots":3,"committee_proposal_review_period":3600,"maximum_transaction_size":98304,"maximum_block_size":2097152,"maximum_time_until_expiration":864 00,"maximum_proposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_witness_co unt":1001,"maximum_committee_count":1001,"maximum_authority_membership":10,"reserve_percent_of_fee":2000,"network_percent_of_fee":2000 ,"lifetime_referrer_percent_of_fee":3000,"cashback_vesting_period_seconds":7776000,"cashback_vesting_threshold":10000000,"count_non_me mber_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":150000,"worker_budget_per_day":"50000000000","max_predica te_opcode":1,"fee_liquidation_threshold":10000000,"accounts_per_fee_scale":1000,"account_fee_scale_bitshifts":4,"max_authority_depth": 2,"extensions":[]}}]],"extensions":[]},"required_active_approvals":["1.2.0"],"available_active_approvals":["1.2.90743","1.2.90744","1. 2.90745","1.2.90746","1.2.90747","1.2.90748","1.2.90749","1.2.90750","1.2.90751","1.2.90752"],"required_owner_approvals":[],"available _owner_approvals":[],"available_key_approvals":[]} 10 assert_exception: Assert Exception itr->get_balance() >= -delta: Insufficient Balance: committee-account's balance of 0 BTS is less than required 20 BTS {"a":"committee-account","b":"0 BTS","r":"20 BTS"} th_a db_balance.cpp:70 adjust_balance {"account":"1.2.0","delta":{"amount":-2000000,"asset_id":"1.3.0"}} th_a db_balance.cpp:76 adjust_balanceAnyway it's up

That exception is fine and expected. Just logging for debug purposes. Will probably remove that logging.
Title: Re: BitShares 2 Release Coordination Thread
Post by: triox on October 15, 2015, 08:27:59 pm: triox-delegate updated without missing a block. I love this tech!
Title: Re: BitShares 2 Release Coordination Thread
Post by: Spectral on October 15, 2015, 08:31:00 pm: witness spectral updated

Code: [Select]
$ git describe --tags v2.15.286-36-g66c18c6
Seed node 46.226.12.230:1984 also updated.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Thom on October 15, 2015, 08:31:56 pm: Witness verbaltech2 updated & replayed.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Xeldal on October 15, 2015, 08:36:38 pm: witness xeldal updated and replayed
Title: Re: BitShares 2 Release Coordination Thread
Post by: taoljj on October 15, 2015, 08:38:42 pm: Quote from: bytemaster on October 15, 2015, 06:45:20 pm
I need all witnesses to update to the latest *bitshares* branch and replay the blockchain. Post here after you have done so.

building now.
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 15, 2015, 08:39:59 pm: The reason for the replay was that the asset permissions were initialized incorrectly in genesis (giving their owners no ability to use some of the new features). Fortunately, the change was to re-initialize the genesis which simply increased the permissions and thus didn't require anyone else to change anything.
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 15, 2015, 08:47:10 pm: witness spartako updated and resynced
Title: Re: BitShares 2 Release Coordination Thread
Post by: maqifrnswa on October 15, 2015, 08:47:23 pm: maqifrnswa (1.6.43) is ready if needed but needs to be voted in
Title: Re: BitShares 2 Release Coordination Thread
Post by: wackou on October 15, 2015, 08:54:32 pm: wackou updated and replayed
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 15, 2015, 08:55:35 pm: Witness 'delegate.ihashfury' is updated and has replayed the blockchain
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 15, 2015, 09:06:32 pm: I think I'd rather have two VPS (2 Core 8G ram) with failover script than one higher-end VPS (4 Core 15G ram). Can you advice me?
Title: Re: BitShares 2 Release Coordination Thread
Post by: taoljj on October 15, 2015, 09:06:53 pm: delegate.taolje updated and replayed
Code: [Select]
get_witness delegate.taolje { "id": "1.6.38", "witness_account": "1.2.10091", "last_aslot": 0, "signing_key": "BTS6oRYTjcbQU8s9TAtEY4qZknY7Xaw3E29ore3L3xX611KxFE5Nr", "vote_id": "1:48", "total_votes": 0, "url": "url-to-proposal", "total_missed": 0, "last_confirmed_block_num": 0
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 15, 2015, 09:13:30 pm: Quote from: clayop on October 15, 2015, 09:06:32 pm
I think I'd rather have two VPS (2 Core 8G ram) with failover script than one higher-end VPS (4 Core 15G ram). Can you advice me?

I'm not sure which would be better. They both have advantages and drawbacks. I will help you out either way if you want to use the script. I just want to be clear it is in its very early stages. For example the reset if production falls below 50% has never been tested. I am pretty sure it will work, but I would hate for you to rely on it and be let down.

I'll start with some better documentation in the script thread
Title: Re: BitShares 2 Release Coordination Thread
Post by: Riverhead on October 15, 2015, 09:21:27 pm: Witness candidate riverhead (1.6.31) updated and replayed.

Code: [Select]
{ "id": "1.6.31", "witness_account": "1.2.793", "last_aslot": 28727, "signing_key": "BTS5RbcVRvqJzpeMJPWeNKH4jbFD8qDcTSdsDJLYmKm7bhyGQUQJ9", "pay_vb": "1.13.71", "vote_id": "1:41", "total_votes": "1023678566145", "url": "riverhead.org", "total_missed": 21, "last_confirmed_block_num": 26428 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: darbon on October 15, 2015, 09:27:08 pm: Witness "holytransaction" is updated and has replayed the blockchain

Code: [Select]
{ "id": "1.6.32", "witness_account": "1.2.31965", "last_aslot": 67536, "signing_key": "BTS8Pr7paLBxGL84YUeA9GdnRHZij1XA1oBPDbvuMRYt12Yx3LTCU", "pay_vb": "1.13.96", "vote_id": "1:42", "total_votes": "13435675917246", "url": "", "total_missed": 58, "last_confirmed_block_num": 63781 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 15, 2015, 09:30:11 pm: Quote from: puppies on October 15, 2015, 09:13:30 pm
Quote from: clayop on October 15, 2015, 09:06:32 pm
I think I'd rather have two VPS (2 Core 8G ram) with failover script than one higher-end VPS (4 Core 15G ram). Can you advice me?

I'm not sure which would be better. They both have advantages and drawbacks. I will help you out either way if you want to use the script. I just want to be clear it is in its very early stages. For example the reset if production falls below 50% has never been tested. I am pretty sure it will work, but I would hate for you to rely on it and be let down.

I'll start with some better documentation in the script thread

I think it is worth to keep running a live testnet. Trying your script is probably just one of many benefits.
Title: Re: BitShares 2 Release Coordination Thread
Post by: pollux on October 15, 2015, 09:30:49 pm: Quote from: bytemaster on October 15, 2015, 08:39:59 pm
The reason for the replay was that the asset permissions were initialized incorrectly in genesis (giving their owners no ability to use some of the new features). Fortunately, the change was to re-initialize the genesis which simply increased the permissions and thus didn't require anyone else to change anything.

is the hash of the genesis not included in the chain's merkle tree? Doesn't this suggest that an attacker could misrepresent some genesis properties - lacking provable correctness?
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 15, 2015, 09:39:14 pm: bue "id": "1.6.25" updated ... vote me in

Code: [Select]
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": "1432644270784", "url": "http://bue.com", "total_missed": 26, "last_confirmed_block_num": 56354 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: triox on October 15, 2015, 10:06:12 pm: Quote from: clayop on October 15, 2015, 09:06:32 pm
I think I'd rather have two VPS (2 Core 8G ram) with failover script than one higher-end VPS (4 Core 15G ram). Can you advice me?

Two machines are absolutely the way to go. I've tested various levels and the only thing that additional cores do at this point is slightly faster builds (if you do 'make j4').
Title: Re: BitShares 2 Release Coordination Thread
Post by: pc on October 15, 2015, 10:11:38 pm: cyrano updated and replayed
Title: Re: BitShares 2 Release Coordination Thread
Post by: pc on October 15, 2015, 10:12:32 pm: Quote from: abit on October 15, 2015, 08:03:46 pm
Why not make a new tag as "a new versioning system"?
+1
Title: Re: BitShares 2 Release Coordination Thread
Post by: lafona on October 16, 2015, 01:43:07 am: delegate-1.lafona updated and replayed
Title: Re: BitShares 2 Release Coordination Thread
Post by: BunkerChainLabs-DataSecurityNode on October 16, 2015, 01:51:08 am: Hey everyone,

Sorry for being so late to the party.. just managed to get access to my accounts today and thus able to register my witness.

Updated as of now and needing votes too:

get_witness datasecuritynode
{
"id": "1.6.49",
"witness_account": "1.2.20638",
"last_aslot": 0,
"signing_key": "BTS7K632MCnVdDPsjgVtbibG1fWGUMUMqmyuTvbU1vfYGgn1UH2AB",
"vote_id": "1:60",
"total_votes": 0,
"url": "http://witness.datasecuritynode.com", << coming soon
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: alt on October 16, 2015, 01:53:52 am: delegate.baozi updated and replaced
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 16, 2015, 04:59:20 am: A few minutes ago a witness asked on Telegram why was he missing blocks. I've found that he was getting negative latency's arround -500ms, asked if hi had ntp installed and he didn't. A minute later (and about 15 minutes after he switched to another node and stoped missing blocks) I missed 3 blocks in a row and witness started showing super high latency's from all witnesses (above 200 seconds??), replayed blockchain and started producing again:

Code: [Select]
1125246ms th_a application.cpp:458 handle_block ] Got block: #72017 time: 2015-10-16T04:18:45 latency: 246 ms from: holytransaction irreversible: 71988 (-29) 1128179ms th_a application.cpp:458 handle_block ] Got block: #72018 time: 2015-10-16T04:18:48 latency: 179 ms from: init10 irreversible: 71990 (-28) 1131131ms th_a application.cpp:458 handle_block ] Got block: #72019 time: 2015-10-16T04:18:51 latency: 131 ms from: delegate-1.lafona irreversible: 71991 (-28) 1134292ms th_a application.cpp:458 handle_block ] Got block: #72020 time: 2015-10-16T04:18:54 latency: 292 ms from: bitcube irreversible: 71995 (-25) 1137159ms th_a application.cpp:458 handle_block ] Got block: #72021 time: 2015-10-16T04:18:57 latency: 159 ms from: init3 irreversible: 71996 (-25) 1140059ms th_a application.cpp:458 handle_block ] Got block: #72022 time: 2015-10-16T04:19:00 latency: 59 ms from: s pectral irreversible: 71997 (-25) 1143163ms th_a application.cpp:458 handle_block ] Got block: #72023 time: 2015-10-16T04:19:03 latency: 163 ms from: init6 irreversible: 71998 (-25) 1146460ms th_a application.cpp:458 handle_block ] Got block: #72024 time: 2015-10-16T04:19:06 latency: 460 ms from: delegate-clayop irreversible: 71999 (-25) 1149207ms th_a application.cpp:458 handle_block ] Got block: #72025 time: 2015-10-16T04:19:09 latency: 206 ms from: init7 irreversible: 72000 (-25) 1152026ms th_a application.cpp:458 handle_block ] Got block: #72026 time: 2015-10-16T04:19:12 latency: 26 ms from: s partako irreversible: 72001 (-25) 1155266ms th_a application.cpp:458 handle_block ] Got block: #72027 time: 2015-10-16T04:19:15 latency: 266 ms from: delegated-proof-of-steak irreversible: 72002 (-25) 1158043ms th_a application.cpp:458 handle_block ] Got block: #72028 time: 2015-10-16T04:19:18 latency: 43 ms from: c yrano irreversible: 72003 (-25) 1160989ms th_a application.cpp:458 handle_block ] Got block: #72029 time: 2015-10-16T04:19:21 latency: -10 ms from: riverhead irreversible: 72004 (-25) 1164001ms th_a witness.cpp:179 block_production_loo ] Generated block #72030 with timestamp 2015-10-16T04:19:24 at time 2015-10-16T04:19:24 1167204ms th_a application.cpp:458 handle_block ] Got block: #72031 time: 2015-10-16T04:19:27 latency: 204 ms from: init5 irreversible: 72006 (-25) 1169258ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011944cd05a88b065c97459067e9433cf8a365","00011952892be327107879d8403f9cea3e6a2137","00011959da81c677a2df19da61c6c4aee44f95a4","0001195d1d6ea4375ae4f68399e9df2ed2b61105","0001195f39e0d57cedc4fdca4ad4dfcf585bdd99"] 1170130ms th_a application.cpp:458 handle_block ] Got block: #72032 time: 2015-10-16T04:19:30 latency: 130 ms from: delegate-1.lafona irreversible: 72007 (-25) 1173026ms th_a application.cpp:458 handle_block ] Got block: #72033 time: 2015-10-16T04:19:33 latency: 26 ms from: bhuz irreversible: 72007 (-26) 1176166ms th_a application.cpp:458 handle_block ] Got block: #72034 time: 2015-10-16T04:19:36 latency: 165 ms from: harvey-xts irreversible: 72008 (-26) 1179163ms th_a application.cpp:458 handle_block ] Got block: #72035 time: 2015-10-16T04:19:39 latency: 163 ms from: init2 irreversible: 72008 (-27) 1182153ms th_a application.cpp:458 handle_block ] Got block: #72036 time: 2015-10-16T04:19:42 latency: 153 ms from: init0 irreversible: 72009 (-27) 1185002ms th_a witness.cpp:179 block_production_loo ] Generated block #72037 with timestamp 2015-10-16T04:19:45 at time 2015-10-16T04:19:45 1188022ms th_a application.cpp:458 handle_block ] Got block: #72038 time: 2015-10-16T04:19:48 latency: 22 ms from: mindphlux.witness irreversible: 72010 (-28) 1191282ms th_a application.cpp:458 handle_block ] Got block: #72039 time: 2015-10-16T04:19:51 latency: 282 ms from: bitcube irreversible: 72011 (-28) 1194157ms th_a application.cpp:458 handle_block ] Got block: #72040 time: 2015-10-16T04:19:54 latency: 157 ms from: init3 irreversible: 72011 (-29) 1197042ms th_a application.cpp:458 handle_block ] Got block: #72041 time: 2015-10-16T04:19:57 latency: 42 ms from: cyrano irreversible: 72011 (-30) 1200339ms th_a application.cpp:458 handle_block ] Got block: #72042 time: 2015-10-16T04:20:00 latency: 339 ms from: bue irreversible: 72011 (-31) 1203185ms th_a application.cpp:458 handle_block ] Got block: #72043 time: 2015-10-16T04:20:03 latency: 185 ms from: init10 irreversible: 72012 (-31) 1206022ms th_a application.cpp:458 handle_block ] Got block: #72044 time: 2015-10-16T04:20:06 latency: 22 ms from: wackou irreversible: 72012 (-32) 1209141ms th_a application.cpp:458 handle_block ] Got block: #72045 time: 2015-10-16T04:20:09 latency: 141 ms from: mr.agsexplorer irreversible: 72013 (-32) 1496796ms th_a application.cpp:458 handle_block ] Got block: #72045 time: 2015-10-16T04:20:09 latency: 287796 ms from: mr.agsexplorer irreversible: 72015 (-30) 1496796ms th_a application.cpp:458 handle_block ] Got block: #72045 time: 2015-10-16T04:20:09 latency: 287796 ms from: mr.agsexplorer irreversible: 72015 (-30) 1496796ms th_a application.cpp:458 handle_block ] Got block: #72046 time: 2015-10-16T04:20:12 latency: 284796 ms from: riverhead irreversible: 72015 (-31) 1496797ms th_a application.cpp:458 handle_block ] Got block: #72047 time: 2015-10-16T04:20:15 latency: 281797 ms from: init4 irreversible: 72015 (-32) 1496797ms th_a application.cpp:458 handle_block ] Got block: #72047 time: 2015-10-16T04:20:15 latency: 281797 ms from: init4 irreversible: 72016 (-31) 1496797ms th_a application.cpp:458 handle_block ] Got block: #72047 time: 2015-10-16T04:20:15 latency: 281797 ms from: init4 irreversible: 72016 (-31) 1496798ms th_a application.cpp:507 handle_transaction ] Got 1 transactions from network 1496798ms th_a application.cpp:458 handle_block ] Got block: #72048 time: 2015-10-16T04:20:18 latency: 278798 ms from: delegate-clayop irreversible: 72016 (-32) 1496799ms th_a application.cpp:458 handle_block ] Got block: #72048 time: 2015-10-16T04:20:18 latency: 278799 ms from: delegate-clayop irreversible: 72016 (-32) 1496799ms th_a application.cpp:458 handle_block ] Got block: #72048 time: 2015-10-16T04:20:18 latency: 278799 ms from: delegate-clayop irreversible: 72016 (-32) 1496799ms th_a application.cpp:458 handle_block ] Got block: #72049 time: 2015-10-16T04:20:21 latency: 275799 ms from: init8 irreversible: 72016 (-33) 1496800ms th_a application.cpp:458 handle_block ] Got block: #72049 time: 2015-10-16T04:20:21 latency: 275800 ms from: init8 irreversible: 72017 (-32) 1496800ms th_a application.cpp:458 handle_block ] Got block: #72049 time: 2015-10-16T04:20:21 latency: 275800 ms from: init8 irreversible: 72017 (-32) 1496801ms th_a application.cpp:458 handle_block ] Got block: #72050 time: 2015-10-16T04:20:24 latency: 272801 ms from: triox-delegate irreversible: 72017 (-33) 1496801ms th_a application.cpp:458 handle_block ] Got block: #72051 time: 2015-10-16T04:20:27 latency: 269801 ms from: init6 irreversible: 72022 (-29) 1496802ms th_a application.cpp:458 handle_block ] Got block: #72051 time: 2015-10-16T04:20:27 latency: 269802 ms from: init6 irreversible: 72022 (-29) 1496802ms th_a application.cpp:458 handle_block ] Got block: #72051 time: 2015-10-16T04:20:27 latency: 269802 ms from: init6 irreversible: 72022 (-29) 1496803ms th_a application.cpp:458 handle_block ] Got block: #72052 time: 2015-10-16T04:20:30 latency: 266803 ms from: delegated-proof-of-steak irreversible: 72022 (-30) 1496804ms th_a application.cpp:458 handle_block ] Got block: #72053 time: 2015-10-16T04:20:33 latency: 263804 ms from: dele-puppy irreversible: 72022 (-31) 1496805ms th_a application.cpp:458 handle_block ] Got block: #72053 time: 2015-10-16T04:20:33 latency: 263805 ms from: dele-puppy irreversible: 72025 (-28) 1496805ms th_a application.cpp:458 handle_block ] Got block: #72054 time: 2015-10-16T04:20:36 latency: 260805 ms from: verbaltech2 irreversible: 72025 (-29) 1496806ms th_a application.cpp:458 handle_block ] Got block: #72054 time: 2015-10-16T04:20:36 latency: 260806 ms from: verbaltech2 irreversible: 72026 (-28) 1496806ms th_a application.cpp:458 handle_block ] Got block: #72054 time: 2015-10-16T04:20:36 latency: 260806 ms from: verbaltech2 irreversible: 72026 (-28) 1496806ms th_a application.cpp:458 handle_block ] Got block: #72055 time: 2015-10-16T04:20:39 latency: 257806 ms from: in.abit irreversible: 72026 (-29) 1496807ms th_a application.cpp:458 handle_block ] Got block: #72055 time: 2015-10-16T04:20:39 latency: 257807 ms from: in.abit irreversible: 72031 (-24) 1496807ms th_a application.cpp:458 handle_block ] Got block: #72055 time: 2015-10-16T04:20:39 latency: 257807 ms from: in.abit irreversible: 72031 (-24) 1496807ms th_a application.cpp:458 handle_block ] Got block: #72056 time: 2015-10-16T04:20:42 latency: 254807 ms from: spartako irreversible: 72031 (-25) 1496808ms th_a application.cpp:458 handle_block ] Got block: #72056 time: 2015-10-16T04:20:42 latency: 254808 ms from: spartako irreversible: 72032 (-24) 1496808ms th_a application.cpp:458 handle_block ] Got block: #72056 time: 2015-10-16T04:20:42 latency: 254808 ms from: spartako irreversible: 72032 (-24) 1496808ms th_a application.cpp:458 handle_block ] Got block: #72057 time: 2015-10-16T04:20:45 latency: 251808 ms from: delegate.ihashfury irreversible: 72032 (-25) 1496810ms th_a application.cpp:458 handle_block ] Got block: #72058 time: 2015-10-16T04:20:48 latency: 248810 ms from: maqifrnswa irreversible: 72033 (-25) 1496811ms th_a application.cpp:458 handle_block ] Got block: #72058 time: 2015-10-16T04:20:48 latency: 248811 ms from: maqifrnswa irreversible: 72034 (-24) 1496811ms th_a application.cpp:458 handle_block ] Got block: #72059 time: 2015-10-16T04:20:51 latency: 245811 ms from: roadscape irreversible: 72034 (-25) 1496812ms th_a application.cpp:458 handle_block ] Got block: #72059 time: 2015-10-16T04:20:51 latency: 245812 ms from: roadscape irreversible: 72035 (-24) 1496812ms th_a application.cpp:458 handle_block ] Got block: #72060 time: 2015-10-16T04:20:54 latency: 242812 ms from: elmato irreversible: 72035 (-25) 1496814ms th_a application.cpp:458 handle_block ] Got block: #72060 time: 2015-10-16T04:20:54 latency: 242814 ms from: elmato irreversible: 72036 (-24) 1496814ms th_a application.cpp:458 handle_block ] Got block: #72061 time: 2015-10-16T04:20:57 latency: 239814 ms from: fox irreversible: 72036 (-25) 1496815ms th_a application.cpp:458 handle_block ] Got block: #72062 time: 2015-10-16T04:21:00 latency: 236815 ms from: holytransaction irreversible: 72037 (-25) 1496816ms th_a application.cpp:458 handle_block ] Got block: #72062 time: 2015-10-16T04:21:00 latency: 236816 ms from: holytransaction irreversible: 72038 (-24) 1496816ms th_a application.cpp:458 handle_block ] Got block: #72062 time: 2015-10-16T04:21:00 latency: 236816 ms from: holytransaction irreversible: 72038 (-24) 1496817ms th_a application.cpp:458 handle_block ] Got block: #72063 time: 2015-10-16T04:21:03 latency: 233817 ms from: xeldal irreversible: 72038 (-25) 1496818ms th_a application.cpp:458 handle_block ] Got block: #72064 time: 2015-10-16T04:21:06 latency: 230818 ms from: spectral irreversible: 72039 (-25) 1496819ms th_a application.cpp:458 handle_block ] Got block: #72065 time: 2015-10-16T04:21:09 latency: 227819 ms from: init7 irreversible: 72040 (-25) 1496820ms th_a application.cpp:458 handle_block ] Got block: #72066 time: 2015-10-16T04:21:12 latency: 224820 ms from: bitcube irreversible: 72041 (-25) 1496821ms th_a application.cpp:458 handle_block ] Got block: #72066 time: 2015-10-16T04:21:12 latency: 224821 ms from: bitcube irreversible: 72042 (-24) 1496821ms th_a application.cpp:458 handle_block ] Got block: #72067 time: 2015-10-16T04:21:15 latency: 221821 ms from: bhuz irreversible: 72042 (-25) 1496822ms th_a application.cpp:458 handle_block ] Got block: #72068 time: 2015-10-16T04:21:18 latency: 218822 ms from: init4 irreversible: 72043 (-25) 1496822ms th_a application.cpp:458 handle_block ] Got block: #72068 time: 2015-10-16T04:21:18 latency: 218822 ms from: init4 irreversible: 72043 (-25) 1496830ms th_a websocket_api.cpp:120 on_message ] e.to_detail_string(): 10 assert_exception: Assert Exception !ec: websocket send failed: invalid state {"msg":"invalid state"} th_a websocket.cpp:164 send_message 1496830ms th_a database_api.cpp:200 ~database_api_impl ] freeing database api 166198384 1496831ms th_a database_api.cpp:200 ~database_api_impl ] freeing database api 218846336

Produced a few blocks and again, missed another block, high latency's again above 70 sec but this time things came back to normal alone.

Code: [Select]
huz irreversible: 72427 (-29) 2452531ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011aeb78343c7bbd2c7ab4798208a27da4aad4","00011afa837 d1e88f1cfeedd86602831a9590572","00011b02964b12ec207adae71bd2b13a4a0a9d7f","00011b0689886d20ab9f0dc27ad97a66999f121e","00011b08a9ac06e2c6ab01 f5b508a4654518e7fc"] 2454393ms th_a application.cpp:458 handle_block ] Got block: #72457 time: 2015-10-16T04:40:54 latency: 393 ms from: in.abit irreversible: 72428 (-29) 2457171ms th_a application.cpp:458 handle_block ] Got block: #72458 time: 2015-10-16T04:40:57 latency: 170 ms from: init7 irreversible: 72429 (-29) 2460020ms th_a application.cpp:458 handle_block ] Got block: #72459 time: 2015-10-16T04:41:00 latency: 20 ms from: s partako irreversible: 72430 (-29) 2463039ms th_a application.cpp:458 handle_block ] Got block: #72460 time: 2015-10-16T04:41:03 latency: 39 ms from: w ackou irreversible: 72430 (-30) 2466273ms th_a application.cpp:458 handle_block ] Got block: #72461 time: 2015-10-16T04:41:06 latency: 273 ms from: maqifrnswa irreversible: 72430 (-31) 2469135ms th_a application.cpp:458 handle_block ] Got block: #72462 time: 2015-10-16T04:41:09 latency: 135 ms from: mr.agsexplorer irreversible: 72431 (-31) 2470809ms th_a application.cpp:507 handle_transaction ] Got 1 transactions from network 2472120ms th_a application.cpp:458 handle_block ] Got block: #72463 time: 2015-10-16T04:41:12 latency: 120 ms from: init0 irreversible: 72433 (-30)^[[B^[[B 2554005ms th_a application.cpp:458 handle_block ] Got block: #72463 time: 2015-10-16T04:41:12 latency: 82005 ms from: init0 irreversible: 72434 (-29) 2554005ms th_a application.cpp:458 handle_block ] Got block: #72464 time: 2015-10-16T04:41:15 latency: 79005 ms from: xeldal irreversible: 72434 (-30) 2554006ms th_a application.cpp:458 handle_block ] Got block: #72464 time: 2015-10-16T04:41:15 latency: 79006 ms from: xeldal irreversible: 72434 (-30) 2554012ms th_a application.cpp:458 handle_block ] Got block: #72465 time: 2015-10-16T04:41:18 latency: 76012 ms from: bue irreversible: 72434 (-31) 2554014ms th_a application.cpp:458 handle_block ] Got block: #72465 time: 2015-10-16T04:41:18 latency: 76014 ms from: bue irreversible: 72435 (-30) 2554014ms th_a application.cpp:458 handle_block ] Got block: #72465 time: 2015-10-16T04:41:18 latency: 76014 ms from: bue irreversible: 72435 (-30) 2554014ms th_a application.cpp:458 handle_block ] Got block: #72465 time: 2015-10-16T04:41:18 latency: 76014 ms from: bue irreversible: 72435 (-30) 2554020ms th_a application.cpp:458 handle_block ] Got block: #72466 time: 2015-10-16T04:41:24 latency: 70020 ms from : harvey-xts irreversible: 72435 (-31) 2554021ms th_a application.cpp:458 handle_block ] Got block: #72466 time: 2015-10-16T04:41:24 latency: 70021 ms from : harvey-xts irreversible: 72435 (-31) 2554022ms th_a application.cpp:458 handle_block ] Got block: #72467 time: 2015-10-16T04:41:27 latency: 67022 ms from: init4 irreversible: 72435 (-32) 2554023ms th_a application.cpp:458 handle_block ] Got block: #72467 time: 2015-10-16T04:41:27 latency: 67023 ms from: init4 irreversible: 72436 (-31) 2554023ms th_a application.cpp:458 handle_block ] Got block: #72468 time: 2015-10-16T04:41:30 latency: 64023 ms from: spectral irreversible: 72436 (-32) 2554025ms th_a application.cpp:458 handle_block ] Got block: #72468 time: 2015-10-16T04:41:30 latency: 64025 ms from: spectral irreversible: 72439 (-29) 2554025ms th_a application.cpp:458 handle_block ] Got block: #72468 time: 2015-10-16T04:41:30 latency: 64025 ms from: spectral irreversible: 72439 (-29) 2554025ms th_a application.cpp:458 handle_block ] Got block: #72469 time: 2015-10-16T04:41:33 latency: 61025 ms from: dele-puppy irreversible: 72439 (-30) 2554026ms th_a application.cpp:458 handle_block ] Got block: #72470 time: 2015-10-16T04:41:36 latency: 58026 ms from 2554028ms th_a application.cpp:458 handle_block ] Got block: #72471 time: 2015-10-16T04:41:39 latency: 55028 ms from: init3 irreversible: 72441 (-30) 2554035ms th_a application.cpp:458 handle_block ] Got block: #72472 time: 2015-10-16T04:41:42 latency: 52035 ms from: init8 irreversible: 72441 (-31) 2554036ms th_a application.cpp:458 handle_block ] Got block: #72473 time: 2015-10-16T04:41:45 latency: 49036 ms from: riverhead irreversible: 72443 (-30) 2554038ms th_a application.cpp:458 handle_block ] Got block: #72474 time: 2015-10-16T04:41:48 latency: 46038 ms from: init5 irreversible: 72443 (-31) 2554039ms th_a application.cpp:458 handle_block ] Got block: #72475 time: 2015-10-16T04:41:51 latency: 43039 ms from: delegate-1.lafona irreversible: 72446 (-29) [[B2563531ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011afa837d1e88f1cfeedd86602831a9590572","00011b0be306f248278d8bfc0197490b71fed46e","00011b14920371991c39b89346a7ba38e1ff7d3a","00011b18e99b70aab449c520e2a32b8876ea1b30","00011b1a8c7f9c65faf922cdec51403ad4906d7e","00011b1b640dc038ce0ab632469edcf1d3b65478"] 2563541ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011afa837d1e88f1cfeedd86602831a9590572","00011b0be306f248278d8bfc0197490b71fed46e","00011b14920371991c39b89346a7ba38e1ff7d3a","00011b18e99b70aab449c520e2a32b8876ea1b30","00011b1a8c7f9c65faf922cdec51403ad4906d7e","00011b1b640dc038ce0ab632469edcf1d3b65478"] 2563549ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011afa837d1e88f1cfeedd86602831a9590572","00011b0be306f248278d8bfc0197490b71fed46e","00011b14920371991c39b89346a7ba38e1ff7d3a","00011b18e99b70aab449c520e2a32b8876ea1b30","00011b1a8c7f9c65faf922cdec51403ad4906d7e","00011b1b640dc038ce0ab632469edcf1d3b65478"] 2563558ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011afa837d1e88f1cfeedd86602831a9590572","00011b0be306f248278d8bfc0197490b71fed46e","00011b14920371991c39b89346a7ba38e1ff7d3a","00011b18e99b70aab449c520e2a32b8876ea1b30","00011b1a8c7f9c65faf922cdec51403ad4906d7e","00011b1b640dc038ce0ab632469edcf1d3b65478"] 2563614ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563616ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563621ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563625ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563678ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563771ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563771ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563795ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563966ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2564145ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2565061ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2565231ms th_a application.cpp:507 handle_transaction ] Got 1 transactions from network 2565345ms th_a application.cpp:458
any clue?
Title: Re: BitShares 2 Release Coordination Thread
Post by: triox on October 16, 2015, 05:17:18 am: Quote from: rnglab on October 16, 2015, 04:59:20 am
A few minutes ago a witness asked on Telegram why was he missing blocks. I've found that he was getting negative latency arround -500ms, asked him if hi had ntp installed and he didn't. A minute later (and about 15 minutes after he switched to another node and stoped missing blocks) I missed 3 blocks in a row and witness started showing super high latency's from all witnesses (above 300 seconds?), replayed blockchain and started producing again:

Code: [Select]
1125246ms th_a application.cpp:458 handle_block ] Got block: #72017 time: 2015-10-16T04:18:45 latency: 246 ms from: holytransaction irreversible: 71988 (-29) 1128179ms th_a application.cpp:458 handle_block ] Got block: #72018 time: 2015-10-16T04:18:48 latency: 179 ms from: init10 irreversible: 71990 (-28) 1131131ms th_a application.cpp:458 handle_block ] Got block: #72019 time: 2015-10-16T04:18:51 latency: 131 ms from: delegate-1.lafona irreversible: 71991 (-28) 1134292ms th_a application.cpp:458 handle_block ] Got block: #72020 time: 2015-10-16T04:18:54 latency: 292 ms from: bitcube irreversible: 71995 (-25) 1137159ms th_a application.cpp:458 handle_block ] Got block: #72021 time: 2015-10-16T04:18:57 latency: 159 ms from: init3 irreversible: 71996 (-25) 1140059ms th_a application.cpp:458 handle_block ] Got block: #72022 time: 2015-10-16T04:19:00 latency: 59 ms from: s pectral irreversible: 71997 (-25) 1143163ms th_a application.cpp:458 handle_block ] Got block: #72023 time: 2015-10-16T04:19:03 latency: 163 ms from: init6 irreversible: 71998 (-25) 1146460ms th_a application.cpp:458 handle_block ] Got block: #72024 time: 2015-10-16T04:19:06 latency: 460 ms from: delegate-clayop irreversible: 71999 (-25) 1149207ms th_a application.cpp:458 handle_block ] Got block: #72025 time: 2015-10-16T04:19:09 latency: 206 ms from: init7 irreversible: 72000 (-25) 1152026ms th_a application.cpp:458 handle_block ] Got block: #72026 time: 2015-10-16T04:19:12 latency: 26 ms from: s partako irreversible: 72001 (-25) 1155266ms th_a application.cpp:458 handle_block ] Got block: #72027 time: 2015-10-16T04:19:15 latency: 266 ms from: delegated-proof-of-steak irreversible: 72002 (-25) 1158043ms th_a application.cpp:458 handle_block ] Got block: #72028 time: 2015-10-16T04:19:18 latency: 43 ms from: c yrano irreversible: 72003 (-25) 1160989ms th_a application.cpp:458 handle_block ] Got block: #72029 time: 2015-10-16T04:19:21 latency: -10 ms from: riverhead irreversible: 72004 (-25) 1164001ms th_a witness.cpp:179 block_production_loo ] Generated block #72030 with timestamp 2015-10-16T04:19:24 at time 2015-10-16T04:19:24 1167204ms th_a application.cpp:458 handle_block ] Got block: #72031 time: 2015-10-16T04:19:27 latency: 204 ms from: init5 irreversible: 72006 (-25) 1169258ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011944cd05a88b065c97459067e9433cf8a365","00011952892be327107879d8403f9cea3e6a2137","00011959da81c677a2df19da61c6c4aee44f95a4","0001195d1d6ea4375ae4f68399e9df2ed2b61105","0001195f39e0d57cedc4fdca4ad4dfcf585bdd99"] 1170130ms th_a application.cpp:458 handle_block ] Got block: #72032 time: 2015-10-16T04:19:30 latency: 130 ms from: delegate-1.lafona irreversible: 72007 (-25) 1173026ms th_a application.cpp:458 handle_block ] Got block: #72033 time: 2015-10-16T04:19:33 latency: 26 ms from: bhuz irreversible: 72007 (-26) 1176166ms th_a application.cpp:458 handle_block ] Got block: #72034 time: 2015-10-16T04:19:36 latency: 165 ms from: harvey-xts irreversible: 72008 (-26) 1179163ms th_a application.cpp:458 handle_block ] Got block: #72035 time: 2015-10-16T04:19:39 latency: 163 ms from: init2 irreversible: 72008 (-27) 1182153ms th_a application.cpp:458 handle_block ] Got block: #72036 time: 2015-10-16T04:19:42 latency: 153 ms from: init0 irreversible: 72009 (-27) 1185002ms th_a witness.cpp:179 block_production_loo ] Generated block #72037 with timestamp 2015-10-16T04:19:45 at time 2015-10-16T04:19:45 1188022ms th_a application.cpp:458 handle_block ] Got block: #72038 time: 2015-10-16T04:19:48 latency: 22 ms from: mindphlux.witness irreversible: 72010 (-28) 1191282ms th_a application.cpp:458 handle_block ] Got block: #72039 time: 2015-10-16T04:19:51 latency: 282 ms from: bitcube irreversible: 72011 (-28) 1194157ms th_a application.cpp:458 handle_block ] Got block: #72040 time: 2015-10-16T04:19:54 latency: 157 ms from: init3 irreversible: 72011 (-29) 1197042ms th_a application.cpp:458 handle_block ] Got block: #72041 time: 2015-10-16T04:19:57 latency: 42 ms from: cyrano irreversible: 72011 (-30) 1200339ms th_a application.cpp:458 handle_block ] Got block: #72042 time: 2015-10-16T04:20:00 latency: 339 ms from: bue irreversible: 72011 (-31) 1203185ms th_a application.cpp:458 handle_block ] Got block: #72043 time: 2015-10-16T04:20:03 latency: 185 ms from: init10 irreversible: 72012 (-31) 1206022ms th_a application.cpp:458 handle_block ] Got block: #72044 time: 2015-10-16T04:20:06 latency: 22 ms from: wackou irreversible: 72012 (-32) 1209141ms th_a application.cpp:458 handle_block ] Got block: #72045 time: 2015-10-16T04:20:09 latency: 141 ms from: mr.agsexplorer irreversible: 72013 (-32) 1496796ms th_a application.cpp:458 handle_block ] Got block: #72045 time: 2015-10-16T04:20:09 latency: 287796 ms from: mr.agsexplorer irreversible: 72015 (-30) 1496796ms th_a application.cpp:458 handle_block ] Got block: #72045 time: 2015-10-16T04:20:09 latency: 287796 ms from: mr.agsexplorer irreversible: 72015 (-30) 1496796ms th_a application.cpp:458 handle_block ] Got block: #72046 time: 2015-10-16T04:20:12 latency: 284796 ms from: riverhead irreversible: 72015 (-31) 1496797ms th_a application.cpp:458 handle_block ] Got block: #72047 time: 2015-10-16T04:20:15 latency: 281797 ms from: init4 irreversible: 72015 (-32) 1496797ms th_a application.cpp:458 handle_block ] Got block: #72047 time: 2015-10-16T04:20:15 latency: 281797 ms from: init4 irreversible: 72016 (-31) 1496797ms th_a application.cpp:458 handle_block ] Got block: #72047 time: 2015-10-16T04:20:15 latency: 281797 ms from: init4 irreversible: 72016 (-31) 1496798ms th_a application.cpp:507 handle_transaction ] Got 1 transactions from network 1496798ms th_a application.cpp:458 handle_block ] Got block: #72048 time: 2015-10-16T04:20:18 latency: 278798 ms from: delegate-clayop irreversible: 72016 (-32) 1496799ms th_a application.cpp:458 handle_block ] Got block: #72048 time: 2015-10-16T04:20:18 latency: 278799 ms from: delegate-clayop irreversible: 72016 (-32) 1496799ms th_a application.cpp:458 handle_block ] Got block: #72048 time: 2015-10-16T04:20:18 latency: 278799 ms from: delegate-clayop irreversible: 72016 (-32) 1496799ms th_a application.cpp:458 handle_block ] Got block: #72049 time: 2015-10-16T04:20:21 latency: 275799 ms from: init8 irreversible: 72016 (-33) 1496800ms th_a application.cpp:458 handle_block ] Got block: #72049 time: 2015-10-16T04:20:21 latency: 275800 ms from: init8 irreversible: 72017 (-32) 1496800ms th_a application.cpp:458 handle_block ] Got block: #72049 time: 2015-10-16T04:20:21 latency: 275800 ms from: init8 irreversible: 72017 (-32) 1496801ms th_a application.cpp:458 handle_block ] Got block: #72050 time: 2015-10-16T04:20:24 latency: 272801 ms from: triox-delegate irreversible: 72017 (-33) 1496801ms th_a application.cpp:458 handle_block ] Got block: #72051 time: 2015-10-16T04:20:27 latency: 269801 ms from: init6 irreversible: 72022 (-29) 1496802ms th_a application.cpp:458 handle_block ] Got block: #72051 time: 2015-10-16T04:20:27 latency: 269802 ms from: init6 irreversible: 72022 (-29) 1496802ms th_a application.cpp:458 handle_block ] Got block: #72051 time: 2015-10-16T04:20:27 latency: 269802 ms from: init6 irreversible: 72022 (-29) 1496803ms th_a application.cpp:458 handle_block ] Got block: #72052 time: 2015-10-16T04:20:30 latency: 266803 ms from: delegated-proof-of-steak irreversible: 72022 (-30) 1496804ms th_a application.cpp:458 handle_block ] Got block: #72053 time: 2015-10-16T04:20:33 latency: 263804 ms from: dele-puppy irreversible: 72022 (-31) 1496805ms th_a application.cpp:458 handle_block ] Got block: #72053 time: 2015-10-16T04:20:33 latency: 263805 ms from: dele-puppy irreversible: 72025 (-28) 1496805ms th_a application.cpp:458 handle_block ] Got block: #72054 time: 2015-10-16T04:20:36 latency: 260805 ms from: verbaltech2 irreversible: 72025 (-29) 1496806ms th_a application.cpp:458 handle_block ] Got block: #72054 time: 2015-10-16T04:20:36 latency: 260806 ms from: verbaltech2 irreversible: 72026 (-28) 1496806ms th_a application.cpp:458 handle_block ] Got block: #72054 time: 2015-10-16T04:20:36 latency: 260806 ms from: verbaltech2 irreversible: 72026 (-28) 1496806ms th_a application.cpp:458 handle_block ] Got block: #72055 time: 2015-10-16T04:20:39 latency: 257806 ms from: in.abit irreversible: 72026 (-29) 1496807ms th_a application.cpp:458 handle_block ] Got block: #72055 time: 2015-10-16T04:20:39 latency: 257807 ms from: in.abit irreversible: 72031 (-24) 1496807ms th_a application.cpp:458 handle_block ] Got block: #72055 time: 2015-10-16T04:20:39 latency: 257807 ms from: in.abit irreversible: 72031 (-24) 1496807ms th_a application.cpp:458 handle_block ] Got block: #72056 time: 2015-10-16T04:20:42 latency: 254807 ms from: spartako irreversible: 72031 (-25) 1496808ms th_a application.cpp:458 handle_block ] Got block: #72056 time: 2015-10-16T04:20:42 latency: 254808 ms from: spartako irreversible: 72032 (-24) 1496808ms th_a application.cpp:458 handle_block ] Got block: #72056 time: 2015-10-16T04:20:42 latency: 254808 ms from: spartako irreversible: 72032 (-24) 1496808ms th_a application.cpp:458 handle_block ] Got block: #72057 time: 2015-10-16T04:20:45 latency: 251808 ms from: delegate.ihashfury irreversible: 72032 (-25) 1496810ms th_a application.cpp:458 handle_block ] Got block: #72058 time: 2015-10-16T04:20:48 latency: 248810 ms from: maqifrnswa irreversible: 72033 (-25) 1496811ms th_a application.cpp:458 handle_block ] Got block: #72058 time: 2015-10-16T04:20:48 latency: 248811 ms from: maqifrnswa irreversible: 72034 (-24) 1496811ms th_a application.cpp:458 handle_block ] Got block: #72059 time: 2015-10-16T04:20:51 latency: 245811 ms from: roadscape irreversible: 72034 (-25) 1496812ms th_a application.cpp:458 handle_block ] Got block: #72059 time: 2015-10-16T04:20:51 latency: 245812 ms from: roadscape irreversible: 72035 (-24) 1496812ms th_a application.cpp:458 handle_block ] Got block: #72060 time: 2015-10-16T04:20:54 latency: 242812 ms from: elmato irreversible: 72035 (-25) 1496814ms th_a application.cpp:458 handle_block ] Got block: #72060 time: 2015-10-16T04:20:54 latency: 242814 ms from: elmato irreversible: 72036 (-24) 1496814ms th_a application.cpp:458 handle_block ] Got block: #72061 time: 2015-10-16T04:20:57 latency: 239814 ms from: fox irreversible: 72036 (-25) 1496815ms th_a application.cpp:458 handle_block ] Got block: #72062 time: 2015-10-16T04:21:00 latency: 236815 ms from: holytransaction irreversible: 72037 (-25) 1496816ms th_a application.cpp:458 handle_block ] Got block: #72062 time: 2015-10-16T04:21:00 latency: 236816 ms from: holytransaction irreversible: 72038 (-24) 1496816ms th_a application.cpp:458 handle_block ] Got block: #72062 time: 2015-10-16T04:21:00 latency: 236816 ms from: holytransaction irreversible: 72038 (-24) 1496817ms th_a application.cpp:458 handle_block ] Got block: #72063 time: 2015-10-16T04:21:03 latency: 233817 ms from: xeldal irreversible: 72038 (-25) 1496818ms th_a application.cpp:458 handle_block ] Got block: #72064 time: 2015-10-16T04:21:06 latency: 230818 ms from: spectral irreversible: 72039 (-25) 1496819ms th_a application.cpp:458 handle_block ] Got block: #72065 time: 2015-10-16T04:21:09 latency: 227819 ms from: init7 irreversible: 72040 (-25) 1496820ms th_a application.cpp:458 handle_block ] Got block: #72066 time: 2015-10-16T04:21:12 latency: 224820 ms from: bitcube irreversible: 72041 (-25) 1496821ms th_a application.cpp:458 handle_block ] Got block: #72066 time: 2015-10-16T04:21:12 latency: 224821 ms from: bitcube irreversible: 72042 (-24) 1496821ms th_a application.cpp:458 handle_block ] Got block: #72067 time: 2015-10-16T04:21:15 latency: 221821 ms from: bhuz irreversible: 72042 (-25) 1496822ms th_a application.cpp:458 handle_block ] Got block: #72068 time: 2015-10-16T04:21:18 latency: 218822 ms from: init4 irreversible: 72043 (-25) 1496822ms th_a application.cpp:458 handle_block ] Got block: #72068 time: 2015-10-16T04:21:18 latency: 218822 ms from: init4 irreversible: 72043 (-25) 1496830ms th_a websocket_api.cpp:120 on_message ] e.to_detail_string(): 10 assert_exception: Assert Exception !ec: websocket send failed: invalid state {"msg":"invalid state"} th_a websocket.cpp:164 send_message 1496830ms th_a database_api.cpp:200 ~database_api_impl ] freeing database api 166198384 1496831ms th_a database_api.cpp:200 ~database_api_impl ] freeing database api 218846336

Produced a few blocks and again, missed another block, high latency's again but this time things came back to normal without restarting the witness:

Code: [Select]
huz irreversible: 72427 (-29) 2452531ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011aeb78343c7bbd2c7ab4798208a27da4aad4","00011afa837 d1e88f1cfeedd86602831a9590572","00011b02964b12ec207adae71bd2b13a4a0a9d7f","00011b0689886d20ab9f0dc27ad97a66999f121e","00011b08a9ac06e2c6ab01 f5b508a4654518e7fc"] 2454393ms th_a application.cpp:458 handle_block ] Got block: #72457 time: 2015-10-16T04:40:54 latency: 393 ms from: in.abit irreversible: 72428 (-29) 2457171ms th_a application.cpp:458 handle_block ] Got block: #72458 time: 2015-10-16T04:40:57 latency: 170 ms from: init7 irreversible: 72429 (-29) 2460020ms th_a application.cpp:458 handle_block ] Got block: #72459 time: 2015-10-16T04:41:00 latency: 20 ms from: s partako irreversible: 72430 (-29) 2463039ms th_a application.cpp:458 handle_block ] Got block: #72460 time: 2015-10-16T04:41:03 latency: 39 ms from: w ackou irreversible: 72430 (-30) 2466273ms th_a application.cpp:458 handle_block ] Got block: #72461 time: 2015-10-16T04:41:06 latency: 273 ms from: maqifrnswa irreversible: 72430 (-31) 2469135ms th_a application.cpp:458 handle_block ] Got block: #72462 time: 2015-10-16T04:41:09 latency: 135 ms from: mr.agsexplorer irreversible: 72431 (-31) 2470809ms th_a application.cpp:507 handle_transaction ] Got 1 transactions from network 2472120ms th_a application.cpp:458 handle_block ] Got block: #72463 time: 2015-10-16T04:41:12 latency: 120 ms from: init0 irreversible: 72433 (-30)^[[B^[[B 2554005ms th_a application.cpp:458 handle_block ] Got block: #72463 time: 2015-10-16T04:41:12 latency: 82005 ms from: init0 irreversible: 72434 (-29) 2554005ms th_a application.cpp:458 handle_block ] Got block: #72464 time: 2015-10-16T04:41:15 latency: 79005 ms from: xeldal irreversible: 72434 (-30) 2554006ms th_a application.cpp:458 handle_block ] Got block: #72464 time: 2015-10-16T04:41:15 latency: 79006 ms from: xeldal irreversible: 72434 (-30) 2554012ms th_a application.cpp:458 handle_block ] Got block: #72465 time: 2015-10-16T04:41:18 latency: 76012 ms from: bue irreversible: 72434 (-31) 2554014ms th_a application.cpp:458 handle_block ] Got block: #72465 time: 2015-10-16T04:41:18 latency: 76014 ms from: bue irreversible: 72435 (-30) 2554014ms th_a application.cpp:458 handle_block ] Got block: #72465 time: 2015-10-16T04:41:18 latency: 76014 ms from: bue irreversible: 72435 (-30) 2554014ms th_a application.cpp:458 handle_block ] Got block: #72465 time: 2015-10-16T04:41:18 latency: 76014 ms from: bue irreversible: 72435 (-30) 2554020ms th_a application.cpp:458 handle_block ] Got block: #72466 time: 2015-10-16T04:41:24 latency: 70020 ms from : harvey-xts irreversible: 72435 (-31) 2554021ms th_a application.cpp:458 handle_block ] Got block: #72466 time: 2015-10-16T04:41:24 latency: 70021 ms from : harvey-xts irreversible: 72435 (-31) 2554022ms th_a application.cpp:458 handle_block ] Got block: #72467 time: 2015-10-16T04:41:27 latency: 67022 ms from: init4 irreversible: 72435 (-32) 2554023ms th_a application.cpp:458 handle_block ] Got block: #72467 time: 2015-10-16T04:41:27 latency: 67023 ms from: init4 irreversible: 72436 (-31) 2554023ms th_a application.cpp:458 handle_block ] Got block: #72468 time: 2015-10-16T04:41:30 latency: 64023 ms from: spectral irreversible: 72436 (-32) 2554025ms th_a application.cpp:458 handle_block ] Got block: #72468 time: 2015-10-16T04:41:30 latency: 64025 ms from: spectral irreversible: 72439 (-29) 2554025ms th_a application.cpp:458 handle_block ] Got block: #72468 time: 2015-10-16T04:41:30 latency: 64025 ms from: spectral irreversible: 72439 (-29) 2554025ms th_a application.cpp:458 handle_block ] Got block: #72469 time: 2015-10-16T04:41:33 latency: 61025 ms from: dele-puppy irreversible: 72439 (-30) 2554026ms th_a application.cpp:458 handle_block ] Got block: #72470 time: 2015-10-16T04:41:36 latency: 58026 ms from 2554028ms th_a application.cpp:458 handle_block ] Got block: #72471 time: 2015-10-16T04:41:39 latency: 55028 ms from: init3 irreversible: 72441 (-30) 2554035ms th_a application.cpp:458 handle_block ] Got block: #72472 time: 2015-10-16T04:41:42 latency: 52035 ms from: init8 irreversible: 72441 (-31) 2554036ms th_a application.cpp:458 handle_block ] Got block: #72473 time: 2015-10-16T04:41:45 latency: 49036 ms from: riverhead irreversible: 72443 (-30) 2554038ms th_a application.cpp:458 handle_block ] Got block: #72474 time: 2015-10-16T04:41:48 latency: 46038 ms from: init5 irreversible: 72443 (-31) 2554039ms th_a application.cpp:458 handle_block ] Got block: #72475 time: 2015-10-16T04:41:51 latency: 43039 ms from: delegate-1.lafona irreversible: 72446 (-29) [[B2563531ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011afa837d1e88f1cfeedd86602831a9590572","00011b0be306f248278d8bfc0197490b71fed46e","00011b14920371991c39b89346a7ba38e1ff7d3a","00011b18e99b70aab449c520e2a32b8876ea1b30","00011b1a8c7f9c65faf922cdec51403ad4906d7e","00011b1b640dc038ce0ab632469edcf1d3b65478"] 2563541ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011afa837d1e88f1cfeedd86602831a9590572","00011b0be306f248278d8bfc0197490b71fed46e","00011b14920371991c39b89346a7ba38e1ff7d3a","00011b18e99b70aab449c520e2a32b8876ea1b30","00011b1a8c7f9c65faf922cdec51403ad4906d7e","00011b1b640dc038ce0ab632469edcf1d3b65478"] 2563549ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011afa837d1e88f1cfeedd86602831a9590572","00011b0be306f248278d8bfc0197490b71fed46e","00011b14920371991c39b89346a7ba38e1ff7d3a","00011b18e99b70aab449c520e2a32b8876ea1b30","00011b1a8c7f9c65faf922cdec51403ad4906d7e","00011b1b640dc038ce0ab632469edcf1d3b65478"] 2563558ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011afa837d1e88f1cfeedd86602831a9590572","00011b0be306f248278d8bfc0197490b71fed46e","00011b14920371991c39b89346a7ba38e1ff7d3a","00011b18e99b70aab449c520e2a32b8876ea1b30","00011b1a8c7f9c65faf922cdec51403ad4906d7e","00011b1b640dc038ce0ab632469edcf1d3b65478"] 2563614ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563616ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563621ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563625ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563678ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563771ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563771ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563795ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2563966ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2564145ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2565061ms th_a application.cpp:778 get_blockchain_synop ] synopsis: ["00011b0d956a01f4b06ecab56e024757167c0cea","00011b1d15be486b5977df8f47f22ec3fe4b2cbf","00011b25829cea17b02b78c6168ca0eee65a724d","00011b2927707acd5e5d0fd6bb4b5f5321c1df5f","00011b2b3e7377c6f75c178587286331461be982","00011b2c3a103e5a3d35cd6dcaace58b1e5d3308"] 2565231ms th_a application.cpp:507 handle_transaction ] Got 1 transactions from network 2565345ms th_a application.cpp:458
any clue?

I originally built from Vagrantfile, and it indeed doesn't inlcude ntp in dependencies. So after installing ntp per rnglab's advice, I updated witness to switch back to the main node and at that point I noticed on the spare box all blocks delivered with huge negative latencies.

Edit: the anomaly on my end was in the -500ms range
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 16, 2015, 05:34:53 am: My "delayed" node is on Digitalocean Amsterdam 2 location. Triox's is an EC2. Might be just a coincidence?
Title: Re: BitShares 2 Release Coordination Thread
Post by: triox on October 16, 2015, 05:44:48 am: Quote from: rnglab on October 16, 2015, 05:34:53 am
My "delayed" node is on Digitalocean Amsterdam 2 location. Triox's is an EC2. Might be just a coincidence?

What I don't get is why I started receiving all blocks with -500 ms on my backup box the moment I updated the witness back to the main box.
Title: Re: BitShares 2 Release Coordination Thread
Post by: kenCode on October 16, 2015, 06:08:32 am: Quote from: bytemaster on October 15, 2015, 06:45:20 pm
I need all witnesses to update to the latest *bitshares* branch and replay the blockchain. Post here after you have done so.
Hi BitSharers,
I just managed to get access to my accounts today and thus able to register my witness.
Updated as of now and needing votes PLEASE:

get_witness delegate.kencode
{
"id": "1.6.47",
"witness_account": "1.2.35917",
"last_aslot": 0,
"signing_key": "BTS82YPKCWM8RuJQAThHUouwJ4igzG7nwjQffLrxdTmRB9GiMmEe8",
"vote_id": "1:58",
"total_votes": 0,
"url": "http://BitShares-Munich.de",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: checkrasier on October 16, 2015, 06:20:59 am: Witness checkraiser has been updated and asking for your vote.

get_witness checkraiser
{
"id": "1.6.44",
"witness_account": "1.2.13774",
"last_aslot": 0,
"signing_key": "BTS8Jr9MQE61fZUa9tRvSYcFQRRr8j2baWouknxjRbPkpVtNACa9m",
"vote_id": "1:55",
"total_votes": 0,
"url": "url-to-proposal",
"total_missed": 0,
"last_confirmed_block_num": 0
Title: Re: BitShares 2 Release Coordination Thread
Post by: boombastic on October 16, 2015, 06:52:31 am: mr.agsexplorer is updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: Harvey on October 16, 2015, 07:12:12 am: harvey-xts updated.
Title: Re: BitShares 2 Release Coordination Thread
Post by: betax on October 16, 2015, 07:51:05 am: betaxtrade updated replayed and node running
Title: Re: BitShares 2 Release Coordination Thread
Post by: ffwong on October 16, 2015, 12:23:57 pm: Witness dragonball updated and synced, and node is running. Ready to serve the network.

Please give dragonball some votes. Thanks

Quote
get_witness dragonball
{
"id": "1.6.46",
"witness_account": "1.2.95289",
"last_aslot": 0,
"signing_key": "BTS6R58dMYBsz2WxfFXoq659kTjowRjQRwkDyMwU6QTmRFpBg5Bo3",
"vote_id": "1:57",
"total_votes": "89708199329",
"url": "http://www.dragonball",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: abit on October 16, 2015, 08:29:47 pm: Recent fork is because of this?
Code: [Select]
2015-10-16T20:00:35 p2p:message read_loop process_ordinary_mes ] client rejected message sent by peer 178.62.88.151:43208, {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":557,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:00:35"},"format":"(skip & skip_transaction_dupe_check) || trx_idx.indices().get<by_trx_id>().find(trx_id) == trx_idx.indices().get<by_trx_id>().end(): ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":615,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:00:35"},"format":"","data":{"trx":{"ref_block_num":25210,"ref_block_prefix":2700722878,"expiration":"2015-10-16T20:00:47","operations":[[1,{"fee":{"amount":500000,"asset_id":"1.3.0"},"seller":"1.2.22517","amount_to_sell":{"amount":100,"asset_id":"1.3.121"},"min_to_receive":{"amount":300000,"asset_id":"1.3.0"},"expiration":"2020-10-16T20:00:30","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["2045d2960d4e04514eeb2a1211c0d7cdc2bcdaa52abd783b2d3db98e7d896293c644653f7544740468097239cf2f645583c1afeff4171c61750d4b7829bb6b61b5"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":219,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:00:35"},"format":"","data":{"trx":{"ref_block_num":25210,"ref_block_prefix":2700722878,"expiration":"2015-10-16T20:00:47","operations":[[1,{"fee":{"amount":500000,"asset_id":"1.3.0"},"seller":"1.2.22517","amount_to_sell":{"amount":100,"asset_id":"1.3.121"},"min_to_receive":{"amount":300000,"asset_id":"1.3.0"},"expiration":"2020-10-16T20:00:30","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["2045d2960d4e04514eeb2a1211c0d7cdc2bcdaa52abd783b2d3db98e7d896293c644653f7544740468097239cf2f645583c1afeff4171c61750d4b7829bb6b61b5"]}}},{"context":{"level":"warn","file":"application.cpp","line":513,"method":"handle_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:00:35"},"format":"","data":{"transaction_message":{"trx":{"ref_block_num":25210,"ref_block_prefix":2700722878,"expiration":"2015-10-16T20:00:47","operations":[[1,{"fee":{"amount":500000,"asset_id":"1.3.0"},"seller":"1.2.22517","amount_to_sell":{"amount":100,"asset_id":"1.3.121"},"min_to_receive":{"amount":300000,"asset_id":"1.3.0"},"expiration":"2020-10-16T20:00:30","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["2045d2960d4e04514eeb2a1211c0d7cdc2bcdaa52abd783b2d3db98e7d896293c644653f7544740468097239cf2f645583c1afeff4171c61750d4b7829bb6b61b5"]}}}}]} node.cpp:3822
Or this?
Code: [Select]
2015-10-16T20:07:39 p2p:message read_loop process_ordinary_mes ] client rejected message sent by peer 127.0.0.1:60003, {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"db_block.cpp","line":578,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:07:39"},"format":"trx.ref_block_prefix == tapos_block_summary.block_id._hash[1]: ","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":615,"method":"_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:07:39"},"format":"","data":{"trx":{"ref_block_num":25353,"ref_block_prefix":41879959,"expiration":"2015-10-16T20:08:09","operations":[[19,{"fee":{"amount":100000,"asset_id":"1.3.0"},"publisher":"1.2.35248","asset_id":"1.3.120","feed":{"settlement_price":{"base":{"amount":421179,"asset_id":"1.3.120"},"quote":{"amount":1000000000,"asset_id":"1.3.0"}},"maintenance_collateral_ratio":1750,"maximum_short_squeeze_ratio":1500,"core_exchange_rate":{"base":{"amount":421179,"asset_id":"1.3.120"},"quote":{"amount":1000000000,"asset_id":"1.3.0"}}},"extensions":[]}]],"extensions":[],"signatures":["202a290391dc581fdea967ac65d6f00506d53fedbee4755b35a257c48056bc67e22520517c062a618f06a7bf9f5ee9dc45c6bbc47e4be747884fb0af9eb41ef5a3"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":219,"method":"push_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:07:39"},"format":"","data":{"trx":{"ref_block_num":25353,"ref_block_prefix":41879959,"expiration":"2015-10-16T20:08:09","operations":[[19,{"fee":{"amount":100000,"asset_id":"1.3.0"},"publisher":"1.2.35248","asset_id":"1.3.120","feed":{"settlement_price":{"base":{"amount":421179,"asset_id":"1.3.120"},"quote":{"amount":1000000000,"asset_id":"1.3.0"}},"maintenance_collateral_ratio":1750,"maximum_short_squeeze_ratio":1500,"core_exchange_rate":{"base":{"amount":421179,"asset_id":"1.3.120"},"quote":{"amount":1000000000,"asset_id":"1.3.0"}}},"extensions":[]}]],"extensions":[],"signatures":["202a290391dc581fdea967ac65d6f00506d53fedbee4755b35a257c48056bc67e22520517c062a618f06a7bf9f5ee9dc45c6bbc47e4be747884fb0af9eb41ef5a3"]}}},{"context":{"level":"warn","file":"application.cpp","line":513,"method":"handle_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:07:39"},"format":"","data":{"transaction_message":{"trx":{"ref_block_num":25353,"ref_block_prefix":41879959,"expiration":"2015-10-16T20:08:09","operations":[[19,{"fee":{"amount":100000,"asset_id":"1.3.0"},"publisher":"1.2.35248","asset_id":"1.3.120","feed":{"settlement_price":{"base":{"amount":421179,"asset_id":"1.3.120"},"quote":{"amount":1000000000,"asset_id":"1.3.0"}},"maintenance_collateral_ratio":1750,"maximum_short_squeeze_ratio":1500,"core_exchange_rate":{"base":{"amount":421179,"asset_id":"1.3.120"},"quote":{"amount":1000000000,"asset_id":"1.3.0"}}},"extensions":[]}]],"extensions":[],"signatures":["202a290391dc581fdea967ac65d6f00506d53fedbee4755b35a257c48056bc67e22520517c062a618f06a7bf9f5ee9dc45c6bbc47e4be747884fb0af9eb41ef5a3"]}}}}]} node.cpp:3822
And another assertion exception
Code: [Select]
2015-10-16T20:17:12 p2p:message read_loop on_closing_connectio ] Peer 14.136.246.148:38935 is disconnecting us because of an error: You offered us a block that we reject as invalid, exception: {"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"asset_evaluator.cpp","line":225,"method":"graphene::chain::asset_update_evaluator::do_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:16:15"},"format":"!(o.new_options.issuer_permissions & ~a.options.issuer_permissions): Cannot reinstate previously revoked issuer permissions on an asset.","data":{}},{"context":{"level":"warn","file":"asset_evaluator.cpp","line":244,"method":"graphene::chain::asset_update_evaluator::do_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:16:15"},"format":"","data":{"o":{"fee":{"amount":50000001,"asset_id":"1.3.0"},"issuer":"1.2.32567","asset_to_update":"1.3.350","new_options":{"max_supply":"999999999999999","market_fee_percent":20,"max_market_fee":"1000000000000000","issuer_permissions":79,"flags":128,"core_exchange_rate":{"base":{"amount":"4759691381","asset_id":"1.3.0"},"quote":{"amount":100000000,"asset_id":"1.3.350"}},"whitelist_authorities":[],"blacklist_authorities":[],"whitelist_markets":[],"blacklist_markets":[],"description":"exchangeable for Bitcoin from BlockTrades","extensions":[]},"extensions":[]}}},{"context":{"level":"warn","file":"evaluator.cpp","line":36,"method":"graphene::chain::generic_evaluator::start_evaluate","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:16:15"},"format":"","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":623,"method":"graphene::chain::database::apply_operation","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:16:15"},"format":"","data":{}},{"context":{"level":"warn","file":"db_block.cpp","line":606,"method":"graphene::chain::database::_apply_transaction","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:16:15"},"format":"","data":{"trx":{"ref_block_num":25538,"ref_block_prefix":2067906275,"expiration":"2015-10-16T20:17:24","operations":[[11,{"fee":{"amount":50000001,"asset_id":"1.3.0"},"issuer":"1.2.32567","asset_to_update":"1.3.350","new_options":{"max_supply":"999999999999999","market_fee_percent":20,"max_market_fee":"1000000000000000","issuer_permissions":79,"flags":128,"core_exchange_rate":{"base":{"amount":"4759691381","asset_id":"1.3.0"},"quote":{"amount":100000000,"asset_id":"1.3.350"}},"whitelist_authorities":[],"blacklist_authorities":[],"whitelist_markets":[],"blacklist_markets":[],"description":"exchangeable for Bitcoin from BlockTrades","extensions":[]},"extensions":[]}]],"extensions":[],"signatures":["1f2cbf4cdb0d7b13b01ab17f8a4235c455c88817c7455caf63501094d46eb169b81c56a3dfc545f20eb44d42b3b6f29a55b3dde5bf9cef90025bbadad9abc8cb95"]}}},{"context":{"level":"warn","file":"db_block.cpp","line":509,"method":"graphene::chain::database::_apply_block","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:16:15"},"format":"","data":{"next_block.block_num()":91075}},{"context":{"level":"warn","file":"db_block.cpp","line":191,"method":"graphene::chain::database::_push_block","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:16:15"},"format":"","data":{"new_block":{"previous":"000163c2e3be417b412082327b723a7534aadd48","timestamp":"2015-10-16T20:16:57","witness":"1.6.1","transaction_merkle_root":"4028cc7060ccd29d57b3f32e45d020b619e77ba1","extensions":[],"witness_signature":"20211740def22e1a890c2b11558431b3fb4ee883a3d02002baf083f8b63a568dc7200f60f6f065a6a8263930ce9e2d96dcdcd5e00643ec730f234f5b818a25b644","transactions":[{"ref_block_num":25538,"ref_block_prefix":2067906275,"expiration":"2015-10-16T20:17:24","operations":[[11,{"fee":{"amount":50000001,"asset_id":"1.3.0"},"issuer":"1.2.32567","asset_to_update":"1.3.350","new_options":{"max_supply":"999999999999999","market_fee_percent":20,"max_market_fee":"1000000000000000","issuer_permissions":79,"flags":128,"core_exchange_rate":{"base":{"amount":"4759691381","asset_id":"1.3.0"},"quote":{"amount":100000000,"asset_id":"1.3.350"}},"whitelist_authorities":[],"blacklist_authorities":[],"whitelist_markets":[],"blacklist_markets":[],"description":"exchangeable for Bitcoin from BlockTrades","extensions":[]},"extensions":[]}]],"extensions":[],"signatures":["1f2cbf4cdb0d7b13b01ab17f8a4235c455c88817c7455caf63501094d46eb169b81c56a3dfc545f20eb44d42b3b6f29a55b3dde5bf9cef90025bbadad9abc8cb95"],"operation_results":[[0,{}]]}]}}},{"context":{"level":"warn","file":"application.cpp","line":489,"method":"graphene::app::detail::application_impl::handle_block","hostname":"","thread_name":"th_a","timestamp":"2015-10-16T20:16:15"},"format":"","data":{"blk_msg":{"block":{"previous":"000163c2e3be417b412082327b723a7534aadd48","timestamp":"2015-10-16T20:16:57","witness":"1.6.1","transaction_merkle_root":"4028cc7060ccd29d57b3f32e45d020b619e77ba1","extensions":[],"witness_signature":"20211740def22e1a890c2b11558431b3fb4ee883a3d02002baf083f8b63a568dc7200f60f6f065a6a8263930ce9e2d96dcdcd5e00643ec730f234f5b818a25b644","transactions":[{"ref_block_num":25538,"ref_block_prefix":2067906275,"expiration":"2015-10-16T20:17:24","operations":[[11,{"fee":{"amount":50000001,"asset_id":"1.3.0"},"issuer":"1.2.32567","asset_to_update":"1.3.350","new_options":{"max_supply":"999999999999999","market_fee_percent":20,"max_market_fee":"1000000000000000","issuer_permissions":79,"flags":128,"core_exchange_rate":{"base":{"amount":"4759691381","asset_id":"1.3.0"},"quote":{"amount":100000000,"asset_id":"1.3.350"}},"whitelist_authorities":[],"blacklist_authorities":[],"whitelist_markets":[],"blacklist_markets":[],"description":"exchangeable for Bitcoin from BlockTrades","extensions":[]},"extensions":[]}]],"extensions":[],"signatures":["1f2cbf4cdb0d7b13b01ab17f8a4235c455c88817c7455caf63501094d46eb169b81c56a3dfc545f20eb44d42b3b6f29a55b3dde5bf9cef90025bbadad9abc8cb95"],"operation_results":[[0,{}]]}]},"block_id":"000163c3d93c2d7dc2a9738d646e0fa24b7fcb17"},"sync_mode":true}}]} node.cpp:2899
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 16, 2015, 09:18:58 pm: The fork was caused by an asset update (the soft-fork that we rolled out yesterday) that didn't have any impact until today.

We knew exactly when it would happen because I was watching the network we we broadcast the transaction that we knew would break it.
Title: Re: BitShares 2 Release Coordination Thread
Post by: liondani on October 16, 2015, 11:38:45 pm: waiting for your votes ;)

Code: [Select]
get_witness liondani { "id": "1.6.48", "witness_account": "1.2.376", "last_aslot": 0, "signing_key": "BTS7WngKXi3p6Ui1Zn41tK6mfSkH6H3TYVWbr6nNHbEQ5xUrzL19j", "vote_id": "1:59", "total_votes": 0, "url": "https://bitsharestalk.org/index.php/topic,6406.msg245698.html#msg245698", "total_missed": 0, "last_confirmed_block_num": 0 }
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 17, 2015, 08:47:30 am: Disappointed I lost my witness position. I have removed myself from Telegram Bitshares_Witnesses and Slack.

Seeds, feed and witness nodes are still up and running. ;)
Title: Re: BitShares 2 Release Coordination Thread
Post by: kenCode on October 17, 2015, 09:32:28 am: Votes badly needed Please :)

get_witness delegate.kencode
{
"id": "1.6.47",
"witness_account": "1.2.35917",
"last_aslot": 0,
"signing_key": "BTS82YPKCWM8RuJQAThHUouwJ4igzG7nwjQffLrxdTmRB9GiMmEe8",
"vote_id": "1:58",
"total_votes": 0,
"url": "http://BitShares-Munich.de",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Title: Re: BitShares 2 Release Coordination Thread
Post by: emski on October 17, 2015, 10:03:56 am: Got several lines of red messages like this one on the seed node. And then it crashed.

Code: [Select]
2896541ms th_a fork_database.cpp:51 push_block ] Pushing block to fork database that failed to link: 000163c506a2394a3bff81ef8bb132aca3208a3a, 91077 2896541ms th_a fork_database.cpp:52 push_block ] Head: 91387, 000164fbf83d3e90b2bb69c05e38d31c9ffd42c2 2896544ms th_a application.cpp:477 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:72 _push_block {"new_block":{"previous":"000163c4d902d1b8f9922112b51fda3aa97342e4","timestamp":"2015-10-16T20:17:03","witness":"1.6.45","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f6b7201f5ec0d128842872188c1d624d96af34a05a75445f145a973c9c25f79cf4fc3993a967ffb905f18e00edd8a3d2db1fbd29fa38ed532297530d66f722cf5","transactions":[]}} th_a db_block.cpp:191 _push_block witness_node: /home/emski/bitshares2/bitshares-2/libraries/net/node.cpp:1605: void graphene::net::detail::node_impl::schedule_peer_for_deletion(const peer_connection_ptr&): Assertion `_closing_connections.find(peer_to_delete) == _closing_connections.end()' failed. Aborted (core dumped)
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 17, 2015, 12:04:50 pm: spartako, delegate.IHashFury and DataSecurityNode during the minor fork have lost many votes for killing the fork.

I hope we can get these votes again because we recovered in less then an hour our nodes.
(spartako is anyway in the current active list because has 20M votes).
Title: Re: BitShares 2 Release Coordination Thread
Post by: mindphlux on October 17, 2015, 12:07:25 pm: I would think, it is kind unfair to the witnesses when they get punished for forks that happen due to network code and bugs. After all, they fixed those issues within a very short timeframe. It's a different story when a witness stays on a fork for days and continues to miss blocks.
Title: Re: BitShares 2 Release Coordination Thread
Post by: BunkerChainLabs-DataSecurityNode on October 17, 2015, 01:18:29 pm: Quote from: spartako on October 17, 2015, 12:04:50 pm
spartako, delegate.IHashFury and DataSecurityNode during the minor fork have lost many votes for killing the fork.

I hope we can get these votes again because we recovered in less then an hour our nodes.
(spartako is anyway in the current active list because has 20M votes).

Yes.. it was particularly frustrating last night when witness feeds needed updating and I couldn't do anything to help because all my efforts to update didn't count being voted out.

I was away from a computer for 2hrs and as soon I saw something had happened got the update.

Ah well growing pains.
Title: Re: BitShares 2 Release Coordination Thread
Post by: tonyk on October 17, 2015, 06:49:18 pm: wackou, bue, harvey-xts, delegate.ihashfury, datasecuritynode, bts-bitshares-argentina, fox

Please update to 110% if you like your witness positions....it is way too many hours now.

especially @wackou, and @bue

Update: If you have done it but have not been in the active list since, please post here.
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 17, 2015, 07:07:00 pm: Quote from: tonyk on October 17, 2015, 06:49:18 pm
wackou, bue, harvey-xts, delegate.ihashfury, datasecuritynode, bts-bitshares-argentina, fox

Please update to 110% if you like your witness positions....it is way too many hours now.

especially @wackou, and @bue

FYI, only active witnesses can provide price feeds. datasecuritynode has changed his feed script but not able to provide feed because he was temporary voted out of the active list (possibly because of the recent fork). delegate.ihashfury was an active and contributing witness but he was temporary voted out too.
Title: Re: BitShares 2 Release Coordination Thread
Post by: wackou on October 17, 2015, 10:39:25 pm: Quote from: tonyk on October 17, 2015, 06:49:18 pm
wackou, bue, harvey-xts, delegate.ihashfury, datasecuritynode, bts-bitshares-argentina, fox

Please update to 110% if you like your witness positions....it is way too many hours now.

especially @wackou, and @bue

Update: If you have done it but have not been in the active list since, please post here.

I am not sure what you mean exactly... Do you want us to update the core exchange rate in the published feeds to be 10% higher than the external feed (instead of the 5% it is now)?
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 17, 2015, 10:57:04 pm: Quote from: wackou on October 17, 2015, 10:39:25 pm
Quote from: tonyk on October 17, 2015, 06:49:18 pm
wackou, bue, harvey-xts, delegate.ihashfury, datasecuritynode, bts-bitshares-argentina, fox

Please update to 110% if you like your witness positions....it is way too many hours now.

especially @wackou, and @bue

Update: If you have done it but have not been in the active list since, please post here.

I am not sure what you mean exactly... Do you want us to update the core exchange rate in the published feeds to be 10% higher than the external feed (instead of the 5% it is now)?
same ask
Title: Re: BitShares 2 Release Coordination Thread
Post by: Troglodactyl on October 17, 2015, 11:02:24 pm: Quote from: wackou on October 17, 2015, 10:39:25 pm
Quote from: tonyk on October 17, 2015, 06:49:18 pm
wackou, bue, harvey-xts, delegate.ihashfury, datasecuritynode, bts-bitshares-argentina, fox

Please update to 110% if you like your witness positions....it is way too many hours now.

especially @wackou, and @bue

Update: If you have done it but have not been in the active list since, please post here.

I am not sure what you mean exactly... Do you want us to update the core exchange rate in the published feeds to be 10% higher than the external feed (instead of the 5% it is now)?

No. There are other parameters in your feed updates other than the price ratio. The MSSR determines the price at which margin called short positions will be forced to buy to cover. Initially I believe that was set to 150%, and now most witnesses have it at 110%. Having it at 150% caused serious problems as you may have seen.
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 17, 2015, 11:02:35 pm: @wackou @bue

Get the latest script version from github. Change the config file for line

Code: [Select]
maximum_short_squeeze_ratio = 1100
If you need futher info, please come to the witness telegram channel or slack group. Most witnesses are there to help.
Title: Re: BitShares 2 Release Coordination Thread
Post by: roadscape on October 17, 2015, 11:04:23 pm: It's in reference to the SQP (maximum_short_squeeze_ratio) variable of price feeds..
https://bitsharestalk.org/index.php/topic,18852.msg246398.html#msg246398 (a lot of details in earlier posts)
https://bitsharestalk.org/index.php/topic,19102.0.html

The default value is thought to be too high for the market in its current state.. setting it to something like 1100 helps stop margin calls.
Title: Re: BitShares 2 Release Coordination Thread
Post by: wackou on October 17, 2015, 11:18:02 pm: oh ok, thanks for the explanation. Well, I'm not using xeroc's script but my own, and haven't caught up yet on all that happened and the fine tunings that I should implement (I am currently stumped by a mem leak that I have in my tools that's sucking all my energy to track :-\ )

I will temporarily stop publishing feeds then and will fix them in the coming days.
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 17, 2015, 11:30:31 pm: updated and published new price feed under new configure

Code: [Select]
discount = 0.995 core_exchange_factor = 1.05 # 5% surplus if paying fees in bitassets maintenance_collateral_ratio = 1750 #Call when collateral only pays off 175% the debt maximum_short_squeeze_ratio = 1100 # Stop calling when collateral only pays off 110% $ minValidAssetPriceInBTC = 0.00001 change_min = 0.5
Quote from: tonyk on October 17, 2015, 06:49:18 pm
wackou, bue, harvey-xts, delegate.ihashfury, datasecuritynode, bts-bitshares-argentina, fox

Please update to 110% if you like your witness positions....it is way too many hours now.

especially @wackou, and @bue

Update: If you have done it but have not been in the active list since, please post here.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Fox on October 19, 2015, 11:16:15 am: All fox nodes are updated, online, synced and ready to serve. Once voted back into the active witness list, I will update my price feeds. I am connected with the other witnesses thru Telegram and Slack.
Title: Re: BitShares 2 Release Coordination Thread
Post by: wackou on October 19, 2015, 12:09:46 pm: Quote from: wackou on October 17, 2015, 11:18:02 pm
I will temporarily stop publishing feeds then and will fix them in the coming days.

I have resumed publishing feeds with proper params yesterday night
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 19, 2015, 05:38:36 pm: Quote from: tonyk on October 17, 2015, 06:49:18 pm
wackou, bue, harvey-xts, delegate.ihashfury, datasecuritynode, bts-bitshares-argentina, fox

Please update to 110% if you like your witness positions....it is way too many hours now.

especially @wackou, and @bue

Update: If you have done it but have not been in the active list since, please post here.

My seeds, feed and witness nodes are still up and running.
Title: Re: BitShares 2 Release Coordination Thread
Post by: BunkerChainLabs-DataSecurityNode on October 19, 2015, 06:09:50 pm: Quote from: tonyk on October 17, 2015, 06:49:18 pm
wackou, bue, harvey-xts, delegate.ihashfury, datasecuritynode, bts-bitshares-argentina, fox

Please update to 110% if you like your witness positions....it is way too many hours now.

especially @wackou, and @bue

Update: If you have done it but have not been in the active list since, please post here.

My node was among the first to get updated, however I was voted out so all that was being reported was residual data and my updated feed had no impact once I was no longer an active witness.

Since this posting the witnesses have coordinated with each other to ensure a consistent input of feed data using slots that each of us have committed too.

Today I was voted back in as a witness(thank you!) so you can see the new updated info. All the witnesses appear to be on the same page as well now.
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 19, 2015, 06:20:35 pm: Please vote again for spartako and iHashFury, we recovered from the fork in less then an hour.
ihashFury has created the telegram chat that was reveled very useful for witness coordination and I wrote the bot for witnesses and I'm porting it to slack
Thanks!
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 19, 2015, 08:16:20 pm: Quote from: spartako on October 19, 2015, 06:20:35 pm
Please vote again for spartako and iHashFury, we recovered from the fork in less then an hour.
ihashFury has created the telegram chat that was reveled very useful for witness coordination and I wrote the bot for witnesses and I'm porting it to slack
Thanks!

spartako's witness alert bot is the reason why active witnesses who subscribe to it can sleep with a peace of mind, know that their witness nodes are safely running and securing the bts2 network. iHashFury has been making active contributions in his own right. Please do consider voting these two helpful witnesses. Your support will become their motivation.
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 19, 2015, 08:17:46 pm: Quote from: cube on October 19, 2015, 08:16:20 pm
Quote from: spartako on October 19, 2015, 06:20:35 pm
Please vote again for spartako and iHashFury, we recovered from the fork in less then an hour.
ihashFury has created the telegram chat that was reveled very useful for witness coordination and I wrote the bot for witnesses and I'm porting it to slack
Thanks!

spartako's witness alert bot is the reason why active witnesses who subscribe to it can sleep with a peace of mind, know that their witness nodes are safely running and securing the bts2 network. iHashFury has been making active contributions in his own right. Please do consider voting these two helpful witnesses. Your support will become their motivation.

+5% +5% +5%
Title: Re: BitShares 2 Release Coordination Thread
Post by: Thom on October 19, 2015, 09:56:03 pm: Quote from: DataSecurityNode on October 19, 2015, 06:09:50 pm
Today I was voted back in as a witness(thank you!) so you can see the new updated info. All the witnesses appear to be on the same page as well now.

@DSN: Glad to see you back in.

I noticed everybody but me and one other witness has set their short squeeze ratio parameters to 1100 (maximum). I decided to go midway.

Frankly I don't believe witnesses should have their finger on such important parameter that influence the markets.

That is where we are right now however. Our governance is far from being tweeked and stable. It's gonna take some time. I hope people realize the importance of our DPoS structure and the need to transition away from CNX dominance. That's what BM wants, that's also what I think is best.
Title: Re: BitShares 2 Release Coordination Thread
Post by: BunkerChainLabs-DataSecurityNode on October 20, 2015, 12:25:52 pm: Quote from: Thom on October 19, 2015, 09:56:03 pm
Quote from: DataSecurityNode on October 19, 2015, 06:09:50 pm
Today I was voted back in as a witness(thank you!) so you can see the new updated info. All the witnesses appear to be on the same page as well now.

@DSN: Glad to see you back in.

I noticed everybody but me and one other witness has set their short squeeze ratio parameters to 1100 (maximum). I decided to go midway.

Frankly I don't believe witnesses should have their finger on such important parameter that influence the markets.

That is where we are right now however. Our governance is far from being tweeked and stable. It's gonna take some time. I hope people realize the importance of our DPoS structure and the need to transition away from CNX dominance. That's what BM wants, that's also what I think is best.
Of course we shouldn't decide. However in the absence of the committee leadership to submit a proposal for the community to vote into effect.. it was great to see the witnesses taking ownership of an emergency situation that threatened our network and did their best to coordinate a solution.

We weren't just a bunch of miners who only cared about generating blocks... I think it was a fantastic showing of the D in DPOS showing it's awesome power to effectively protection the network even when one of its branches was not operating.
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 20, 2015, 12:27:12 pm: Quote from: DataSecurityNode on October 20, 2015, 12:25:52 pm
Quote from: Thom on October 19, 2015, 09:56:03 pm
Quote from: DataSecurityNode on October 19, 2015, 06:09:50 pm
Today I was voted back in as a witness(thank you!) so you can see the new updated info. All the witnesses appear to be on the same page as well now.

@DSN: Glad to see you back in.

I noticed everybody but me and one other witness has set their short squeeze ratio parameters to 1100 (maximum). I decided to go midway.

Frankly I don't believe witnesses should have their finger on such important parameter that influence the markets.

That is where we are right now however. Our governance is far from being tweeked and stable. It's gonna take some time. I hope people realize the importance of our DPoS structure and the need to transition away from CNX dominance. That's what BM wants, that's also what I think is best.
Of course we shouldn't decide. However in the absence of the committee leadership to submit a proposal for the community to vote into effect.. it was great to see the witnesses taking ownership of an emergency situation that threatened our network and did their best to coordinate a solution.

We weren't just a bunch of miners who only cared about generating blocks... I think it was a fantastic showing of the D in DPOS showing it's awesome power to effectively protection the network even when one of its branches was not operating.

he's right, great job guys +5%
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 20, 2015, 09:50:57 pm: The reason witnesses have the finger on that parameter is because it may need to be dynamic (depending upon market conditions).

Technically committee members can also publish feeds, but because committee members are not PAID they do not have income (nor skills) necessary to setup a VPS system to publish feeds.

Witnesses are also "witnessing" the price, and "testifying" as to the feed.

We wanted to have "voting" on this parameter and using the median of the feeds is a way of voting. No single witness can manipulate this parameter.

Also we wanted it be easy to change quickly, and committee actions normally take a 2 week review period.
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 21, 2015, 05:25:25 pm: @bytemaster and team,

There is a coming hard fork in the latest bts2 github commit. Should we make a formal announcement to inform of the witnesses of the need to update their nodes?

Edit:

bts2 github releases a new tag. I sent out an alert to both telegram and slack groups. Any witnesses and devs can send out similar alerts in future.

Edit:

bitcube node and seed updated at the time of this post.
Title: Re: BitShares 2 Release Coordination Thread
Post by: abit on October 21, 2015, 07:35:18 pm: Quote from: cube on October 21, 2015, 05:25:25 pm
@bytemaster and team,

Edit:

bts2 github releases a new tag. I sent out an alert to both telegram and slack groups. Any witnesses and devs can send out similar alerts in future.
But isn't it a pre-release, not a release?

//Edit: in.abit updated.
Title: Re: BitShares 2 Release Coordination Thread
Post by: rnglab on October 21, 2015, 07:53:10 pm: updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 21, 2015, 07:54:32 pm: delegate-clayop is updated.

ps. can we vote for "spartako"? He's very passionate and skillful in running witness node.
Title: Re: BitShares 2 Release Coordination Thread
Post by: pc on October 21, 2015, 08:08:52 pm: Updated.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Thom on October 21, 2015, 08:27:01 pm: If I update now will another be required on the 23rd?
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 21, 2015, 08:50:56 pm: @bytemaster

Please vote spartako back in.
He was in since the testnet, all the witnesses are using his bot for checking the feed, status, and to get notify it our own witness is missing blocks.
Always available on telegram, reliable and fast on updates/managing forks.
He also managed to stay in without your vote in the last couple of days, thanks to 40M votes from the community... but now he is out.
He should have the priority over newer witnesses asking for your vote.
So please, vote him back!
Title: Re: BitShares 2 Release Coordination Thread
Post by: Xeldal on October 21, 2015, 08:51:27 pm: updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: BunkerChainLabs-DataSecurityNode on October 21, 2015, 08:53:20 pm: Quote from: Bhuz on October 21, 2015, 08:50:56 pm
@bytemaster

Please vote spartako back in.
He was in since the testnet, all the witnesses are using his bot for checking the feed, status, and to get notify it our own witness is missing blocks.
Always available on telegram, reliable and fast on updates/managing forks.
He also managed to stay in without your vote in the last couple of days, thanks to 40M votes from the community... but now he is out.
He should have the priority over newer witnesses asking for your vote.
So please, vote him back!

+5%

datasecuritynode also updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: clayop on October 21, 2015, 08:55:10 pm: Quote from: Bhuz on October 21, 2015, 08:50:56 pm
@bytemaster

Please vote spartako back in.
He was in since the testnet, all the witnesses are using his bot for checking the feed, status, and to get notify it our own witness is missing blocks.
Always available on telegram, reliable and fast on updates/managing forks.
He also managed to stay in without your vote in the last couple of days, thanks to 40M votes from the community... but now he is out.
He should have the priority over newer witnesses asking for your vote.
So please, vote him back!

+5%
Title: Re: BitShares 2 Release Coordination Thread
Post by: ElMato on October 21, 2015, 08:57:09 pm: Quote from: Bhuz on October 21, 2015, 08:50:56 pm
@bytemaster

Please vote spartako back in.
He was in since the testnet, all the witnesses are using his bot for checking the feed, status, and to get notify it our own witness is missing blocks.
Always available on telegram, reliable and fast on updates/managing forks.
He also managed to stay in without your vote in the last couple of days, thanks to 40M votes from the community... but now he is out.
He should have the priority over newer witnesses asking for your vote.
So please, vote him back!

+5%
Title: Re: BitShares 2 Release Coordination Thread
Post by: maqifrnswa on October 21, 2015, 09:04:48 pm: maqifrnswa is updated
(ppa is updated too)

spartako appears to be back in as a witness
Title: Re: BitShares 2 Release Coordination Thread
Post by: fav on October 21, 2015, 09:07:34 pm: Quote from: Bhuz on October 21, 2015, 08:50:56 pm
@bytemaster

Please vote spartako back in.
He was in since the testnet, all the witnesses are using his bot for checking the feed, status, and to get notify it our own witness is missing blocks.
Always available on telegram, reliable and fast on updates/managing forks.
He also managed to stay in without your vote in the last couple of days, thanks to 40M votes from the community... but now he is out.
He should have the priority over newer witnesses asking for your vote.
So please, vote him back!

+5%
(http://ipfs.pics/ipfs/QmXMRKB2JCar5VvepP9VcDrCH6RS8Msw6aZnCqQxM9qX5j)
Title: Re: BitShares 2 Release Coordination Thread
Post by: emski on October 21, 2015, 09:18:50 pm: seed+witness up to date
Title: Re: BitShares 2 Release Coordination Thread
Post by: Bhuz on October 21, 2015, 09:31:58 pm: updated and signing
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 21, 2015, 10:05:14 pm: updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: wackou on October 21, 2015, 10:21:53 pm: updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: spartako on October 21, 2015, 10:27:25 pm: spartako updated and signing (thanks all of you guys for supporting me!)
Title: Re: BitShares 2 Release Coordination Thread
Post by: lafona on October 21, 2015, 11:46:56 pm: updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: ffwong on October 22, 2015, 12:52:33 am: dragonball updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: dichalcog3nid3 on October 22, 2015, 04:12:08 am: Up to date.
Title: Re: BitShares 2 Release Coordination Thread
Post by: taoljj on October 22, 2015, 04:31:11 am: delegate.taolje updated.
Only active witness can feed price?
Title: Re: BitShares 2 Release Coordination Thread
Post by: Shentist on October 22, 2015, 05:11:38 am: when does get the windows community the possibilty to have a standalone client?

i am aware that all CNX people are using mac, but this is a small portion of the population.
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 22, 2015, 02:13:02 pm: Quote from: Shentist on October 22, 2015, 05:11:38 am
when does get the windows community the possibilty to have a standalone client?

i am aware that all CNX people are using mac, but this is a small portion of the population.

They have had a stand alone light wallet from DAY 1 and they have had pre-compiled witness_node and cli_wallet exes this whole time.
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 22, 2015, 02:15:18 pm: Quote from: taoljj on October 22, 2015, 04:31:11 am
delegate.taolje updated.
Only active witness can feed price?

Voted for you.
Voted out kencode after seeing fav's post that his witness was being run by datasecuritynode and thus not actually providing any decentralization.
Title: Re: BitShares 2 Release Coordination Thread
Post by: alt on October 22, 2015, 02:25:55 pm: some witness missed block, you can vote for delegate.baozi if need
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 22, 2015, 02:29:55 pm: Quote from: alt on October 22, 2015, 02:25:55 pm
some witness missed block, you can vote for delegate.baozi if need

Done
Title: Re: BitShares 2 Release Coordination Thread
Post by: iHashFury on October 22, 2015, 02:36:36 pm: If your in the voting mood - some votes for witness 'delegate.ihashfury' would be appreciated.
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 22, 2015, 02:51:52 pm: Quote from: iHashFury on October 22, 2015, 02:36:36 pm
If your in the voting mood - some votes for witness 'delegate.ihashfury' would be appreciated.

done.
Title: Re: BitShares 2 Release Coordination Thread
Post by: bytemaster on October 22, 2015, 03:04:01 pm: Quote from: bytemaster on October 22, 2015, 02:15:18 pm
Quote from: taoljj on October 22, 2015, 04:31:11 am
delegate.taolje updated.
Only active witness can feed price?

Voted for you.
Voted out kencode after seeing fav's post that his witness was being run by datasecuritynode and thus not actually providing any decentralization.

delegate.taolje you are missing blocks!
Title: Re: BitShares 2 Release Coordination Thread
Post by: taoljj on October 22, 2015, 03:06:33 pm: back now！
producing nice

Quote from: bytemaster on October 22, 2015, 03:04:01 pm
Quote from: bytemaster on October 22, 2015, 02:15:18 pm
Quote from: taoljj on October 22, 2015, 04:31:11 am
delegate.taolje updated.
Only active witness can feed price?

Voted for you.
Voted out kencode after seeing fav's post that his witness was being run by datasecuritynode and thus not actually providing any decentralization.

delegate.taolje you are missing blocks!
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 22, 2015, 03:10:30 pm: Dele-puppy is updated.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Riverhead on October 22, 2015, 03:14:08 pm: riverhead is updated to v2.15.294. While not officially in the running I don't see any reason to turn it off.
Title: Re: BitShares 2 Release Coordination Thread
Post by: emski on October 22, 2015, 03:17:34 pm: Latest tag. Witness cant synchronize with the following cycle:
Code: [Select]
916125ms th_a application.cpp:524 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:81 _push_block {"new_block":{"previous":"0003e258da8ba8a4297d95c6397bb52fb21cd799","timestamp":"2015-10-22T14:23:51","witness":"1.6.14","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f4d9de85b26f4466d8e7bf21eeb012672d842645d577550802c72d26af2eca0a426c26f90f9a2e46d3b6d80ce75360470a64b1281ff3c2194695e8c15262bb430","transactions":[]}} th_a db_block.cpp:200 _push_block 916126ms th_a fork_database.cpp:60 push_block ] Pushing block to fork database that failed to link: 0003e25aff0e90296a70625feea4d03798a68b4c, 254554 916126ms th_a fork_database.cpp:61 push_block ] Head: 254425, 0003e1d91a65ae9a74abb2d2c6c38884f053f784 916126ms th_a application.cpp:524 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:81 _push_block {"new_block":{"previous":"0003e259e3f0a7f055aff18cd643a84729ce0719","timestamp":"2015-10-22T14:23:54","witness":"1.6.22","transaction_merkle_root":"7883d1cad9c917b47f4aaaaa12ca74a21da302b6","extensions":[],"witness_signature":"1f05800866df7ec90d0b61507c4922c3a9ae0e42ec93a22ed27efda360902aed164e087fa0540146801ff37ce913b3ee0975b09595fbcc60a73584fee042e5d6a6","transactions":[{"ref_block_num":57945,"ref_block_prefix":4037538019,"expiration":"2015-10-22T14:24:06","operations":[[1,{"fee":{"amount":1000000,"asset_id":"1.3.0"},"seller":"1.2.23707","amount_to_sell":{"amount":16582298,"asset_id":"1.3.113"},"min_to_receive":{"amount":"6377807400","asset_id":"1.3.0"},"expiration":"2020-10-22T14:23:47","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["1f14b1089e27b707446d52fad82917bf7679a7801822d4fed9f4b644a6a4da4dae7500b84e1e6963acddaf1ed417d80d18dd321184fe74b50c4ffe66c37bc231a9"],"operation_results":[[1,"1.7.1374"]]}]}} th_a db_block.cpp:200 _push_block 916126ms th_a fork_database.cpp:60 push_block ] Pushing block to fork database that failed to link: 0003e25bf57b0358aaaf5f5ce6f2ec9430c94a49, 254555 916126ms th_a fork_database.cpp:61 push_block ] Head: 254425, 0003e1d91a65ae9a74abb2d2c6c38884f053f784 916126ms th_a application.cpp:524 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:81 _push_block {"new_block":{"previous":"0003e25aff0e90296a70625feea4d03798a68b4c","timestamp":"2015-10-22T14:23:57","witness":"1.6.20","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f056acfc41a934bfad4aff3258b42bd07c2175aa88a9c2fd790dd61d2ac1e83c61a54e5501401cd07818c5e99df55eadecdf979cc10abf1850a606db7facb5851","transactions":[]}} th_a db_block.cpp:200 _push_block 916127ms th_a fork_database.cpp:60 push_block ] Pushing block to fork database that failed to link: 0003e25c186ef2e90aa0b7311bd339451a801d98, 254556 916127ms th_a fork_database.cpp:61 push_block ] Head: 254425, 0003e1d91a65ae9a74abb2d2c6c38884f053f784 916127ms th_a application.cpp:524 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:81 _push_block {"new_block":{"previous":"0003e25bf57b0358aaaf5f5ce6f2ec9430c94a49","timestamp":"2015-10-22T14:24:00","witness":"1.6.42","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f52dbec94e4696b8afeb66890878b61b1aec321172de4f4750665472442bec24b1a46c98085535b8a0edd4003a501bfa4b6eb9cb0d1c76435d36214bc542722d4","transactions":[]}} th_a db_block.cpp:200 _push_block 916127ms th_a fork_database.cpp:60 push_block ] Pushing block to fork database that failed to link: 0003e25d32a3934e4ee8b80e1913977ba2ab8961, 254557 916127ms th_a fork_database.cpp:61 push_block ] Head: 254425, 0003e1d91a65ae9a74abb2d2c6c38884f053f784 916127ms th_a application.cpp:524 handle_block ] Error when pushing block: 3080000 unlinkable_block_exception: unlinkable block block does not link to known chain {} th_a fork_database.cpp:81 _push_block {"new_block":{"previous":"0003e25c186ef2e90aa0b7311bd339451a801d98","timestamp":"2015-10-22T14:24:06","witness":"1.6.32","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f6bdef4fde43434655d735d2e4a305929f02da613e13e8eff95e516d915d807472d05d4fec1724f0e6887bfcadb7498d14272e20ac2debc4fa181221cf96b3657","transactions":[]}} th_a db_block.cpp:200 _push_block
EDIT: --replay-blockchain doesn't help
EDIT: looks that this is witness 1.6.24 that forked and produced on its own fork. The result is my node is not synchronizing.
Title: Re: BitShares 2 Release Coordination Thread
Post by: kenCode on October 22, 2015, 03:26:59 pm: Quote from: bytemaster on October 22, 2015, 02:15:18 pm
Voted for you.
Voted out kencode after seeing fav's post that his witness was being run by datasecuritynode and thus not actually providing any decentralization.

I agree with your decision 100% BM. DSN has always run my server for me, he is excellent. Decentralization is key however, so if he runs a Witness on his network, then I must move to a new webhost for my Witness.

Just curious, how many Witnesses are running their server at a company owned, or Partnered with Amazon?
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 22, 2015, 05:17:33 pm: bue has been updated to v2.15.294.

It was required --resync-blockchain .... replay does not work... :)
Title: Re: BitShares 2 Release Coordination Thread
Post by: mindphlux on October 22, 2015, 05:25:59 pm: Updated my witness this morning. Running fine.
Title: Re: BitShares 2 Release Coordination Thread
Post by: Spectral on October 22, 2015, 08:50:03 pm: Witness spectral updated
Title: Re: BitShares 2 Release Coordination Thread
Post by: maqifrnswa on October 23, 2015, 01:34:57 am: Quote from: kenCode on October 22, 2015, 03:26:59 pm
I agree with your decision 100% BM. DSN has always run my server for me, he is excellent. Decentralization is key however, so if he runs a Witness on his network, then I must move to a new webhost for my Witness.

Just curious, how many Witnesses are running their server at a company owned, or Partnered with Amazon?

Good point, decentralization includes a diversity of administrators and hardware/VPSes. I think everyone would happily switch VPS providers to ensure diversity.

Also, kencode, you should look into a worker proposal, I'd support your work.
Title: Re: BitShares 2 Release Coordination Thread
Post by: puppies on October 23, 2015, 02:06:47 am: I use so you start aws and digital ocean.
Title: Re: BitShares 2 Release Coordination Thread
Post by: ffwong on October 23, 2015, 03:36:34 am: dragonball runs on my own machine(s), not owned by any cloud service providers.
Title: Re: BitShares 2 Release Coordination Thread
Post by: maqifrnswa on October 23, 2015, 03:50:28 am: Me: DO NYC3 with my own hardware for failover
Title: Re: BitShares 2 Release Coordination Thread
Post by: kenCode on October 23, 2015, 08:11:44 am: Quote from: maqifrnswa on October 23, 2015, 01:34:57 am
Quote from: kenCode on October 22, 2015, 03:26:59 pm
I agree with your decision 100% BM. DSN has always run my server for me, he is excellent. Decentralization is key however, so if he runs a Witness on his network, then I must move to a new webhost for my Witness.
Just curious, how many Witnesses are running their server at a company owned, or Partnered with Amazon?
Good point, decentralization includes a diversity of administrators and hardware/VPSes. I think everyone would happily switch VPS providers to ensure diversity.
Also, kencode, you should look into a worker proposal, I'd support your work.

Thank you @maqifrnswa :)

Quote from: ffwong on October 23, 2015, 03:36:34 am
dragonball runs on my own machine(s), not owned by any cloud service providers.

Who serves up the gateway to your router? Comcast? T-Mobile? __________?

Good info guys, we need to track this stuff somewhere. (a private, consensus-driven sidechain perhaps?)
Title: Re: BitShares 2 Release Coordination Thread
Post by: abit on October 23, 2015, 08:12:24 pm: Missed a block today:
Code: [Select]
2015-10-23T13:40:34 th_a:Witness Block Production block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time. witness.cpp:197 2015-10-23T13:40:34 th_a:invoke get_blockchain_synopsis get_blockchain_synop ] synopsis: ["00044e96bc00dbac113a661f9fadf7ac48b7d9a1","00044ea3fbc78cd46ff1b8ae08d1f51cca560f42","00044ea9d2c1e249c9d2a772af24e361e3c0cc4e","00044eac93d30606ddecaf9f1556c2a22d00b482","00044eaed7842cd0729fbe9b67f0a874c5f6b2b4"] application.cpp:816 2015-10-23T13:40:35 th_a:Witness Block Production block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time. witness.cpp:197
//Edit:
My main node is in China. My own hardware. ISP is China Telecom.
Title: Re: BitShares 2 Release Coordination Thread
Post by: cube on October 24, 2015, 03:07:06 am: I and a number of witnesses have mentioned our node locations and hosting/non-hosting information in the Witness-only channels in Telegram and Slack. Does mentioning of our node locations in this public forum become an attack vector and compromises the bts network security? Are we giving the hackers, spammers, bad governments and other bad actors out there more information than we should?
Title: Re: BitShares 2 Release Coordination Thread
Post by: twitter on October 24, 2015, 03:36:20 am: agree. Do not post witness detail hosting information and vps location here?please use our telegram
Title: Re: BitShares 2 Release Coordination Thread
Post by: kenCode on October 24, 2015, 09:47:32 am: Quote from: cube on October 24, 2015, 03:07:06 am
I and a number of witnesses have mentioned our node locations and hosting/non-hosting information in the Witness-only channels in Telegram and Slack. Does mentioning of our node locations in this public forum become an attack vector and compromises the bts network security? Are we giving the hackers, spammers, bad governments and other bad actors out there more information than we should?

Quote from: twitter on October 24, 2015, 03:36:20 am
agree. Do not post witness detail hosting information and vps location here?please use our telegram

Exactly. I think it would be wise to assume the worst. Assume the NSA, Mi5, hackerboy123, etc has bots already tracking and trying to penetrate from every angle, and don't rule out their tracing methods or social engineering either:

https://www.youtube.com/watch?v=3VlyZIywY9c

BitShares is going to change the world. Do not take our security lightly.
1. One human should not control more than 1 Witness account. That human should not be friends or even geo-located near another Witness-controlling human.
2. Amazon controls many webhosting providers. Amazon should not have access to more than 1 Witness. (ie: who owns namecheap? who owns godaddy? who owns digital ocean? etc)
3. No more than 1 Witness should be physically hosted in 1 country.
Title: Re: BitShares 2 Release Coordination Thread
Post by: abit on October 24, 2015, 10:05:50 am: //Edit: missed blocks due to latency issue

Code: [Select]
2015-10-24T09:50:24 th_a:invoke handle_block handle_block ] Got block: #306412 time: 2015-10-24T09:50:24 latency: 344 ms from: delegate.ihashfury irreversible: 306386 (-26) application.cpp:496 2015-10-24T09:50:30 th_a:Witness Block Production block_production_loo ] Generated block #306413 with timestamp 2015-10-24T09:50:30 at time 2015-10-24T09:50:30 witness.cpp:179 2015-10-24T09:50:30 th_a:invoke handle_block handle_block ] Got block: #306413 time: 2015-10-24T09:50:27 latency: 3422 ms from : verbaltech2 irreversible: 306387 (-26) application.cpp:496 2015-10-24T09:50:33 th_a:invoke handle_block handle_block ] Got block: #306414 time: 2015-10-24T09:50:33 latency: 374 ms from: wackou irreversible: 306387 (-27) application.cpp:496 2015-10-24T09:50:33 th_a:invoke handle_block _push_block ] Switching to fork: 0004acee321e2d9ba26852c24af99e9a6d826bed db_block.cpp:137 2015-10-24T09:50:33 th_a:invoke handle_block _push_block ] pushing blocks from fork 306413 0004aced9d269bbd0bb17fa02cbbe7f16262ff23 db_block.cpp:147 2015-10-24T09:50:33 th_a:invoke handle_block _push_block ] pushing blocks from fork 306414 0004acee321e2d9ba26852c24af99e9a6d826bed db_block.cpp:147 2015-10-24T09:50:36 th_a:invoke handle_block handle_block ] Got block: #306415 time: 2015-10-24T09:50:36 latency: 345 ms from: dele-puppy irreversible: 306388 (-27) application.cpp:496
And earlier another:
Code: [Select]
2015-10-24T03:25:00 th_a:invoke handle_block handle_block ] Got block: #298723 time: 2015-10-24T03:25:00 latency: 551 ms from: mindphlux.witness irreversible: 298700 (-23) application.cpp:496 2015-10-24T03:25:06 th_a:Witness Block Production block_production_loo ] Generated block #298724 with timestamp 2015-10-24T03:25:06 at time 2015-10-24T03:25:06 witness.cpp:179 2015-10-24T03:25:06 th_a:invoke handle_block handle_block ] Got block: #298724 time: 2015-10-24T03:25:03 latency: 3723 ms from : rnglab irreversible: 298701 (-23) application.cpp:496 2015-10-24T03:25:09 th_a:invoke handle_transaction handle_transaction ] Got 1 transactions from network applic ation.cpp:545 2015-10-24T03:25:10 th_a:invoke handle_block handle_block ] Got block: #298725 time: 2015-10-24T03:25:09 latency: 1010 ms from : delegate-1.lafona irreversible: 298701 (-24) application.cpp:496 2015-10-24T03:25:10 th_a:invoke handle_block _push_block ] Switching to fork: 00048ee5fc659531b4974f3d9781a7a82be5625b db_block.cpp:137 2015-10-24T03:25:10 th_a:invoke handle_block _push_block ] pushing blocks from fork 298724 00048ee4bee8781d6a7755ba09e9e71c1a0d1d8b db_block.cpp:147
Title: Re: BitShares 2 Release Coordination Thread
Post by: xeroc on October 24, 2015, 07:51:16 pm: I think it should be ok to release some basic network/hosting information as long as they dont allow others to identify you machine

Edit: keeping all information 'secret' will not help shareholders decide