KARDIAN WORLD · TOKENOMICS
Two tokens. Clear roles. Development in progress.

Tokenomics Overview

Kardian World is developing a two-token economy. DIAN supports the governance design, while KDU is intended for in-world utility. The reviewed source specifies supply caps of 5 billion DIAN and 500 million KDU, with permissioned issuance and configurable controls. Source-code findings do not verify a public deployment, circulating supply or live gameplay integration.

5B
DIAN supply cap in reviewed source
500M
KDU absolute mint cap
Variable
Allocation-specific vesting
Unverified
Public launch and circulating supply

DIAN vs KDU

DIAN and KDU have distinct intended roles. Both require authorized issuance. Vesting schedules govern specific DIAN allocations; KDU minting depends on permissions and configured caps, not proof of gameplay alone.

Property
DIAN
KDU
Max Supply
5,000,000,000 outstanding-supply cap
500,000,000 (hard cap)
Issuance Mechanism
Authorized minting; allocation-specific vesting
Minted on demand, annual cap 10M (1–50M range)
Unlock at Launch
Depends on funded schedules and launch configuration
Initial supply is a deployment parameter
Burn Mechanism
Burn functionality exists; fee routing depends on the module
Module-specific burn rules; no universal consumption rate
Primary Purpose
Governance, staking, value transfer
In-world resource, wages, crafting

DIAN Allocation

The distribution below represents the project allocation plan. Percentages do not prove that tokens have been minted, funded into vesting contracts or distributed. Confirm the deployed configuration and on-chain balances before treating any allocation as circulating supply.

5.0BDIAN supply
Protocol Treasury25% · 1.25B
Investors20% · 1.00B
Ecosystem20% · 1.00B
Team15% · 750M
Marketing10% · 500M
Advisors5% · 250M
Community5% · 250M

DIAN Unlock Curve

The chart below is an illustrative legacy schedule, not a verified circulation forecast. Actual releases depend on each schedule’s start, cliff, duration and funded balance. The cliff is included in the total duration. The reviewed token source does not permanently freeze minting at month 48.

0%50%100%37.5%73.3%100%T+0T+12T+24T+36T+48

DIAN Vesting Schedule

Read each duration from the schedule start; it already includes the cliff. Category defaults do not establish an actual payout date. Start times, beneficiaries, funded balances and deployed settings must be verified for each schedule.

Category
Cliff
Duration
Source
Team
12 months
36 months
Constant
Investors
6 months
24 months
Constant
Advisors
3 months
18 months
Constant
Community
None
48 months
Constant
Partners
3 months
24 months
Constant
Ecosystem
1-month release delay
36 months
DAO-set duration
Protocol Treasury
None
48 months
DAO-set
Marketing
None
24 months
DAO-set

KDU Issuance Caps

KDU issuance is permissioned. The reviewed implementation includes a 500 million supply cap, a configurable annual allowance and additional controls for specific minting paths. Initial supply is a deployment parameter; gameplay balances alone do not establish on-chain issuance.

Layer 1 — Absolute Cap
Source cap
500M
KDU MAX_SUPPLY
The reviewed implementation enforces this supply ceiling. Assess upgrade permissions and the deployed implementation before treating it as a permanent system guarantee.
Layer 2 — Annual Cap
Oracle-adjusted
10M
default / year
The baseline annual allowance is 10M KDU and can be configured within 1M–50M. Applicable adjustments and remaining allowance depend on contract configuration; 13M is not a universal ceiling.
Layer 3 — Daily & TX Caps
Anti-spike
1M
max per transaction
Additional limits depend on the minting module. Emergency minting is limited to 5% of year-start supply with a 24-hour cooldown and remains inside the annual allowance.

KDU issuance and DIAN vesting are separate mechanisms. KDU supports a configurable initial supply and authorized minting paths. Neither source code nor a local game balance proves who holds tokens or how circulating tokens were obtained. Verify deployment parameters, role assignments and transaction history before making those claims.

KDU Minting Buckets

The figures below illustrate a proposed split of a 10M annual budget. They are not verified live allocations, promised rewards or proof that every module is enabled. Effective budgets depend on the deployed configuration, permissions and remaining annual allowance.

10MKDU / year
Gameplay Rewards30% · 3.0M
Refinery (rKDU→KDU)25% · 2.5M
Virtual Mining15% · 1.5M
Staking Rewards12% · 1.2M
Liquidity & Market8% · 0.8M
Developer Grants5% · 0.5M
Operating Reserve5% · 0.5M

rKDU → KDU Refinery

The refinery design links raw resource accounting to a controlled KDU conversion process. Availability, efficiency, fees and processing times depend on implementation and configuration. Local Unreal Engine resource balances are not verified on-chain deposits, and this page does not establish a live conversion service.

Refinery Tiers
5 tiers
85%
average efficiency
Tier 0–4, topping out at 95% efficiency at the highest tier. Minimum deposit is 1 rKDU.
Processing Speed
Optional boost
10 KDU
per hour to accelerate
Minimum gap between refines is 10 seconds. Acceleration can be applied for up to 720 hours.
Cancellation & Revenue
Anti-abuse
5%
cancellation penalty
Half of any penalty is burned; the rest goes to the pool. 70% of refinery revenue routes to the treasury.