BitShares 2 Release Coordination Thread

[clayop]

delegate-clayop is updated.

ps. can we vote for "spartako"? He's very passionate and skillful in running witness node.

[rnglab]

updated

[abit]

@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.

[cube]

@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.

[bytemaster]

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.

[fav]

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 

[BunkerChainLabs-DataSecurityNode]

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.

[Thom]

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.

[clayop]

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.

 

[cube]

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.

[spartako]

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!

[BunkerChainLabs-DataSecurityNode]

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.

[iHashFury]

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.

[wackou]

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

[Fox]

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.