mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
31 lines
1.3 KiB
TeX
31 lines
1.3 KiB
TeX
\section{Why Q-Chain}
|
|
|
|
\label{sec:qchain}
|
|
|
|
The Q-Chain (Quantum Chain) is the preferred anchor target for three reasons.
|
|
|
|
\paragraph{PQ-safe finality.}
|
|
Q-Chain blocks carry Quasar certificates: triple-signed (BLS + ML-DSA +
|
|
Pulsar) finality proofs. An anchor finalized by a QuasarCert inherits
|
|
post-quantum security. C-Chain finality relies on Snow consensus
|
|
(probabilistic, classical signatures only).
|
|
|
|
\paragraph{DAG parallelism.}
|
|
Q-Chain processes transactions as a DAG, not a sequential block. Anchor
|
|
submissions from independent appIDs are conflict-free and process in
|
|
parallel. On C-Chain, all transactions compete for sequential block space.
|
|
|
|
\paragraph{Cost.}
|
|
Q-Chain transaction fees are validator-set-determined and currently near
|
|
zero for data-only transactions (no EVM execution). A C-Chain anchor at
|
|
25,400 gas $\times$ 25 nLUX/gas = 635 nLUX ($\approx$ \$0.001 at
|
|
\$1.50/LUX). Q-Chain is 10--100$\times$ cheaper for equivalent data
|
|
anchoring because it avoids EVM metering overhead.
|
|
|
|
\paragraph{C-Chain alternative.}
|
|
If the application already pays C-Chain gas (e.g., a DeFi protocol on
|
|
C-Chain), using the same chain for anchoring avoids cross-chain
|
|
complexity. The precompile is registered on both chains.
|
|
|
|
% ============================================================================
|