faddat
March 1, 2023, 8:35am
1
If desiring to support by getting attention on the core issues, you can retweet or discuss here:
If desiring to work on the code, there is a tracking issue here:
opened 07:09AM - 01 Mar 23 UTC
bug
**Describe the bug**
Terra classic halted on this block:
* https://atomscan.… com/terra/blocks/11734001
**To Reproduce**
Unknown
**Context & versions**
Latest release
**(if applicable) suggested solution**
This issue should be used to centralize information about the halt. Useful information includes:
* sha256sums of binaries from validators
* logs from validators
* anecdotal information from developers and validators
Should speak to validators in order of their votepower. In order to bing the chain back up, you'll need 2/3rd of votepower online. So, start with the highest ranked validator, and check the version of software that they are running. If a whitelisted account was present in the halt block, but different versions were running simultaneously, this would explain the halt.
If a VaaS provider with >1/3rd of votepower was running a different version of the software, this could also be responsible for the chain halt.
I am concerned with the timing of this PR:
* https://github.com/classic-terra/core/pull/149
@inon-man may very well be correct: if binaries had already been released to validators, then it is possible that some were running a version of lunc that did not include #149. I don't know all of the other changes in the upgrade, and am looking into it now.
## Additional information
* https://github.com/classic-terra/core/compare/v1.0.5...v1.1.0
* It seems that the work on linting the repository that I did has been magically memory holed. It also seems that the main branch contains the commit that is tagged for v1.1.0.
* In emergencies, having a fully linted repository makes the code far easier to work with, because it is standardized. So, I will begin by linting.
* Todd thinks that it could be the golang version, and this is the easiest item to fix. Before linting, I will address that. https://twitter.com/blockpane/status/1630832835899822080
**These services, as well as the security incident reporting concerning allnodes.com, are funded by delegations to the Notional validator on LUNC.**
Currently I am working on pull requests:
Resolve possible golang version conflict by faddat · Pull Request #159 · classic-terra/core · GitHub ← done, may resolve conflicting go versionsCleanup to make for easier triage by faddat · Pull Request #160 · classic-terra/core · GitHub ← I am repeating work that I did months ago that was tossed out by the layer one task force
my request
Please put Notional above Allnodes, with your delegations. Please delegate to us. I figure that bringing back a $1b chain – twice, is worth some juicy delegations. Of course, if we fail, well, then everything will have simply gone to $0 anyhow, and you’ll never be able to delegate to us, except on oither chains, which have more merit driven engineering processes, where you should indeed look.
But I bet that:
we can get LUNC running again
we can transform engineering on LUNC to a merit-driven process that rigorously uses every available code quality tool so that nothing like this happens again
See, they’re not able to do anything in this situation, and harm network security.
Delegate to notional
Delegate to blockpane
Delegate to PFC
Unlike the current #1 validator, we work.
1 Like
Seems like the net is back
2 Likes
