Security model

Khromosome's security is layered — from the cryptography that protects identities, through the contracts and consensus, down to operations. The defining choice is that the chain is post-quantum secured from genesis, not retrofitted.

The layers

1. Cryptography & keys. Accounts use ECDSA/secp256k1 (which a quantum adversary breaks via Shor's algorithm), so Khromosome adds a quantum-safe path natively: an on-chain ML-DSA-87 precompile, PQRegistry identity anchors, and PQVerifier for on-chain verification. See Post-Quantum Security.
2. Smart contracts. Core contracts (KhromeChain, ValidatorRewards, vesting) are audit-prepped with documented invariants and a fuzzed conservation suite for the rewards pool. See Contracts.
3. Consensus. Unmodified Ethereum proof-of-stake (Reth + Lighthouse) — the network inherits Ethereum's audited consensus rather than a bespoke mechanism. See Architecture.
4. Off-chain components. RPC endpoints are operationally separated from validators; the cross-chain bridge relayer is a trusted component with its own threat model.
5. Operations & governance. Privileged actions are minimized and monitored; admin roles can rotate and start emissions but never move user funds.

Reporting

Found a vulnerability? Disclose it responsibly to the team rather than opening a public issue. Production deployments are gated behind an external audit and a pre-mainnet security review.

warning

Several application-layer components (e.g. the on-chain vault and the bridge relayer) may be unaudited or in review at any given time. Check the current status before trusting them with value or sensitive data.