source

Finally, scotbot is back online :). Scotbot is using the @fullnodeupdate service, which is used to determine which node is online and working.

Sortly after the chain halt, it returned the working but delayed https://api.steemit.com node. I fixed this by adding a check for the api time. Only when the api timestamp is far behind the server time, it is considered as a working node.

Adapt keychain settings

At the moment, https://steemd.minnowsupportproject.org is the only working node. So go to preferences and select the following node:

Why did the steem blockchain frooze?

The problem was fixed here: https://github.com/steemit/steem/commits/20190901-fix-curation-weight

The following lines seems be the problematic ones

cv.weight = new_weight - old_weight;
max_vote_weight = cv.weight;
uint128_t w(max_vote_weight);

In one post/comment, old_weight was bigger then new_weight on payout evaluation. This means that max_vote_weight was getting negative. When a negative integer is converted to a unsigned integer, its becoming the maximal possible number, which is for uint128_t, a really huge number. This broke then the chain.