Here's what's known about Cerberus from @Arcium ↓ Cerberus = zero-trust MPC protocol built for privacy under real adversarial conditions. • Dishonest-majority security (t = n − 1) Cerberus preserves privacy even if all but one node are malicious. This is the bar institutions care about. • Malicious security, no trusted dealer No setup assumptions, no “just trust the coordinator.” Security holds even against active attackers. • Exact encrypted compute Uses additive secret sharing → fast local additions + one-round multiplications, no noise growth, no approximation games. • Economic enforcement baked in Node operators stake to activate hardware, earn for correct execution, and get slashed for misbehavior. Crypto-native accountability. • Scaling is being engineered, not hand-waved Planned integration with @doublezero multicast reduces most communication from O(n²) → O(n), which is critical for real workloads. • Cheater identification is an active focus Cheater identification + identifiable abort is being built harden security guarantees. The thesis is simple but rare: Privacy without security and correctness is useless. Cerberus is Arcium’s attempt to make encrypted compute correct by construction, even when the environment is hostile. Bullish on @Arcium.