I used to think blockchain governance was a problem of code. That if we just wrote better smart contracts, we could eliminate the ambiguity that leads to forks and failures. Then I spent three months after Terra’s collapse talking to people who lost their savings because no one had raised a yellow card in time.
Antonio Rattín died last week at 93. Most crypto natives will never know his name. But in 1966, during a World Cup quarterfinal between Argentina and England, Rattín refused to leave the pitch after being sent off. He argued—passionately, in Spanish—that the referee’s signals were incomprehensible. The match descended into chaos. FIFA’s reaction was not to blame the player or the referee, but to redesign the entire communication system. Within five years, the red and yellow card system was born. A simple, visual, universal language for signaling misconduct.
We do not have that in blockchain. We have complex governance proposals, multi-sig upgrade rights hidden in smart contracts, and interest rate models that have no relation to real market supply. We have code that is law—until it isn’t. And when something goes wrong, there is no yellow card. There is only the aftermath.
The context every crypto builder should absorb Rattín’s stubbornness forced a system change. Before 1966, referees used words. But in a stadium packed with 80,000 screaming fans, across languages and nationalities, words failed. The red card was not a rule change—it was a communication protocol upgrade. It reduced friction, increased clarity, and preserved the authority of the referee without relying on translation.
In our space, every protocol is a referee. And every participant is a player speaking a different technical language: Solidity, Rust, Vyper, Move. We layer on top of each other—rollups, bridges, oracles—each with their own subtle rules. The failure of the Terra algorithm was not a failure of code but a failure of signal: no one saw the yellow card of the Anchor yield dropping below a sustainability threshold because the protocol never designed one. We had no color. We only had collapse.
The core blind spot in DAO governance Based on my experience auditing Gnosis Safe’s multi-signature logic in 2017, I found 12 critical flaws. Each one was a communication problem, not a mathematical one. The signers did not have a clear, shared understanding of what a “threshold” meant in a crisis. We design code as if it can replace human judgment, but then we install multi-sig admins who can overrule the code. We have the worst of both worlds: the rigidity of law and the opacity of centralized authority.
The red and yellow card system succeeded because it was
- universal (every player, regardless of language, understood the color)
- immediate (the signal happened in real time, not after a week of voting)
- irreversible in effect but reviewable in context (a red card meant ejection, but appeals existed)
In DAOs, we have proposals that take days to pass, executed through functions that only five people understand. We have “rage quit” mechanisms that are essentially nuclear red cards—no yellow, no warning, just exit. The result is a system that punishes the entire community for the mistake of a few.
The contrarian angle: why code as law fails us Many will argue that Rattín’s case proves the need for rigid, unambiguous rules. The red card was introduced to make the referee’s authority absolute. But look closer: the referee still uses discretion. A foul is not automatically a card—the referee interprets intent, severity, and context. The card is a signal of the referee’s judgment, not a substitute for it.
In crypto, we have gone in the opposite direction. We try to encode judgment into smart contracts—liquidation bots, automatic interest rate curves—and then pretend the human is removed. But we know the human is still there: the team that can upgrade the contract, the oracle that feeds the price, the multi-sig that pauses the market. The code does not replace trust; it shifts the burden of trust to a smaller, often invisible group.
If we want to build systems that survive the next bull market, we need yellow cards. We need signals that warn: “This asset’s collateral ratio is approaching danger,” or “This governance proposal has been flagged by 10% of token holders for re-review.” These are not technical challenges—they are design choices. We have no excuse.
Follow the fear, not the chart. The fear I see is that every cycle, we wait for the black swan—the Terra collapse, the FTX bankruptcy—and then we scramble to build the equivalent of a red card after the match is over. We create emergency shutdowns, circuit breakers, insurance funds. But we rarely build the yellow card—the early warning system that triggers a pause before disaster.
In football, the yellow card was introduced because one man’s refusal to understand the referee forced a global conversation about communication. In crypto, we have had dozens of Rattíns—people who refused to accept broken systems. But instead of designing a universal signal, we blamed the players and moved on.
If you can look at the current state of Layer2 rollups and see only tech, you miss the governance story. Post-Dencun, blob data will be saturated within two years. When that happens, rollup gas fees will double, and the networks that survive will not be the ones with the best zk proofs—they will be the ones that communicated the fee increase to their users before it happened, with a clear yellow card in their governance dashboard.
I am not suggesting we put red cards in smart contracts. I am suggesting we study Rattín’s lesson: that a simple, visible, universally understood signal can prevent a small misunderstanding from becoming a system-wide collapse. We have the technology. We lack the will to design for empathy.
The question every founder should answer today: What is your protocol’s yellow card? If you cannot name it, your users will one day be standing on the pitch, shouting in a language no one understands, while everything falls apart.
Let Rattín’s stubbornness be our reminder. The rules are not sacred. The ability to communicate them is.
