Upgrade NNS Canister: qoctq-giaaa-aaaaa-aaaea-cai to wasm with hash: 8f65959b5a7fc4abcd82775d476be62c0abd8e2a9880c80ce58c234a9b57050f

Upgrade frontend NNS Dapp canister to commit 11bffada1ed28c7184042209eac67f7b6a80797a

Wasm sha256 hash: 8f65959b5a7fc4abcd82775d476be62c0abd8e2a9880c80ce58c234a9b57050f (https://github.com/dfinity/nns-dapp/actions/runs/33148458369)

Change Log

Added

• A banner in the swap participation modal states that the participant is responsible for their own legal compliance.

Commit Log

+ bash -xc "git log --format='%C(auto) %h %s' 4d44112a2..11bffada1"
 11bffada1 bot: Update snsdemo to release-2026-08-26 (#8009)
 23c149e2b bot: Update SNS Aggregator Response (#8007)
 0e7b01e97 feat(swap): add a compliance banner to the participation modal (#8008)
 038505c96 Update changelog after release (#8003)
 e9db05e0c chore(deps): bump docker/setup-buildx-action from 4.2.0 to 4.3.0 (#8002)
 28d14ebf9 bot: Update IC Cargo Dependencies to release-2026-08-20_03-30-base (#8001)

Wasm Verification

To build the wasm module yourself and verify its hash, run the following commands from the root of the nns-dapp repo:

git fetch  # to ensure you have the latest changes.
git checkout "11bffada1ed28c7184042209eac67f7b6a80797a"
git merge-base --is-ancestor HEAD origin/main && echo "OK" || echo "Commit is not on main branch!"
./scripts/docker-build
sha256sum nns-dapp.wasm.gz

You may also want to verify the canister arguments. In the proposal they are binary, which is not very readable. Docker provides both binary and text formats and you can verify that the text format corresponds to the binary arg_hash field in the proposal.

cat nns-dapp-arg-mainnet.did
didc encode "$(cat nns-dapp-arg-mainnet.did)" | xxd -r -p | sha256sum