be classified as an emergency as it's not fixing a major security issue or something and it's been known to be coming for a long time now. Why not had it posted a week ago already?
Emergency in this case may mean that upgrade must be done ASAP to meet with some white label integration deadlines. But still, we need to define word "emergency" in order to exclude situations as current one.
Sure, could be, but this is a known upcoming upgrade for a long time already. Could have been posted on CW some time ago. Even if all the details were not yet ready, the general changes could be already up there.
actually I agree, it kinda saddens me that this proposal is qualified as emergency, but it doesn't match the "any security-related threat or chain-breaking code that needs updating" description from prop 29, and according to prop 12, the community should vote NWV for such a proposal, even it's a good thing. also, not having a CW thread limits the community's ways of providing feedback to the team regarding the proposal. IMO proceeding with CW thread on a proposal would work out waaay more nice
All of the code for the upgrade and changes to hub have been visible for past months, community members such as freqnik has been going through hub revisions as well. This is not a sudden upgrade or announcement this has been the most anticipated proposal for past months
Also a reason why the team could have submitted a cw thread
Will the staking module change?
Agree. This is not an emergency proposal.
Обсуждают сегодня