Overview
Digital money and tokenization look simple on the surface: a dollar in a wallet, a fund share on-chain, a tokenized deposit. This site studies what those products depend on underneath: reserve custody, redemption design, routing defaults, settlement rules, and the operators who control recovery when something breaks.
Put differently: the label on the token matters less than the reserve structure, the control layer, and the operator that has to make the product work under stress.
One thesis, two research tracks, four decision contexts.
A digital token designed to hold a stable value, typically $1. Whether it actually holds that value depends on what backs it (reserves), how a holder gets out (redemption), and who operates the infrastructure in between (the gateway).
Tokenization is the representation of a traditional financial product on token-based rails. The core question is whether the tokenized version preserves legal rights, operational resilience, and economic behavior under stress as well as in normal conditions.
A tokenized deposit is a bank deposit represented on token-based rails. It remains a bank liability inside the banking perimeter, with bank supervision and, where applicable, deposit insurance protecting the holder's claim.
A gateway is the issuer, exchange, or protocol that routes tokenized value. The same token can inherit different compliance, routing, and stress properties depending on which gateway processes it. This is the central unit of analysis in the research program.
The control layer is the set of interfaces, routing defaults, sweep logic, holds/freezes, disclosures, and audit trails that turn policy into executable operations. This is often where liability, concentration, and value capture attach in practice.
The same wallet can show three products that look similar in calm conditions but behave very differently under stress.
Settlement objects designed to behave like digital cash. Reserve quality, redemption plumbing, and operational resilience matter most. The GENIUS Act reinforces the payment-stablecoin perimeter by requiring liquid reserve backing, monthly public reserve disclosures, 1:1 redemption, restrictions on misleading marketing, and priority for stablecoin holders in insolvency. Deposit tokens and yield wrappers require separate treatment.
Bank deposits in token form. The bank liability structure, bank supervision, and resolution framework matter most. These stay inside the banking perimeter. OCC Interpretive Letter 1188 (December 2025) confirms that national banks may engage in riskless principal crypto-asset transactions, but only in a safe and sound manner and in compliance with applicable law.
Investment and cash-management products such as tokenized money funds, Treasury wrappers, and sweep programs. Disclosure, liquidity governance, custody, and marketing rules matter most. When the payment object stays clean, yield migrates here.
Same wallet surface, different rights, backstops, and failure sequences.
Asset quality is only part of the story. Concentration, segregation mechanics, and contingency paths matter just as much. The monetary impact depends on which issuer absorbs the growth and which banks hold those reserves.
Weekend gaps, queue priority, banking-hour dependencies, and gateway capacity all matter once markets get stressed. The stress test: a redemption request arrives at 2am Saturday. The token settles in seconds. The underlying reserve will not mobilize until Monday.
Technical confirmation, economic finality, and legal enforceability can diverge. Settlement finality includes value integrity (does the settled amount hold its intended value?) and convertibility (can the holder actually redeem?). If those definitions differ, the gap has to be named and allocated.
Routing, sweep logic, custody, and hold operations determine how the system behaves in practice. The operator with the compliance obligation becomes the chokepoint. Required artifacts: screening, policy routing, audit logs, and hold workflows.
Every product has a failure sequence. If that sequence has not been documented before launch, the product is not ready. The MVEP framework defines the minimum evidence that must exist; the CLII monitors whether the control surface degrades after approval.
| If you are... | Start with |
|---|---|
| Evaluating policy, concentration, or systemic risk | Policy & Market Infrastructure |
| Evaluating a tokenized product for institutional capital | Asset Management & Tokenization |
| Building or launching a stablecoin or tokenized-money product | Stablecoin & Payments Strategy |
| Evaluating controls, diligence, or escalation paths | Risk, Controls & Market Infrastructure |
| Working on DePIN, incentives, or protocol design | Tokenomics & DePIN track |
| Reading the core thesis first | 5-minute flagship brief |
Routing the Dollar. Gateway concentration, regime-dependent monetary-policy transmission, and operator accountability under stress. The CLII measures how heavily regulated each gateway is across five dimensions. A high score means more regulatory obligations; stress performance depends on reserve-bank exposure and other entity-specific conditions.
Minimum Viable Equivalence Packs. Three equivalence claims (legal, operational, economic) tested through nine diligence categories. MVEP is the entry gate; CLII is the drift detector.
Dollar v3. Three digital-dollar objects, Layer 0, and deposit mutation. The GENIUS Act reinforces the payment-stablecoin perimeter; deposit tokens and yield wrappers require separate treatment.
The Control Layer War. How CLARITY-style provisions (House-passed form analyzed here) attach compliance at the control layer: interfaces, routing defaults, hold workflows, and audit logs.
Adaptive Tokenomics. Systems-engineering design laboratory stress-tested with a 240-run Monte Carlo simulation. Adaptive emissions as downside insurance; slashing dominates token burns during the early growth phase.
Operational Risk in Token Economies. 624-configuration simulation: adaptive controllers become more resilient under infrastructure shocks. Reputation-weighted governance collapses when the designer sets the recovery threshold above what operators can reliably achieve (99%); lowering it to 95% stabilizes the system.
Overview explains the objects. Frameworks explains the decision tools: CLII for gateway monitoring, MVEP for entry-gate diligence, the Credit Migration Model for deposit and funding-structure analysis, and the Regime Dashboard for control-layer and operating-regime classification.
Tell me what you are building or evaluating. I will point you to the most relevant paper, resume version, or supporting material.