QOM X QOM X
QOM mainnet is live· qom_33303-1

Post-quantum where it matters. EVM where you already are.

QOM, the Quantum Operating Machine, is a hybrid post-quantum Cosmos EVM Layer 1: every validator vote carries an ML-DSA-87 signature, and nodes reject any vote whose signature doesn't match that validator's on-chain key. Accounts can add an ML-DSA-87 key and smart contracts can verify ML-DSA-87 natively, while secp256k1 keeps MetaMask and your existing tools working.

Stake QOMX Start building →

Network at a glance Explorer ↗
Latest block
—
live from scan.qomx.io
Block time
~5 s
single-slot finality
Vote signature
ML-DSA-87
NIST FIPS 204, Level 5
Simple transfer
≈ 1 QOMX
21,000 gas at base fee
EVM chain ID
33303
Supply on QOM
200M
Inflation
0%

What is QOM

A familiar EVM, with quantum-resistant signatures where they count.

Most blockchains secure their consensus and accounts with elliptic-curve cryptography (ECDSA, Ed25519, BLS). A large enough quantum computer could forge those signatures. QOM requires NIST-standard ML-DSA-87 signatures on validator votes and lets accounts opt into them, while keeping full Ethereum compatibility so users and builders don't have to change tools.

QOMX is the native gas and staking token of QOM. It also exists on BNB Smart Chain, and holders switch between the two through the QOM X Market (see Token & fees).

Post-quantum consensus

Every validator vote carries an ML-DSA-87 signature, and nodes reject votes that don't match the validator's on-chain key.

Hybrid PQ accounts

Optionally register an ML-DSA-87 key. It then co-signs every Cosmos transaction and opens time-limited MetaMask windows.

Full EVM

Solidity, MetaMask, Hardhat, Foundry, ethers and viem. Deploy existing contracts unchanged.

Fast, final blocks

CometBFT consensus: ~5 s blocks with instant finality. No reorgs, no waiting for confirmations.

Hybrid by design

Post-quantum where it matters today. Classical where wallets still need it.

QOM uses ML-DSA-87 where a forged signature would do the most damage, and keeps classical cryptography where today's wallets and tools still depend on it. Here is exactly which is which.

Post-quantum today

  • Consensus votes: every validator precommit carries an ML-DSA-87 signature, and votes that don't match the validator's on-chain key are rejected.
  • Validator key binding: each validator's ML-DSA-87 key is bound on-chain, and a node refuses to start if its key is missing or doesn't match.
  • Opt-in accounts: register an ML-DSA-87 key and every Cosmos transaction must be co-signed with it; MetaMask transactions then need a time-boxed EVM window opened with that key.
  • Key rotation: account and validator ML-DSA-87 keys can be replaced, with a signature from the current key.
  • Smart contracts: a native precompile verifies ML-DSA-87 signatures inside Solidity.

Classical today

  • Node-to-node encryption between peers.
  • Block proposals and commit signatures (Ed25519).
  • Light clients and IBC, which verify Ed25519 commit signatures.
  • MetaMask and other EVM transactions (secp256k1), including a registered account's transactions during an open window.

Kept classical so every EVM wallet works, and replaceable by chain upgrade.

Post-quantum security, explained simply

Three layers of protection.

A blockchain makes promises at three levels: that blocks were agreed by the validators (consensus), that only you can move your funds (accounts), and that apps can check who signed what (contracts). QOM adds NIST-standard ML-DSA-87 signatures at each level, without breaking the wallets people already use.

Layer 1

Consensus: ML-DSA-87 vote extensions

When a validator votes to finalize a block, it signs the vote with ML-DSA-87 (FIPS 204, the highest NIST security level) as well as CometBFT's usual Ed25519 key. Each validator's ML-DSA-87 public key is registered on-chain, and nodes reject any vote whose ML-DSA-87 signature doesn't match that key. New validators bind theirs with evmd tx pqauth register-validator-mldsa-key; until they do, their votes are rejected.

  1. 1Each validator signs its precommit with ML-DSA-87, covering the chain, height, round, vote type, block hash and its own address. A validator node refuses to start if its ML-DSA-87 key is missing or doesn't match the key bound to it on-chain.
  2. 2Every node checks other validators' votes against their on-chain ML-DSA-87 keys. A vote with a missing, invalid or mismatched signature is rejected and doesn't count.
  3. 3A block finalizes once more than two-thirds of the voting power has cast accepted precommits.
Layer 2

Accounts: the hybrid pqauth model

Every QOM account starts as a normal Ethereum-style account signed with secp256k1, so MetaMask just works. With the pqauth module, an account can choose to register an ML-DSA-87 key. From then on, every Cosmos transaction needs the ML-DSA-87 key as well as secp256k1, and Ethereum transactions sent from the account are rejected unless its EVM window is open. secp256k1 is still required, and while a window is open it alone authorizes the account's MetaMask transactions.

1. Register
Bind an ML-DSA-87 key to your address, with proof that you hold it. It can't be removed, and rotating it needs the current key.
2. Sign with both
Every Cosmos transaction from the account then needs a valid ML-DSA-87 signature as well as the secp256k1 one.
3. Open an EVM window
Ethereum (MetaMask) transactions sent from the account are rejected unless its EVM window is open. You open one with an ML-DSA-signed transaction; it lasts 1,000 blocks (about 83 minutes) and then closes automatically.

Accounts that don't register a key work exactly as on any EVM chain. Registration and window commands use the evmd CLI (evmd tx pqauth gen-mldsa-key, register-mldsa-key, open-evm-window). See the FAQ in the Validator portal.

Each ML-DSA-87 check costs 250,000 gas (about 12 QOMX at today's base fee), so co-signed transactions cost more than plain ones.

Layer 3

Contracts: ML-DSA-87 verify precompile

Verify ML-DSA-87 signatures inside Solidity. The precompile at 0x0000000000000000000000000000000000000401 takes message ‖ public key (2,592 bytes) ‖ signature (4,627 bytes) and returns 1 if the signature is valid, 0 if not.

  • Gas: 250,000 plus 8 per input byte (about 308,000 for a 32-byte message, plus calldata).
  • Use it for post-quantum-guarded vaults, multisigs and smart wallets.
  • Pure ML-DSA-87 with an empty context string, so signers must not set a context.
MLDSA87.sol
// ML-DSA-87 verify precompile on QOM
// input: message || pubKey (2,592 bytes) || sig (4,627 bytes)
address constant MLDSA87 = address(uint160(0x0401));

function verifyMLDSA87(
    bytes memory message,
    bytes memory pubKey,
    bytes memory sig
) view returns (bool) {
    (bool ok, bytes memory out) =
        MLDSA87.staticcall(abi.encodePacked(message, pubKey, sig));
    return ok && out.length == 32 && out[31] == 0x01;
}
Straight talk: no public blockchain is “quantum-proof” in every component today. On QOM, block proposals and commit signatures are Ed25519; the ML-DSA-87 signatures travel in vote extensions, are checked live and aren't stored in blocks. Each node checks other validators' votes, so with today's single validator the cross-check starts to matter as more validators join. During an open EVM window, MetaMask transactions from a registered account are authorized by secp256k1 alone. Node-to-node encryption and light-client/IBC verification still use classical cryptography, and accounts without a registered key use classical secp256k1.

The path to full post-quantum

Tightened by chain upgrade, as wallets catch up.

QOM's post-quantum rules live in its own on-chain module and node code. Going further is a chain upgrade, made once EVM wallets and tooling can sign with post-quantum keys. We don't put dates on it.

  1. 1Live

    Today

    Post-quantum consensus votes, opt-in post-quantum accounts and ML-DSA-87 verification for contracts, live on mainnet.

  2. 2Chain upgrade

    Next

    Stricter rules for registered accounts, such as shorter EVM windows and tighter limits on what a window can reach.

  3. 3Chain upgrade

    When EVM wallets sign ML-DSA

    Accounts that require a post-quantum signature on every transaction, then post-quantum block signatures, peer encryption and light clients as the underlying software supports them.

EVM & MetaMask

Connect in one click.

QOM runs Cosmos EVM, so it speaks standard Ethereum JSON-RPC. Add the network to MetaMask (or Rabby, OKX, Trust, Bitget) with the button, or enter the details by hand.

Get QOMX on the Market
  • ✓Native gas token QOMX, with 18 decimals like ETH
  • ✓EIP-1559 fee market (base fee + priority fee)
  • ✓30,000,000 gas per block
Add network manually tap a value to copy
Network name
RPC URL
Chain ID
Currency symbol
Block explorer

Staking & validators

Stake QOMX, earn from network fees.

QOM is proof-of-stake. Delegate QOMX to a validator in the QOM Validator portal using MetaMask: delegate, claim rewards and undelegate in a few clicks. Because inflation is 0%, rewards come from real transaction fees, not newly minted tokens.

Where decentralization stands today: QOM launched with a single genesis validator operated by the QOM X team. The protocol supports up to 100 active validators, and the validator set will grow as independent operators join.
Open the Validator portal
Unbonding period
14 days
Max validators
100
Active validators
1
Reward source
Fees (98%)
2% community pool
Double-sign slash
5%
Downtime slash
1%
+10 min jail
Governance: on-chain proposals with a 1 QOMX deposit, 48-hour voting period, 33.4% quorum and 50% pass threshold. Vote from the Validator portal.

Token & fees

QOMX: fixed supply, tiny fees.

Supply on QOM
200,000,000

Native QOMX on QOM. Mint inflation is 0%, so staking creates no new tokens.

Base fee
47,619 gwei

A plain QOMX transfer (21,000 gas) costs about 1 QOMX. The base fee adjusts with demand (EIP-1559).

Where fees go
Validators & delegators98%
Community pool2%

One token on two chains, 200M in effect

QOMX exists as 200,000,000 native tokens on QOM and 200,000,000 BEP-20 tokens on BNB Smart Chain. You can get QOMX on the QOM X Market by trading the QOMX/USDT pair (USDT can be deposited from Ethereum or BSC), or by depositing QOMX from BSC. Then withdraw it to QOM (or to BSC). While you switch chains, the exchange holds the tokens in custody, so the circulating supply across both chains stays at 200M in effect, not 400M.

BSC: 0xc9e127bfca0b16c276444fdc9600ee876281a831

Two ways onto QOM

Both routes finish the same way: you withdraw QOMX from the QOM X Market to your address on QOM.

Route A · QOM X Market

  1. 1Deposit USDT to the QOM X Market from Ethereum or BSC.
  2. 2Buy QOMX on the QOMX/USDT pair.
  3. 3Withdraw QOMX to QOM.

Route B · Q Bridge on BSC

  1. 1Bridge USDC or USDT from Ethereum to BSC as Q with the QOM X Bridge.
  2. 2Buy QOMX with Q or BNB on QOM DEX.
  3. 3Deposit the QOMX to the QOM X Market.
  4. 4Withdraw QOMX to QOM.

ⓘWhile QOMX moves between BSC and QOM it is held in exchange custody, so the effective supply stays 200M.

Network details

Everything in one table.

NetworkQOM (mainnet)
Cosmos chain IDqom_33303-1
EVM chain ID33303 (0x8217)
Native token / base denomQOMX, 18 decimals / aqomx
EVM JSON-RPChttps://rpc.qomx.io
Block explorerhttps://scan.qomx.io
FrameworkCosmos SDK v0.54 + Cosmos EVM, CometBFT consensus
Consensus signaturesEd25519 block signatures + ML-DSA-87 vote extensions (enabled from block 1). Votes whose ML-DSA-87 signature is missing or doesn't match the on-chain key are rejected.
Account signaturessecp256k1; optional ML-DSA-87 via pqauth (required on Cosmos transactions once registered)
EVM window (pqauth)1,000 blocks (≈ 83 min); set at genesis, changeable by chain upgrade
Post-quantum verify precompileML-DSA-87 at 0x…0401; 250,000 gas + 8 per input byte
Block time / finality~5 s, single-slot (instant) finality
Block gas limit30,000,000
Minimum gas price47,619,047,619,048 aqomx (≈ 47,619 gwei)
Supply on QOM / inflation200,000,000 QOMX / 0%
Unbonding period14 days
Getting QOMX on QOM / switching chainsOn the QOM X Market: trade QOMX/USDT (USDT deposits from Ethereum or BSC) or deposit QOMX from BSC, then withdraw to QOM or BSC (exchange custody)

Ecosystem

One account, a full suite of apps.

Built and run by QOM X. Connect the same wallet across every app.

How QOM compares

Post-quantum, without leaving the EVM.

A factual snapshot of how leading chains approach quantum-resistant signatures, based on each project's public documentation as of November 2026.

Swipe the table sideways →

ChainPQ signatures in consensusPQ accountsMetaMask / EVMStatus
QOM ✓Votes need an ML-DSA-87 signature matching the on-chain key (with Ed25519) ✓Optional ML-DSA-87 key; EVM via time-limited window; ML-DSA-87 verify for contracts ✓Native, standard tooling Mainnet live (1 validator)
QRL 2.0 (Zond) ✓ ML-DSA-87 ✓ML-DSA-87 only EVM-like (QRVM, Hyperion); needs QRL-specific tooling Testnet; mainnet date not set
Algorand Falcon state proofs for history; PQ consensus on roadmap ✓Native Falcon-1024 accounts No (AVM) Mainnet
Ethereum, Monad, Sei, Avalanche C-Chain Classical elliptic-curve signatures Classical (secp256k1) ✓Native Mainnet
Solana, Sui, Aptos Classical elliptic-curve signatures Classical by default No (non-EVM VMs) Mainnet

Large chains are much faster and more decentralized than QOM today. QOM's focus is post-quantum signatures with full EVM compatibility. Corrections welcome on Telegram.

Developer quickstart

Ship your Solidity app in minutes.

Point your existing toolchain at the QOM RPC. No new language, compiler or SDK.

  1. 1Add QOM to your wallet and get QOMX: buy it on the Market and withdraw to QOM.
  2. 2Add the network to Hardhat or Foundry.
  3. 3Deploy, then verify on QOM Scan.
Read the docs
hardhat.config.js
// npm i -D hardhat @nomicfoundation/hardhat-toolbox
module.exports = {
  solidity: "0.8.24",
  networks: {
    qom: {
      url: "https://rpc.qomx.io",
      chainId: 33303,
      accounts: [process.env.PRIVATE_KEY],
    },
  },
};
Foundry
forge create src/Token.sol:Token \
  --rpc-url https://rpc.qomx.io \
  --private-key $PRIVATE_KEY \
  --broadcast
Check the chain
cast chain-id --rpc-url https://rpc.qomx.io
# 33303
cast block-number --rpc-url https://rpc.qomx.io

FAQ

Questions, answered.

What does "QOM" stand for?+

Quantum Operating Machine. It's the Layer 1 blockchain behind the QOM X ecosystem, and QOMX is its native token.

Is QOM fully quantum-proof?+

No, and no chain is today. QOM is a hybrid: validator votes must carry ML-DSA-87 signatures that match on-chain keys, accounts can opt in to ML-DSA-87 co-signing, and contracts can verify ML-DSA-87. MetaMask transactions, block signatures, node-to-node encryption and light clients still use classical cryptography, and these can be upgraded as post-quantum wallets and tooling mature.

Can smart contracts verify post-quantum signatures?+

Yes. QOM has a native ML-DSA-87 verify precompile at 0x0000000000000000000000000000000000000401. Pass message ‖ public key (2,592 bytes) ‖ signature (4,627 bytes) and it returns 1 if the signature is valid, 0 if not. It costs 250,000 gas plus 8 gas per input byte and uses pure ML-DSA-87 with an empty context string.

What is still classical on QOM?+

Node-to-node encryption, Ed25519 block proposals and commit signatures, light clients and IBC, and MetaMask (secp256k1) transactions, including those from a registered account during an open EVM window. They stay classical so existing wallets and tools keep working, and they can be upgraded by chain upgrade as post-quantum wallets and tooling mature.

Why do MetaMask transactions need an EVM window?+

No mainstream EVM wallet can sign with ML-DSA yet. If your account has a registered ML-DSA-87 key, the chain rejects Ethereum (MetaMask) transactions sent from it unless you have opened an EVM window with an ML-DSA-signed transaction (evmd tx pqauth open-evm-window). The window lasts 1,000 blocks (about 83 minutes) and closes automatically. Accounts without a registered key never need a window.

How do I get QOMX on QOM?+

There are two ways. Route A: deposit USDT to the QOM X Market from Ethereum or BSC, buy QOMX on the QOMX/USDT pair, then withdraw QOMX to QOM. Route B: bridge USDC or USDT from Ethereum to BSC as Q with the QOM X Bridge, buy QOMX with Q or BNB on QOM DEX, deposit the QOMX to the QOM X Market, then withdraw it to QOM.

How do I get QOMX on QOM, or move it between BSC and QOM?+

Through the QOM X Market: buy QOMX on the QOMX/USDT pair (you can deposit USDT from Ethereum or BSC), or deposit QOMX from BSC, then withdraw it to QOM (or to BSC). The exchange holds the tokens in custody while you switch chains, so the effective supply stays 200M. The QOM X Bridge is a separate app for USDT/USDC from Ethereum to the Q stablecoin on BSC.

Is the total QOMX supply 400 million?+

No. There are 200M QOMX on QOM and 200M on BSC, but tokens only move between chains through exchange custody. The circulating supply across both chains stays at 200M in effect.

How do I register a post-quantum key for my account?+

Registration is optional and currently done with the evmd CLI: generate a key with evmd tx pqauth gen-mldsa-key, then register it with evmd tx pqauth register-mldsa-key (which includes a proof that you hold the key). Registration can't be undone. Rotating with rotate-mldsa-key needs your current ML-DSA-87 key, so if you lose that key file the account can no longer send transactions. Keep an offline backup. Registering also removes any authz grants and fee allowances you had given.

How much does a transaction cost?+

A simple transfer uses 21,000 gas. At the current base fee that's about 1 QOMX, a fraction of a cent. Contract calls cost more gas, and the base fee rises slightly when blocks are busy.

How many validators secure QOM?+

Today, one genesis validator operated by the QOM X team. The chain supports up to 100 active validators. Anyone can already delegate QOMX in the Validator portal.

Is QOMX inflationary? Where do staking rewards come from?+

No. Inflation on QOM is 0%, so no new QOMX is minted. Staking rewards come from transaction fees: 98% go to validators and their delegators, 2% to the community pool.

How long does unstaking take?+

14 days. Undelegated QOMX stops earning right away and returns to your wallet automatically when the unbonding period ends.

Build on the post-quantum EVM.

Get QOMX on the QOM X Market by trading QOMX/USDT (deposit USDT from Ethereum or BSC) or depositing QOMX from BSC, then withdraw to QOM. Add QOM to your wallet, stake QOMX, or deploy your first contract today.