mirror of
https://github.com/lux-apps/papers.git
synced 2026-11-02 11:39:52 +00:00
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/.
164 lines
4.3 KiB
TeX
164 lines
4.3 KiB
TeX
\section{LP (Lux Proposal) Standardization Process}
|
|
|
|
|
|
\subsection{LP Lifecycle}
|
|
|
|
\begin{figure}[h]
|
|
\centering
|
|
\begin{verbatim}
|
|
+----------+ +-----------+ +----------+ +---------+
|
|
| IDEA |-->| DRAFT |-->| PROPOSED |-->| REVIEW |
|
|
+----------+ +-----------+ +----------+ +---------+
|
|
|
|
|
+----------+ +-----------+ +----------+ |
|
|
| ACTIVATED|<--| VOTING |<--|IMPLEMENT.|<-----+
|
|
+----------+ +-----------+ +----------+
|
|
\end{verbatim}
|
|
\caption{LP lifecycle from ideation to activation}
|
|
\end{figure}
|
|
|
|
\subsection{Phase 1: Ideation}
|
|
|
|
\textbf{Duration}: Unlimited
|
|
|
|
\textbf{Platform}: GitHub Discussions, Discord, Community Calls
|
|
|
|
\textbf{Activities}:
|
|
\begin{itemize}
|
|
\item Author posts rough idea for feedback
|
|
\item Community discusses feasibility and value
|
|
\item Similar past proposals identified
|
|
\item Rough consensus to proceed
|
|
\end{itemize}
|
|
|
|
\subsection{Phase 2: Draft}
|
|
|
|
\textbf{Duration}: 2-4 weeks typical
|
|
|
|
\textbf{Requirements}:
|
|
\begin{itemize}
|
|
\item Follow LP template structure
|
|
\item Include problem statement, specification, rationale
|
|
\item Provide examples and reference implementation (if applicable)
|
|
\item Address backwards compatibility
|
|
\item Estimate implementation cost
|
|
\end{itemize}
|
|
|
|
\textbf{Review Criteria}:
|
|
\begin{itemize}
|
|
\item \textbf{Clarity}: Can developers understand and implement?
|
|
\item \textbf{Completeness}: All necessary details provided?
|
|
\item \textbf{Feasibility}: Technically achievable with reasonable effort?
|
|
\end{itemize}
|
|
|
|
\subsection{Phase 3: Proposed}
|
|
|
|
\textbf{Duration}: 1-2 weeks
|
|
|
|
\textbf{Process}:
|
|
\begin{enumerate}
|
|
\item Author submits LP via Pull Request to \texttt{luxfi/lps}
|
|
\item LP assigned unique number (e.g., LP-304)
|
|
\item Formal review begins
|
|
\item LP editors check formatting and completeness
|
|
\end{enumerate}
|
|
|
|
\subsection{Phase 4: Review}
|
|
|
|
\textbf{Duration}: 2-6 weeks depending on complexity
|
|
|
|
\textbf{Review Types}:
|
|
|
|
\begin{enumerate}
|
|
\item \textbf{Technical Review}:
|
|
\begin{itemize}
|
|
\item Code feasibility analysis
|
|
\item Performance impact assessment
|
|
\item Security audit for critical changes
|
|
\item Integration testing with existing systems
|
|
\end{itemize}
|
|
|
|
\item \textbf{Economic Review}:
|
|
\begin{itemize}
|
|
\item Token economics impact
|
|
\item Incentive structure analysis
|
|
\item Game-theoretic attack vectors
|
|
\item Long-term sustainability
|
|
\end{itemize}
|
|
|
|
\item \textbf{Community Review}:
|
|
\begin{itemize}
|
|
\item Use case validation
|
|
\item Adoption likelihood
|
|
\item User experience implications
|
|
\item Ecosystem partner feedback
|
|
\end{itemize}
|
|
\end{enumerate}
|
|
|
|
\textbf{Reviewers}:
|
|
\begin{itemize}
|
|
\item Core protocol developers
|
|
\item Security researchers
|
|
\item Economic analysts
|
|
\item Community representatives
|
|
\item Validator operators
|
|
\end{itemize}
|
|
|
|
\subsection{Phase 5: Implementable}
|
|
|
|
\textbf{Duration}: Variable
|
|
|
|
\textbf{Requirements}:
|
|
\begin{itemize}
|
|
\item All major concerns addressed
|
|
\item Reference implementation completed (if code change)
|
|
\item Test cases documented and passing
|
|
\item Security audit completed (for critical changes)
|
|
\item Migration plan documented (if breaking change)
|
|
\end{itemize}
|
|
|
|
\textbf{Signal}: Ready for formal DAO vote
|
|
|
|
\subsection{Phase 6: Voting}
|
|
|
|
\textbf{Duration}: 1-2 weeks
|
|
|
|
\textbf{Voting Mechanisms by LP Type}:
|
|
|
|
\begin{table}[h]
|
|
\centering
|
|
\begin{tabular}{@{}llll@{}}
|
|
\toprule
|
|
\textbf{LP Type} & \textbf{Threshold} & \textbf{Quorum} & \textbf{Validators} \\ \midrule
|
|
Standard & Simple majority (>50\%) & 10\% & Optional \\
|
|
Protocol & Supermajority (67\%) & 15\% & Required \\
|
|
Economic & Weighted voting & 12\% & Enhanced weight \\
|
|
Emergency & Fast-track (75\%) & 20\% & Required \\ \bottomrule
|
|
\end{tabular}
|
|
\caption{Voting thresholds by LP type}
|
|
\end{table}
|
|
|
|
\textbf{Voting Process}:
|
|
\begin{enumerate}
|
|
\item Proposal enters prediction market (holographic consensus)
|
|
\item If boosted, fast-tracked to full DAO vote
|
|
\item 7-14 day voting period (depends on LP type)
|
|
\item Token holders cast votes (For/Against/Abstain)
|
|
\item Validators cast enhanced-weight votes for protocol LPs
|
|
\item Results finalized on-chain
|
|
\end{enumerate}
|
|
|
|
\subsection{Phase 7: Activation}
|
|
|
|
\textbf{Duration}: Coordinated with network upgrade cycle
|
|
|
|
\textbf{Process}:
|
|
\begin{enumerate}
|
|
\item LP scheduled in next network upgrade
|
|
\item Validators update node software
|
|
\item Activation at predetermined block height
|
|
\item Post-activation monitoring for 30 days
|
|
\item Incident response team on standby
|
|
\end{enumerate}
|
|
|