From 0057b622167c6d1e6b0feec6ed00dfa862067996 Mon Sep 17 00:00:00 2001 From: j pimmel Date: Fri, 15 Nov 2024 18:53:10 +0100 Subject: [PATCH] Last protocol updates --- .../2024/sprint-kickoff/2024-11-15-Flow-Sprint-Kickoff.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/agendas/2024/sprint-kickoff/2024-11-15-Flow-Sprint-Kickoff.md b/agendas/2024/sprint-kickoff/2024-11-15-Flow-Sprint-Kickoff.md index 667f324f7..8beeb2c49 100644 --- a/agendas/2024/sprint-kickoff/2024-11-15-Flow-Sprint-Kickoff.md +++ b/agendas/2024/sprint-kickoff/2024-11-15-Flow-Sprint-Kickoff.md @@ -152,6 +152,9 @@ Cycle Objective(s): - [EFM Integration Test Part 2 ](https://github.com/onflow/flow-go/pull/6424) - [Node ejected before epoch recovery](https://github.com/onflow/flow-go/pull/6632) - [Create integration test where DKG and consensus committees form a symmetric difference](https://github.com/onflow/flow-go/issues/6645) + - [Benchnet testing EFM recovery](https://github.com/onflow/flow-go/issues/5945) + - [Investigating service event verification bug revealed by Benchnet testing](https://github.com/onflow/flow-go/issues/6622) + - Finding a resolution which is low-enough effort and also compatible with HCU upgrade * Data Availability - KROK Team @@ -180,6 +183,8 @@ Cycle Objective(s): * EFM Recovery - Wrap up outstanding PRs currently under review - [Implement last planned integration test](https://github.com/onflow/flow-go/issues/6645) + - Resolving the VN events chunk verification [bug](https://github.com/onflow/flow-go/issues/6622). Still some uncertainly on which approach we will take. + - Resume Benchnet testing * Data Availability @@ -202,7 +207,7 @@ Cycle Objective(s): **Done last sprint** * Update Hyperlane validators to latest version and confirmed path to launch -* Diagnosed rate limit issue that was blocking Snag when using Flow EVM +* Diagnosed rate limit issue that was blocking Snag when using Flow EVM via Thirdweb **This sprint** * Finalize multi-sign approach for Hyperlane and launch cbBTC bridge