Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.
Back to Referendum Canceller
This Referendum has been created to cancel Referendum #106
#110 Cancel #106 Kusama runtime upgrade to 9380
Description
AI Summary
Votes Bubble
Timeline
Evaluation
On Chain Info
Stats
This referendum aims to cancel referendum #106, which upgrades Kusama to runtime 9380.
A followup referendum will be proposed later to enact this runtime upgrade at a later date.
Kusama runtime 9380 contains XCM v3 which is major breaking change. We have confirmed it is not compatible with current version of Karura and expect to upgrade Karura next week to address the compatibility issue. It also removes XCM v0 and v1 support which is the only option exposed from xcmPallet. This means all the wallets and dApps are required add additional logic to detect the new version to be compatible. I don't know about others but Karura Bridge UI and Polkawallet are expected to complete the upgrade next week. However iOS release will likely take more time due to App Store review.
The Polkadot v0.9.38 release is created less than a week ago and it could be enacted in another week. This means everyone have less than 2 weeks to develop & test & release in order to compatible with the new version. While this is not an unreasonable timeframe, it unnecessarily add pressures to all the parachain and tooling teams.
Also I don't think we have any urgency on this release anyway so it should be safe to delay it until the ecosystem is ready.
Show More
Please Log In to comment
Users are saying...
Based on all comments and repliesOverall 100 % of users are feeling neutral. This proposal seeks to cancel referendum 106 for upgrading Kusama to runtime v9380 with XCM v3, a major breaking change. The Karura team needs more time for testing. Voting is encouraged at convenience. Discussion can be found HERE.
AI-generated from comments
3Comments
GLVe...F7wj
This proposal aims to cancel referendum 106, to then be submitted taking a particular block number for execution. To note, referendum 106 aims to upgrade Kusama to runtime v9380, and contains XCM v3: which is major breaking change. The Karura team has requested more time to finalise testing. Please make sure to vote at your convenience!
Discussion: HERE.
GLVe...F7wj
This proposal aims to cancel referendum 106, to then be submitted taking a particular block number for execution. To note, referendum 106 aims to upgrade Kusama to runtime v9380, and contains XCM v3: which is major breaking change. The Karura team has requested more time to finalise testing. Please make sure to vote at your convenience!
Discussion: HERE.
GqC3...m8Jj
I think it would be a bit more reasonable to vote AYE on 106 until it reaches 5% support and then ask the ecosystem to abstain so that the referendum starts confirming close to the end of its decisionPeriod. If the ecosystem complies then 106 will start confirming at block ~16,946,900. It takes 24 hours to confirm then another 24 to enact which means its enactment block wouldn't be until block ~16,975,600; that's ~10.5 days from now.
To cancel the referendum entirely would eventually require the fellowship to prepare and vote on another fellowship referendum. In my opinion we shouldn't make them do that again for v0938, especially if teams can adapt in 1 - 2 weeks.
Kusama is meant to push the envelope on innovation and XCM v3 needs to be battle tested ASAP. This upgrade certainly stirs up chaos but that's what Kusama is all about - I'd rather upgrade in ~10.5 days and break a few apps than wait for parachain teams to catch up, burden the fellowship, and have to wait another couple of weeks to see XCM v3 in action.
I can't stress enough how teams and individuals should be tracking developments on Parity's github. XCM v3 on Polkadot was merged on January 17th and for Cumulus it was merged on January 19th, plus there have been a number of forum posts about this upgrade. dApps waiting for a runtime upgrade to become an on-chain referendum is not being very proactive - XCM v3 shouldn't be delayed more than it has to be.
Voting NAY on this one.
Discover similar proposals
#509
E5qF...tqrg
Deciding
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
See More
Treasurer
Treasurer
#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
E5qF...tqrg
This RFP was adapted over several weeks on AAG to turn a treasury proposal in discussion to an RFP with refined scope and oversight.
To apply for the prize pls fill out this form.
Prize Pool: $43,000
Finder’s Fee: $2,000 **
Supervisors: $5,000
Supervisors (Bounty Curators)
- Flipchan
- Byte (Erin)
- James Slusser
Excess or unused funds will be returned to the treasury by Bounty Curators.
Timeline
Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators ✅
4 Weeks after Bounty Funding - Submission Deadline Thursday
July 31 - Project Completion (Pending Kusama Hub Launch)
Project Scope
Smart Contract Development
- A Solidity-based smart contract deployed on Kusama Hub
- ZK enabled for private deposits & withdrawals
- Compatibility with all Kusama Hub assets
User Interface
- Browser-based, mobile-ready UI hosted on IPFS
- Support for: Deposits, Withdrawals, Transfers, XCM Transfers
- Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)
Anti-correlation Attack Mitigations:
- Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
- Batch payouts for withdrawals to multiple users
Interoperability - Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.
Open-Source Delivery
- All code (smart contracts and UI) published under the MIT license
- Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
- Developer & User documentation
Milestones
Milestone 1, Initial Pools & Basic UI:
$16,200 USD
1 month
- Tests - Smart contract test
- Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
- Basic UI - A basic UI for interacting with the smart contract
Milestone 2, UI + XCM:
$9,900
1 month
- Tests - tests for all features
- User interface design - UI design
- XCM transfers - XCM transfer assets in UI
- Fixed amount transfer only - Allow fixed amount transfers in the UI
Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months
- Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
- Public documentation - Documentation for using Kusama shield and developer integration documentation
- Test - tests for contract
- V1 UI - User tested & something we can be proud of
** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.
See More
Deciding
