## Update

This last week I worked on:

- adding gossip message validation [#331](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/331)
- adding telemetry to the node [#348](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/348), with prometheus and grafana for observability [#354](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/354) [#355](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/355)
- improving the performance of our in-memory fork-choice temporary storage [#357](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/357)
- adding dependencies required to run [`etop`](https://www.erlang.org/doc/man/etop.html) (a module with a functionality similar to Linux's `top` command) [#346](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/346)
- fixing a flaky networking test [#347](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/347)
- improving the makefile experience [#345](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/345) [#351](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/351) [#352](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/352)

With telemetry and `etop`, we can start actively viewing the performance of the networking modules, along with general VM health (memory, CPU, and messaging queue lengths).

## Next steps

I'll be checking the data retrieved from telemetry to make some easy improvements like [#357](https://github.com/lambdaclass/lambda_ethereum_consensus/pull/357). After that, I'll continue work on the state transition function that all contributors have already been working on! With this, we should finally be able to have a syncing consensus node.