I’m testing a frontend deployment using the sns-testing repository. I’ve replaced the test asset canister with a simple webapp build output to test the deployment. Here are the steps I’ve taken: ./setup_locally.sh Update assets entry in dfx.json: "assets": { "frontend": { "entrypo…

You can find detailed instructions and ready-to-use scripts here . Happy to answer questions if you run into problems :slightly_smiling_face:

The example used for asset canister in the repo uses a wasm and not individual assets which cause a little confusion. The only part related to updating asset canister is point 6. I’ve tried using the ./commit_assets.sh script, but did not find a way to create a SNS proposal out of the update. For…

Steps 4 and 5 are required, and I found some more WIP documentation on the next steps. Copy/pasting it here for reference: New SNS GenericNervousSystemFunctions Submit a new AddGenericNervouSystemFunction SNS Proposal to support the commit_proposed_batch API. The target canister id should be the a…

I’m having trouble with the formatting of the commit_proposed_batch command, I gave myself prepare permissions to trouble shoot. Rather than calling the proposal, I’m just trying to get the command formatted correctly: First I encode the evidence: didc encode '("255e5e9d4e2e4b29d336c7a975a03158a48…

compute_evidence produces bytes. It looks like you then converted these bytes to a hex string. Then you take the hex string and pack it into a candid message. Last, you send the candid message blob in a candid message to the canister, as evidenced by the canister saying presented evidence 4449444c00…

Great, that helped me through… Maybe its an obvious point or there is another way to format the arg, but to get the blob from the evidence, it was just a matter of adding \'s : evidence = 255e5e9d4e2e4b29d336c7a975a03158a48986efa3d25f58dc17840d888e06ef blob = blob "\25\5e\5e\9d\4e\2e\4b\29\d3\36…

Hi @Vivienne , I think I’m getting lost as I could see a wasm to gzip in the frontend .dfx folder, so I tried this route. I commited my frontend as a batch: [image] and then ran: dfx canister call OpenFPL_frontend commit_proposed_batch ‘(record {batch_id=203:nat; evidence =blob “\5f\2d\8f\ac\45…

Did you hand that canister over to an SNS? Then probably only the SNS has Commit permissions and you need to decide about the proposal in a vote. Otherwise you can give yourself the rights either via grant_permission or upgrade args (see did file for exact naming)

Yes I handed the canister over to the SNS, it was in the sns_init file. Yeah proposal in a vote is cool, how do i raise the proposal linking this commit? I can’t do it the same as the backend because I don’t have a single frontend wasm to gzip.

You need to register a generic function call (see docs here ) and then run the function with the computed evidence (see your screenshot above).

How to update asset canister after SNS proposal?

Developers

Vivienne September 10, 2024, 8:19am 19

Answered over here if someone runs into the same issue: Batch computed evidence does not match presented evidence

Topic		Replies	Views
Batch computed evidence does not match presented evidence Developers sns	46	225	September 13, 2024
SNS Updating the frontend asset canister? Developers	5	838	December 3, 2022
SNS: How do we adapt a script that's been depoying to a replica to now submit an SNS proposal instead? Command Line Tools sns	11	653	June 9, 2023
SNS Update May 22 Developers sns	2	641	May 27, 2023
SNS Asset Canister Documentation Education Documentation , sns , asset-canister	7	638	July 7, 2023

How to update asset canister after SNS proposal?

Related topics