exchange token
HTX DAO HTX
HTX DAO (HTX) is a standard multi-chain governance token deployed on TRON, Ethereum, BSC, and BTTC with a market cap of approximately $1.5–1.8B. The token contract is immutable with no admin keys or minting capabilities—a positive design property. However, HTX DAO has published no quantum risk assessment, cryptographic inventory, PQC migration plan, or quantum-resistant implementation. All token spend authorization inherits quantum-vulnerable ECC signatures from its four host chains. Critically, the DAO's governance execution relies on classical multi-signature administrators whose ECC-based keys are quantum-vulnerable. The QRI Score of 6.5 reflects the total absence of quantum readiness activity combined with the availability of public evidence to assess the risk (on-chain contracts, whitepaper, and audit). The score is capped at 10 by the 'No public cryptographic inventory' Readiness & Risk Cap and at 20 by Stage 1. The project qualifies as 'Inherits L1 Score' for token-transaction purposes but carries material token-specific quantum risk from its DAO governance multisig layer.
Token InheritanceRoadmap OnlyMulti-ChainGovernance TokenExchange Token
Category breakdown
QRI Factors
Algorithm & Implementation Assurance
5.45 / 20
Migration Mechanism, Governance & Ecosystem Coordination
0 / 15
Migration Status & Value-at-Risk
1 / 25
Production Cryptographic Protection
0 / 35
Security Assessment & Evidence Preparedness
0 / 5
Critical Quantum Blockers
- No public cryptographic inventory or quantum threat model has been published by HTX DAO. Readiness & Risk Cap: 10.
- All token spend authorization across TRON, Ethereum, BSC, and BTTC relies entirely on host-chain ECC signatures (ECDSA secp256k1 on ETH/BSC, Ed25519/ECDSA on TRON). These are quantum-vulnerable and no PQC migration path exists at the token level.
- HTX DAO governance execution is controlled by classical multi-signature administrators using quantum-vulnerable ECC keys. A quantum adversary compromising these keys could deploy malicious governance actions affecting treasury and ecosystem funds.
- No quantum risk assessment, PQC migration plan, or quantum-resistant cryptography implementation exists at any level of the HTX DAO ecosystem.
Key Risks
- A cryptographically relevant quantum computer could derive private keys from exposed public keys on any of the four host chains, enabling theft of all HTX tokens held in EOA/standard accounts that have ever sent transactions.
- The DAO multi-signature administrators control governance execution including treasury management, liquidity operations, and ecosystem fund allocation. Quantum compromise of the multisig keys could enable unauthorized deployment of governance decisions.
- The token inherits quantum risk from four separate L1s, each with different quantum readiness postures. TRON and BSC have less publicly documented quantum migration plans compared to Ethereum's structured roadmap.
- Quarterly burn transactions executed by the Governance Committee create recurring quantum-vulnerable signing events with long-exposure public keys on TRON.
- No emergency governance process, quantum-specific incident response, or cryptographic agility mechanism exists to respond to a quantum breakthrough affecting any host chain.
Assurance Notes
- ChainSecurity audit confirms standard TRC-20 token implementation with immutable parameters, fixed supply, and no admin/minting keys. Audit scope is functional correctness and TRC-20 spec compliance, not quantum resistance.
- Token contract itself has no admin keys or minting privileges (positive for token-specific security), but DAO governance relies on classical multi-signature administrators.
- No evidence of quantum risk assessment, PQC migration planning, or quantum-resistant cryptography implementation found in official documentation or public sources.
- Token inherits quantum vulnerability from host chains (TRON, Ethereum, BSC, BTTC), all of which use classical ECC cryptography for transaction signatures and consensus.
- DAO multisig governance represents a long-exposure quantum-vulnerable surface per industry threat models (Google Quantum AI 2026, CertiK 2026).
Non-Scoring Caveats
- ChainSecurity audit is scope-mismatched (TRC-20 compliance only). This is an assurance caveat that affects confidence but does not independently reduce the QRI Score since the quantum-critical vulnerability (total absence of PQC) is already verifiable from other evidence.
- The HTX token has no admin keys or minting capabilities at the token contract level. Token supply integrity cannot be compromised by a quantum adversary through the token contract itself. This is a positive design property but does not mitigate the spend-authorization or governance-multisig vulnerabilities.
- HTX is deployed across four host chains with different quantum readiness postures. Token holders on Ethereum may benefit from Ethereum's structured PQC roadmap (targeting ~2029), while TRON and BSC have less publicly documented quantum migration plans. This diversity creates complex inherited risk.
- Quarterly burns are executed by the HTX DAO Governance Committee through classical wallet signatures (visible on Tronscan). Each quarterly burn transaction exposes public keys and creates a quantum-vulnerable signing event.
Evidence record
Claims and Caveats
Security Assessment & Evidence Preparedness
Public cryptographic inventory and quantum threat model
Claim: HTX DAO has not published any cryptographic inventory, quantum threat model, or quantum risk assessment.
Coverage basis: Assessment preparedness documentation
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Quantum blocker: No public cryptographic inventory exists. Triggers Readiness & Risk Cap of 10.
Assurance: Absence confirmed through review of all official documentation (whitepaper, website, HTX exchange token page), audit reports, and web searches. No quantum-related content found in any official HTX DAO channel.
The project has published extensive documentation on tokenomics, governance, and ecosystem mechanics but zero content addressing quantum risk, cryptographic inventory, or post-quantum planning.
Security Assessment & Evidence Preparedness
Public evidence record supporting assessment
Claim: No quantum-specific evidence record (code references, specs, audits, transaction examples, or reproducible analytics) has been published by HTX DAO.
Coverage basis: Evidence preparedness documentation
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: The ChainSecurity audit covers TRC-20 functional correctness and is not quantum-scoped. It confirms the token has no admin keys, which is relevant but not a quantum-specific assessment.
Third-party evidence (explorers, audit, whitepaper) allows external assessment of quantum vulnerability, but the project itself has produced no quantum-focused evidence.
Production Cryptographic Protection
Spend authorization / transaction signatures are PQC or hybrid-PQC on mainnet
Claim: All HTX token transfers rely on host-chain ECC signatures (ECDSA secp256k1 on Ethereum/BSC, Ed25519/ECDSA on TRON). No PQC or hybrid-PQC spend authorization exists at any level.
Coverage basis: Host-chain signature inheritance
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Quantum blocker: All spend authorization is ECC-only across all four host chains. No PQC path exists.
Assurance: Verified through mainnet explorers and token contract verification on all four chains. Standard TRC-20/ERC-20/BEP-20 tokens have no custom signature logic.
Token inherits host-chain cryptographic properties per Section 7.2. HTX itself has no mechanism to upgrade or change the signature scheme used for token transfers.
Production Cryptographic Protection
Account, address, public-key exposure, and key-derivation design
Claim: All four host chains use classical ECC-based account models. HTX token inherits these designs with no PQC or hybrid controls. Transacted accounts on Ethereum/BSC have fully exposed public keys.
Coverage basis: Host-chain account model inheritance
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: Standard account models on all four chains expose public keys for any account that has sent a transaction. TRON accounts that have only received tokens may have some additional hash-based protection, but most active HTX accounts have exposed public keys.
HTX DAO has no control over host-chain account design. Token holders are subject to the quantum vulnerability of whichever chain they hold HTX on.
Production Cryptographic Protection
Consensus-critical authentication is PQC or hybrid-PQC
Claim: N/A — HTX token has no independent consensus mechanism.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Production Cryptographic Protection
State-integrity and data-availability mechanisms are quantum-safe
Claim: N/A — HTX token has no independent state-integrity or data-availability mechanism.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Production Cryptographic Protection
Privacy and proof layers are quantum-safe
Claim: N/A — HTX token has no privacy features, ZK proof systems, shielded transactions, or confidential transfer mechanisms.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Production Cryptographic Protection
P2P transport, node identity, and peer authentication
Claim: N/A — HTX token has no independent P2P network layer.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Production Cryptographic Protection
Critical wallet, custody, HSM, signer, and hardware-wallet workflows support PQ/hybrid path
Claim: The DAO multi-signature administrators and HTX exchange hot wallets use classical ECC-based custody with no PQC support. No PQ/hybrid wallet workflow exists for any critical HTX ecosystem participant.
Coverage basis: Governance and exchange custody
Implementation score: 0 · Evidence confidence: Medium
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Quantum blocker: DAO multisig administrators and exchange hot wallets use quantum-vulnerable ECC custody with no migration path.
Assurance: The exact multisig administrator addresses are not publicly disclosed in a structured manner. Evidence confidence is Medium because the existence of classical multisig governance is confirmed in the whitepaper but specific key exposure cannot be independently verified.
HTX exchange hot wallet identified on Avalanche (0xa77ff0e1C52f58363a53282624C7BaA5fA91687D) and other chains. These are classical EOA wallets with exposed public keys.
Migration Status & Value-at-Risk
Percentage of economically relevant value-at-risk protected from quantum key-recovery attacks
Claim: 0% of HTX's ~$1.5-1.8B market cap is protected from quantum key-recovery attacks. All value resides on classical ECC-secured host chains with no PQC migration. Coverage falls in the <25% band.
Coverage basis: Market cap and circulating supply data
Implementation score: 0.05 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Quantum blocker: All ~$1.5-1.8B in HTX value is quantum-vulnerable with no protection or migration path.
Assurance: Market cap data sourced from CoinMarketCap (~$1.77B) and CoinGecko (~$1.48B) as of early June 2026. Circulating supply approximately 905-920T HTX. Total supply: 999.99T HTX. All value is held on quantum-vulnerable classical chains.
Coverage is effectively 0%. The <25% threshold implementation score of 0.05 (1/20) is applied per the coverage thresholds table. No portion of HTX value has any quantum protection.
Migration Status & Value-at-Risk
Critical wallets migrated, protected, or inherently PQ-native
Claim: No critical HTX ecosystem wallets (DAO multisig, HTX exchange hot/cold wallets, treasury, liquidity pool managers, governance committee) are migrated to PQC or protected by PQ-native controls.
Coverage basis: Critical wallet inventory
Implementation score: 0 · Evidence confidence: Medium
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Quantum blocker: DAO multisig governance and exchange custody remain fully quantum-vulnerable.
Assurance: Confidence is Medium because the exact multisig administrator addresses and exchange wallet architecture are not fully publicly documented. The existence of multisig governance is confirmed in the whitepaper. Quarterly burn transactions on Tronscan demonstrate governance committee signing activity.
The HTX DAO Governance Committee executes quarterly burns (Q1 2026: ~$19.92M, 10.83T HTX). Each burn transaction is a quantum-vulnerable signing event with exposed public keys on TRON.
Migration Status & Value-at-Risk
Legacy vulnerable pools/accounts/UTXOs/contracts identified, measurable, deprecated, or proven not to exist by design
Claim: No identification, measurement, deprecation, or migration of quantum-vulnerable HTX holdings has been performed. The project has not acknowledged quantum-vulnerable pools or accounts.
Coverage basis: Legacy pool identification
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: The token launched in January 2024, so there is no 'legacy' migration from a predecessor token in the classical sense. However, all current HTX holdings on all chains are quantum-vulnerable and no identification or measurement of vulnerable pools has been conducted.
The HT-to-HTX conversion channel (voluntary migration from the older HT exchange token) is a classical ECC-based migration that itself creates quantum-vulnerable signing events. This is an operational note rather than a separate quantum-critical vulnerability.
Migration Mechanism, Governance & Ecosystem Coordination
Public migration or protection roadmap with sequencing, activation criteria, and dependencies
Claim: No quantum migration or PQC protection roadmap exists for HTX DAO.
Coverage basis: Roadmap documentation
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: The whitepaper explicitly states: 'There is no preset roadmap for the HTX DAO or inherent value of the HTX token.' This confirms absence of any structured planning including quantum migration.
While the token itself cannot independently implement PQC (it inherits host-chain cryptography), the DAO could publish a quantum risk acknowledgement and coordinate with host-chain migration timelines. No such activity exists.
Migration Mechanism, Governance & Ecosystem Coordination
Migration accessibility and defaults: PQ/hybrid account creation, wallet tooling, transaction paths, custody paths, user-facing warnings, education, and migration prompts
Claim: No PQ/hybrid account creation, wallet tooling, migration prompts, or user education exists for HTX. Users have no quantum-safe path for holding or transacting HTX.
Coverage basis: Migration tooling and user experience
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: HTX is traded on multiple centralized exchanges (HTX, BitMart, AscendEX, MEXC, KuCoin, Bit2Me) and decentralized exchanges (SUN.IO, Uniswap, PancakeSwap). None offer PQC-protected custody or trading workflows for HTX.
As a token that inherits host-chain account models, HTX cannot independently offer PQ accounts. This subfactor is scored at the project level for awareness, coordination, and user guidance—all of which are absent.
Migration Mechanism, Governance & Ecosystem Coordination
Migration enforcement and coordination: enforcement mechanisms, deprecation, freeze, disabled legacy signing, restricted withdrawals, unsafe-path blocking, and exchange/custody/bridge/wallet coordination
Claim: No migration enforcement mechanisms exist. No deprecated legacy paths, freeze capabilities, disabled signing, withdrawal restrictions, or exchange coordination for quantum safety.
Coverage basis: Enforcement and coordination mechanisms
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: The token contract has no freeze, pause, or admin functions. While this is generally a security-positive design, it also means there is no mechanism to enforce a quantum migration or restrict vulnerable transactions at the token level.
The immutable token contract design means migration enforcement would need to happen at the host-chain layer or through exchange-level coordination. Neither has been pursued.
Migration Mechanism, Governance & Ecosystem Coordination
Emergency disclosure, incident-response, or governance process for quantum-related vulnerabilities
Claim: No quantum-specific emergency disclosure process, incident-response plan, or governance mechanism exists for HTX DAO.
Coverage basis: Incident response and governance processes
Implementation score: 0 · Evidence confidence: High
Issue classification: assurance-only caveat · Score treatment: score-reducing
Assurance: The whitepaper mentions general security considerations including 'potential vulnerabilities or exploits within smart contracts, and the potential for errors by multi-signature administrators' but contains no quantum-specific incident response planning. This is classified as an assurance-only caveat because the more fundamental quantum-critical vulnerability (total absence of any PQC protection) already drives the score.
While the absence of a quantum-specific IR playbook is an assurance gap, it does not independently reduce the score beyond what the total absence of PQC protection already dictates.
Algorithm & Implementation Assurance
Uses NIST-standardized, standards-track, or broadly reviewed PQC/hybrid-PQC algorithms
Claim: N/A — HTX token has no independent PQC algorithms. Token inherits host-chain cryptography.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Algorithm & Implementation Assurance
Independent cryptographic and implementation audit exists for the quantum-critical scope
Claim: The ChainSecurity audit covers TRC-20 functional correctness and standard compliance, not quantum-critical cryptographic review. No quantum-scoped audit exists.
Coverage basis: Audit scope and coverage
Implementation score: 0 · Evidence confidence: High
Issue classification: assurance-only caveat · Score treatment: score-reducing
Assurance: The ChainSecurity audit (based on a legacy OpenZeppelin TRC-20 implementation) confirms no admin keys, no minting, immutable supply, and standard transfer/approve functionality. It is a quality functional audit but is scope-mismatched for quantum review. The audit does not assess any quantum-critical properties because the token has no custom cryptography to assess.
The audit's confirmation of no special-privilege roles is relevant: it means the token contract itself cannot be exploited by a quantum adversary to mint or manipulate supply. This is a positive design property but does not constitute quantum assurance.
Algorithm & Implementation Assurance
Open-source, reproducible implementation
Claim: The HTX token contract source code is verified and publicly available on all four host chain explorers. The implementation is reproducible from on-chain bytecode.
Coverage basis: Code availability and verifiability
Implementation score: 1 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Assurance: All four contract deployments are verified on their respective explorers. The source code is publicly accessible and the ChainSecurity audit confirmed bytecode matches compiled source. This is a positive property for transparency.
While the token implementation is open-source, this provides no quantum security benefit since there is no PQC code to review. The score reflects that the codebase is transparent and verifiable.
Algorithm & Implementation Assurance
Parameter agility and future upgrade path are documented
Claim: No parameter agility or PQC upgrade path is documented. The token contract is immutable with no upgrade mechanism.
Coverage basis: Upgrade path documentation
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: The token contract is immutable by design—no proxy, no upgradeability, no admin functions. While this prevents malicious upgrades, it also means the token cannot be upgraded to support PQC at the contract level. Any quantum migration would require a new token contract and coordinated ecosystem transition.
The immutability is a double-edged sword: positive for supply integrity assurance, negative for cryptographic agility. A quantum migration would require issuing a new token and coordinating exchange/wallet/user migration.
Algorithm & Implementation Assurance
Stateful-signature safety, side-channel, fault-injection, state-management, hardware-wallet, HSM, or custody implementation risks
Claim: N/A — HTX token has no PQC signature implementation and therefore no stateful-signature or PQC-specific side-channel risks to assess.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Algorithm & Implementation Assurance
Performance and resource-impact analysis exists where PQ signature/verification costs could affect safe deployment
Claim: N/A — No PQC operations exist to benchmark at the token level.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Report metadata