
The VTXVault contract is the heart of the ecosystem. After deployment, the full 20,000,000,000 VTX are transferred from the token contract into the Vault. Only when the Vault holds the entire supply can it be finalized.
The function finalizeVaultInit() checks that the Vault’s balance is
exactly equal to the full supply. Only then does vaultInitialized turn true.
Until that moment, no vesting, no dev payouts, no liquidity moves are allowed.
The Owner Pool of 4,000,000,000 VTX is held inside the Vault and
released only through a strict, time-based schedule. The function
ownerVestingReleasable() calculates how much can be claimed based on:
• Total vesting period: 10 years
• Unlock rate: 10% of the Owner Pool per year
• Actual elapsed time since vestingStart
The owner (or the designated owner wallet) can call
claimOwnerVesting() to receive the releasable amount. This function:
• Requires the Vault to be initialized
• Uses the releasable calculation
• Decreases the internal Owner pool balance
• Transfers tokens directly to the owner wallet
There are no manual shortcuts and no arbitrary unlocks.
Each pool inside the Vault is connected to a specific role:
Dev module, Rewards module, Maintenance module, HyperChain module and
the LiquidityManager. These roles are set once by the owner and then
permanently locked with lockRoles().
After roles are locked:
• Only the Dev module can call payDev()
• Only the Rewards module can call payReward()
• Only the Maintenance module can call payMaintenance()
• Only the Hyper module can call payHyperGrant()
• Only the LiquidityManager can call moveToLiquidity()
The owner cannot directly drain any of these pools.