-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Design review] Jovian + Karst: Consensus influencing event nonces #183
Comments
Thank you for this @mdehoog! I had an initial question: Could this review wait until the week of January 20th? I ask as this team is currently at an offsite and working on a high-priority project until then. So we're doing our best to minimize context switching and disruption. That said, if you feel this is urgent please let me know your constraints and I will do my best to find a solution that works for all! 🙏 |
Hi @op-aaron, thanks for helping triage this. I don't feel this is particularly urgent, however I plan to be on parental leave from next week (for 4 weeks) so my availability will be more limited, thus this week is preferred from my side. However I can plan to have some meetings specifically about getting this change out in Isthmus during my leave if it's going to be hard to schedule this week. Also I believe that Isthmus was hoping to be code-complete by Jan 15th, so week of Jan 20th would be too late? Let me know if that's a false assumption. |
Hey @mdehoog - At this point, there isn't any chance of getting this change into the upgrade scheduled for Cycle 34: Sorry if the hard fork inclusion process wasn't clear. Our goal is to have regular enough L1 upgrades + hard forks so that they can simply happen on a regular enough cadence that even if a change doesn't make it into a given HF, it won't be painful to wait get it included in the next upgrade |
Okay, I can target Jovian if needed. My understanding was that the deposit queue was still being considered (and is mentioned in the tracker ticket). This work was meant as a replacement / stand-in for that, as it's one of the pieces of a deposit queue implementation. |
Thank you for the clarification @K-Ho! @mdehoog - Unfortunately I'm unable to book this team before the week of January 20th. Some options for a 30-minute meeting that week are:
Please let me know if any of those times work for you and the best email to send the invite to. Of course, if you would prefer to wait until you are back (or these don't work) please let me know and I can provide some avails for your preferred week. Thank you! |
@op-aaron no problem, given we're moving to Jovian there is no real urgency on this. Anytime in the week of Jan 20th works for me. I'll be in AEDT hours, so after 12pm PT is preferred if possible. |
@mdehoog - Thanks for the quick reply. It looks like the earliest availability we have after 12 pm PT would be on Monday, January 27th at 12:30 pm PT. Would that work for you? |
Yep that works for me, thanks. |
@mdehoog - Done! ✔️ You should receive an invite at your coinbase email and have permission to invite others from your team if you'd like. Please let me know if you have any questions or issues with the invite. Have a good design review! |
Title of Meeting
Jovian + Karst: Consensus influencing event nonces.
Date, Time and Duration
January 27th at 12:30 pm PT
Link to design doc
PR: #182
Additional Context
Tracker issue: ethereum-optimism/optimism#13543
Requested Attendees
@tynes @protolambda @ajsutton @sebastianst
The text was updated successfully, but these errors were encountered: