βοΈToken Distribution per Sale
Each project launched on DegenDapp follows a strict and transparent tokenomics model to ensure fairness, clarity, and sustainability for both creators and participants.
At the core of every token launch is a fixed 1 billion token supply, governed by smart contracts, with allocations and flows executed automatically upon sale completion.
π§± 1. Token Creation & Initial Supply
When a token creator initiates a launch:
A total of 1,000,000,000 tokens is minted via the
CustomToken
contract.This supply is immediately held and managed by the platformβs
TokenSaleManager
contract.No additional minting rights exist. The supply is immutable.
π― β Immutable and fully on-chain token issuance.
π 2. Sale Allocation: 76% to Community Buyers
During the token sale:
76% of the token supply (760,000,000 tokens) is made available for public purchase.
Sale parameters:
Softcap: 10 BNB
Hardcap: 20 BNB
Duration: 3 days (fixed window)
Contributions are tracked per address. If softcap is met but hardcap is not, unsold tokens are automatically handled (see below).
π¦ β Sale logic is governed entirely by smart contracts. No manual allocation.
𧬠3. Post-Sale Distribution Logic
Upon successful completion of the token sale (softcap reached and/or time expired), the system triggers an atomic Finalize Sale
process, executing the following:
πͺ a. 5% to Platform Staking Pool
50,000,000 tokens are transferred directly to the platform staking contract.
These tokens become rewards for $DGD stakers, distributed across Bronze, Silver, and Gold tiers.
π β A protocol-wide incentive for long-term DGD holders.
π§ b. 19% to PancakeSwap Liquidity
190,000,000 tokens are added to liquidity on PancakeSwap.
Paired with BNB raised in the sale.
Liquidity is added and locked via
addLiquidityETH()
through PancakeSwap Router V3.LP tokens are sent to a burn address or time-lock (depending on platform config).
βοΈ β Ensures instant tradability and price stability post-launch.
π§Ύ c. Treasury Funding: 10% BNB
10% of total BNB raised is sent to the DegenDapp Treasury.
Used for:
Platform maintenance
Future feature development
Security auditing and grants
The remaining BNB (after treasury and liquidity allocation) is effectively used for LP or remains with creators depending on vesting logic.
π¦ β Treasury funding is fixed, capped, and transparent per sale.
π₯ 4. Unsold Token Handling: Auto-Burn
In the event that the token sale does not reach the hardcap, the difference in unsold tokens is:
Automatically burned
Burn is executed via a
burn()
function on the ERC-20 contractVerified and recorded on-chain for full auditability
π β Protects token value, prevents inflation, and rewards early buyers.
β
Allocation Summary per Sale
Community Sale
76% (760M)
Public sale via SaleManager
Staking Rewards (Platform)
5% (50M)
Sent to DGD staking pool
Liquidity on PancakeSwap
19% (190M)
Added via router + BNB pairing
Treasury (BNB)
10% of raised
Sent to treasury wallet
Unsold Tokens
Varies
Burned if not sold
π Designed for Security & Transparency
100% of sale allocation logic is automated
No manual overrides or admin keys
All flows (tokens + BNB) are executed by verified smart contracts
Burns and liquidity events are visible on-chain
With every token sale, DegenDapp reinforces its commitment to trustless token distribution, fair launch mechanics, and on-chain verifiabilityβmaking rug-pulls and opaque fundraising a thing of the past.
Last updated