mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
Restructured from flat .tex/.pdf files into per-paper subdirectories. Added Antje Worring as co-author on all papers. Synced PDFs to pdfs/ for download site.
33 lines
1.7 KiB
TeX
33 lines
1.7 KiB
TeX
\section{Introduction}
|
|
|
|
\label{sec:introduction}
|
|
|
|
The security of every major blockchain rests on the hardness of the discrete logarithm
|
|
problem (DLP) on elliptic curves. Bitcoin uses ECDSA on secp256k1. Ethereum uses
|
|
ECDSA on secp256k1 for transactions and BLS12-381 for consensus. Lux uses BLS12-381
|
|
for consensus, ECDSA for C-Chain transactions, and EdDSA for bridge operations.
|
|
Shor's algorithm~\cite{shor1997} solves DLP in polynomial time on a quantum computer,
|
|
breaking all of these schemes simultaneously.
|
|
|
|
This paper is not about whether quantum computers will eventually break blockchain
|
|
cryptography---they will, given sufficient scale. It is about \emph{when} and
|
|
\emph{how}, and what the consequences are for systems that do not prepare.
|
|
|
|
The central argument is that blockchain is \emph{uniquely} vulnerable to quantum
|
|
attack compared to other cryptographic systems, for three reasons:
|
|
|
|
\begin{enumerate}[leftmargin=2em]
|
|
\item \textbf{Permanent public record}: Every signature ever produced is stored
|
|
on-chain forever. There is no concept of session expiry.
|
|
\item \textbf{Harvest-now-decrypt-later}: An adversary need not have a quantum
|
|
computer today. Recording signed transactions and public keys today is
|
|
sufficient to mount attacks years later.
|
|
\item \textbf{Economic persistence}: Unlike a TLS session protecting a single
|
|
HTTP request, blockchain signatures protect assets that may appreciate in
|
|
value over decades.
|
|
\end{enumerate}
|
|
|
|
%% ========================================================================
|
|
%% 2. SHOR'S ALGORITHM: IMPACT ON BLOCKCHAIN PRIMITIVES
|
|
%% ========================================================================
|