Skip to content
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

Consensus-layer Call 87 Agenda #527

Closed
timbeiko opened this issue May 11, 2022 · 6 comments
Closed

Consensus-layer Call 87 Agenda #527

timbeiko opened this issue May 11, 2022 · 6 comments

Comments

@timbeiko
Copy link
Collaborator

timbeiko commented May 11, 2022

Consensus-layer Call 87 Agenda

prev: call 86

Meeting Date/Time: Thursday 2022/5/19 at 14:00 UTC
Meeting Duration 1.5 hours
live stream

  1. Merge
  2. Other client updates (if any)
  3. Research, spec, etc
  4. Open Discussion/Closing Remarks
@arwer13
Copy link

arwer13 commented May 12, 2022

I would propose to have a brief discussion on "Whether 0x01 withdrawal credentials initiated exits should be added to Shanghai along with the withdrawals" (regarding post).

@djrtwo
Copy link
Collaborator

djrtwo commented May 13, 2022

I would like to bring up the step deprecation to decide if it should be included or not
ethereum/consensus-specs#2856

@timbeiko
Copy link
Collaborator Author

I would like to discuss whether to update the Ropsten Merge TTD value. On the last ACD, we agreed to set it to 43531756765713534 such that the fork happens around June 8th. It seems the estimator we used to determine this number was wrong and this value is more likely to occur late-June than around June 8th.

There are a few options for what we can do:

  1. Keep the same TTD and increase hashrate on Ropsten significantly in the week before June 8th to ensure we hit this value during that week. Initial estimates indicate it's probably not cost-prohibitive to do this, but we should be sure and figure out who can provide mining power.

  2. Use a lower TTD value which we expect to happen around June 8th. While this may seem "obvious", we did get it wrong the first time around! We should make sure that we don't accidentally select a TTD which we end up hitting prior to Bellatrix's activation on the Ropsten Beacon Chain.

  3. A mix of 1+2, use a lower TTD value which, given current hashrate, we expect to hit around, say, June 15th, but then add hashrate to the network to hit it earlier.

@q9f
Copy link
Contributor

q9f commented May 18, 2022

Mario updated the predictions: https://bordel.wtf/

@benjaminion
Copy link

Call notes

geovgy added a commit to geovgy/pm-1 that referenced this issue May 24, 2022
Meeting notes for Consensus Layer 87 (issue ethereum#527 )
This was referenced May 24, 2022
@timbeiko
Copy link
Collaborator Author

timbeiko commented Jun 2, 2022

closed in favor of #536

@timbeiko timbeiko closed this as completed Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants