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.
80 lines
2.6 KiB
TeX
80 lines
2.6 KiB
TeX
\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{array}
|
|
\usepackage{xcolor}
|
|
\usepackage{tikz}
|
|
\usepackage{float}
|
|
\usepackage{enumitem}
|
|
\usepackage{mathtools}
|
|
|
|
\usetikzlibrary{arrows.meta,positioning,shapes.geometric,fit,calc}
|
|
|
|
\newtheorem{theorem}{Theorem}[section]
|
|
\newtheorem{lemma}[theorem]{Lemma}
|
|
\newtheorem{proposition}[theorem]{Proposition}
|
|
\newtheorem{corollary}[theorem]{Corollary}
|
|
\newtheorem{definition}{Definition}[section]
|
|
\newtheorem{remark}{Remark}[section]
|
|
\newtheorem{invariant}{Invariant}[section]
|
|
|
|
\hypersetup{
|
|
colorlinks=true,
|
|
linkcolor=black,
|
|
citecolor=blue,
|
|
urlcolor=blue
|
|
}
|
|
|
|
\title{\textbf{The Capsule: A Sovereign Encrypted Process\\for Web5 Computing}}
|
|
|
|
\author{
|
|
Lux Research\thanks{Corresponding author: [email protected]}\\
|
|
\textit{Lux Industries}\\
|
|
\texttt{[email protected]}
|
|
}
|
|
|
|
\date{2025}
|
|
|
|
\begin{document}
|
|
|
|
\luxcoverpage
|
|
|
|
\begin{abstract}
|
|
A Capsule is the fundamental unit of Web5 computing: a sovereign encrypted process
|
|
that binds an identity to a local data vault, a capability system, a sync topology,
|
|
and a compute policy. Every user, organization, AI agent, workspace, and device
|
|
gets one. The vault is an encrypted SQLite database (AES-256-CBC via SQLCipher),
|
|
synchronized offline-first through CRDTs, anchored to Lux for trust---identity
|
|
roots, key policy, threshold controls, and audit receipts. This paper gives the
|
|
formal definition of a Capsule, proves its security properties under standard
|
|
cryptographic assumptions, classifies the three application classes it enables
|
|
(local-first private, threshold-controlled, and confidential compute), and
|
|
specifies the trust kernel that Lux provides. The thesis: Base owns state, Lux
|
|
owns trust, providers own service quality, users own keys and exit rights. The
|
|
Capsule is not a decentralized database. It is the personal computer of Web5.
|
|
\end{abstract}
|
|
|
|
% ============================================================================
|
|
|
|
\input{sections/01-introduction}
|
|
\input{sections/02-the-capsule-model}
|
|
\input{sections/03-three-classes-of-applications}
|
|
\input{sections/04-the-trust-kernel}
|
|
\input{sections/05-the-data-plane}
|
|
\input{sections/06-the-post-quantum-security-stack}
|
|
\input{sections/07-provider-model}
|
|
\input{sections/08-agent-capsules}
|
|
\input{sections/09-migration-path}
|
|
\input{sections/10-hardest-unsolved-problems}
|
|
\input{sections/11-related-work}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|