mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
dd93cb41f7
Sweep across the non-Tier-1 paper catalogue (Tier-1 owned by parallel
agent and excluded). All 113 processed papers already had luxcover
wired up; this commit fixes 14 build breakers and produces fresh
PDFs across the catalogue.
Fixes:
- lux-blockchain-scaling-laws: em-dash inside lstlisting -> --
- lux-corona-pq: stale \input pointing at 03-the-corona-scheme renamed
to 03-the-corona-scheme (file already renamed on disk)
- lux-lattice-cryptography-primer: same Corona->Corona rename
- lux-formal-verification-lean4: Lean source uses unicode (×, ∀, ∃, ∈,
∧, ∨, ∩, ≠, ⟨, ⟩, ·, ¬) inside lstlistings. Added a literate map
so listings render the math glyphs without UTF-8 fault.
- lux-id-did-specification: ✓/✗ in tabular replaced with \ding{51}
/ \ding{55} (pifont). Added pifont package.
- lux-ntt-simd-implementation: middle-dot in Go assembly listings;
added literate {·}{\textperiodcentered}.
- lux-ntt-transform: μ, ×, –, — in regular text (no T1 fontenc).
Replaced with $\mu$/$\times$/--/--- via unicode->latex sweep.
- lux-perpetuals-derivatives, lux-quantum-consensus,
lux-quasar-consensus, lux-tee-computing-mesh: same unicode->latex
sweep across body text. Also fixed broken math segment
`$L_{avg} = 10$\times$$` -> `$L_{avg} = 10\times$`.
- lux-zchain: emoji glyphs in roadmap table replaced with
parenthetical text.
- lux-triple-proof-consensus: dropped duplicate \usepackage{geometry}
that clashed with luxcover (geometry option clash).
- pq: defined missing \Rq macro.
PDFs rebuilt for the full Tier-2/3 set.
Excluded (Tier-1, parallel agent): lp-073-pulsar, lp-stricte2epq,
dag-evm-formal, lp-010-quasar-stm-{3,4}, lp-020-quasar-consensus,
lux-institutional-custody, lux-nist-mptc-submission, pqsafe-il5,
pq-rns, plus shared/ and lps/.
98 lines
3.8 KiB
TeX
98 lines
3.8 KiB
TeX
|
|
%% ===================================================================
|
|
%% LP-134 canonical naming (2025-12-15):
|
|
%% Per LP-134 (Lux Chain Topology), T-Chain has been split into:
|
|
%% M-Chain — MPC ceremonies for bridge custody of EXTERNAL wallets
|
|
%% (CGGMP21, FROST, Pulsar-general)
|
|
%% F-Chain — FHE compute + TFHE bootstrap-key generation (encrypted EVM)
|
|
%% The legacy name "T-Chain" is retained ONLY for `teleportvm` (LP-6332).
|
|
%% Where this paper says "T-Chain MPC" / "T-Chain threshold governance" /
|
|
%% "T-Chain TFHE" / "T-Chain custody", read as M-Chain (MPC) or F-Chain (FHE).
|
|
%% ===================================================================
|
|
|
|
\documentclass[11pt,a4paper]{article}
|
|
\usepackage{../shared/luxcover}
|
|
\usepackage[utf8]{inputenc}
|
|
\usepackage[T1]{fontenc}
|
|
\usepackage{amsmath,amssymb,amsfonts,amsthm}
|
|
\usepackage{graphicx}
|
|
\usepackage{hyperref}
|
|
\usepackage{algorithm}
|
|
\usepackage{algpseudocode}
|
|
\usepackage{booktabs}
|
|
\usepackage{enumitem}
|
|
\usepackage{tikz}
|
|
\usetikzlibrary{arrows.meta,positioning,shapes.geometric}
|
|
|
|
\newtheorem{theorem}{Theorem}[section]
|
|
\newtheorem{lemma}[theorem]{Lemma}
|
|
\newtheorem{proposition}[theorem]{Proposition}
|
|
\newtheorem{corollary}[theorem]{Corollary}
|
|
\newtheorem{definition}{Definition}[section]
|
|
\newtheorem{remark}{Remark}[section]
|
|
|
|
\hypersetup{
|
|
colorlinks=true,
|
|
linkcolor=black,
|
|
citecolor=blue,
|
|
urlcolor=blue
|
|
}
|
|
|
|
\title{\textbf{Lux as Trust Kernel:\\Identity, Key Policy, Threshold Governance,\\and Receipts}}
|
|
|
|
\author{
|
|
Zach Kelling\thanks{Corresponding author: [email protected]}\\
|
|
\textit{Lux Industries}\\
|
|
\texttt{[email protected]}
|
|
}
|
|
|
|
\date{2025}
|
|
|
|
\begin{document}
|
|
|
|
\luxcoverpage
|
|
|
|
\begin{abstract}
|
|
We formalize Lux Network as a \emph{trust kernel}: a minimal on-chain substrate that
|
|
provides identity binding, key lifecycle policy, threshold governance, and tamper-evident
|
|
receipts---without storing application data on-chain. The trust kernel model inverts the
|
|
common blockchain-as-database pattern. Applications retain full data sovereignty in local
|
|
encrypted vaults (capsules) while delegating exactly four concerns to the chain:
|
|
(i)~globally-unique identity via decentralized identifiers (\texttt{did:lux:*}),
|
|
(ii)~key registration and rotation policy on the K-Chain,
|
|
(iii)~quorum-controlled reveal and treasury approval on the T-Chain with TFHE policy
|
|
evaluation and CKKS confidential compute,
|
|
and (iv)~multi-party threshold signatures on the M-Chain via FROST and CGGMP21.
|
|
Every state transition produces a cryptographic receipt anchored on-chain, enabling
|
|
provider-independent auditability. We define the trust kernel formally, prove that it
|
|
preserves capsule sovereignty under Byzantine fault tolerance assumptions, and show
|
|
that the architecture enables cross-capsule coordination (key exchange, capability
|
|
delegation, threshold approval) without revealing plaintext to any single party.
|
|
All critical protocols are verified in Lean~4 against mechanized proofs for
|
|
consensus safety, FROST unforgeability, CGGMP21 threshold composition, and
|
|
trust authority delegation.
|
|
|
|
\textbf{Keywords}: trust kernel, decentralized identity, threshold governance,
|
|
key policy, receipt anchoring, post-quantum cryptography, TFHE, CKKS, FROST, CGGMP21
|
|
\end{abstract}
|
|
|
|
\tableofcontents
|
|
\newpage
|
|
|
|
%% ===================================================================
|
|
|
|
\input{sections/01-introduction}
|
|
\input{sections/02-k-chain-key-registry-and-policy}
|
|
\input{sections/03-t-chain-threshold-governance}
|
|
\input{sections/04-m-chain-mpc-signing}
|
|
\input{sections/05-i-chain-decentralized-identity}
|
|
\input{sections/06-receipt-anchoring}
|
|
\input{sections/07-provider-accountability}
|
|
\input{sections/08-cross-capsule-coordination}
|
|
\input{sections/09-security-model}
|
|
\input{sections/10-formal-verification}
|
|
\input{sections/11-related-work}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|