You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of dynamic module loading, binary hash checking of Kybra canisters won't give the same benefits or guarantess as Rust/Motoko/Azle binary hashes. We'll need to come up with mechanisms to fix this.
Keep in mind that with Kybra, the binary hash will basically be useless, as much of the actual code/functionality will change and not be in the binary. Perhaps we could send the Python source code up in the binary to help with this?
We could probably hash all source code and include the hash in the binary though
The text was updated successfully, but these errors were encountered:
This shouldn't be a problem anymore, except for the python stdlib. Only on first deploy will the stdlib be a part of the binary, so the hash will change on subsequent deploys. This is a much simpler problem now
Because of dynamic module loading, binary hash checking of Kybra canisters won't give the same benefits or guarantess as Rust/Motoko/Azle binary hashes. We'll need to come up with mechanisms to fix this.
The text was updated successfully, but these errors were encountered: