BitShares 2 Release Coordination Thread

Started by bytemaster, October 13, 2015, 03:50:02 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ElMato

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
}

mindphlux

#31
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.
Please consider voting for my witness mindphlux.witness and my committee user mindphlux. I will not vote for changes that affect witness pay.

triox

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

iHashFury

My seed nodes are up:

23.95.43.126:50696

109.73.172.144:50696

fav

Join us on Hive: [url="https://peakd.com/c/hive-120117/created"]https://peakd.com/c/hive-120117/created[/url]

Bhuz

bhuz ready on ID 1.6.17

"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

triox

Seed node 52.28.180.40:35681 up on the production chain.

twentythree

if i understand it correctly 2.0 is complete different ting. but we transfer amount and value of coins with the snapshot.


Fox

#23
I'm in with Witness ID 1.6.16

Please vote for fox.

EDIT:

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
}
Witness: fox

spartako

spartako (1.6.15) up ready for producing blocks


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
}
wallet_account_set_approval spartako

Akado

[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Pheonike

Can the bitshares homepage be updating with a message saying the the transition in progress, please check back today for further instructions or something?

puppies

Alright witness set up on 3 nodes with 3 different keys.  Failover script is running.  I'm as ready as I can get.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

cube

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.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.