Meeting Time: Wednesday, April 15, 2026 at 14:00 UTC (60 minutes)
Meeting Summary:
The team held a client and spec update meeting focused on DevNet 4 stability and interoperability testing. Client teams including Zim, Grandine, Lantern, ETH Lambda, and others reported progress on implementing DevNet 4 specifications and participating in interoperability testing with other clients. The spec team added numerous test vectors and implemented visualization tools through Hive for testing client compatibility and interoperability. Research and development updates included progress on Prong K3 and LeanVM cryptography work, with discussions about potential improvements to continuous integration testing environments. The team is currently in a stability period, with all client teams working to debug issues and add more comprehensive testing while maintaining focus on DevNet 4 implementation.
Click to expand detailed summary
Gajinder reported that Zim achieved interop for DevNet 4 over the weekend and is now focusing on stability and optimizations. The team is working on aggregating signatures and discussing DevNet 5 features with Anshal and Emil, including how to handle signature repacking. Gajinder also mentioned plans to produce a shadow-compatible build and conduct shadow simulations with Kamil once the codebase is more stable.
The team discussed updates on DevNet 4 implementation and testing across different clients. Shariq reported progress on testing with Zim and Grandine, focusing on stability and updating spec test suites. Ruslan mentioned implementing DevNet 4 but noted the absence of case separation testing and identified potential performance issues with recursive fabrication. Mihir shared that their team had integrated with Brandean and Zim, added new test vectors, and was awaiting the DevNet4 metric merge. Pablo reported on implementing station count caps, proof aggregation changes, and updates to Lin Multisig, while also initiating work on formalizing state transition functions in Lean.
The team provided updates on various implementations and research efforts related to DevNet 4. Shaaibu reported progress on support for dual keys, attestation, and recursive aggregation, with testing against Zim and IT Lambda showing positive results. Mercy shared that the team has implemented DevNet 4 and is testing locally for stability, with metrics implementation pending PR merge. The spec team added numerous test vectors and edge case scenarios, with plans to develop a visualization tool for test results, though test duration concerns were raised due to recursive aggregation. Research progress included work on Prong K3 and LeanVM, with additional PRs and optimizations in the pipeline.
Thomas and Emil discussed simplifications to LeanVM, including batching checks and reducing complexity. They explored the possibility of renting a server for faster continuous integration, particularly to utilize AVX 512 capabilities not available on GitHub. Thomas suggested an alternative approach of mocking aggregation for specific tests where precise aggregation testing isn’t necessary. The discussion ended with Shariq mentioning plans to show tooling integration for visualization of spec tests across clients.
Derek demonstrated Hive, a test harness tool that runs tests through Docker and produces visualized results in a workspace. The tool currently tests RPC compatibility and can run multiple clients simultaneously, with plans to expand to cover interoperability tests between different clients. Thomas suggested migrating some tests to test vectors within the spec, which Derek agreed could be done either way, noting that the current proof of concept could be adapted to test spec-defined vectors. The discussion concluded with a plan to expand Hive to include additional test categories such as p2p behavior, syncing, and RPC compatibility.
The team discussed ongoing work on DevNet 4 stabilization, with Derek presenting updates on test frameworks and integration with Hive. The group clarified that Hive serves as a black box testing tool while Kurtosis functions as a devnet assertion tool. Thomas emphasized the importance of using the lean spec client as the source of truth for most tests, though exceptions may exist for specific scenarios. Katya reported that a PR for dashboard updates is open for review, with plans to merge it by Friday, and Parthasarathy shared progress on running multiple subnets with three clients. The team confirmed they are in a stability period across all client teams and lead spec development, with plans for a cryptography event in Rome in early May.
Next Steps:
- Gajinder and Anshal: Discuss and determine the best approach for DevNet 5 block level aggregation of signatures, including how to reutilize signatures in repacking of attestations
- Gajinder and Anshal: Discuss with Emil and Thomas about the interface for block level aggregation
- Zim team: Produce a shadow compatible build once DevNet 4 codebase is stable
- Zim team: Conduct shadow simulations with Kamil after stable DevNet 4 build is ready
- Thomas and Emil: Discuss block scenes for DevNet 5, potentially in next week’s call
- Mercy: Send message to Thomas about visualization tool for client test results
- Thomas: Respond to Mercy’s message about visualization tool today
- Thomas: Check and regenerate production keys after latest Post-Aidon update to fix production test vectors
- Thomas: Investigate test duration issues, particularly related to recursive aggregation in DevNet 4
- Thomas and Emil: Consider renting a dedicated server for faster CI with AVX 512 support
- Shariq/Derek: Continue updating Hive integration and work on matrix test this week
- Shariq/Derek: Present matrix test results in a future call
- All client teams: Aggressively integrate with Hive testing framework
- Derek: Send links to Thomas for any tests discovered that are not in LeanSpec so they can be added to the spec
- Katya: Merge metrics PR by Friday this week at the latest
- All teams: Review and comment on Katya’s metrics PR for DevNet 4
- Parthasarathy: Include additional clients in DevNet 4 testing today and share logs once stable
Recording Access:
- Join Recording Session
- Download Transcript (Passcode:
4mKd*v0.) - Download Chat (Passcode:
4mKd*v0.) - Download Audio (Passcode:
4mKd*v0.)
YouTube recording available: https://youtu.be/ul6VepXd98o