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.
75 lines
2.2 KiB
TeX
75 lines
2.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{booktabs}
|
|
\usepackage{algorithm}
|
|
\usepackage{algpseudocode}
|
|
\usepackage{enumitem}
|
|
\usepackage{xcolor}
|
|
\usepackage{listings}
|
|
|
|
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
|
|
|
|
\newtheorem{theorem}{Theorem}[section]
|
|
\newtheorem{lemma}[theorem]{Lemma}
|
|
\newtheorem{definition}{Definition}[section]
|
|
\newtheorem{remark}{Remark}[section]
|
|
|
|
\lstset{
|
|
basicstyle=\ttfamily\small,
|
|
breaklines=true,
|
|
frame=single,
|
|
numbers=left,
|
|
numberstyle=\tiny,
|
|
language=Go
|
|
}
|
|
|
|
\title{LP-Anchor: On-Chain Checkpoint Anchoring\\for CRDT State Durability}
|
|
|
|
\author{
|
|
Lux Research\thanks{Corresponding author: [email protected]}\\
|
|
\textit{Lux Industries, Inc.}\\
|
|
\texttt{[email protected]}
|
|
}
|
|
|
|
\date{February 2026}
|
|
|
|
\begin{document}
|
|
|
|
\luxcoverpage
|
|
|
|
\begin{abstract}
|
|
We describe a mechanism for anchoring CRDT document state to a Lux chain
|
|
so that clients hold cryptographic proof that a given Merkle root existed at
|
|
a given logical height. The anchor precompile accepts a 72-byte payload
|
|
(32-byte app ID, 8-byte height, 32-byte root) and stores it in EVM state
|
|
at approximately 25,400 gas on C-Chain or near-zero cost on Q-Chain via
|
|
Quasar DAG parallelism. Users verify anchors by querying the chain and
|
|
recomputing their local Merkle root. A rollup-style batching mode amortizes
|
|
cost across 1,000 anchors per on-chain transaction. The design is
|
|
implemented as a stateful EVM precompile at address \texttt{0x0700\ldots10}
|
|
in the Lux precompile registry (Privacy/Encryption page, item 0x10).
|
|
\end{abstract}
|
|
|
|
\tableofcontents
|
|
|
|
% ============================================================================
|
|
|
|
\input{sections/01-problem-statement}
|
|
\input{sections/02-architecture}
|
|
\input{sections/03-why-q-chain}
|
|
\input{sections/04-anchor-transaction-format}
|
|
\input{sections/05-verification-path}
|
|
\input{sections/06-adversary-model}
|
|
\input{sections/07-cost-analysis}
|
|
\input{sections/08-batched-anchoring}
|
|
\input{sections/09-implementation}
|
|
\input{sections/10-comparison-with-prior-art}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|