deuszx

Hey @HCastano , can you share any updates on this? As I describe in the issue mentioned above - not being able to use the nightly rust is a big...

Hey @pgherveou , I saw that the benchmarks have finished but I'm not sure how to interpret the results. Are there any findings regarding possible execution improvements here?

Not sure if I'm reading the [new gas benchmarks](https://weights.tasty.limo/compare?unit=weight&ignore_errors=true&threshold=10&method=asymptotic&repo=polkadot-sdk&old=master&new=pg%2Fwasmi-to-v0.32.0-beta.7&path_pattern=substrate%2Fframe%2F**%2Fsrc%2Fweights.rs%2Cpolkadot%2Fruntime%2F*%2Fsrc%2Fweights%2F**%2F*.rs%2Cpolkadot%2Fbridges%2Fmodules%2F*%2Fsrc%2Fweights.rs%2Ccumulus%2F**%2Fweights%2F*.rs%2Ccumulus%2F**%2Fweights%2Fxcm%2F*.rs%2Ccumulus%2F**%2Fsrc%2Fweights.rs) correct but it seems that quite a few methods have regressed >10%.

> I'm a bit confused about the ‘Browser Wallet’ project on this PR. What's the connection to the browser wallet? It might be worth reassessing whether these changes are still...

When you install from `main` it expects that you're working with `cargo-contract 4.X.Y`

Try `0.8.7` - it was just fixed 2 days ago. `0.8.7` is still `ink! 4` and `[email protected]`.

> What I am saying is the fact that you can have a session in CLI with multiple contracts, selecting a specific contract in the menu and making a call...

Another option is to distribute (and handle) system messages separately from user-application ones. This way we wouldn't need to implement the concept of `Skippable`/`Protected` messages at the protocol level: -...

This also means that a validator with five times the stake can cause five times the censorship, doesn't it?

Will YUL contracts be able to call (Wasm) ink! ones (and vice versa)?