mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekayandHanzo Dev
70f6883235
A July commit removed eight papers on the premise "no license — DEX/non-custodial only". That premise is wrong: Lux operates an ATS, a broker-dealer, a transfer agent and a bank, and this material is resold at lux.financial. The merge that brought main in preserved the removal because the commit stated a reason, which is how a stale reason outlives the fact it rested on. Back, at the versions main carried — main never received the removal, so its copies are the later ones: the ATS architecture, the security-token standard, smart order routing, institutional custody, MPC custody, post-quantum securities, the SSB partnership and the CoinBridge brief. 83 files. Co-authored-by: Hanzo Dev <[email protected]>
118 lines
4.2 KiB
TeX
118 lines
4.2 KiB
TeX
\section{Implementation Timeline}
|
|
|
|
\label{sec:timeline}
|
|
%% =====================================================================
|
|
|
|
End-to-end implementation, from contract execution with Lux
|
|
Industries to first cold ceremony, is a 90-day plan. The plan is
|
|
front-loaded into hardware procurement and SCIF fit-out because
|
|
those are the long-poles.
|
|
|
|
\subsection{Phase 0 (Pre-Contract: Days $-30$ to $0$)}
|
|
|
|
\begin{enumerate}[nosep]
|
|
\item Statement of work and contract execution.
|
|
\item Threat-model briefing with the fund's CISO and legal teams.
|
|
\item Audit-firm selection for the witness role.
|
|
\item Vault selection in three jurisdictions.
|
|
\item Insurance broker engagement.
|
|
\end{enumerate}
|
|
|
|
\subsection{Phase 1 (Days 0--30): Hardware and Sites}
|
|
|
|
\begin{enumerate}[nosep]
|
|
\item Order Thales Luna 7 HSM pair (lead time: typical 4 weeks).
|
|
\item Order Utimaco SR-Se200 Gen2 pair (lead time: typical 6 weeks).
|
|
\item Order YubiHSM 2 inventory (lead time: typical 1 week).
|
|
\item Provision AWS CloudHSM clusters in two regions.
|
|
\item Provision GCP Cloud HSM key rings in two regions.
|
|
\item Provision Azure Dedicated HSM.
|
|
\item Begin SCIF fit-out at the ceremony location.
|
|
\item Begin DR-site physical infrastructure provisioning.
|
|
\item Hire or rotate custody operations team to required headcount
|
|
(\(\geq 6\) engineers).
|
|
\end{enumerate}
|
|
|
|
\subsection{Phase 2 (Days 30--60): Software, Policy, and Pre-Ceremony}
|
|
|
|
\begin{enumerate}[nosep]
|
|
\item Deploy Lux MPC orchestrator
|
|
(\texttt{luxfi/mpc}, \texttt{luxfi/hsm}) on customer infrastructure.
|
|
\item Configure HSM-resident policy modules: per-tier daily caps,
|
|
destination allowlists, time-lock parameters.
|
|
\item Configure M-Chain custody-ledger client and BLS+ML-DSA
|
|
audit-log signing.
|
|
\item Document SOC 2 Type II control narratives.
|
|
\item Document ISO 27001 ISMS scope.
|
|
\item Document CCSS Level 3 evidence package.
|
|
\item Run a mock ceremony in the SCIF using disposable HSMs to
|
|
validate the run-book end-to-end.
|
|
\item Witness-firm pre-brief and sign-off on ceremony procedure.
|
|
\end{enumerate}
|
|
|
|
\subsection{Phase 3 (Days 60--75): Ceremonies}
|
|
|
|
\begin{enumerate}[nosep]
|
|
\item Day 60: cold-tier DKG ceremony, witnessed; transcript published
|
|
on M-Chain.
|
|
\item Day 65: warm-tier DKG ceremony, witnessed.
|
|
\item Day 70: hot-tier DKG ceremony.
|
|
\item Day 70--75: sealed envelopes deposited at three jurisdictions;
|
|
chain-of-custody documented and counter-signed.
|
|
\end{enumerate}
|
|
|
|
\subsection{Phase 4 (Days 75--90): Migration of Funds}
|
|
|
|
\begin{enumerate}[nosep]
|
|
\item Day 75: small-amount migration (1\% of AUM) from incumbent
|
|
custodian to validate end-to-end.
|
|
\item Day 75--80: incumbent withdrawal of cold-tier funds in batched
|
|
tranches; deposit into the new cold-tier public key.
|
|
\item Day 80--85: warm-tier and hot-tier funding from cold-tier
|
|
movements.
|
|
\item Day 85: parallel-running window begins; both custodians
|
|
operational with the fund's positions split.
|
|
\item Day 90: incumbent contract notice served; parallel-running
|
|
continues per the migration plan (Section~\ref{sec:migration}).
|
|
\end{enumerate}
|
|
|
|
\subsection{Phase 5 (Days 90--180): Audits}
|
|
|
|
\begin{enumerate}[nosep]
|
|
\item Day 90--150: SOC 2 Type II audit period begins (Type II
|
|
requires a minimum 6-month observation window).
|
|
\item Day 150: ISO 27001 stage-1 audit.
|
|
\item Day 180: ISO 27001 stage-2 audit; certificate issuance
|
|
expected day 200.
|
|
\item Day 180: CCSS Level 3 audit.
|
|
\end{enumerate}
|
|
|
|
\subsection{Critical-Path Items}
|
|
|
|
The two critical-path items are \textbf{HSM lead times} (Utimaco
|
|
SR-Se200 at 6 weeks is the longest) and \textbf{SCIF fit-out} (4--6
|
|
weeks depending on existing infrastructure). Both must start on day
|
|
0; any slip cascades into the ceremony date. Cloud HSMs have no
|
|
lead time and are not on the critical path.
|
|
|
|
\begin{table}[h]
|
|
\centering
|
|
\small
|
|
\begin{tabular}{lll}
|
|
\toprule
|
|
\textbf{Item} & \textbf{Lead time} & \textbf{Phase} \\
|
|
\midrule
|
|
Utimaco SR-Se200 procurement & 6 weeks & Phase 1 \\
|
|
Thales Luna 7 procurement & 4 weeks & Phase 1 \\
|
|
SCIF fit-out & 4--6 weeks & Phase 1 \\
|
|
Cloud HSM provisioning & 1--3 days & Phase 1 \\
|
|
YubiHSM 2 procurement & 1 week & Phase 1 \\
|
|
SOC 2 Type II audit period & 6 months minimum & Phase 5 \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\caption{Critical-path lead times.}
|
|
\label{tab:lead-times}
|
|
\end{table}
|
|
|
|
%% =====================================================================
|