Unlock para 2281 (Kreivo)
The Incident
On Saturday, June 29, Kreivo stopped producing blocks after a runtime upgrade to version 0.13.0. This upgrade aimed to introduce pallet contracts, enable bridged DOT reception from Kusama AssetHub, and update our PolkadotSDK dependency from version 1.5 to 1.12. The main goal was to prepare Kreivo for async backing, which would reduce block times from 12 to 6 seconds.
The Issue
Despite thorough testing before the upgrade, the problem only appeared hours after enactment(at the end of the era). The current rapid development of the PolkadotSDK makes it challenging for small teams like ours to constantly update and migrate code. Our main issue stemmed from the significant version jump (1.5 to 1.12), likely missing crucial intermediate migrations.
Impact
While most of our users (DAOs) are aware of Kreivo's beta testing stage and aren't critically affected, two key exceptions are:
- Virto team: Our salaries are paid through the DAO's governance, which is currently inaccessible.
- KSM Community: This decentralized voice in Kusama can't vote on OpenGov proposals.
Proposed Solution
While this proposal is being voted on, we'll prepare an updated WASM of the runtime that fixes the issue. Unlocking Kreivo means the "manager account" will be able to do a schedule_code_upgrade
to manually set the updated parachain's code in the relay chain to match the code manually set by collators with the codeSubstitute
feature of the chainspec.
Request
We ask Kusama governance and the Fellowship to approve unlocking the Kreivo parachain so we can restore functionality. After resolution, we'll conduct a public postmortem and implement additional safeguards for the future.
We are glad this kind of issue occurred this early in the lifetime of the chain when impact is manageable and are now more convinced builders need simpler ways to manage this kind of outages, ironically I believe a "governance parachain" like Kreivo where parachains can host their governance can be a great solution to this issue as people can vote to unlock a parachain even if it has halted.
Comments (6)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (115)0.0 DOT
Support0.0 DOT
Nay (0)0.0 DOT
Hello, on behalf of the AIWeb3 DAO (the most vibrant Chinese community within the Polkadot ecosystem, with the mission to amplify the voice of the Chinese-speaking community and support Chinese content creators, ensuring it plays a pivotal role in shaping the future of Polkadot), I would like to invite you to join our weekly Twitter Space and discuss your proposal since we are not familiar with the background. Our Twitter Space is held every Tuesday at 10 AM (UTC+8) on our official Twitter: https://x.com/aiweb3dao. Please join our Telegram group if you have any questions, English TG group: https://t.me/aiweb3dao_eng and Chinese TG group: https://t.me/aiweb3dao
We will make our final decision based on the discussion and input from community members in AIWeb3.
您好,我代表AIWeb3 DAO,这个波卡生态中最具活力的中文社区,旨在放大中文社区的声音,支持中文内容创作者,确保其在塑造波卡未来中发挥重要作用。我们诚挚邀请您参加我们的每周Twitter空间并讨论您的提案。我们的Twitter空间是每周二上午10点(UTC+8), 在我们的官方推特:https://x.com/aiweb3dao. 。如有任何问题,请加入我们的Telegram讨论:英文Telegram https://t.me/aiweb3dao_eng , 中文 TG group: https://t.me/aiweb3dao。我们将根据讨论和AIWeb3社区成员的意见做出最终决定。
Twitter space link: https://x.com/aiweb3dao/status/1807637848713257059
AYEd Maybe you could explain how you ended having your blockchain locked. That would help for the global understanding.