
Program is: active now
LiveFoundational blockchain platform powering decentralized apps, stablecoins, and post quantum resistant smart contracts via QVM.
| Target | Type | Severity |
|---|---|---|
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. | Protocol | Critical |
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. | Protocol | Critical |
QRC-CONSENSUS The committee BFT consensus and deterministic finality. A flaw can fork the chain, break finality, or stop block production. | Protocol | Critical |
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. | Protocol | Critical |
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 Contract | High |
The hash-based STARK prover and verifier. A soundness flaw lets a false statement be proven and accepted on chain. | Protocol | High |
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.
The following never earn a reward, at any severity, whatever the repository:
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.
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:
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.