I think @Walrus 🦭/acc is mispriced because its Sui-posted Proof-of-Availability is being treated like continuous service assurance, but it’s really a one-time acceptance receipt. The system-level catch: PoA can prove enough shards existed when the certificate was posted, yet it does not continuously force operators to keep blobs highly retrievable with tight latency across epochs when churn, bandwidth ceilings, or hotspot demand arrive, unless there are ongoing, slashable service obligations. Under stress, that gap expresses itself as fat-tail latency and occasional “certified but practically unreachable” blobs until enforcement becomes explicit in protocol parameters. Implication: value PoA-certified blobs with an availability discount unless Walrus makes liveness and retrieval performance an onchain, punishable obligation. $WAL #walrus