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.
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.
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.
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.
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.
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.
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.
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.