mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
f4ee7a0525
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.
36 lines
1.8 KiB
TeX
36 lines
1.8 KiB
TeX
\documentclass[11pt]{article}
|
|
\usepackage{../shared/luxcover}
|
|
\usepackage{amsmath, amssymb, algpseudocode, graphicx, hyperref, booktabs, listings}
|
|
|
|
\title{FHE API and Developer Model for Practical Private Applications}
|
|
\author{
|
|
Lux Research\thanks{Corresponding author: [email protected]}\\
|
|
\textit{Lux Industries, Inc.}\\
|
|
\texttt{[email protected]}
|
|
}
|
|
\date{2025}
|
|
|
|
\lstset{basicstyle=\ttfamily\small, frame=single, breaklines=true}
|
|
|
|
\usepackage{amsthm}
|
|
\newtheorem{definition}{Definition}
|
|
\begin{document}
|
|
|
|
\luxcoverpage
|
|
|
|
\begin{abstract}
|
|
We describe the Go API and developer model for Lux FHE, an original lattice-based fully homomorphic encryption implementation built on \texttt{luxfi/lattice}. The library provides boolean gate evaluation on encrypted bits with programmable bootstrapping, radix-decomposed encrypted integers (uint8--uint256), and SIMD-optimized NTT for polynomial arithmetic. This paper specifies the developer-facing abstractions: parameter selection, key lifecycle (generation, serialization, threshold distribution), encryption/decryption patterns, evaluator design, error handling, batching strategies for amortized cost, and safe-by-default API patterns that prevent common misuse (key reuse, nonce collision, ciphertext malleability). The API is designed for blockchain integration via EVM precompiles and the \texttt{fhed} daemon's HTTP interface, with supported circuits including comparison, arithmetic, bitwise operations, and conditional selection.
|
|
\end{abstract}
|
|
|
|
\input{sections/01-introduction}
|
|
\input{sections/02-parameter-selection}
|
|
\input{sections/03-key-lifecycle}
|
|
\input{sections/04-encryption-and-decryption}
|
|
\input{sections/05-evaluator-operations}
|
|
\input{sections/06-batching-and-amortization}
|
|
\input{sections/07-safe-by-default-patterns}
|
|
\input{sections/08-evm-integration}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|