Éloïs

> I'm not sure why --all is there. It could be just a simplification/workaround for compatibility with workspaces. What is certain is that the removal of the `--all` option has...

> I suspect that may be the case Yes, sometimes, but not systematically :) > I mean to ensure everything is built, instead of passing --all, cargo-deb should probably specify...

I need this feature for my project. This is the only reason why I cannot use `sled` and must stay on `LMDB` :/ > A big goal for this project...

Yes, there is two GH workflows, one to upgrade the typescript API code, and another one to publish any specified version. The first is already merged.

Yes, since this PR the on-chain runtime does not contain any logs: https://github.com/PureStake/moonbeam/pull/1441 the goal is to reduce the size of the runtime bytecode stored in the onchain storage. To...

> the wasm bytecode size wasn't different from the previous ones: Ok, so it's not worth it, I revert: https://github.com/PureStake/moonbeam/pull/1513

@4meta5 this is something that is still relevant to do, do we have a JIRA issue for this?

All proxy precompile functions that take an encoded call as parameter should take bounded inputs, like this PR: https://github.com/PureStake/moonbeam/pull/1656

I decided to strongly simplify these conventions, to stick to what we actually did to hotfix the 1500 runtime. And anyway if conventions are too complex nobody will apply them...

> I'm suggesting we use a "local" node instead (there is a script in package.json for that) with moon[base/river/beam]-local runtime to get the latest version It's not that simple, it...