Sometimes there's a confluence of circumstances that ends up meaning that a solo staker may be proposing, with a local EL building, and needing to include 6 blobs currently.

Because of a number of factors, this may mean a large volume of data (roughly 80-100MB for 6 blobs - corrected down after twitter discussion) being pushed out of a home internet which may only be ADSL, and this can ultimately lead to missed block proposals.

As a home staker, I would like to be able to dictate the maximum number of blobs for inclusion in a block that I'm building, so that I can have the best chance of publishing the block for inclusion.

Clearly this still needs to apply normal max rules, so if i set --max-blobs=1000, that would be invalid, but I'd like to be able to do something like set --max-blobs=3, or even --max-blobs=1 if i know that I'm unlikely to be able to publish larger volumes of data given my internet circumstances.

There's also no financial incentive for a block producer to produce large amounts of blob data, so the fact that these large objects can ruin my proposals seems very unfair. I'd rather get a block out in time than miss a proposal completely.