When will it be possible to veriify the integrity of a smart contract on-chain? While the WASM hash can be checked off chain using DFX canister info, it presently cannot be checked on chain. How is it possible to trust a smart contract when the controller could update the code to perform something…

I think that’s accurate. Verifying that a canister is blackhole controlled is one option. https://covercode.ooo/ is a good start on another approach where source code can be verified and audited, and verification status of a canister can be queried.

Developers have the freedom to decide whether states like wasm hash or cycle balance should be exposed or not. I create the black hole canister exactly for this purpose: Introduce the black hole to help with canister status lookup + make them immutable

Also, once outgoing HTTP call is implemented, one can use it to call the read_state API endpoint of the iC itself to get this info.

While blackholed and controllerless canisters are suitable for some applications, it does not address all. There are usecases that support the need to detect a canister has changed its code base on chain without the developer having to relinquish control. Canister consumers could review the code b…

[image] northman: There are usecases that support the need to detect a canister has changed its code base on chain without the developer having to relinquish control Oh no, it is a typical misunderstanding of how blackhole can be used (the blame is on me choosing this name), but one can alway…

So maybe I can rephrase to ensure my understanding. Canister A is a canister with some critical code whose hash we want to check on-chain. A second canister called Canister B is created and made a controller of Canister A in addition to the existing controller. That way the existing controller ca…

Yes, you summarized it well. I’d add that the downside is “Canister B” may not be trustworthy to show the hash to a 3rd party. This is where using blackhole can help.

[image] northman: While the WASM hash can be checked off chain using DFX canister info, it presently cannot be checked on chain. Just wanted to mention that the ability to check for a controller “on chain” is on our backlog.

Developers have the freedom to decide whether states like wasm hash or cycle balance should be exposed or not. My understanding is that wasm hash is public state and should be queryable by anyone, controller or not. (Although in practice, getting the wasm hash is easier done via ingress calls, as…

Canister integrity verification on chain is missing

Developers

skilesare January 18, 2022, 7:58pm 3

This would be a good place to see some activity relevant to this request: RFC: Standardising how smart contracts expose state

Topic		Replies	Views
Is there a way to programmatically retrieve the wasm module of a canister? Developers	14	2193	December 17, 2022
Feature suggestion: Validate module hash Developers Discussing , community-consideration	19	398	July 4, 2024
Canister version validation when making an api call Developers	11	856	June 21, 2022
Verifying the code of the Internet Identity service (a walk-through) Developers	8	2834	November 19, 2021
Any way to know if a canister was updated? Developers	15	1858	January 15, 2022

Canister integrity verification on chain is missing

Related topics