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.
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), F-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)
|
|
%% F-Chain is REMOVED entirely; teleport is B-Chain (bridgevm, LP-6000). No teleportvm.
|
|
%% Where this paper says "F-Chain MPC" / "F-Chain threshold governance" /
|
|
%% "F-Chain TFHE" / "F-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{multirow}
|
|
\usepackage{array}
|
|
\usepackage{xcolor}
|
|
\usepackage{float}
|
|
\usepackage{enumitem}
|
|
\usepackage{mathtools}
|
|
\usepackage{tikz}
|
|
\usetikzlibrary{arrows.meta,positioning,shapes.geometric}
|
|
|
|
\newtheorem{theorem}{Theorem}
|
|
\newtheorem{lemma}[theorem]{Lemma}
|
|
\newtheorem{proposition}[theorem]{Proposition}
|
|
\newtheorem{definition}{Definition}
|
|
\newtheorem{corollary}[theorem]{Corollary}
|
|
\newtheorem{remark}{Remark}
|
|
|
|
\hypersetup{
|
|
colorlinks=true,
|
|
linkcolor=blue,
|
|
citecolor=blue,
|
|
urlcolor=blue
|
|
}
|
|
|
|
\title{\textbf{Threshold UX: Making Quorum, Recovery, and Shared Control Normal Product Experiences}\\[6pt]
|
|
\large Invisible Threshold Cryptography for Approval Flows,\\Social Recovery, and Progressive Security on Lux Network}
|
|
|
|
\author{
|
|
Lux Research\thanks{Corresponding author: [email protected]}\\
|
|
\textit{Lux Industries}\\
|
|
\texttt{[email protected]}
|
|
}
|
|
|
|
\date{2025}
|
|
|
|
\begin{document}
|
|
|
|
\luxcoverpage
|
|
|
|
\begin{abstract}
|
|
Threshold cryptography is one of the most powerful primitives in applied
|
|
cryptography: $t$-of-$n$ signature schemes, secret sharing, and multi-party
|
|
computation enable security properties---recovery without seed phrases, shared
|
|
control without a single admin, regulatory compliance without centralized
|
|
escrow---that no single-key system can provide. Yet threshold cryptography
|
|
remains almost entirely absent from consumer products. The reason is not
|
|
technical. The primitives are mature. The reason is UX: threshold protocols
|
|
are presented to users as cryptographic ceremonies involving share distribution,
|
|
quorum assembly, and reconstruction rituals that make no sense outside a
|
|
cryptographer's mental model. This paper presents Threshold UX---a set of
|
|
design patterns that embed threshold cryptography into normal product
|
|
experiences on Lux Network. We show how $t$-of-$n$ threshold signatures
|
|
(FROST on the M-Chain) map to approval flows (``2 of 3 team members must
|
|
approve''), social recovery (``any 3 of your 5 trusted contacts can restore
|
|
your account''), shared workspaces (threshold access control over collaborative
|
|
documents), treasury management (multi-party spend authorization), regulated
|
|
access (compliance-gated reveal), and progressive security (start simple,
|
|
add guardians as stakes increase). We formalize each pattern as a composition
|
|
of M-Chain and F-Chain operations, prove security properties under standard
|
|
threshold assumptions, and define the UX interaction model that hides
|
|
cryptographic complexity behind familiar product metaphors.
|
|
\end{abstract}
|
|
|
|
\input{sections/01-introduction}
|
|
\input{sections/02-threshold-primitives-on-lux}
|
|
\input{sections/03-approval-flows}
|
|
\input{sections/04-social-recovery}
|
|
\input{sections/05-shared-workspaces}
|
|
\input{sections/06-treasury-management}
|
|
\input{sections/07-regulated-access}
|
|
\input{sections/08-progressive-security}
|
|
\input{sections/09-ux-interaction-patterns}
|
|
\input{sections/10-security-analysis}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|