Status DataClose notification
Bug bounty Triaged by HackenProof New

Quantova: Program info

Quantova

Company: Quantova

Scope Review:
310
Submissions:
5
Total rewards:
$0
Reputation
150 points required
PoC
Required
Submission fee
$5

Program is: active now

Live

Foundational blockchain platform powering decentralized apps, stablecoins, and post quantum resistant smart contracts via QVM.

Scope

In scope
TargetTypeSeverity

Q-Crypto The post-quantum cryptography library (ML-DSA-65, SLH-DSA, ML-KEM-768, SHA3). It produces every signature and hash on the network, so a flaw compromises keys, signatures and integrity across the whole stack.

ProtocolCritical

Quantova-Chain The node, ledger and state machine. Transaction execution, value conservation, staking, governance and fees. The largest attack surface. A flaw can move or mint funds, corrupt state, or halt the chain.

ProtocolCritical

QRC-CONSENSUS The committee BFT consensus and deterministic finality. A flaw can fork the chain, break finality, or stop block production.

ProtocolCritical

QVM The virtual machine that executes untrusted smart-contract bytecode under gas metering and memory bounds. A flaw lets hostile contract code escape isolation or corrupt state.

ProtocolCritical

Quanta-Smart-Contract-language The smart-contract language and compiler that make unsafe contracts fail to compile. A compiler flaw lets an unsafe contract build and deploy.

Smart ContractHigh

The hash-based STARK prover and verifier. A soundness flaw lets a false statement be proven and accepted on chain.

ProtocolHigh

Focus Area

Quantova pays only for a reproducible, protocol-level break proven with a working proof of concept that runs against the exact pinned commit on the main branch of an in-scope repository. A reward is earned only in the two categories below. No other class of report is eligible for payment, at any severity, in any repository.

CRITICAL paid only when the proof of concept demonstrates, against the pinned commit, one of:

  • Loss of funds. A party who does not own a balance can create, take, move or permanently lock value that is not theirs. This covers minting outside the governed supply, moving a balance without a valid signature from its holder, breaking value conservation across a transaction, forging a signature or key that authorises a transfer, and permanently locking user balances so they can never be spent.
  • Full chain freeze. A remotely triggerable, reproducible failure that halts block production or finality across the honest validator set and does not recover on its own. The honest validators must be following the protocol and must not be under the reporter's control.

HIGH paid only for a chain-freezing defect that is real but short of a permanent full halt, and only as:

  • A remotely triggerable defect in the consensus, node or execution logic that stops finality or block production across the honest validator set for a sustained period and clears only through a coordinated restart, not on its own.
  • A reproducible protocol defect that forces the whole validator set below its guaranteed finality and block production for a sustained period. A High freeze is paid only when the trigger is a defect in the protocol logic, the honest validators are following the protocol, and the effect is shown on the whole set rather than on one node. A single node that stalls, panics or restarts while the set keeps producing and finalising blocks is not a freeze and is not paid.

Not eligible for a reward

The following never earn a reward, at any severity, whatever the repository:

  • Any report without a working proof of concept that reproduces against the exact pinned commit.
  • Theoretical findings, missing hardening, best-practice notes, code quality or style observations, and anything that cannot be shown to move funds or freeze the chain as defined above.
  • Denial of service from volume or load, request flooding, rate-limit behaviour, memory or CPU pressure under legitimate traffic, and any network-layer or infrastructure attack.
  • A crash, panic or restart of a single node that does not halt the honest validator set or its finality.
  • Anything that needs control of a validator majority, privileged or operator access, a stolen or mishandled operator key, physical access, or social engineering.
  • Fees, slashing, staking rewards, governance parameters, supply policy and other economic or governance design choices. These are set by the owner and are not defects.
  • Findings only reachable on a fork, a modified build, a different commit, or outside the pinned scope.
  • Issues already known, already fixed on the main branch, previously reported, or disclosed publicly before the report.
  • Test code, benchmarks, examples, documentation, build and continuous integration tooling, and third-party dependencies and their published advisories.

Testnet. The network in scope is a testnet and its unit TQTOV carries no monetary value. A loss-of-funds report is judged on the protocol logic that would move or lock real value on the same code, not on the testnet balance. Reports are paid on the strength of the demonstrated break, never on the testnet amount involved. Tier and payment. The tier shown against each repository under Scope marks where critical and high impact is most likely, not an entitlement. Payment is set by the demonstrated impact category above, not by the repository a finding sits in. Reward amounts within each paid category are set in the HackenProof program.

A valid submission names the in-scope repository and the exact commit, states which paid category it meets, and includes a self-contained proof of concept an engineer can run to reproduce it. A report that does not establish loss of funds or a chain freeze as defined above, with a working proof of concept, is closed without a reward.

Program Rules

  • Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
  • Make every effort not to damage or restrict the availability of products, services, or infrastructure
  • Avoid compromising any personal data, interruption, or degradation of any service
  • Don’t access or modify other user data, localize all tests to your accounts
  • Perform testing only within the scope
  • Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
  • Don’t spam forms or account creation flows using automated scanners
  • In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
  • Don’t break any law and stay in the defined scope
  • Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
  • All communication regarding the program must take place exclusively through the HackenProof platform. Contacting the project team directly through support channels, social media, or any other external communication channels is strictly prohibited. Researchers who violate this rule may be disqualified from the program and may face account suspension.

Eligibility and Coordinated Disclosure

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

  • You must be the first reporter of a vulnerability.
  • The vulnerability must be a qualifying vulnerability.
  • Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
  • You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
  • You must not be a former or current employee of us or one of its contractor.
  • ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
  • Provide detailed but to-the point reproduction steps.
  • AI-generated reports without runable PoC are not accepted under this program.

Disclosure Guidelines

  • Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • No vulnerability disclosure, including partial is allowed for the moment.
  • Platform-Only Disclosure: Disclosure is only possible through the HackenProof Disclosure function.
  • Researchers may request disclosure (Limited or Full) within the report ticket;
  • We reserve the right to approve, redact, or deny disclosure requests at our sole discretion.
  • Mutual Required: Any publication requires explicit mutual agreement. Reports must remain Private until the status is officially changed to "Public" on the HackenProof platform by the team.

Testing Standards

Security testing must be conducted in accordance with applicable law and ethical research standards. Testing activities must not involve unauthorized access, disruption, or exposure of systems, data, or assets not owned or expressly authorized by the researcher.

Testing must be limited to local environments, designated test networks, or explicitly permitted resources.