Jurisdictions and Vetoes: Managing Conflict

Transcript

SPEAKER_1: Alright, so last lecture we landed on this idea that roles define who can act, but what happens when two roles, or two parts of a protocol, genuinely disagree? And I've been thinking—what happens when two roles, or two parts of a protocol, genuinely disagree? Like, structurally, how does a governance framework handle conflict before it becomes a crisis? SPEAKER_2: That's exactly where jurisdictional design comes in. And it's the piece most protocol builders skip entirely. They define roles and assume voting resolves everything. It doesn't. Conflict resolution requires a prior question: who even has the authority to hear this dispute in the first place? SPEAKER_1: So jurisdiction—in the legal sense—maps onto protocol governance how exactly? SPEAKER_2: Almost directly. In law, jurisdiction is the authority of a court to hear a case. You have personal jurisdiction over the parties, subject matter jurisdiction over the type of dispute, and territorial jurisdiction over the geographic scope. In a protocol, you translate those into: which governance body has authority over these actors, over this category of decision, and within which domain of the protocol. SPEAKER_1: So a sub-DAO managing liquidity parameters, for instance, has subject matter jurisdiction over that narrow domain—but not over, say, a core protocol upgrade. SPEAKER_2: Exactly. And that boundary is load-bearing. When you grant a sub-DAO autonomy over a narrow domain, you get speed and specialization. The risk is what happens when that sub-DAO's decision bleeds into territory it wasn't designed to govern. That's where the global veto becomes essential. SPEAKER_1: Walk me through how a global veto actually works in practice. Because our listener might be thinking—isn't that just handing power back to a central authority? SPEAKER_2: It's a fair concern. The U.S. constitutional model is instructive here. The President can veto legislation passed by Congress, but that veto can be overridden by a two-thirds majority in both houses. The veto isn't absolute power—it's a circuit breaker. In protocol terms, a Security Council or Guardian body holds veto rights over sub-DAO actions that threaten global protocol integrity, but the broader token-holder community can override that veto with a supermajority. SPEAKER_1: So the veto is a pause mechanism, not a permanent block. SPEAKER_2: Right. And the Yale Law Journal's work on self-help and separation of powers makes this precise—branches of government cure wrongs through their own actions rather than waiting for courts. Protocols need the same capacity. A Guardian that can only petition for a vote while an exploit is draining the treasury is not a Guardian. It needs self-help authority: the power to pause, freeze, or revert, subject to later community review. SPEAKER_1: Optimism's Security Council is the case everyone points to here. What does it actually illustrate about conflict management? SPEAKER_2: Optimism built a two-chamber structure—a Token House and a Citizens' House—with the Security Council holding emergency veto power. When a critical vulnerability was identified, the Council acted within hours, without waiting for a governance vote that would have taken days. The key design choice: the Council's emergency actions were time-limited and subject to retroactive community ratification. Speed at the local level, accountability at the global level. SPEAKER_1: That retroactive ratification piece is interesting. It's almost like the comity principle in international law—voluntary recognition of another body's decisions. SPEAKER_2: That's a sharp parallel. Comity in law is the voluntary recognition and enforcement of another jurisdiction's decisions. It's not mandatory, but it's what makes cross-jurisdictional systems function without constant litigation. In protocol governance, when a sub-DAO acts and the broader community ratifies it retroactively, that's comity in practice. It builds trust between governance layers without requiring every decision to go through a central bottleneck. SPEAKER_1: What about the risk of renvoi—where you get this loop of jurisdictions referring decisions back and forth to each other? Does that happen in DAOs? SPEAKER_2: Constantly, and it's underappreciated. Renvoi in law occurs when a court applies another jurisdiction's conflict-of-laws rules, which then refer the case back or to a third jurisdiction. In DAOs, you see this when a sub-DAO escalates a dispute to the core DAO, which refers it back to a working group, which escalates again. The loop is governance deadlock. The fix is the significant contacts approach—assign the dispute to whichever body has the closest operational connection to the issue, and make that assignment rule explicit in advance. SPEAKER_1: So pre-defined escalation paths. Not just 'vote on it' but 'this type of conflict goes here first, then here if unresolved.' SPEAKER_2: Precisely. And there's a public policy exception built into most serious frameworks—the equivalent of a court refusing to apply foreign law that violates fundamental local principles. A sub-DAO cannot make a decision that contradicts the protocol's core security assumptions, even if it has subject matter jurisdiction. That exception is the backstop against governance capture. SPEAKER_1: Governance capture—that's the scenario where a well-resourced actor takes over a sub-DAO and uses its autonomy to extract value from the broader protocol. SPEAKER_2: Exactly. And the backstop mechanism is what prevents local autonomy from becoming a vector for system-wide capture. Think of it as the most significant relationship test from conflict-of-laws doctrine—when multiple jurisdictions could apply, you identify which one has the strongest ties to the outcome. In protocol terms: when a sub-DAO decision has system-wide consequences, global governance jurisdiction supersedes local autonomy. SPEAKER_1: So for someone building this from scratch—what's the sequencing? Do they define the sub-DAO domains first, or the veto structure first? SPEAKER_2: Veto structure first, always. Define what cannot be done at any level before you define what each level can do. That's the domicile principle applied to governance—establish the legal residence of authority before you start assigning rights. If the global veto is an afterthought, sub-DAOs will expand into the vacuum, and by the time capture happens, there's no clean mechanism to reverse it. SPEAKER_1: So for our listener, the core insight from this lecture is really that jurisdictional clarity and veto architecture aren't constraints on decentralization—they're what makes decentralization safe to actually deploy. SPEAKER_2: That's the synthesis. Resilient governance frameworks use jurisdictional boundaries to enable rapid, specialized local action—and a global veto structure to ensure no single actor can capture the whole system. The veto is not centralization. It is the safety net that makes genuine autonomy at the sub-level possible. Without it, every grant of local authority is also a potential attack surface.