Files
zeekay abf99d05fc papers: reorganize into per-paper dirs, add Antje Worring as co-author
Restructured from flat .tex/.pdf files into per-paper subdirectories.
Added Antje Worring as co-author on all papers.
Synced PDFs to pdfs/ for download site.
2026-04-18 21:50:07 -07:00

83 lines
3.3 KiB
TeX

\section{Asset Taxonomy}
\label{sec:taxonomy}
Three mutually exclusive asset classes exist within the protocol. Conflating classes is a protocol violation enforceable at both the contract and legal layers.
\subsection{Class~1: Credit Assets}
\label{sec:credit}
\begin{definition}[Credit Asset]
A credit asset is an overcollateralized, in-kind redeemable liability of the protocol, minted against vault-backed base assets subject to a hard LTV cap.
\end{definition}
\noindent\textbf{Instances.} LETH (backed by ETH), LBTC (backed by BTC).
\begin{requirement}[Credit Asset Properties]
\label{req:credit}
A credit asset \textsc{must} satisfy all of the following:
\begin{enumerate}[nosep]
\item Minted only against recognized, attested backing.
\item Redeemable 1:1 in kind: $\texttt{burn}(x) \Rightarrow \texttt{release}(x)$ of the underlying base asset.
\item Hard issuance cap at or below the configured LTV ratio.
\item No direct claim on strategy yield.
\item No governance, profit-share, or security rights.
\end{enumerate}
\end{requirement}
\begin{invariant}[Class Separation]
\label{inv:class-sep}
\[
\texttt{creditAsset} \neq \texttt{yieldShare} \neq \texttt{securityToken}
\]
Enforced technically and legally via separate token contracts, separate registries, separate accounting buckets, and separate disclosures. A single contract or accounting path \textsc{must not} conflate two classes.
\end{invariant}
\paragraph{Canonical phrasing.} For regulatory filings, disclosures, and counterparty agreements:
\begin{quote}
\emph{LETH is a protocol-issued, fully collateralized, in-kind redeemable credit token backed by ETH vault assets and minted subject to a hard maximum loan-to-value ratio of 90\%, with strategy yield accruing to protocol surplus rather than to LETH holders.}
\end{quote}
\subsection{Class~2: Yield and Equity Instruments}
\label{sec:yield}
\begin{definition}[Yield/Equity Instrument]
A yield/equity instrument represents a claim on protocol surplus, not on redemption principal backing.
\end{definition}
\noindent\textbf{Instances.} xLUX, protocol equity accounting unit.
\begin{requirement}[Yield Instrument Properties]
\label{req:yield}
\begin{enumerate}[nosep]
\item Absorbs upside from strategy earnings.
\item May absorb losses after buffer depletion, depending on instrument design.
\item Never used as collateral equivalence for credit redemptions unless explicitly approved by governance action.
\end{enumerate}
\end{requirement}
The structural separation between credit assets and yield instruments is the primary mechanism by which the protocol avoids characterization as a security or investment contract with respect to credit holders.
\subsection{Class~3: Security Assets}
\label{sec:security}
\begin{definition}[Security Asset]
A security asset is issued and controlled under the ATS/compliance layer and is not fungible with protocol credit liabilities.
\end{definition}
\noindent\textbf{Instances.} Tokenized equity, fund interests, real-world assets.
\begin{requirement}[Security Asset Properties]
\label{req:security}
\begin{enumerate}[nosep]
\item Compliance-enforced transferability (whitelist, lockup, KYC).
\item Jurisdictional controls per offering type.
\item Separate wrapping policy when bridged into Lux (Section~\ref{sec:ats-boundary}).
\end{enumerate}
\end{requirement}