-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protocol Team Pickup Notes #14
Comments
|
|
|
|
For me pretty similar to Seb:
|
I had done this exercise on a notepad at home, tucked in my laptop, but for posterity it was:
When I get back, I'll be:
And then we have a list of work for the Stability Milestone -- I am working through this now, I've now got the branch fully functional and now expanding test coverage before seeking approval/merge. |
Mon, Jan 6, 2024 - Kickoff Meeting (see above for more granular task lists) Vinod - Resolved testing issues around Isthmus presumptioms about pre-Isthmus blocks. Added details around to ticket. Currently working on getting Kurtosis to work w/Isthmus local fork with Slipper and team. George - See above for tasks but primarily supporting superchain and Holocene activation Seb - Supporting Unichain and to get log access. Just waiting for a way to access the full logs via VPN to look into issues. Working with George on recovery mode for sequencer after incident. Also looking to get op-geth merges in. Emilia - Is looking to pull in some folks around reth bug. Group suggested tagging a few folks who may have more context (clabby, etc) Axel - Focused on supervisor and testing refactor which is nearly complete (see above for complete task list) Aaron - Reminder that CDMX proofs spike is next 2 weeks so folks may be a little less communicative than usual but I can help with communication so ping me whenever! |
This issue is meant to track various in progress things that we don't want to forget about after the holidays. We will use the things documented in this ticket to seed the next kickoff meeting in the new year.
The text was updated successfully, but these errors were encountered: