Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Upgrade] Test upgrades on Rococo: using referenda system #269

Closed
2 tasks
Tracked by #254 ...
shannonwells opened this issue Jul 27, 2022 · 1 comment · Fixed by #491
Closed
2 tasks
Tracked by #254 ...

[Upgrade] Test upgrades on Rococo: using referenda system #269

shannonwells opened this issue Jul 27, 2022 · 1 comment · Fixed by #491
Assignees
Labels
chore No feature changes
Milestone

Comments

@shannonwells
Copy link
Collaborator

shannonwells commented Jul 27, 2022

Notes

To Do

  • Referenda system: chain upgrade
  • Referenda system: Storage migration
@shannonwells shannonwells added this to the Mainnet milestone Jul 28, 2022
@wilwade wilwade changed the title Test upgrades on Rococo: using referenda system [Upgrade] Test upgrades on Rococo: using referenda system Aug 15, 2022
@wilwade wilwade added the planning Discuss & point in planning meeting label Sep 6, 2022
@shannonwells
Copy link
Collaborator Author

shannonwells commented Sep 12, 2022

How to create a new proposal:

This should probably go in a markdown but it's short so I'm putting it here for now:

In a nutshell, to make a proposal through the Polkadot UI, you would go to Governance → Democracy and click “Submit preimage”.

Then you can select an extrinsic to be enacted, providing the needed parameters.
IMPORTANT: whatever extrinsic is submitted for proposal must be able to succeed as the Root origin. For example, if the proposal is to transfer a balance, you would need to submit this as a forceTransfer operation.

Once you choose the extrinsic to execute, the preimage and its hash is constructed for you. There is a storage fee for the proposal based in part on the size of the preimage.

After the submit preimage transaction is included in a block, then you must copy the preimage hash and submit it in the proposal. After the referendum passes, the extrinsic will be executed.

If the proposal is for an upgrade, then you can proceed similarly to a scheduled Sudo upgrade in which you upload the file and submit the proposal using the uploaded WASM file. Note you must still submit extrinsic for authorizing the upgrade before the proposal is enacted, as documented in the link for this issue.

Once you’ve submitted a preimage and it is included in a block, you can go to the Block Explorer panel, then copy the preimage hash by expanding the extrinsic under "recent extrinsics" and submit that.

In a dev environment, to get proposals to work, you’ll need to run the parachain with a relay chain; it doesn’t work with instant sealing.

@wilwade wilwade mentioned this issue Sep 12, 2022
13 tasks
@aramikm aramikm removed the blocked Blocked by another issue label Sep 16, 2022
@dopatraman dopatraman self-assigned this Sep 22, 2022
dopatraman added a commit that referenced this issue Oct 13, 2022
# Goal
The goal of this PR is to document a process for enacting runtime
upgrades via Polkadot's governance/referendum process.

Closes #269 

# Discussion
This PR includes scripts for proposing, endorsing, and voting on
upgrades. Authorization and enactment still must be done manually (via
Polkadot JS UI etc). It may be possible to automate these in the future.

Authored-by: Prakash Venkatraman <pvenkatraman@westmonroe.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore No feature changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants