Files
zeekay f4ee7a0525 Publish under the org, not a person
Bylines, paper authorship, correspondence addresses and the founder blurb under
each post named an individual. They name the organisation that published the
work instead: the brand on posts and pages, the research byline on papers, and
research@ in place of a personal address. Both are what these repositories
already used elsewhere — nothing new was coined.

Co-authors are untouched. Where a paper named someone else alongside, they stay
named; only the one byline changed. Bibliography entries, running heads,
PDF metadata and affiliations move with it, so a citation still resolves to
whoever the cited paper names.

Sample and fixture data uses the placeholder name these tests already use
elsewhere, so no assertion changed meaning.
2026-09-01 08:58:10 -07:00

69 lines
2.4 KiB
TeX

\documentclass[11pt,a4paper]{article}
\usepackage{../shared/luxcover}
\usepackage[utf8]{inputenc}
\usepackage{amsmath,amssymb,amsfonts,amsthm}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{algorithm}
\usepackage{algpseudocode}
\usepackage{xcolor}
\usepackage{booktabs}
\usepackage{enumitem}
\usepackage{listings}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
\newtheorem{theorem}{Theorem}[section]
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{corollary}[theorem]{Corollary}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{definition}{Definition}[section]
\newtheorem{remark}{Remark}[section]
\lstset{basicstyle=\ttfamily\small, frame=single, breaklines=true}
\title{\textbf{Lux FHE: A GPU-Native FHE Runtime\\for Confidential Blockchain Execution}}
\author{
Lux Research\thanks{Corresponding author: [email protected]}\\
\textit{Lux Industries, Inc.}\\
\texttt{[email protected]}
}
\date{2026}
\begin{document}
\luxcoverpage
\begin{abstract}
Lux FHE is a dual-runtime fully homomorphic encryption stack: a Go reference
runtime defines canonical semantics, KATs, and chain integration, while a
C++/GPU-native production runtime executes high-throughput encrypted
computation. The Go runtime defines the semantics; the C++/GPU runtime
realizes the throughput. Cross-runtime KATs ensure semantic equivalence.
We further bind the FHE runtime into Lux's post-quantum consensus stack:
every finalized FHE evaluation contributes to a $\mathsf{nebula\_fhe\_root}$
commitment that the QuasarRoundDescriptor consumes. Quasar's Pulsar
threshold lane (lattice / Module-LWE) and ML-DSA attestation lane
(FIPS 204) finalize the encrypted execution result through Horizon
finality (LP-105) --- the FHE step is private, but the finality of the
result is a post-quantum-rooted certificate. This paper specifies the
dual-runtime split, the cross-runtime katology, the Nebula-FHE
DAG/GPU-native scheduler, the Quasar finality binding, GPU benchmarks
on NVIDIA H100, and the security posture (LWE-rooted, no PQ rollback).
\end{abstract}
\input{sections/01-introduction}
\input{sections/02-fhe-go-reference-runtime}
\input{sections/03-fhe-cpp-production-runtime}
\input{sections/04-cross-runtime-katology}
\input{sections/05-nebula-fhe-scheduling}
\input{sections/06-quasar-finality-binding}
\input{sections/07-benchmarks}
\input{sections/08-related-work}
\input{sections/09-security}
\end{document}