-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add New Command for Submitting Upgrade-Asset-Canister-Proposal Without Bash Script Payload Encoding #243
base: master
Are you sure you want to change the base?
Conversation
Also, Clippy fails with
|
Change summary option description Co-authored-by: Severin Siffert <[email protected]>
Delete wrong comment Co-authored-by: Severin Siffert <[email protected]>
Hi @sesi200. Thank you for the review. I fixed them. |
Looking great, thank you very much, @ClankPan! In the PR template you have the checklist what still needs to be done: documentation, and a small test. Would you mind adding these as well? Then this is ready to merge. For prior art, have a look over here: https://github.com/dfinity/quill/pull/171/files, files |
CI complaints (not sure if you can see it as an external contributor):
|
I don't follow GH notifications reliably. If you want me to have another look please ping me on the forum |
Hi Dfinity devs, I'm working on KinicDAO.
This PR adds a new command to quill sns that allows submitting an upgrade-asset-canister-proposal without payload encoding in a bash script.
Description
I have added a new command file,
src/commands/sns/make_commit_proposed_batch_proposal.rs
, and modifiedsns.rs
to integrate the new command.This new command accepts evidence in hex format directly and uses a function ID as an argument. This simplifies the process by eliminating the need for complex Candid encoding in bash scripts, as discussed in this thread.
This PR is related to issue #242.
Testing
We tested the command locally using sns-testing and on our SNS asset canister. The proposal here was submitted using the custom command.
To test the command in your local environment, follow the instructions in issue #242.
Checklist