Frequently Asked Questions & Answers
This section covers one of the areas where the Second Value Protocol's approach is genuinely unusual — building monetary reform from the community level upward, rather than waiting for national or global institutions to act.
SECTION 9: Communities
The SVP is built around communities — rather than nations, corporations, or a single global system — because community-level adoption doesn't require anyone's permission, because Second Value itself is generated at the community level in the first place, and because a network made of many independent communities has no single central point that could ever be captured.
Every previous attempt at monetary reform has been defeated by the same structural problem: it needed permission from institutions — legislatures, central banks, international bodies — whose interests were threatened by the reform itself (see Question 83, Section 10). Building around individual communities sidesteps this entirely. A farming cooperative, a fishing association, or a rural township can adopt the SVP without lobbying a single legislature or waiting for any regulator's approval, because the protocol is open-source and permissionless by design (see Question 31, Section 3).
There's also a deeper conceptual reason. Second Value — the broader economic wealth a production event generates beyond the direct payment between buyer and seller — is, by its nature, generated within a community's collective economic life (see Question 22, Section 3). It makes sense, then, that the entity governing how that wealth is recognized and distributed should be the community itself, rather than a distant national or global institution. And because the SVP's long-term vision is a federated network of independently governed communities rather than one centralized system, there's no single global authority for a hostile actor to capture — undermining the network would mean undermining every participating community simultaneously, which becomes harder, not easier, as the network grows.
Related: Question 22 (Section 3) for the concept of Second Value this connects to; Question 56 (Section 6) for how this federated structure resists capture more broadly.
Learn more: Chapter 5.8, "The Four Phases of Network Deployment" (p. 306–307)
69. Why communities?
70. Can small towns use the protocol?
Yes — in fact, the SVP's own deployment roadmap deliberately starts with a single small community rather than attempting to launch at national or global scale, precisely because a smaller, closely-knit community makes it easier to build the registration base, local governance, and trust that a new monetary system needs in its earliest days.
The protocol's first phase of deployment is explicitly designed around a single, modest-sized community — ideally an agricultural cooperative, a rural township, or a farming association with a defined membership and existing local governance structures already in place. This isn't a limitation the protocol works around; it's the intentional starting point. A smaller community offers a natural registration base for wallet holders, a pre-existing institutional structure that can manage community governance, and a scale at which any early technical problems can be identified and corrected without large-scale consequences.
The kind of production a small town needs to generate isn't enormous, either — the protocol's own first-year targets for a pilot community are modest: on the order of 100 or more registered wallet holders and a few hundred thousand dollars of total verified production value in the first year. This is well within reach for a genuinely small agricultural or resource-producing town, which is exactly why small communities — rather than major cities or national economies — are the SVP's natural and intended starting point.
Related: Question 43 (Section 5) for who specifically can register as a producer; Question 75 for how small communities can eventually connect with others once established.
Learn more: Chapter 5.8, "The Four Phases of Network Deployment" (p. 297–300)
71. Can developing countries use it?
Yes — communities in developing economies are identified as some of the SVP's most compelling deployment contexts, precisely because they're often the communities most thoroughly underserved by conventional banking despite having substantial primary productive capacity, and because widespread mobile and smartphone access has made the SVP's digital wallet infrastructure genuinely deployable in places that never had access to conventional banking.
Agricultural cooperatives across sub-Saharan Africa, small-scale mining communities in Latin America, and artisanal fishing communities across Southeast Asia and the Pacific Islands are specifically named as natural adopter communities — places whose primary production already supports global supply chains, but where producers typically receive only a small fraction of that value as income and finance their operations through expensive informal credit. The mismatch between how much genuine economic value these communities generate and how little of it they retain is exactly the problem the SVP is designed to address.
The protocol's verification system is also deliberately built to accommodate the realities of developing-world production contexts rather than assuming the formal infrastructure of advanced economies. In artisanal fishing communities, for instance, where catch may be landed at dozens of informal points with limited regulatory oversight, the verification system relies more heavily on vessel GPS tracking and community-based certification from local fisheries associations rather than the certified landing facilities available in more formal fishing economies — an adaptation specifically designed to extend genuine verification integrity into contexts that lack developed institutional infrastructure.
Related: Question 20 (Section 2) for the deeper "manufactured scarcity" problem this responds to; Question 68 (Section 8) for the practical connectivity requirements this depends on.
Learn more: Chapter 5.8, "The Four Phases of Network Deployment" (p. 301–302), and Chapter 12.3, "Building the Coalition" (p. 435)
72. What would participation look like?
For most community members, participation means registering a wallet through the community's onboarding process, receiving a weekly Universal Dividend automatically, and having a genuine vote in how the community's shared Commons Fund is spent; for registered producers, it also means having real production sales verified and triggering new token creation.
Joining starts with wallet registration: proving community membership (which might mean geographic residency, cooperative membership, or another criterion the community itself defines — see Question 42, Section 4), completing an identity verification step designed to prevent one person from registering multiple wallets, and installing a wallet application on a smartphone or similar device. From that point on, participation is largely passive for most members: every week, a share of that week's newly created tokens lands automatically in their wallet as the Universal Dividend, calculated by dividing the community's pool by the number of active registered wallets (see Question 41, Section 4).
Members who want a more active role can participate in the community's democratic governance — submitting or voting on proposals for how the Commons Fund's resources should be spent, with every registered wallet holder getting exactly one equal vote (see Question 42, Section 4). And for the subset of community members who are primary producers — farmers, fishers, miners, energy generators — participation also means registering their land, equipment, or vessel, and then having genuine production sales verified through the protocol's evidence system each time they sell to a buyer, triggering the creation of new tokens (see Question 46, Section 5).
Related: Question 36 (Section 4) for the Universal Dividend mechanics in full; Question 51–56 (Section 6) for the complete governance process.
Learn more: Chapter 5.8, "The Four Phases of Network Deployment" (p. 298–299)
Yes — because the SVP operates as a parallel system alongside existing currencies rather than a replacement that locks communities in, a community (or an individual within it) can simply stop using it, and unlike debt-based obligations, there's no outstanding loan or contractual commitment that has to be unwound to walk away.
This follows directly from the SVP's design as a voluntary, permissionless, parallel monetary infrastructure rather than a mandatory replacement for existing currencies (see Question 31, Section 3). Nothing about the protocol requires ongoing participation — a community that adopts it isn't taking on debt, isn't signing a binding long-term contract, and isn't surrendering any legal authority to the protocol or its developers. If a community's members simply stop registering new production events and stop transacting in Resource Credit tokens, participation naturally winds down.
Individual members retain their tokens as their own property even if they step back from active participation, and the protocol's broader architecture includes token exchange infrastructure that allows tokens to be converted into local fiat currency through licensed cryptocurrency exchanges — meaning someone who wants to exit isn't left holding an asset with no path back into the conventional financial system they may still need for other obligations. This is a genuinely different situation from the debt-based system, where exiting a loan or a mortgage means actively paying off or defaulting on a binding obligation — there's no equivalent "unwinding" process required to stop using the SVP.
Related: Question 31 (Section 3) for the full explanation of why the SVP doesn't require replacing existing currencies; Question 41 (Section 4) for how the dividend works while someone remains active.
Learn more: Chapter 5.8, "The Four Phases of Network Deployment" (p. 304–305)
73. Can communities leave?
74. Does this replace local government?
No — the SVP is a monetary and economic infrastructure, not a system of political governance, and it doesn't replace elected local government, courts, or public administration; what it can do is give a local government a new, non-debt source of public finance to draw on alongside its existing tax base.
The distinction the book draws is between monetary sovereignty and political sovereignty — related concepts, but not the same thing. A community's elected government, its legal institutions, and its public administration continue to function exactly as they did before; the SVP doesn't claim any authority over elections, law enforcement, courts, or the everyday business of local political governance. What changes is the community's access to a new stream of public finance: local and regional governments facing fiscal pressure from central government austerity or bond market constraints are specifically identified as natural adopters, because the Commons Fund model provides public finance drawn from local productive surplus — not subject to central government allocation, bond market approval, or the interest costs of municipal borrowing.
In practice, this means a local government could participate in the SVP much like any other community institution — registering wallets, drawing on Commons Fund resources for locally-approved infrastructure or services through the community's democratic governance process — without that participation displacing its existing political authority or legal responsibilities in any way. It's better understood as a new fiscal tool a local government can use, not a replacement for the government itself.
Related: Question 52 (Section 6) for how governments more broadly can participate in SVP governance; Question 53 (Section 6) for what communities can and can't customize about how the protocol operates.
Learn more: Chapter 10.3, "Local Sovereignty and Monetary Self-Determination" (p. 412), and Chapter 12.3, "Building the Coalition" (p. 435)
75. Can multiple communities cooperate?
Yes — the SVP is specifically designed to grow into a network of connected communities rather than staying isolated, using an inter-community bridge protocol that lets tokens move between communities so a grain-farming community and a fishing community, for example, can trade with each other without needing to convert through an external currency.
No single community can produce everything its members need — a farming community needs manufactured equipment, a fishing community needs agricultural products, a mining community needs timber — which is exactly the gap the SVP's inter-community bridge protocol is built to close. Using a "lock-and-mint" mechanism, tokens sent from one community's blockchain are locked in place while an equivalent quantity is created on the receiving community's chain, with the transfer itself confirmed by a joint panel of validators drawn from both communities — preventing either community from unilaterally creating tokens on the other's ledger.
This is the foundation of the protocol's long-term vision: not a single global system, but a federated network of independently governed communities, each maintaining its own governance, validator set, and democratic control over its own monetary affairs, connected through these bridges into a wider regional — and eventually global — economy. Crucially, joining this wider network doesn't require any community to give up its own self-governance: there's no global SVP central bank or governing board sitting above individual communities, only shared technical standards that keep the bridges compatible with one another.
Related: Question 31 (Section 3) for how the SVP relates to conventional currencies at this larger scale; Question 56 (Section 6) for why this federated design specifically resists capture.
Learn more: Chapter 5.8, "The Four Phases of Network Deployment" (p. 303–307)