Teambeam github1/1/2024 We would like to thank the following community members for having helped us to handle this situation with humor and self-depreciation.We would like to thank Sparkpool and Beepool for cooperation and swift decision-making.We would like to thank the Beam community for understanding and support.By the time of this writing, blocks are processed normally and hashrate returned to similar levels as before the incident.No Beam transactions were processed between 9:13 AM until 2:29 PM GMT.No Beam blocks were produced from 9:13 AM until 11:42 AM GMT.03:58 PM (GMT): Team Beam released the Agile Atom Hotfix that solves the issue.Transaction processing resumed (see block 25820 with 1019 outputs.) 02:29 PM (GMT): Sparkpool independently built Beam nodes from source and deployed to production.Community and mining pools were notified. 01:59 PM (GMT): After testing, the code was committed to Github.14:02 TeamBeam darf spielen 00:15 TeamBeam - was. 12:00 PM (GMT): Beam’s Dev Team coded a fix and started testing. 07:12 Automatically renaming the default git branch to devel.11:42 AM (GMT): Sparkpool and possibly other pools have independently created a fix and continued creating blocks without processing the transactions (empty blocks) and mining continued.The root cause of the issue was identified. 11:02 AM (GMT): Beam’s Dev Team succeeded to reproduce the issue.10:22 AM(GMT): After confirming the issue, Team Beam issued a tweet and notified the community that the issue is under investigation.Beam developers immediately started looking into it. 9:20 AM (GMT): Team Beam and some people in the community identified that there is an issue.9:13 AM (GMT): Beam Blockchain stopped producing blocks at block 25709.The technical details of the issue and the fix are available in our Github Issue #386. ![]() The root cause of the issue was that two cloned wallets (most likely created by copying the same wallet.db file) both sent the same cloned UTXO to the blockchain, which resulted in incorrect cut-through processing and ultimately to an invalid block. The issue was identified by Team Beam and eventually fixed. Today, on January 21st, 2019, Beam Blockchain experienced a temporary stop.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |