Working on the Rust node of @MinaProtocol, week 2. We are a bit more active than last week, even though we had a few unrelated meetings. We end the week with a few pending pull requests, simply because we have to wait for the CI. And we will also have one person focusing on the voting website for the coming HF. Otherwise, the activity would have been higher. You can see the pending CHANGELOG here for the next release: The new release won't have any new feature to be honest, compared to v0.16.0. Next week, we will focus on the CD and spawning a few block producers on dev-net. We will have a better infrastructure in place to automate our workflow. This week has been focused a lot on the CI and starting the website for three personas: - Engineers working on the codebase - Node runners/infrastructure. - Researchers - we will probably move it to the mina protocol website later to avoid duplication. We are now in sync with the latest OCaml node release in the test suite, 3.2.0-beta1. The website is being polished a bit before officially announcing it - working on the content. We are also cleaning the GitHub issues, and tagging the ones we will prioritize. The work can be followed day-to-day using the issues: When an issue is assigned to someone, it means it is being worked on. Two team members are porting changes that were implemented in forks used by the node: - - The second one will also have a future impact on o1js, but this is not the first goal - do not expect it soon. We are also tagging the parts of the codebase that will need to be changed to support the next hardfork. I probably forget many things. To keep being up-to-date, I recommend you to check: - check CHANGELOG - the activity on the GitHub issues - the activity on the pull requests We will have a dashboard with the projects soon. I am a bit delaying this to be honest - I should not, I know. We're building at @o1_labs.