@StrathCole
Of course I’ve reviewed it. The concerns in specific are around the upgrade handler and the testing that has been done around it, like I’ve mentioned in this proposal. The conduct of the L1 JTF’s programming leadership (particularly Zaradar) has only added to my concerns around the integrity of this release, for the reasons I’ve listed above.
@Tonu_Magi
Here. You can see my posts as Nova Validator engaging with the L1 TF (particularly Ed) multiple times about the upgrade.
It’s worth noting that Ed’s response here only happened as a result of me following up with him in the Terra Classic Validator Discord, which you may not be a member of since it tends to be focused around validator specific duties.
Note also this post from Jacob Gadikian pointing out his concerns as well around the upgrade handler, which is a concern that has yet to be addressed as well. Updated v1.0.5 upgrade - #34 by faddat
@SockPuppet
@lunaticlunclover69
@EZMehrtenz
@Lunc_Global
Put aside any dislike you may currently have for how Jacob handled the Allnodes security risk situation.
Put aside any dislike you may have for me for putting up proposals that the community disagrees with because they’re unpopular opinions that are based on facts that can be tangibly pointed to.
I have a lot to lose as a validator if this upgrade handler blows up in a way we don’t expect. Every validator does. If we end up losing state on the chain because we didn’t do the proper testing and due diligence on this release as a group of validators, that’s a big problem that we can’t really easily come back from and we’ll have failed our delegators and we’ll have failed to secure the chain.
Postponing the release so everyone can take a closer look at it and give it the proper testing it deserves, and also giving ourselves time to sort through the fact that our chain is filled with compromised validators right now, is the responsible thing for every validator to be doing.
I honestly don’t see why this is even up for debate.