Content
@
0 reply
0 recast
0 reaction
✳️ dcposch on daimo
@dcposch.eth
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.
9 replies
8 recasts
66 reactions
polymutex
@polymutex.eth
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.
0 reply
0 recast
1 reaction
