Back to Whitelisted Caller
Executed

#374 Enable async backing on kusama

Proposer:
alexggh
 
in Democracy
4th Apr '24

This referendum is meant for enabling async-backing on kusama, more information about what is async backing and what this parameter changes will do can be found here async backing

Currently on kusama, all async backing logic has been enabled since v1.1.0 runtime was enacted, but it is running in sync mode, parachains can produce block only at 12s rate.

After this referendum parachains can decide to produce blocks at 6s rate, by following this guide https://wiki.polkadot.network/docs/maintain-guides-async-backing, but that is not mandatory, they will still run at 12s rate without any changes needed on their side.

Testing done

Async backing has been running on Rococo since December 2023 and on Westend since February 2023 with all system parachains migrated to produce blocks at 6s rate.

Our final checklist enablement can be found here: https://github.com/paritytech/polkadot-sdk/issues/3226

Dependencies

Some critical fixes for async backing are in the upcoming v1.2 runtime release, so this referendum is configured to be enacted AFTER v1.2 https://kusama.subsquare.io/referenda/373 release has been enacted.

Whitelisted by: https://kusama.subsquare.io/fellowship/referenda/70

Known issues

No critical issues are known at this moment, however since the async backing subsystems in sync mode has been enabled a few issues that have arosed, this referendum won't change anything regarding that.

  • There are still around 3-5% validators in the active set that are not upgrade, so when it is their turn to back they won't back anything, and if 2 out of 3 nodes are in the same backing group the group won't be able to back the candidates it is assigned to. Action Un-upgraded validators please upgrade to something higher than 1.8 node version.
  • New validators entering the active set will get 0 backing point the first session they enter, Action No action needed it has been fixed with and will be included in 1.2 runtime release.
  • Validators were accidentally changing they network-key(PeerId) at restart/upgradge which made them to not be properly discovered by the network for 36h and get 0 backing rewards. Action Double-check your validators doesn't do that, the network key is persistent next to the db so make sure it gets persisted across restarts, more details

Show More

Proposal Passed

of 3

Summary
Passed
99.9%Aye
AyeNay
0.1%Nay
Ayes(219)
808.64K KSM
Nays(17)
1.19K KSM
Support
806.16K KSM
Voting Details
Approval0.00%Threshold0.00%
Support0.00%Threshold0.00%
Please Log In to comment

Discover similar proposals


#508
KSM

Remove Gabe from the fellowship

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.

See More

24th Mar '25

Fellowship Admin

Fellowship Admin

#508 Remove Gabe from the fellowship
KSM
24th Mar '25

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.

Invarch failed to provide the first two, so Gabe, a founding member of the team, does not meet the ethical standards required to have a voice in the Fellowship.

TENETS (extract from the fellowship manifesto)

"Members are expected to faithfully uphold the following tenets.
Clarifications to the rules should be in agreement with these tenets. Acting in clear breach of these tenets may be considered by voters as grounds for non-promotion, demotion or, in extreme cases, exclusion from the Fellowship.


(1) Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it.
(2) Respect the philosophy and principles of Polkadot.
(3) Respect the operational procedures, norms and voting conventions of the Fellowship.
(4) Respect your fellow Members and the wider community"

See More

#509
JayChrawnna
Deciding

KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!

See More

24th Mar '25
68%

Treasurer

Treasurer

#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
JayChrawnna
24th Mar '25
68%

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

  1. Tests - Smart contract test
  2. Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
  3. Basic UI - A basic UI for interacting with the smart contract

Milestone 2, UI + XCM:
$9,900
1 month

  1. Tests - tests for all features
  2. User interface design - UI design
  3. XCM transfers - XCM transfer assets in UI
  4. Fixed amount transfer only - Allow fixed amount transfers in the UI

Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months

  1. Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
  2. Public documentation - Documentation for using Kusama shield and developer integration documentation
  3. Test - tests for contract
  4. 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