Estimate the effect of grouping Celestia blobs into one payment
Regular PayForBlobs submissions carry transaction overhead as well as blob-size-dependent costs. Grouping can change both fee estimation and the unit that an operator retries.
Compare matching payloads
Encode three real application batches once. Ask the same client to estimate three individual submissions and one grouped submission at the same gas price. Compare total estimated gas, holding the namespace and data constant. The grouped form amortizes fixed transaction overhead but still pays for the submitted blobspace.
option A: PFB(batch 1), PFB(batch 2), PFB(batch 3)
option B: PFB(batch 1, batch 2, batch 3)
Account for the shared outcome
One rejected payment transaction affects all three batches. Track each commitment while keeping the common transaction identifier so workers cannot independently resubmit portions of an already included group. Estimates describe the candidate at the chosen settings and do not guarantee inclusion at that price.