Witness Alerts and Status

bytemaster · March 31, 2016, 12:55:46 PM

A bug-fix HARD FORK has been released:

https://github.com/bitshares/bitshares-2/releases/tag/2.0.160328

All full nodes will be required to upgrade to this release by Mon Apr 4 17:00:00 UTC 2016.

Bugfixes

Fix an incorrect asset ID returned by cli_wallet for non-BTS vesting balances #625
Fix a bug causing multisig to (incorrectly) fail in some cases #631
Restore p2p shutdown logic fix which was unintentionally excluded from the previous release #598 #637
Restore extension serialization fix which was unintentionally excluded from the previous release #599 #637

Testing

Fix slightly buggy verify_asset_supplies() check in unit tests #639
Build system

Various fixes to make install target
Fix out-of-tree builds #633

bytemaster · March 16, 2016, 03:27:27 PM

A new release and HARD FORK has been posted.

https://github.com/bitshares/bitshares-2/releases/tag/2.0.160316

All full nodes must update by March 23.

bytemaster · February 16, 2016, 08:54:33 PM

A new release and HARD FORK has been posted to github.

https://github.com/bitshares/bitshares-2/releases

This release includes a multitude of bug fixes and enhancements.

All full nodes must update by Tue Feb 23 18:00:00 UTC 2016.

bytemaster · January 29, 2016, 02:29:21 AM

All full nodes will have to upgrade to the latest commit on github to get synced with the blockchain.

bytemaster · January 04, 2016, 03:54:33 AM

It appears 40% of the witnesses are now up to date and in sync using this:

Witnesses:

* If you want to follow my chain, please add my seed node 114.92.254.159:62015. and
add this to the witness_node start command:

--checkpoint '[2359545,"002400f965e4ad8b494d48dfb8d311d59cd771bc"]' -s "114.92.254.159:62015"

The checkpoint is not needed, but will help avoid any confusion.

https://github.com/bitshares/bitshares-2/releases/tag/2.0.160103b

There may be a follow up release later this week that fixes this issue in greater detail after we have more time for peer review.

bytemaster · January 04, 2016, 02:49:50 AM

Everyone running a full node with the latest release, please shut it down, it will no longer sync with the network due to a recent bug and it may end up preventing others from joining the network.

Once we are sure all issues have been resolved we will make an official release. For now, join the witnesses in telegram for help reviving the network.

bytemaster · December 16, 2015, 08:02:47 PM

We have a new release out that addresses some late breaking security concerns issues. Most exchanges have already been notified. There have been a series of releases over the past two days. The most recent release fixes a operation numbering bug and is only necessary for those using operation ids. Otherwise, the unannounced release made last night is identical to the release made today.

We apologize for the rapid release (3 updates in 3 days), but would like to thank the community members (you know who you are) who helped us identify and fix a significant security vulnerability before any money was lost.

https://github.com/bitshares/bitshares-2/releases

cass · December 10, 2015, 12:04:08 AM

New release 2.0.151209 at https://github.com/bitshares/bitshares-2/releases

Re-indexing will be required. Hardfork takes effect at 2015-12-16 at 18:00 UTC.

This release incorporates numerous improvements and fixes.

List of changes
---------------

OP = https://bitsharestalk.org/index.php/topic,20527.0.html

mindphlux · December 02, 2015, 04:54:55 PM

All witnesses,

please update your witness to the latest pricefeed script from xeroc and use the recommended settings in the example config file. The script has been updated to use more chinese exchanges for the CNY price, and as a result it is much more accurate to the real price now and all witnesses should upgrade to it.

Once the committee sees that the bitCNY price is moving in the right direction, we'll create a committee proposal to unlock force settlement. This shouldn't take long hopefully.

bytemaster · November 02, 2015, 05:04:23 PM

All full nodes will have until Wednesday to upgrade for a hard fork.

https://bitsharestalk.org/index.php/topic,19676.msg252506.html#msg252506

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

bytemaster · October 27, 2015, 10:45:06 PM

All full nodes should be restarted with --replay-blockchain until a patch can be released.

https://bitsharestalk.org/index.php/topic,19538.msg250655.html#msg250655

Failure to replay on startup may cause your node to fork when a vesting balance is claimed.

bytemaster · October 23, 2015, 06:30:51 PM

Quote from: bytemaster on October 21, 2015, 05:48:44 PM
New release required (witness only)

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

Today someone registered an account name that is valid under this hardfork but not valid under the old rules. All full nodes will be required to upgrade rather than just witnesses.

Harvey · October 23, 2015, 01:32:33 PM

Harvey-xts updated

Thom · October 22, 2015, 09:03:40 PM

Same here - verbaltech2 witness and all seed nodes updated to latest commit.

Riverhead · October 22, 2015, 05:55:15 PM

Quote from: ElMato on October 21, 2015, 07:37:03 PM
ElMato Updated
Blockchain replayed automatically because of db upgrade.
Done reindexing, elapsed time: 37.57736299999999829 sec

That kills my 57.7 second reindex :P.

Anyway, riverhead updated to latest commit.

twitter · October 22, 2015, 05:47:34 PM

bue ( "id": "1.6.25") has been updated to v2.15.294.

It was required --resync-blockchain .... replay does not work... :) and missed lots of blockes

asimov · October 22, 2015, 05:40:34 PM

Witness asimov updated to last version v.-2.15.294.
Ready to run!
Thanks!

ElMato · October 21, 2015, 07:37:03 PM

ElMato Updated
Blockchain replayed automatically because of db upgrade.
Done reindexing, elapsed time: 37.57736299999999829 sec

bytemaster · October 21, 2015, 05:48:44 PM

New release required (witness only)

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

cube · October 19, 2015, 10:12:56 AM

A telegram group is created for the purpose of disseminating alerts and important/urgent messages. The group is named 'BTS Witness Alerts' and in operation. Most of the active witnesses have registered with it, except maqifrnswa, delegated-proof-of-steak (dev), and delegate.btsnow (dev).

A similar private group 'Bitshares Witnesses' is created in Slack as a backup channel.

My skype id is bitcube7. The problem I have with skype is that it is a memory hogger (memory leaking?) and it slows down everything in my PC.

iHashFury · October 19, 2015, 09:29:38 AM

witness: delegate.ihashfury

Telegram: @iPerky

Harvey · October 19, 2015, 02:12:19 AM

Witness node: harvey-xts
Skype account: maxweizhao

puppies · October 18, 2015, 04:35:57 AM

One of the things I've noticed on telegram is that even if I have the channel muted I will still receive a notification if someone mentions with the @

triox · October 17, 2015, 06:31:20 PM

The telegram chat is great and the bot works wonderfully but it's too general for an emergency channel. I often find myself muting it for 8 hours at a time, because there's just too much chatter to keep up with. The same happened to the nullstreet slack group back in the day, it became impossible and pointless to follow. An emergency/alert system has to be heavily curated, used very scarcely and impossible to ignore. A restricted forum thread that witnesses subscribe to fits the bill.

mindphlux · October 17, 2015, 04:49:15 PM

Yes please, BM, please join us on telegram, the majority of the witnesses are already there.

Also, I think any witness who is NOT in our primary telegram channel shouldn't be voted in since he can't react to events happening in realtime. We're very well connected and almost a family now. We're self-organizing.

fav · October 17, 2015, 04:42:47 PM

Most witnesses are in telegram. Also, many don't use Skype due to privacy concerns.

Come to telegram please BM instead of trying to change an already established communication channel

Thom · October 17, 2015, 02:23:28 PM

I'm on Telegram and it's working well for me to receive notification of missed blocks. I would like to add other witnesses to my Telegram contacts for chat, should real-time coordination be necessary.

BM, get it for whatever platform you prefer: https://www.telegram.org/

If there is a real emergency, you have seen how congested and slow this forum can get. Telegram is also encrypted.

Bhuz · October 14, 2015, 09:12:55 PM

Quote from: spartako on October 14, 2015, 09:05:12 PM
We already set up a telegram group for witness with a bot (spartako_bot) that notify when witnesses miss blocks. We are already 10 active delegates. If you give us your telegram nick we add you

Yes pls, join us

Quote from: ElMato on October 14, 2015, 09:10:07 PM
Telegram group (plus spartako_bot) is working really good for witness coordination.
I'm already in.

+5%

ElMato · October 14, 2015, 09:10:07 PM

Telegram group (plus spartako_bot) is working really good for witness coordination.
I'm already in.

betax · October 14, 2015, 09:06:53 PM

Quote from: spartako on October 14, 2015, 09:05:12 PM
We already set up a telegram group for witness with a bot (spartako_bot) that notify when witnesses miss blocks. We are already 10 active delegates. If you give us your telegram nick we add you

Telegram is good as you don't have to reveal your skype address here, but if we setup skype, can we do it via pms.

betax · October 14, 2015, 09:05:20 PM

subscribed and running (not voted) a node and a witness.

spartako · October 14, 2015, 09:05:12 PM

We already set up a telegram group for witness with a bot (spartako_bot) that notify when witnesses miss blocks. We are already 10 active delegates. If you give us your telegram nick we add you

bytemaster · October 14, 2015, 08:54:33 PM

This thread should be followed by anyone operating a full node or anyone interested in keeping tabs on network issues.

If there are problems with witnesses that need coordination to resolve, that coordination should happen in this thread. If you are a witness you should also post your skype ID to receive notifications / real time discussion of events.

Witness Alerts and Status

iHashFury