Go to app

Gavin Wood’s Core Governance & Design Concerns

Published 7/2/2026, 9:11:11 AM

Gavin Wood’s governance concerns regarding Polkadot center on the inefficiency of the "parachain export-only" model, the cadence of revenue generation, and the centralization risks inherent in a protocol that requires governance approval for every application-level change [Source: https://medium.com/polkadot-network/dot-daoism-under-jam-an-island-story].

The Join-Accumulate Machine (JAM) addresses these concerns by shifting Polkadot from an "upgradable relay chain" to a fixed protocol with permissionless service deployment [Source: https://wiki.polkadot.com/learn/learn-jam-chain/]. While JAM itself does not introduce a new "JAM token" (it continues to use DOT), it introduces a new scarce resource called JAMKB (state storage) which is central to its new economic and governance model [Source: https://graypaper.com].

Gavin Wood’s Core Governance & Design Concerns

Based on Wood’s 2025-2026 writings, his primary concerns include:

How JAM’s Design Addresses These Concerns

FeatureHow it Addresses Wood's Concerns
Permissionless ServicesRemoves the need for governance approval to deploy or upgrade applications. Anyone can upload code (Services) that executes on JAM without a DAO vote [Source: https://wiki.polkadot.com/learn/learn-jam-chain/].
JAMKB (State Token)Introduces a fixed supply (21M units) of "always-in-RAM" state storage. This creates a new, tangible demand for DOT (as the DOT DAO initially owns JAMKB) and rations a scarce resource [Source: https://graypaper.com].
Fixed Core ProtocolFreezes core parameters (hashing, networking, timing) to allow for extreme optimization, moving "governance-heavy" logic to independent services [Source: https://wiki.polkadot.com/learn/learn-jam-chain/].
RAMTIME (Proposed)A community-led "leasehold" model for JAMKB that would replace permanent ownership with time-limited tickets, addressing the "cadence problem" and preventing hoarding [Source: https://forum.polkadot.network/t/17928].

The "JAM Token" and DOT Tokenomics

There is no separate "JAM token" for investors. Instead, the ecosystem has evolved to support the JAM model through significant changes to DOT:

  1. DOT remains the primary token for economic security, staking, and governance.
  2. JAMKB is a technical accounting unit (1:1 mapping to kilobytes of state) used to manage the machine's memory [Source: https://graypaper.com].
  3. Supply Cap: To support this new model, Polkadot implemented a 2.1 billion DOT supply cap (Referendum 1710) with a halving inflation schedule starting March 14, 2026, to improve DOT's "hard money" status [Verified: https://polkadot.polkassembly.io/referenda/1710, https://x.com/Polkadot/status/1967241017314115889].

Remaining Risks and Uncertainties

While JAM addresses technical and economic bottlenecks, some governance challenges remain:

  • The Leasehold Debate: The DOT DAO must still decide whether to distribute JAMKB as permanent "freeholds" or use the RAMTIME leasehold model. Wood has signaled that the leasehold model better addresses his long-term sustainability concerns [Source: https://forum.polkadot.network/t/17928].
  • Governance Fatigue: While JAM reduces the number of technical votes by making service deployment permissionless, the complexity of managing the "Services" layer and the Treasury remains a challenge for the OpenGov framework.

In conclusion, JAM addresses Gavin Wood's concerns by removing governance as a gatekeeper for application deployment and introducing a "leasehold" economic model (RAMTIME) to ensure continuous demand for DOT, though the final implementation of these economic mechanics remains subject to DAO approval.