ZENTORY is a pre-TGE quantitative research and vault protocol being built on HyperEVM. The project combines non-custodial ERC-4626 vaults with an on-chain signal marketplace where quants submit signed signals, stake ZENT behind those signals, and are scored over time. The core idea is to make quant reputation and strategy performance more verifiable than traditional private signal groups or custodial copy-trading platforms. From a product perspective, the protocol currently has a public testnet deployment, including vaults, staking, governance, signal registry, scoring, and execution contracts. The mainnet launch and ZENT TGE are explicitly gated on external audit completion, multisig migration, and legal review. This makes it suitable for pre-TGE diligence because the token is not yet live on mainnet and there is no active public ICO. Tokenomics The published TGE structure currently proposes a fixed total supply of 1,000,000,000 ZENT with no post-launch mint function. Current working allocation: - Team + founders: 18% - Treasury: 20% - Quant contributor rewards: 22% - LP rewards: 10% - Protocol-owned liquidity: 8% - Testnet airdrop: 3% - Strategic round: 10% - Public DEX float: 5% - Bug bounty + insurance: 4% The project states that exact percentages may still shift by approximately ±2% before finalization. At TGE, the expected tradable float is approximately 57.5M ZENT, or 5.75% of total supply, consisting mainly of the 5% public DEX float plus 25% of the testnet airdrop allocation. Because there is no public token price yet, FDV should be modeled rather than stated as a fixed number: FDV = 1,000,000,000 × assumed token price Circulating market cap at TGE = 57,500,000 × assumed token price This creates a meaningful gap between initial circulating valuation and fully diluted valuation. Unlock and Dilution Risk The most important long-term risk is not the TGE float itself, but how supply enters the market afterward. Published vesting terms include: - Team + founders: 1-year cliff, then 4-year linear vesting - Strategic round: 6-month cliff, then 18-month linear vesting - LP rewards: 24-month emission - Testnet airdrop: 25% at TGE, remaining 75% over 6 months - Quant contributor rewards: ongoing emissions through the scoring system - Treasury: governance-controlled releases rather than one fixed schedule This means dilution pressure accelerates in stages. Around month 6, strategic unlocks begin and the remaining airdrop supply continues entering circulation. Around month 12, team vesting begins. Quant rewards and treasury releases add additional uncertainty because they are not governed by a single simple cliff schedule. For that reason, the project should be evaluated using circulating-supply growth and realized unlocks rather than TGE market cap alone. Team Verification The core team is presented as two co-founders, Edge and Shaman. What is verifiable: - Public GitHub organization and protocol repository - Active protocol codebase - Public testnet contract deployments - Published security and audit documentation - Edge is linked to a public GitHub handle - Official project domain and project-controlled GitHub organization What is less independently verifiable: - Detailed employment history and prior professional track record - Some founder social profiles are still marked as TBA - Legal/KYC claims are stated by the project but are not independently evidenced in the repository So the strongest verification signal is shipped technical work, not biography. Key Risks 1. External audit not yet complete The project has completed internal pentesting and Slither analysis, but the external smart-contract audit is still planned. Mainnet launch depends on this gate. 2. Admin and multisig transition risk The project still needs to complete its planned migration to a 3-of-5 multisig. Until that process is fully executed, operational key risk remains relevant. 3. Execution and strategy risk Even if contracts are secure, vault performance depends on strategy quality and off-chain keeper execution. A secure vault does not guarantee profitable alpha. 4. Oracle and scoring risk Signal scoring depends on trusted data inputs and role-based settlement. Stale or incorrect oracle data could distort quant rankings and reward distribution. 5. HyperEVM ecosystem dependency The protocol is closely tied to HyperEVM and Hyperliquid infrastructure. Chain, validator, or integration failures can directly affect availability and execution. 6. Token incentive sustainability A large portion of supply is reserved for contributor rewards, LP incentives, treasury, and future unlocks. Long-term value depends on protocol usage growing faster than token emissions and dilution. 7. Regulatory risk The project itself identifies token classification as one of its largest live risks. It plans to restrict US users at launch and seek legal opinions under US, EU, and Singapore frameworks. Overall View The strongest part of ZENTORY is that there is already a substantial public technical surface to verify: contracts, testnet deployments, tokenomics documentation, security policy, and launch gating criteria. The weakest part is that the project is still pre-audit, pre-mainnet, and pre-TGE, while the token structure includes a low initial float and significant future emissions. That makes dilution, execution quality, security review, and regulatory clearance more important than headline TGE valuation. I would not evaluate ZENTORY based on early price action alone. The key diligence items after launch would be: - circulating supply growth - actual unlock behavior - treasury releases - vault TVL and fee generation - audit results - protocol revenue - buyback/burn activity - contributor reward emissions - governance decentralization Disclosure I currently hold no ZENT and have received no compensation from ZENTORY Labs. I have no financial relationship with the project. Primary Sources - ZENTORY Protocol Whitepaper: https://github.com/Zentory-Labs/zentory-protocol/blob/main/docs/whitepaper.md - TGE Structure: https://github.com/Zentory-Labs/zentory-protocol/blob/main/docs/TGE_STRUCTURE.md - Current Project State: https://github.com/Zentory-Labs/zentory-protocol/blob/main/STATE.md - Team: https://github.com/Zentory-Labs/zentory-protocol/blob/main/TEAM.md - Investor FAQ: https://github.com/Zentory-Labs/zentory-protocol/blob/main/docs/INVESTOR_FAQ.md - Security Policy: https://github.com/Zentory-Labs/zentory-protocol/blob/main/SECURITY.md