# EPF Cohort 6 - Week 17 & 18 Update

As we move towards PQ Devnet 1 that is going to happen around Devconnect (Nov 15 tentatively), I have planned out the following areas I want to champion going into this devnet:

1. [New Hash Sig Interface](https://github.com/b-wagn/hash-sig/pull/89/files)
2. [Signing Integration](https://github.com/ReamLabs/ream/issues/848)
3. [PQ Devnet 1 - LeanMetrics](https://github.com/leanEthereum/leanMetrics/pulls)
4. [Integrating test vectors for spec testing](https://github.com/leanEthereum/leanSpec/pull/76)

As I was blocked on some of these due to the spec updates not being merged, I spent my time improving the developer experience on the Ream codebase.

## Week 17 & 18

I started working with the [Ream Quickstart Doc](https://github.com/ReamLabs/ream/pull/860) that aims to give a seamless setup experience to a new developer working on Ream. It has commands to setup a lean node, a lean node with metrics and a docker compose with 4 lean nodes from different client teams (local-pq-devnet repo).

As I made the push for this I found that my CI was failing due to an issue in the hash-sig library where due to a dependency on getrandom, the project would fail to build for zkVMs. I started investigating the bug and found the origin to be one of the functions in Plonky3. I created a test repository to test my theory out which is linked in the issues I created in hash-sig and Plonky3. I also found a workaround for this which is currently implemented in Ream [here](https://github.com/ReamLabs/ream/pull/861). Issues have been created in hash-sig and Plonky3 to fix this and an issue in Ream to remove the workaround once the problem is fixed upstream.

I also worked on integrating a spec test: `process_attestations_justification_and_finalization`. This test was failing as Ream implements validation from 3SF-mini that is not implemented in the leanSpec and this discrepancy required me to tweak the test to pass in Ream. However, I would like to fix this in the leanSpec going forward.

## Successful PQ Devnet-0

I want to mention that Ream, QLean and Zeam were able to successfully interop in Cambridge and lead to a successful PQ Devnet 0. This was a great step forward for the Lean Consensus effort.

Further details on this interop can be found here: [PQ Devnet-0 Doc](https://hackmd.io/TahybBLUTcukOZ_51_FDdg) and [PQ Devnet-0 Twitter Post](https://x.com/ReamLabs/status/1981616044537168035).

I was honored to be mentioned in the credits in this doc! :)

## Resources

1. [PQ Devnet-0 Twitter Post](https://x.com/ReamLabs/status/1981616044537168035)
2. [PQ Devnet-0 Doc](https://hackmd.io/TahybBLUTcukOZ_51_FDdg)
3. [Ream Quickstart Doc](https://github.com/ReamLabs/ream/pull/860)
4. [getrandom bug failing to compile workaround](https://github.com/ReamLabs/ream/pull/861)
5. [Related Issue created in Plonky3 repo](https://github.com/Plonky3/Plonky3/issues/1089)
6. [Related Issue created in Hash-Sig repo](https://github.com/b-wagn/hash-sig/issues/90)
7. [Linter Default Variant fix](https://github.com/ReamLabs/ream/pull/863)
8. [CI always failing on forks fix](https://github.com/ReamLabs/ream/pull/865)
9. [process_attestations_justification_and_finalization test PR](https://github.com/ReamLabs/ream/pull/866)