Weekly update 2022-06-01 #6970

akhi3030 · 2022-06-04T04:24:40Z

akhi3030
Jun 4, 2022
Maintainer

Done:

@Ekleog: Started a PR instrumenting wasmer, to get feedback on how we want to proceed feat: add tracing instrumentation for basic things wasmer#131
@Ekleog: The fuzzer seems to be pretty stable nowadays, so #pagoda/fuzzer/private is ready to be opened up to all people with appropriate security clearance
@jakmeier Added my lengthy opinion on lowering gas price floor in the forum.

In Progress:

Upcoming:

@Ekleog: Finish up the wasmer instrumentation
@Ekleog: Invite everyone to the fuzzer results channel
@jakmeier: I want to write up a proposal / design document for reactive undercharging defense options. Basically, making undercharging a SEV1 instead of SEV0 in the future.
@jakmeier: Need to investigate why continuous estimations have variance.

@nagisa: Somehow integrate the benchmark that was provided to us by Aurora so that we can easily estimate the effect on performance with a real-world workload.
@matklad: Upgrading Rust to 1.61.0 chore: upgrade to rust 1.61.0 #6924
@matklad: Refactoring store APIs to ensure only small fraction of code can commit refactor: new ChainStore API #6896
@matklad: Fighting with a flaky test chunks_produced_and_distributed_2_vals_per_shard might be flaky #6920

Blockers/Discussion points:

@Ekleog: Do we have a list of all the people who should be invited to the fuzzer results channel? Should that be 2-3 persons per team who then dispatch to their team's private channel, or everyone?