Tomas Zemanovic

@juped thanks! I'll take a look

it's quite strange, I can reproduce it getting stuck locally, but the command it gets stuck on is: ``` cargo build --message-format=json --package anoma_apps --manifest-path anoma/Cargo.toml --features ABCI --bin anomac...

on another try locally, it got stuck on building anoman :/ CI 2nd try passed though

this is currently blocked, but not a priority as it's only used in intent gossiper

it's integrated in the CI, but it currently fails (it is allowed to fail in the CI)

related to #634

Before we have this, one can use `cargo install --path ./apps --no-default-features --features std --debug`. (we have to specify the features, because the "dev" feature is currently enabled by default...

The "dev" has been switched off by default in #595, the new command is just `cargo install --path ./apps --debug`

The matchmaker is no longer in wasm and it is guaranteed to run from a single thread so there are no data races (it can spawn more threads itself, but...

Another thing we might need to check here is that wasm code doesn't use any internal memory other than what it can get from the host environment. We can also...