Robin Freyler

Would this allow use cases that never need to remove keys? Currently `SlotMap` adds overhead to use cases where keys never need to be removed after first added. Maybe this...

Maybe something like encoder (= Client) and decoder (= Endpoint) because that's what they actually are.

Maybe one solution could be to execute the transaction as RPC right before actually executing it as transaction and thereby showing the RPC-based result. This might not always yield the...

You should not implement this at the moment since we are going to change the metadata format for this due to the fact that our current metadata format for storage...

This has probably already been raised but I couldn't find it in this discussion. Note that for example Rust's procedural macros could expand to non-deterministic code during compilation. I noticed...

> generate ABI definitions for them We actually only really need the ABI definitions of the root Delegator contracts since we only call that one directly. All other contracts are...

Also note that the UI was having a bug with Delegator execution because upon instantiation of the Delegator it always queried the first instantiated contract which apparently wasn't the Delegator...

Sounds good to me!

BytecodeAlliance's https://crates.io/crates/cargo-wasi also uses `wasm-opt` to post process compiled Rust targets. Could as well just use `wasm-opt-rs`.

> but honestly speaking i feel i added too many runtimes. Yeah maybe you did. I think this benchmark with so many different runtimes could even be extended into its...