Protocol Overview
The production map for Vorax contracts, user actions, and value flows.
Vorax combines token launch infrastructure, VRX issuance, and DUSX lending into one BSC protocol. Each surface has its own contracts and user flows, but production releases should be treated as one system: contracts, UI constants, backend services, deployment scripts, and docs must agree.
System Surfaces
| Area | Purpose | Production Notes |
|---|---|---|
| Launchpad | Deploy BSC tokens and initialize launch markets | Creators configure metadata, vaults, airdrops, fee recipients, and admin permissions |
| Mine | Issue VRX through BNB-denominated mint batches | Mint proceeds go to treasury; rewards are native BNB |
| Lending | Let users borrow DUSX against approved collateral | Risk depends on collateral value, oracle health, LTV, and liquidation penalties |
| Revenue Router | Route protocol revenue toward VRX buy-and-burn | Operator-triggered execution with redirect and rescue controls |
| Treasury | Hold mint proceeds and operational capital | Liquidity additions are manual unless a restricted liquidity tool is deployed |
Value Flow
- Users launch tokens, mint VRX, stake, borrow, repay, or provide approved assets.
- Protocol revenue is collected by the module that generated it.
- Per-source redirects can forward a configured share before conversion.
- Remaining revenue can be routed through protected VRX buy execution.
- Acquired VRX can be burned, reducing supply.
Production Rule
Every release that changes contracts, addresses, parameters, or backend behavior must update all of the following:
- Contract deployment scripts.
- Verification scripts.
- UI contract constants and generated ABIs.
- Backend environment and service configuration.
- Documentation and operational runbooks.
If any one of those is stale, the release is not production-ready.