Frequently Asked Questions & Answers
SECTION 6: Governance
This section covers who actually has authority over the Second Value Protocol — and, just as importantly, who doesn't.
51. Who controls the protocol?
No single person, company, or government controls the Second Value Protocol — its core money-creation rules are enforced by open-source, publicly auditable code, and the decisions that can be changed at all are made through a one-wallet-one-vote democratic process in which every community member has exactly equal standing.
This is one of the sharpest contrasts between the SVP and the current monetary system. Under the debt-based system, control of the money supply rests with private commercial banks (through their lending decisions) and, nominally, with central banks — institutions whose officials, as Section 3 (Chapter 2) of the book documents, are often drawn from and deeply intertwined with the very financial sector they're meant to oversee. Under the SVP, the "controller" of the money supply is not a person or institution at all — it's a set of rules, written into public smart contract code, that execute the same way regardless of who's asking.
What can be changed is governed democratically: every registered community member gets exactly one vote, with no extra influence for wealth or token holdings (see Question 54 for the specifics of what requires what threshold). During a new network's early life, a small Genesis Validator Council oversees limited, maintenance-only decisions — but even this temporary authority operates under strict limits, cannot touch the protocol's core rules, and is automatically dissolved once the community reaches a defined size and maturity (see Question 54).
Related: Question 27 (Section 3) for who creates the money itself, as distinct from who governs the protocol; Question 34 (Section 3) for a direct comparison with central banking.
Learn more: Chapter 5.4, "The Commons Governance Fund: Democratic Public Finance" (p. 253–254), and Chapter 6.2, "Who Controls the Money Supply" (p. 316–318)
52. Can governments participate?
Yes — governments, especially local and municipal governments, can adopt and participate in the SVP just like any other community organization, but they don't receive any special authority or privileged status; they hold exactly one vote in the community's governance, the same as every other member.
Local and regional governments are, in fact, identified as one of the SVP's most natural early adopter groups — particularly those facing fiscal pressure from central government austerity or bond market discipline, since the Commons Fund model offers a source of public finance drawn from local productive surplus rather than taxation or borrowing. A municipal government could register wallets, participate in the community's governance process, and potentially benefit from the Commons Fund the same way any local institution can, while gaining no formal control over the protocol's rules beyond the equal vote every registered member holds.
National governments face a more complicated situation, because in most countries, currency issuance is a legal state monopoly, and community monetary systems operating outside conventional banking frameworks encounter genuine regulatory uncertainty that varies significantly by jurisdiction. The SVP's deployment strategy deliberately starts in contexts — agricultural cooperatives, indigenous community organizations, fair trade certification bodies — where existing legal frameworks already accommodate this kind of community economic self-governance, precisely because the protocol doesn't require any government's permission or cooperation to function at the community level (see Question 31, Section 3).
Related: Question 69–75 (Section 9) for how communities more broadly go about adopting the protocol; Question 83 (Section 10) addresses whether governments might simply try to ban it.
Learn more: Chapter 12.3, "Building the Coalition" (p. 435), and Chapter 10.3, "Local Sovereignty and Monetary Self-Determination" (p. 412)
53. Can communities customize the protocol?
Yes, within defined limits — communities have real democratic authority over things like Commons Fund spending priorities, membership eligibility rules, and validator standards, but the protocol's most fundamental parameters — the minting trigger and the core distribution formula — are deliberately harder to change, requiring a high supermajority threshold specifically so they can't be altered by a passing political mood.
Once a community reaches full self-governance, its 1-wallet-1-vote process controls a defined set of decisions: approving Commons Fund expenditures in any of seven broad categories (from physical infrastructure to social services to economic development), adding or removing eligible expenditure categories, setting oracle and validator accreditation standards, and approving new commodity categories eligible for minting. Communities can genuinely shape how the protocol operates within their own context — deciding, for instance, what counts as community membership for dividend eligibility, or which local priorities their Commons Fund should support.
The protocol draws a clear line, though, around its most consequential rules. Changing the core distribution formula — the 80/13.4/3/2.6/1 split — requires a two-thirds supermajority vote and a mandatory 90-day implementation delay, specifically to prevent short-term political pressure from reshaping the system's foundational economics. And during a network's early Genesis Phase, the core minting trigger and distribution mechanics are completely immutable, protected from modification by anyone, including the Genesis Validator Council itself.
Related: Question 42 (Section 4) for how this customization applies specifically to the Universal Dividend; Question 54 for exactly who has authority to make which changes.
Learn more: Chapter 5.4, "The Commons Governance Fund: Democratic Public Finance" (p. 255–259)
Once a community reaches full self-governance, only the community itself — through a one-wallet-one-vote process — can change the protocol's governable rules, with more consequential changes requiring higher supermajority thresholds; before that point, a temporary Genesis Validator Council has narrow authority that automatically expires on a fixed, code-enforced schedule that no one — including the Council itself — can delay or negotiate.
The protocol moves through three defined phases. In Phase 1 (Genesis Governance, roughly the network's first six months or first 500 wallets), a small council of five to eleven trusted validators manages only maintenance-related Commons Fund spending, while the core minting and distribution rules remain completely locked. In Phase 2 (Transitional Governance), community voting gradually activates for smaller expenditure decisions while the Genesis Council retains authority over larger ones. In Phase 3 (Full Community Governance) — triggered automatically once a community reaches 2,000+ active wallets, 18+ months of operation, and 60% average voting participation — all governance authority transfers permanently to the community's democratic vote, and the Genesis Council dissolves or becomes a purely advisory body with no remaining power.
The most important design detail here is that this transition is not a decision anyone makes — it's an automatic execution written into the protocol's code. The Genesis Council cannot delay it, modify its conditions, or retain authority once the conditions are met. This is a deliberate safeguard: governance systems where a temporary authority controls its own succession tend to see that "temporary" authority persist far longer than intended.
Related: Question 51 for the bigger picture of who holds authority overall; Question 56 for how this design specifically prevents any single group from taking control.
Learn more: Chapter 5.4, "The Commons Governance Fund: Democratic Public Finance" (p. 257–259)
54. Who changes the rules?
Disputes are handled differently depending on their nature — disagreements about whether a specific production claim is genuine go through an escalating validator review process (including, for the most suspicious claims, physical on-site inspection), while broader community disagreements about governance decisions are resolved through the same open, democratic proposal-and-vote process used for everything else, supported by community mediation resources the Commons Fund is explicitly permitted to fund.
When a production claim is flagged as suspicious by the protocol's automated fraud detection, it doesn't get rejected outright — it escalates. A moderately flagged claim requires a stronger four-of-five validator supermajority and additional evidence before it can proceed. A claim that trips a "hard flag" — such as a quantity far outside a producer's plausible capacity — is suspended from minting entirely and referred to a full validator panel review, which can include physical inspection of the production site by a registered auditor before any tokens are created. This gives producers and buyers a genuine path to demonstrate a claim's legitimacy rather than facing an automatic, unappealable rejection.
For disagreements that aren't about a specific transaction — disputes over how Commons Fund resources should be allocated, disagreements about governance proposals, or conflicts within the community more broadly — the SVP relies on its open governance process itself: any member can submit a competing proposal, every member gets an equal vote, and the Commons Fund's eligible expenditure categories explicitly include funding for community mediation and legal and administrative capacity, so communities can build out whatever dispute-resolution infrastructure their own context requires.
Related: Question 47–48 for the fraud-detection mechanics behind flagged production claims; Question 53 for how communities fund their own governance and mediation infrastructure.
Learn more: Chapter 5.5, "The Commodity Verification System: Solving the Oracle Problem" (p. 270), and Chapter 5.4, "The Commons Governance Fund: Democratic Public Finance" (p. 255–256)
55. How are disputes resolved?
The protocol is specifically engineered to make this extremely difficult — through hard caps on how much stake any single entity can hold, one-wallet-one-vote governance that gives wealth no extra political weight, random validator selection, and supermajority requirements for the most consequential decisions — though the book is candid that no system can claim capture is completely impossible.
Several independent safeguards work together here. On the technical side, no single wallet holder can control more than 15% of the network's total staked validator capacity, and no coordinated group of related entities can control more than 25% — caps specifically designed to prevent the gradual concentration of consensus power that has affected many other proof-of-stake blockchain systems. Validators are also randomly assigned to each confirmation round, so no one can predict or target which validators will review a given claim.
On the governance side, the SVP deliberately rejected token-weighted voting — the model used by most blockchain governance systems, where the wealthiest holders dominate decisions — in favor of one-wallet-one-vote, so a large token balance buys no additional political influence over the community's shared resources. The most consequential possible changes, like altering the core distribution formula, require a two-thirds supermajority plus a 90-day delay, making it very difficult for any temporary majority or organized faction to reshape the system's fundamentals. The book is honest that this doesn't make capture impossible — see Question 86 (Section 10) for the risks the protocol's own designers acknowledge — but it does mean that seizing control requires overcoming several independent, mutually reinforcing obstacles simultaneously, rather than just one.
Related: Question 50 (Section 5) for the validator-specific diversity requirements; Question 86 (Section 10) for the honest risk assessment of what could still go wrong.
Learn more: Chapter 5.6, "The Blockchain Architecture: The Resource Credit Chain" (p. 281), and Chapter 5.4, "The Commons Governance Fund: Democratic Public Finance" (p. 253–254)