mirror of
https://github.com/hanzoai/papers.git
synced 2026-11-03 02:27:30 +00:00
zeekayandHanzo Dev
de732755b8
The paper architected investor onboarding around a named KYC vendor from the satschel lineage — 13 references across five files, including two TikZ nodes and a \bibitem. That name must not appear in a Hanzo paper. The architecture is unchanged and is legitimately ours: an external KYC provider returns a signed attestation by webhook, compliance validates it, the investor lands in IAM and then on the on-chain ComplianceRegistry. Only the vendor's identity is removed, so the paper still says exactly what it said. The \bibitem was never \cite'd — checked before deleting rather than assuming, since removing a cited key breaks every reference to it. Both TikZ node ids were renamed with their \draw edges in the same pass, so the diagrams still connect. Rebuilt: pdflatex clean, 6 bibitems, 165787 bytes. Co-authored-by: Hanzo Dev <[email protected]>
51 lines
2.0 KiB
TeX
51 lines
2.0 KiB
TeX
\section{Investor Onboarding via Hanzo IAM}
|
|
|
|
\label{sec:onboarding}
|
|
% ============================================================================
|
|
|
|
Investor onboarding combines Hanzo IAM identity management with the KYC
|
|
KYC/AML verification.
|
|
|
|
\subsection{Identity Creation}
|
|
|
|
\begin{enumerate}[leftmargin=1.4em]
|
|
\item Investor registers via ArcaLabs platform. Registration request
|
|
routed through Hanzo Gateway.
|
|
\item Hanzo IAM creates an identity record with OIDC subject
|
|
identifier. The investor receives OAuth 2.0 credentials.
|
|
\item IAM assigns the investor to the ArcaLabs organization with
|
|
the \texttt{investor} role.
|
|
\item All subsequent API calls include the IAM bearer token. Gateway
|
|
extracts the org from the JWT \texttt{owner} claim and scopes all
|
|
data queries to that org.
|
|
\end{enumerate}
|
|
|
|
\subsection{KYC/AML Verification}
|
|
|
|
\begin{enumerate}[leftmargin=1.4em]
|
|
\item ArcaLabs onboarding service redirects the investor to
|
|
the KYC provider's verification flow.
|
|
\item The KYC provider performs: identity document verification, liveness
|
|
detection, OFAC/sanctions screening, PEP screening, and accredited
|
|
investor verification.
|
|
\item Upon completion, the provider returns a signed attestation to
|
|
ArcaLabs via webhook.
|
|
\item ArcaLabs compliance service validates the attestation and
|
|
updates the investor's IAM profile with: KYC status, accreditation
|
|
status, accreditation expiry, jurisdiction.
|
|
\item The compliance service writes the investor to the on-chain
|
|
\texttt{ComplianceRegistry} whitelist on Lux C-Chain.
|
|
\end{enumerate}
|
|
|
|
\subsection{Ongoing Monitoring}
|
|
|
|
The KYC provider performs continuous monitoring:
|
|
\begin{itemize}[leftmargin=1.4em]
|
|
\item Daily sanctions list re-screening.
|
|
\item Adverse media monitoring.
|
|
\item Annual accreditation re-verification trigger.
|
|
\item Alerts delivered to ArcaLabs via Hanzo Webhooks.
|
|
\end{itemize}
|
|
|
|
% ============================================================================
|