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/.
96 lines
3.2 KiB
TeX
96 lines
3.2 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{multirow}
|
|
\usepackage{array}
|
|
\usepackage{xcolor}
|
|
\usepackage{float}
|
|
\usepackage{enumitem}
|
|
\usepackage{mathtools}
|
|
\usepackage{listings}
|
|
\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
|
|
}
|
|
|
|
\lstset{
|
|
basicstyle=\ttfamily\small,
|
|
breaklines=true,
|
|
frame=single,
|
|
xleftmargin=1em,
|
|
framexleftmargin=0.5em,
|
|
columns=fullflexible,
|
|
keepspaces=true,
|
|
showstringspaces=false
|
|
}
|
|
|
|
\title{\textbf{The Firebase Exit: Migrating Cloud Apps to Local-First Cryptographic Architecture}\\[6pt]
|
|
\large From Vendor Lock-In to Sovereign Capsules\\on Lux Network}
|
|
|
|
\author{
|
|
Zach Kelling\thanks{Corresponding author: [email protected]}\\
|
|
\textit{Lux Industries}\\
|
|
\texttt{[email protected]}
|
|
}
|
|
|
|
\date{2025}
|
|
|
|
\begin{document}
|
|
|
|
\luxcoverpage
|
|
|
|
\begin{abstract}
|
|
Firebase, Supabase, Convex, and Notion represent the state of the art in
|
|
developer experience for cloud applications: real-time sync, authentication,
|
|
serverless functions, and managed hosting in a single SDK. They also
|
|
represent the state of the art in vendor lock-in: the provider owns your
|
|
data, your auth identities, your function runtime, and your users' data
|
|
sovereignty. This paper presents the Firebase Exit---a systematic migration
|
|
path from cloud-dependent application architectures to local-first
|
|
cryptographic applications (capsule apps) on Lux Network. We define a
|
|
component-by-component mapping from Firebase/Supabase primitives to their
|
|
capsule equivalents: Firestore becomes encrypted SQLite with CRDT
|
|
synchronization, Firebase Auth becomes I-Chain decentralized identifiers,
|
|
Cloud Functions become Base Functions executing in the capsule's trust
|
|
boundary, and Firebase Hosting becomes the decentralized provider market.
|
|
We provide a step-by-step migration guide, benchmark local SQLite reads
|
|
against Firestore network round-trips (showing $10\times$--$100\times$
|
|
latency improvement for reads), analyze the offline-first advantages for
|
|
mobile and edge deployments, and present four case studies (notes app, CRM,
|
|
team chat, project management) demonstrating that every Firebase app can
|
|
become a sovereign capsule app with equivalent functionality and strictly
|
|
superior data ownership, privacy, and portability.
|
|
\end{abstract}
|
|
|
|
\input{sections/01-introduction}
|
|
\input{sections/02-what-firebase-gets-right}
|
|
\input{sections/03-what-firebase-gets-wrong}
|
|
\input{sections/04-migration-mapping}
|
|
\input{sections/05-step-by-step-migration-guide}
|
|
\input{sections/06-performance-comparison}
|
|
\input{sections/07-offline-first-advantages}
|
|
\input{sections/08-case-studies}
|
|
\input{sections/09-related-work}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|