Open benaadams opened 2 months ago
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
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
Similar request in Besu https://github.com/hyperledger/besu/issues/7683
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