# Emission Plan ![](/files/nkwWSxZ2gJTFNFuW7j1U) ## Description * **The weekly DDDX token emission is adjusted according to the lock-up ratio.** If all participants lock their positions, the DDDX token emission is reduced to 0, if only 50% of the participants lock, the emission is 50%, and the lock-up is inversely proportional to the emission. (For reference only, the actual data after the contract is deployed shall prevail.) * **The proportion of the locked part of DDDX tokens will never be diluted** Liquidity incentive DDDX tokens will be added weekly. The protocol will release the same proportion to the lock-up pool of DDDX according to the proportion of the newly added DDDX tokens in the circulation to ensure that the proportion of DDDX tokens in the lock-up will not be diluted. * **ve locks are NFTs** By tokenizing the lock position this allows a single address to own more than one lock, locks balances are cumulative and each lock contributes to the overall ve balance. This further allows locks to be traded on secondary markets, as well as to allow participants to borrow against their locks in future lending market places. ## Formulas and Cases **The emission of DDDX tokens is determined by multiple factors.** * Token emission on Liquidity Incentive = A = max(Initial Constant\**0.98^n\**((Total supply number of DDDX -Total Voting Power)/Total supply number of DDDX),(Total Supply-Total Voting Power)\**2/1000))* * Token emission for DDDX Lockup Pool = B = Token emission on Liquidity Incentive\*(Total Voting Power/Total Supply). * The number of additional issuances this week = A+B. **For demonstration purposes, assume that the initial total supply of DDDX is 10,000,000, the total voting power is 2,400,000, and the initial constant is 2,900,000.** * Token emission on Liquidity Incentive = **2,159,920** DDDX * Token emission for DDDX lock-up pool = **518,380** DDDX **To sum up, in the above initial state, DDDX token emission in the first week = 2,159,920 + 518,380 = 2,678,300 DDDX** Emissions for the next week are also based on the above rules, please refer: {% embed url="" %} ## DDDX Emissions Allocation Process DDDX tokens will be minted every Thursday at 0:00 UTC and allocated to the reward pool contract. ### 1. Token emission for Liquidity Incentive Token emission for Liquidity Incentive will be transferred to each Gauge Pool that has been voted, and will be released at **a constant rate for the next 7 days.** DDDX emissions will be allocated according to the proportion of LP tokens staked by liquidity providers, and LP tokens bound to veNFT will receive accelerated benefits. ### 2. Token emission for DDDX Lockup Pool Token emission for DDDX Lockup Pool will be transferred to veNFT Reward Pool and released to veNFT holders at **0:00 UTC NEXT Thursday**. The contract will take a snapshot at 0:00 UTC on Thursday to determine the voting power ratio of all veNFT holders. According to this ratio, the contract will be released to veNFT holders at one time after 7 days. {% hint style="info" %} According to the project's launch plan, more veNFTs are owned by the DDDX.io team, BNB Chain partners and investors in the initial stage of the project. For a fair launch of the project, limiting early holders could have a greater impact on the protocol, DDDX.io removed the first week of inflation rewards for veNFT holders. All veNFT holders receive inflationary rewards starting from the second week after the project launches. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://dddx.gitbook.io/dddx.io/tokenomics/emission-plan.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.