Ethereum

A fascinating aspect of cryptoeconomics: critically-important code that ~never executes.
- Slashing
- Coin voting vetos
- Rollup fraud proofs
In each case, the mechanism ensures an attack is -EV > no attack > countermeasure not exercised. Hard problem to ensure it's still live & working.

Real World Ethereum 🌎 
building /daimo ✳️ 

For something like L1 validator slashing, there's enough background noise of people accidentally running broken setups to ensure we have working slashers.

For eg a fraud proof on a less-popular optimistic rollup... IDK

L2BEAT is an open source, public-good analytics and resrarch platform dedicated to L2 scaling solutions. ❤️

I've been thinking about the same thing but for user-initiated forced L2 transaction inclusion. There's no UI for this in any L2 yet.
IMO there should be a periodic forcing function that requires users to make such a transaction, in order to force wallets to support this.
Perhaps @l2beat should start monitoring this.

are there checks to make sure they still work when new upgrades go live? i’m a newbie, just wondering

Problems faced on a daily basis 
Quite interesting aspect about cryptoeconomics