Transparency
DEVORAQ transparency is designed around fixed token rules, clear allocation, visible vesting, traceable reward vaults and published on-chain contract information.
ContractsPublish official addresses
VestingTeam & founders
TreasuryControlled & traceable
Allocation100% defined framework
TRANSPARENCY
OVERVIEW
Fixed Supply
100M DVQNo additional mintingCore token ruleToken Allocation
10 Categories100% defined allocation frameworkAllocation plan publishedStaking Rewards Vault
15,000,000 DVQ15% staking allocationContract address pendingTreasury
5,000,000 DVQ5% treasury allocationMultisig / control setup pendingLiquidity
15,000,000 DVQ15% liquidity allocationLP information to be publishedTeam Vesting
6,000,000 DVQ6% team allocationVesting contract pendingFounders Vesting
5,000,000 DVQ5% founders allocationVesting contract pendingOFFICIAL
CONTRACT REGISTRY
No production contract address is shown until the contract is deployed, verified and confirmed as official. This prevents users from relying on placeholder or incorrect addresses.
| Contract | Purpose | Official Address | Status |
|---|---|---|---|
| DVQ Token | Core BEP-20 token | Not published yet | Pending |
| Allocation | One-time token distribution | Not published yet | Pending |
| Staking | Stake / reward logic | Not published yet | Pending |
| Rewards Vault | Sponsor & level reward funding | Not published yet | Pending |
| Vesting | Team / founders token lock | Not published yet | Pending |
| Treasury | Treasury control | Not published yet | Pending |
| Liquidity | LP / liquidity management | Not published yet | Pending |
TOKEN
ALLOCATION TRANSPARENCY
Fixed supply allocation across ten defined categories.
TEAM TOKENS
6,000,000 DVQ
6% allocationFOUNDERS TOKENS
5,000,000 DVQ
5% allocationSTAKING REWARDS
15,000,000 DVQ
Pre-defined reward allocationReward distribution should be limited by the available pre-funded reward pool and applicable staking rules.Verified Source Code
After deployment, verified source code and official contract addresses should be published together.
Multisig Controls
Treasury and sensitive operational controls should use multiple approvals rather than a single private key.
Vesting Visibility
Team and founder token unlock schedules should be visible and traceable.
On-Chain Traceability
Token movements, staking, rewards and treasury transactions should be independently verifiable.
SMART CONTRACT SECURITY
Test β Review β Audit β Mainnet
Production deployment should follow BSC Testnet testing, unit tests, reward-liability simulation, source verification and independent security review.TREASURY SECURITY
Multisig First
- No single-person treasury control for critical funds.
- Separate operational and long-term treasury wallets.
- Publish official treasury addresses after setup.
- Use timelock where delayed execution improves safety.
Transparency Notice
Contract addresses, circulating supply, locked balances, liquidity, vesting schedules and audit information should be published only when verified and current. Placeholder values must never be presented as live blockchain data.
TRANSPARENCY BY DESIGN