Questions on JAMKB Distribution, Pricing and DOT Value Capture

Ecosystem
1

Gavin’s recent post on JAMKB helped clarify why JAM likely needs a separate state footprint resource-access token rather than using DOT directly.

My understanding is:

  • JAMKB would represent access to JAM state footprint.

  • 1 JAMKB would map to 1 KB of JAM state.

  • Supply would be fixed, possibly around 21 million JAMKB.

  • All JAMKB would initially be owned by DOTDAO.

  • DOT would continue to be used for governance, staking, collateral and coretime payments.

  • JAMKB would not replace DOT, but would represent a scarce JAM resource.

This makes sense from a protocol-design perspective. JAM state footprint is an inelastic resource because all validators must hold it in RAM. A separate resource-access token allows this scarce resource to be priced and allocated more cleanly.

However, I think the community needs clarity on the economic design.

Questions:

  1. How will developers or services acquire JAMKB from DOTDAO?

  2. Will JAMKB be sold for DOT, dotUSD, or another asset?

  3. If JAMKB is sold for dotUSD, how does that value flow back to DOT holders?

  4. Would it make more sense for JAMKB sales or auctions to be denominated in DOT, so that demand for JAM state creates direct demand for DOT?

  5. If JAMKB is released through an on-chain exchange, who determines the release schedule?

  6. Should some JAMKB be reserved for grants, loans, early JAM builders, or public-good services?

  7. If developers need both coretime and JAMKB, what is the intended relationship between DOT, coretime payments, and JAMKB acquisition?

  8. Could DOTDAO use proceeds from JAMKB sales to buy back or burn DOT, fund validators, fund ecosystem development, or replenish the treasury?

  9. What mechanisms will prevent JAMKB from becoming primarily speculative rather than being held by services that actually need state?

  10. What reporting should exist so DOT holders can see how much JAMKB remains under DOTDAO control, how much has been released, and what proceeds were received?

My main view:

JAMKB may be technically necessary, but its economic design must clearly preserve and strengthen DOT value capture.

If DOTDAO owns the JAMKB supply, then DOT holders effectively own the scarce state resource of Polkadot JAM. But for that to matter economically, the path from JAM usage back to DOT needs to be clear.

For me, the central question is:

Should JAMKB be acquired using DOT?

If the answer is yes, then JAM state demand can become direct DOT demand.

If the answer is no, then the community needs to understand how DOT holders benefit from releasing one of JAM’s most important scarce resources.

2

One additional technical question that occurred to me while thinking through JAMKB:

Will JAMKB be divisible?

If 1 JAMKB corresponds to the right to hold 1 KB of JAM state, can a service hold 0.5 JAMKB for 512 bytes or 0.1 JAMKB for roughly 100 bytes?

I assume divisibility would be important for efficient state allocation, but I haven’t seen it discussed yet.