BitShares Block Production Incident Report
On Monday, July 10th 2017 at 9:00am UTC, an incident occurred on the
BitShares network that caused an unplanned interruption of block
production. All block producers have been affected by a memory
corruption that was caused by an automatic resize of a flat_index
container that resulted in an unrecoverable stale state. This has
happened for the first time in over two years of blockchain operations.
After several core developers debugging the code, the cause was
identified and a patch was quickly delivered to the block producers.
Shortly after that, the blockchain recovered and new blocks have been
generated.
All transaction that made it into the blockchain prior to this incident
are unaltered!
It is absolutely necessary that everyone is aware that the nature of the
patch requires all nodes to apply the patch, accordingly, in order to
sync back with the blockchain. We recommend exchanges and third party
providers to update their back-end to tag 2.0.170710 and rebuild.
Leave BitShares Block Production Incident Report to:
Read more #incident posts
Best Posts From Fabian Schuh
We have not curated any of xeroc's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
More Posts From Fabian Schuh
- Awesome-BitShares has a new home
- New BitShares PaperWallet - Now with account registration capabilities
- Resignation as Director of PBSA
- Release Candidate 0 - python-graphenelib 1.0.0
- Experimental Pilot for a BitShares Browser Plugin (Chrome)
- [PSA] BitShares Blockchain Upgrade successful!!
- [pybitshares/uptick] How to add new on-chain features
- New email addresses for workers of the BitShares Blockchain Foundation
- python-bitshares: How to derive transaction ids
- BitShares: Clarification on recent fears, uncertainty and doubt