The underlying idea is to turn beacon chain from a global state database into a lightweight “court” that only verifies proofs – validators prove their own state using #ZK/STARK, no need to store pubkeys, balances, or slashing history forever on‑chain, plus daily pubkey regeneration for re‑anonymization. What keeps me up at night: does daily proof aggregation become a bottleneck at scale? And with slashing, could cross‑day handling open up new attack surfaces? Feels like a big tradeoff – leaner state vs. new operational risks. Curious how others see it. #ETH. .
