Genesis Gate
Last updated
Last updated
Project Registration Project teams can freely submit their applications on the Genesis Gate section of the Diverge Loop website without any mandatory approval process. Applications include detailed information such as the project overview, token issuance details, initial liquidity supply plan, token lock‑up schedule, sale ratio, and reward distribution methods. Submitted information is recorded on‑chain via BSC‑based smart contracts and can be updated later through DAO voting.
Recommended Project Application (Optional) If a project team desires additional exposure and benefits, they can separately apply for Recommended Project status. This application is evaluated by the community (including DAO voting) and the Diverge Loop team; approved projects receive a Recommended badge along with enhanced promotional benefits.
Liquidity Pool Creation and Rewards Approved projects deploy their tokens and initial liquidity (supplied by the project team) on BSC‑based DEXs (e.g., PancakeSwap) to create liquidity pools. Investors provide liquidity by pairing the project tokens with other assets, earning LP tokens proportional to their share. On these DEXs, a fee rate of 0.1% (as determined by Diverge Loop) is distributed among liquidity providers based on their contribution. In addition, LP token holders receive extra token sale allocations according to their share of the total liquidity, based on a bonding curve, lump‑sum, or sequential distribution method specified during registration.
Whitelist Access Restriction and Security Enhancements
Diverge Loop integrates a whitelist mechanism in its smart contracts to ensure that participation in token sale rewards and liquidity provision is limited exclusively to users within the Diverge Loop ecosystem.
Only addresses authenticated and registered through the Diverge Loop platform (via our dedicated frontend with additional security measures such as oracles and multi‑signature controls) are eligible for rewards.
The whitelist data is stored on‑chain using BSC‑based smart contracts, ensuring full transparency.
Additional security measures such as frontend authentication, oracle integration, and multi‑signature schemes are deployed to minimize threats including whitelist data forgery, user authentication spoofing, smart contract vulnerabilities, frontrunning, and external oracle manipulation.
These security enhancements are continuously reinforced through rigorous code audits, multi‑signature requirements, DAO oversight, and the adoption of trusted multi‑oracle systems.