Celestia has switched on Fibre, a feature that lets rollups upload data directly through validators instead of posting blobs the old way. The initial release caps blobs at 128 MiB and allows up to 200 Fibre submissions per block. It's live now, not a testnet preview.
The gap between those limits and Celestia's terabit benchmark is deliberate. This first version runs smaller uploads on a slower block cadence than the benchmark demonstrated. Fibre is shipping in stages, and the numbers attached to this stage are modest.
What Fibre changes for rollups
Rollups on Celestia have relied on a standard path for getting data into the network. Fibre opens a second route: validators accept uploads directly. That's the whole pitch, and it's narrower than it sounds. The feature doesn't alter how rollups settle or how proofs work. It changes who handles the data on the way in.
The 128 MiB blob ceiling matters because rollup batch sizes vary widely. A 128 MiB cap is generous for some and tight for others, and teams will find out quickly which side of that line they're on. The 200-submission-per-block limit is the other constraint. It's a throughput number, and it's the one operators will watch once real traffic arrives.
Smaller uploads, slower cadence, on purpose
Celestia's terabit benchmark set expectations high. Fibre's first release doesn't try to match it. The initial configuration uses smaller uploads and a slower block cadence than that benchmark, which is the kind of gap that invites unflattering comparisons if you ignore the staging.
Staging is the explanation. Fibre is being rolled out in increments, and the limits in this version are the limits for now. Whether Celestia raises the blob size or the submission count next, and on what schedule, hasn't been laid out in the release details.
The validator side of the bargain
Direct uploads put more responsibility on validators. They're no longer just ordering and storing data; they're receiving it from rollups. How that workload scales is the open operational question, and it's the one node operators will answer with their hardware, not with blog posts.
Celestia hasn't published validator requirements specific to Fibre in the release details. Operators running the feature will be the first to know where the pressure points are.
What to watch next
The immediate test is adoption. Rollups have to choose Fibre over the existing path, and the 128 MiB and 200-submission ceilings will shape which ones do. Teams with large batches may wait for a later release. Teams with smaller batches have less reason to.
Celestia hasn't said when the next Fibre increment arrives or which limit gets raised first. For now, the feature is live with the numbers it launched with, and the benchmark remains a target rather than a description of what's running.
