I don’t think Walrus collapses the moment Sui becomes congested, but sustained fee pressure is a real operational concern. Proof submission relies on Sui for settlement and verification.
If fees spike unpredictably, marginal node operators could struggle to submit proofs economically. That said, proofs are typically batched and time-windowed rather than per-request. This gives the system room to absorb temporary congestion.
In my Take , Walrus inherits Sui’s performance profile, but not blindly. Its design assumes variability and leans on amortization rather than constant on-chain interaction.