Files
zeekayandHanzo Dev 178febad68 papers: reconcile T-Chain -> M-Chain / F-Chain / B-Chain per LP-134
Every rendered "T-Chain" / "ThresholdVM" / "teleportvm" reference across
the paper corpus is rewritten to the correct canonical chain by concern:
threshold signing / MPC / bridge custody / key recovery -> M-Chain (MVM);
FHE / encrypted compute / threshold decryption -> F-Chain (FVM); teleport
/ cross-chain messaging -> B-Chain (bridgevm); consensus Pulsar stays
Q-Chain. Section lux-trust-kernel/03-t-chain-threshold-governance.tex
renamed -> 03-f-chain-encrypted-policy.tex (with \input + xref fixes).
Braided "T-Chain" sections split by concern (M vs F). Only lp-020's
chain-separation rationale and the shared lux/chains/thresholdvm library
path retain the name, to record the removal. All changed papers rebuilt
(pdflatex, rc=0, no undefined refs).

ยง09 of lux-dao-governance-framework reframed: fabricated "production
deployment" metrics ($50M/$240k/$12M, survey %s, "as of Oct 2024")
relabeled as illustrative design configurations with no invented
replacements; reality noted (DAO treasury is a 1/1 Safe); conclusion
echo + one "first production" overclaim softened.

This commit also captures concurrent corpus workstreams on the same tree.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-02 00:57:09 -07:00

64 lines
2.1 KiB
TeX

\documentclass[11pt,a4paper]{article}
\usepackage{../shared/luxcover}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb,amsfonts}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{booktabs}
\usepackage{enumitem}
\usepackage{xcolor}
\usepackage{siunitx}
\usepackage{listings}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
\lstset{
basicstyle=\ttfamily\scriptsize,
breaklines=true,
frame=single,
showstringspaces=false,
}
\title{P3Q Magnetar Kind:\\
Hash-Based Threshold Verify on the Unified Precompile Slot}
\author{Lux Industries, Inc. \\
\texttt{[email protected]}}
\date{2026-06-04}
\begin{document}
\luxcoverpage
\begin{abstract}
LP-218 introduces P3Q at EVM slot \texttt{0x012205} as the
PQ-verifier family for rollup-batch authentication, specifying the
unified kind-byte dispatch ABI and the first verifier
kind~$0x01$ (Pulsar / FIPS-204 ML-DSA-65 threshold). This paper specifies \emph{kind $0x03$ Magnetar}: a hash-based
threshold verifier over FIPS-205 SLH-DSA. The shared P3Q framework
--- the unified slot, the kind-byte dispatch ABI, and the
\texttt{P3QVerifier} registration interface --- is specified in
LP-219; this paper gives Magnetar's wire layout, its gas
calibration (\SI{30000}{gas}), and the production parameter-set
lock at SLH-DSA-192f after the 2026-06-04 Quasar 4-scheme matrix
bench measured 192s at \SI{795}{ms}/sign vs 192f at
\SI{36}{ms}/sign on Spark (a $22\times$ reduction that restores
the sub-\SI{1}{s} round budget). Magnetar reduces to the collision
resistance of the SHA-2 / SHA-3 family, independent of the lattice
assumptions underlying Pulsar (LP-223) and Corona (LP-220), and is
the cross-family backstop of the LP-217 PQ-heavy posture. GPU
dispatch is projected, not measured; the on-chain path reserves
Magnetar's dispatch entry and returns \texttt{abiFalse} via
\texttt{ErrKindNotImplemented} until its threshold library lands.
\end{abstract}
\tableofcontents
\newpage
\input{sections/01-introduction}
\input{sections/05-magnetar-kind}
\bibliographystyle{plain}
\bibliography{biblio}
\end{document}