blob.NewBlob will reject > 2 MB blobs even if the square size is increased

[rootulp]

Context

celestia-node enforces a max blob size of 1.97 (1974272 bytes) here.

Problem

If governance votes to allow 8MB blocks via bumping:

• consensus.block.MaxBytes to 8MiB
• blob.GovMaxSquareSize to 128

then celestia-node will reject blobs that could theoretically fit inside a block.

Question

Is the max blob size check here necessary?

• If no, can we remove it and rely on error handling from consensus nodes?
• If yes, can it be made aware of the governance params and infer a max blob size based on them?

Tangent: I think it's quite complex to determine what is the max possible blob size that is submittable on Celestia b/c it depends on a number of parameters that can be changed up or down. We may consider adding an explicit constraint on the max blob size (i.e. 1 MiB) to make checks like this stateless.

[jcstein]

Isn't this max blob size bigger than consensus.block.MaxBytes | 1.88MiB set in celestia-app mainnet parameters?

[rootulp]

1974272 bytes == 1.88 MiB but the params in the specs should be updated to use the exact byte value to make that clearer.

[renaynay]

@rootulp if governance votes to increase or decrease the Max blob size, would that const (DefaultMaxBytes) get updated in the app version? If so, node just needs to import the upgrade and it will automatically adjust to the new value (which is why we point to the app const to begin with).

Please confirm if this is the case. If not, then we can decide how to proceed.

[rootulp]

@rootulp if governance votes to increase or decrease the Max blob size, would that const (DefaultMaxBytes) get updated in the app version?

No it would not. DefaultMaxBytes is the initial value (i.e. the default) for the param. Governance can modify it without a code change to DefaultMaxBytes in celestia-app.

[renaynay]

Okay good to know @rootulp , we will include a fix for this in the following release (v0.15.0) as this doesn't seem pressing for now.