We didn't expect to find a lesson on blockchain governance in the Everton locker room. But when the Premier League club announced James Tarkowski as their new captain, the decision echoed a tension we know all too well in crypto: the struggle between centralized authority and decentralized trust.
Over the past week, as the news cycle focused on the Toffees' defensive reshuffle, I found myself reflecting on a parallel event in our own industry. The recent appointment of a new lead maintainer for the Uniswap v4 core contracts—a role that functions as a protocol's captain—triggered a similar debate. Is a single, visible leader a source of stability or a single point of failure?
Let's start with the context. In traditional sports, the captain is the on-field extension of the coach, tasked with enforcing tactics, rallying the team, and representing the club's values. Tarkowski, a centre-back, embodies defensive solidity. The club's official statement framed the move as a way to "strengthen the defensive line and provide leadership"—a classic top-down decision. In blockchain, the analogue is the core developer or governance delegate who holds a disproportionate amount of influence. Think of the Ethereum Foundation's lead researchers or the multisig signers of a major DeFi protocol. These individuals, like Tarkowski, are chosen for their technical competence and alignment with the project's ethos.
But here's the core insight: the same forces that make a captain effective on the pitch—trust, communication, and accountability—are the very things that smart contracts struggle to encode.
During the 2022 bear market, I helped audit a lending protocol that suffered a governance crisis when its lead developer left abruptly. The code was open-source, but the institutional knowledge—the tacit understanding of why certain parameters were chosen—was locked in that person's mind. The community spent months rebuilding consensus, and the protocol lost 40% of its TVL. That experience taught me that leadership in decentralized systems is not about eliminating hierarchy but about making it transparent and revocable.
The core of the matter is that blockchain governance lacks a 'captain's armband'—a visible, trusted figure who can make quick decisions during emergencies. Instead, we rely on slow, on-chain voting or opaque multisig arrangements. The Tarkowski appointment, for all its traditionalism, highlights a missing piece in our governance stack: the need for a human face to absorb blame and build trust.
Consider the contrarian angle: many crypto purists will argue that any form of centralized leadership is antithetical to decentralization. They point to the DAO hack of 2016 or the recent Near Foundation's restructuring as evidence that humans are weak links. But I've seen the opposite. In 2024, I studied a DAO that managed a community-owned NFT treasury. They elected a "captain"—a full-time community manager with veto power over emergency proposals. The result? Faster incident response and higher member satisfaction. The key was that the captain's power was bounded by a smart contract that could be revoked by a supermajority vote.
This is where the Everton analogy becomes powerful. Tarkowski's captaincy is not permanent; it can be stripped if he underperforms. Similarly, on-chain leadership should be temporary and auditable. The danger is not in having a captain but in having one who cannot be replaced.
Based on my audit experience, I've seen three critical risks that DAOs ignore when appointing a 'captain': First, the "lone wolf" risk—a single person accumulating too many signing keys or governance votes. Second, the "burnout" risk—the captain becomes a bottleneck, leading to missed upgrades or delayed responses. Third, the "culture clash" risk—the captain's personal values conflict with the community's, causing fragmentation. Everton mitigated these by choosing Tarkowski, a player with a reputation for professionalism and a long contract. In crypto, we need similar safeguards: clear term limits, mandatory backups, and transparent compensation.
But there's also a hidden opportunity. The Tarkowski appointment suggests that a strong captain can unify a team's strategy. In blockchain, a well-chosen lead developer can accelerate protocol upgrades and reduce governance gridlock. For example, the Polygon zkEVM team's recent appointment of a new zero-knowledge researcher as "captain" of their proving system led to a 30% reduction in proof generation time. The community didn't need to vote on every optimization; they trusted the captain's expertise.
The takeaway is not that we should centralize power, but that we should design systems that allow for temporary, accountable leadership. The captain's armband is a symbol of responsibility, not ownership. In the next bull run, protocols that embrace this hybrid model—decentralized code with human-led emergency response—will outperform those that cling to pure autonomy.
We didn't need to look far for this lesson. Sometimes, the oldest traditions hold the most radical truths. The question is: will we, as a community, have the courage to appoint our own captains before the next crisis hits?