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

Add max blob inclusion config for block production #7502

Open
benaadams opened this issue Sep 27, 2024 · 3 comments · May be fixed by #7505
Open

Add max blob inclusion config for block production #7502

benaadams opened this issue Sep 27, 2024 · 3 comments · May be fixed by #7505
Assignees

Comments

@benaadams
Copy link
Member

Non-commercial Internet connections are often asymmetric with faster downloads than upload speeds

This means while a solo staker might be able to validate with a high number of blobs; they might not be able to produce blocks and upload the blobs in time (upload)

Describe the solution you'd like

Add a configurable option to cap the number of blob transactions to include when producing blocks

@potuz
Copy link

potuz commented Sep 27, 2024

Can't stress enough how this is a bad option for Ethereum. Baking censorship in clients is not an option. We have the tools to decrease bandwidth needs at our reach

@benaadams
Copy link
Member Author

Can't stress enough how this is a bad option for Ethereum. Baking censorship in clients is not an option. We have the tools to decrease bandwidth needs at our reach

Missed production with 0 blobs is worse than production with 2 blobs surely?

Isn't censorship is matching capacity; would be censorship if it didn't choose the highest priory fee blob txs

@smartprogrammer93 smartprogrammer93 removed their assignment Sep 27, 2024
@benaadams
Copy link
Member Author

Similar request in Besu hyperledger/besu#7683

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants