I just hit the instruction limit!

[kristofer]

I started a new thread for a related topic. The wasmtime execution environment used to run the canisters should expose functionality accessible through ic_cdk to let us run wasm from wasm. So we don’t have to run a wasm runtime inside a wasm runtime like in my benchmark test.

Idea: ic_cdk should let us run wasm in wasm

I have the need to run untrusted user code in my canister, using sort of a plugin system. Currently I am running a JS runtime in the canister which allows me to run that untrusted code in a fully sandboxed secure environment. One drawback with that is that JS is quite inefficient, hitting the instruction limit is a real risk. In another thread we discussed the possibility of running wasm compiled code in the canister, effectively running wasm in wasm. This is some orders of magnitude (6) more e…