DAO Reddit Mentions | ChartExchange

This is not against JAM nor against JAMKB. Quite the opposite: I think the technical case is solid.
The premise I agree with
The state footprint (validator RAM) is inelastic — every validator must keep it in memory. Pricing it with the same token that governs staking, collateral, and coretime mixes heterogeneous scarcity signals. A dedicated resource (JAMKB) is a clean way to separate CPU / RAM / disk, just like no cloud provider prices everything through a single product. From a technical standpoint, this is defensible.
The real concern
The issue is not the technical design. The issue is that the value return path (value accrual) to DOT is being deferred to future referenda instead of being codified as a protocol invariant. As long as this remains open, the DOT investment thesis becomes dependent on governance quality rather than protocol rules. JAM can become an exemplary architecture while DOT simultaneously becomes one of the most governance-dependent theses in crypto — both can be true at the same time.
So my request is narrow: let’s close the economic loop in the rules, before locking anything in.
What I would ask any proposal to satisfy before enabling JAMKB
Non-negotiables:
Settlement in DOT.
JAMKB must be acquired exclusively in DOT — not in pUSD/fiat. Pricing in stablecoins reintroduces jurisdictional dependency, and minting against a stablecoin hard-pegs JAMKB to its issuance rate (a rigid ceiling), killing secondary markets and price-based reallocation — precisely what fixed-supply design is meant to enable.
Value accrual as a protocol invariant, not a treasury decision.
The value flow to DOT must be codified — via an automatic sink/burn of a defined fraction of JAMKB revenue, and/or recurring charges proportional to actual state usage (a prepaid DOT balance that drains as footprint is occupied; the slot is freed once the balance is exhausted).
Deed vs. rent matters: perpetual ownership creates one-off DOT demand that decays as the network matures; recurring flow keeps DOT demand tied to real usage — exactly the coretime model (you rent time, you don’t buy a core forever).
Economic spec published before the vote.
The full economic design — issuance/release policy, pricing mechanism, revenue destination, and its interaction with §9.3 (account footprint / threshold balance) and §4.6 (the single native token) of the Gray Paper — written in clear prose and reviewed before any referendum locks the architecture.
Mechanism safeguards worth specifying
Price-based allocation with eviction, not purely refundable deposits. “Full” is not “well allocated”; without eviction, low-value data never leaves. If deposits are used, the eviction rule must be explicit.
Automatic expiration + reclaim of abandoned state / lost-key state back to the DOT DAO, by rule.
Anti-hoarding mechanisms to avoid a repeat of “coretime barons” (restrict ownership to services with real usage, or apply demurrage to idle positions).
Public-goods allocations should be non-transferable, so grants don’t become resale assets.
Divisibility (1 JAMKB ≈ 1 KB should be fractionable for small services).
On-chain transparency: supply under DOT DAO control, portion released, revenue collected, and amount burned.
The decision question
Before enabling JAMKB, can the proposal answer — with concrete mechanisms, not intent:
Is JAM state charged in DOT?
Is value return to DOT a protocol rule (sink/flow), not a future treasury decision?
Is the economic spec written and published before this vote?
If all three are not verifiably “yes”, the design is not ready to be locked in.
Suggested governance path via referendum
If there is agreement, governance could proceed in two steps to avoid locking architecture without an economic mandate:
Signaling referendum (Wish for Change).
A non-binding referendum on the Wish for Change track, registering the community’s will that JAMKB should only be enabled once the three non-negotiables (DOT settlement, codified value accrual, and spec published before the vote) are satisfied. This measures consensus and provides political mandate before any implementation.
Binding implementation referendum(s).
After the economic spec is published and reviewed, a referendum on the appropriate track (e.g., Root, or the runtime/upgrade track indicated by the Fellowship) to lock in the mechanism with parameters already defined: unit of charge, sink/flow formula, expiration and reclaim rules, and on-chain telemetry.
Core idea: separate the mandate (step 1) from the implementation (step 2), so the community approves the economic design with the spec in hand — not an architecture with the economic layer still open.

.dark-mode .kzQFrf{ color: white; background-color: #333333; border: 2px solid white; }.light-mode .kzQFrf{ color: #333333; background-color: white; border: 2px solid #333333; }DAOUSDCDAO Maker / USD Coincrypto

DAOUSDC
DAO Maker / USD Coin
crypto