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

feat(data): Block Production #35

Closed
mds1 opened this issue Aug 10, 2023 · 3 comments
Closed

feat(data): Block Production #35

mds1 opened this issue Aug 10, 2023 · 3 comments
Assignees

Comments

@mds1
Copy link
Owner

mds1 commented Aug 10, 2023

This issue is eligible for a bounty paid out in ETH on OP Mainnet. Read CONTRIBUTING.md to learn how to qualify.

We are only focused on things that affect execution:

  • Block time
  • Gas limit and pricing (1559) rules (this might be some duplicate data from feat: gas costs #31 so consider how to reuse the data). For non-1559 chains this is a single gas limit value, for 1559 chains it's a gas target and a gas limit
  • Consensus mechanism, since this enables e.g. multi-block MEV
  • Finality definitions / reorg risks
  • Censorship / trust assumptions on e.g. sequencers. Maybe can outsource / link to L2Beat here since I think they have a lot of data around this
  • Timestamp manipulation
@ayushm2003
Copy link

I would like to take this up

@mds1
Copy link
Owner Author

mds1 commented Sep 29, 2023

Thanks! Just tweaked the description. Feel free to DM me on telegram at msolomon4 to agree on a bounty amount and any other questions you have. My suggested plan would be:

  • Open a draft PR that adds the new types along with the data for mainnet and at least one of the other chains. We'll make sure we agree on the data and data types
  • Then, add the UX portion to the PR to actually render the data in a new section

@mds1
Copy link
Owner Author

mds1 commented May 20, 2024

Closing this issue as part of the move to automated data collection in #62. With the new architecture the data here will likely be sliced differently in some TBD way, so will create a new issue for that in the future

@mds1 mds1 closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2024
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

2 participants