The DeFi Trust Problem

[marc0olo]

Hey @rhythmicfields,

thanks for creating the thread. May I ask you around your background? Are you new to the ICP ecosystem or already familiar with ICP and just a late-joiner to the forum?

This is a topic that I think is VERY important. I also happily refer to following dicussion:

Let's discuss reproducible builds and code verification once again

Hey there we have some ongoing discussion around reproducible builds again. I think ever since there is a high demand to be able to verify the source code of deployed canisters as easy as possible. Although there are quite some projects providing instructions how to verify the source code via a reproducible build, this is currently not standardized and thus it is almost impossible to provide a generic service that can perform a reproducible build and check the hash of the build …

I also think that @timo will provide some bigger update for the history-tracker soon

See discussion here:

Canister history on the IC

Thanks for pointing this out. We fixed the problem with empty canisters in this updated frontend: https://history.ic0.info/ A warning: the backend changed as well, so if you added canister ids to the tracking then you will have to add them again. And you will lose old history from before the last 20 changes. This will happen again until we deploy the final version of the backend. It is still under development right now. If anyone has been tracking anything meaningfully in any old version of th…

I definitely support the effort of figuring out the main factor of slow TVL growth. I guess it is a combination of multiple things, including the trust issue. I assume it is more the issue of trust in canister code and canister controllers rather than ICP itself (which is why I was referring to the threads above )