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

chore(protocol): change maxBlocksPerBatch to 768 to support 0.5s average block time #18768

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

dantaik
Copy link
Contributor

@dantaik dantaik commented Jan 14, 2025

If the average L2 block time is 0.5 second, then one epoch is 32*12 = 384 seconds, which means 768 blocks.

@dantaik dantaik marked this pull request as ready for review January 14, 2025 12:18
@dantaik dantaik changed the title maxBlocksPerBatch: 768 chore(protocol): change maxBlocksPerBatch to 768 to support 0.5s average block time Jan 14, 2025
Copy link

maxBlocksPerBatch: 768

Generated at commit: 153e32b27ebf156cdb1d97e37bd989d1d38f2820

🚨 Report Summary

Severity Level Results
Contracts Critical
High
Medium
Low
Note
Total
3
3
0
10
40
56
Dependencies Critical
High
Medium
Low
Note
Total
0
0
0
0
0
0

For more details view the full report in OpenZeppelin Code Inspector

@dantaik dantaik merged commit 82f45da into pacaya_fork Jan 15, 2025
10 checks passed
@dantaik dantaik deleted the maxBlocksPerBatch branch January 15, 2025 07:18
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

Successfully merging this pull request may close these issues.

2 participants