Skip to content
Player's Guide

DYSNOMIA V2 — The Token Base Class (Domain Edition)

One-line pitch: DYSNOMIA V2 is the same as DYSNOMIA V1 from a player’s perspective — a slightly newer edition used by the domain (gameplay) contracts. No practical difference if you’re playing.

V2 has the same public interface as V1. The difference is internal naming (e.g., _addMarketRate vs. AddMarketRate) and which layer of the system inherits it:

Identical ERC-20 behavior, identical Purchase/Redeem flow, identical MultiOwnable pattern. Two flavors purely because the codebase was developed in phases.

  • Closest analogy: solc v0.8.X vs v0.8.Y — same user-facing behavior, different internals, different import paths.
  • Or: React 17 vs 18 — your app works the same; the engine is just a bit different.
Dysnomia term What it maps to
DYSNOMIA V2 Same base as V1, used by domain contracts
Purchase / Redeem Identical to V1
maxSupply Same randomized cap mechanism
  • Nothing V2-specific. Everything you’d do with a V2 token you’d do with a V1 token the same way.

Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.

QINGResolve your player or venue above the call forms.
QING.GetMarketRate(address _a)Read

Open this function to load its call form.

QING.Purchase(address _t, uint256 _a)Simulate / call

Open this function to load its call form.

QING.Redeem(address _t, uint256 _a)Simulate / call

Open this function to load its call form.

  • Cost: identical to V1.
  • Reward: identical to V1.
  • Identical to V1.

Inherited by the domain layer — every gameplay-facing ERC-20.

Q: Can V1 and V2 tokens swap for each other? A: Yes — they’re all compatible via Purchase/Redeem, regardless of which base they inherit.

Q: Will there be a V3? A: If gameplay changes warrant new token-level features, sure. For now V1 + V2 cover every contract in the system.


Want the Solidity? The contract reference lives at technical/core/01_DYSNOMIA_V2.