Back to tech comm proposals
Council Motion#437 >> Tech Committee Proposal#126 >> Referendum#175
Executed

#126 Reduce validationUpgradeCooldown to 6 hours

Proposer:
F2i6...bjTW
 
in Tech Committee
16th Feb '22

This is a techincal committee proposal whose proposer address (F2i6trfXqFknbgB3d9wcd1X98WWdLLktmFtK8Beud75bjTW) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Show More

Council Votes

FhLM...aqhL
Aye
F2i6...bjTW
Aye
Please Log In to comment

1Comments
GLVe...F7wj
 
 
29th May '22

This TC Proposal aims to fast-track motion 484 with the following parameters:

  • "votingPeriod": 14,400 blocks

  • "delay": 600 blocks

The TC decided to fast-track this SOLELY by the fact that unfortunately motion 483 did not execute correctly: there is an issue with the Xcm origin used in the first two motions and the origin needs to be Superuser, and passed via external motion. Additionally, referendum 193, aiming to enact the same, did not enact successfully due to a similar error on submission. Please note the proposal was then approved twice by Council and once by the community in referenda queue.

Motion 484 finally tries to enact RMRK token sufficiency on Statemine. The call is the same one as the last, but now with Superuser origin, meaning this proposal will need to be voted again by the community to enact - hopefully, and given the proposal was already approved twice this can move forward faster.


Discover similar proposals


Empty Icon

No Active Proposals