#211 Pichiu-2102 genesis state reset on Kusama
We post a new batchCall proposal for this issue. https://kusama.polkassembly.io/proposal/69.
This proposal for Pichiu(Kylin canary) genesis state reset on Kusama.
Pichiu is the winner of the #31-35 auctions. ParaId 2102, Slot 32. https://parachains.info/auctions/kusama-31-35
We would like to launch on Kusama before 05/16/2022 but cannot for the following reasons:
- During the upgrade from 0.9.12 to 0.9.18, we lost the ability to do so. The genesis state hash did not match.
- We would like to adjust the total supply amount from 50M to 100M.
State preimage hash: **0x3ad9336915ecedeca1a1e491ea9f83c678f15b52b75923c3bc155505e0cdba66**
New state&wasm resource on **https://github.com/Kylin-Network/kylin-collator/tree/main/res/kusama**
Another proposal for wasm reset: https://kusama.polkassembly.io/proposal/68.
more details: https://kusama.polkassembly.io/post/1533
Show More
Overall 66 % of users are feeling neutral. This proposal aims to accomplish what was already achieved by referendum 205; thus, it should be rejected. A new batch of proposals is being considered, and if approved, previous ones like #67 and #68 may need cancellation. For endorsement, additional contextual information is requested before voting on the new proposal at https://kusama.polkassembly.io/proposal/69.
Overall 33 % of users are feeling against it. The submission of forceSetCurrentHead and forceSetCurrentCode as separate proposals was not ideal, with a better approach being one batch call like Proposal 65. However, due to time constraints, the suggested batch will require motion and fast-tracking by the TC for approval.
AI-generated from comments
Please add the contextual information to this proposal here in order for the community to endorse and vote.
Hey Pichiu,
It looks like you submitted forceSetCurrentHead and forceSetCurrentCode as two seperate proposals. It would have been better to execute this as one batch call. An example of this can be found with Proposal 65.
Also, given the requested timeframe the suggested batch will need to be submitted via motion and fast-tracked by the TC if they are so inclined.
The floor is opened for other suggestions.
Thank you, sir! If we post a new batch proposal, do these two proposals #67 and #68 need to be cancelled?
A new batchCall for forceSetCurrentHead and forceSetCurrentCode proposal will post, maybe we need to cancel this proposal!
Vote for the new proposal https://kusama.polkassembly.io/proposal/69.
Thanks, cancelling isn't an option. We'll have to vote to reject these when the time comes.
@All: what this proposal aims to do was accomplished by referendum 205: please note the info above and make sure to reject this proposal. Thank you.
Discover similar proposals
