Fusaka will fix this. But also, safety first is of the utmost importance for Fusaka. The core feature, PeerDAS, is trying to do something pretty unprecedented: have a live blockchain that does not require any single node to download the full data. The way PeerDAS works is that each node only asks for a small number of "chunks", as a way of probabilistically verifying that more than 50% of chunks are available. If more than 50% of chunks are available, then the node theoretically can download those chunks, and use erasure coding to recover the rest. In the first version, there are two cases where the full data of a block still needs to exist in one place: (i) initial broadcasting, (ii) reconstruction, in case a publisher publishes 50% <= p < 100% of a block. But these roles are untrusted: we only need one honest actor to do them, if there are also 100 dishonest actors the protocol simply bypasses them. And different nodes can perform this task for different blocks. In the future, cell-level messaging and distributed block building will allow even these two functions to be distributed. This is all new technology, and the core devs are wise to be super cautious on testing, even after they have been working on this for years. This is also why the blob count will increase conservatively at first, and then become more aggressive over time. But it is the key to L2 scaling (and eventually L1 scaling, once the L1 gas limit goes high enough that we have to put L1 exec data into blobs)