Definition

SVA captures the expected loss from a stablecoin losing its 1:1 peg to the reference fiat currency. It is the single most important XVA component for stablecoin holdings because it directly challenges the assumption that $1 USDC = $1 USD at all times.

The holding-period multiplier reflects that longer exposures increase the probability of encountering a depeg event.

Typical Values by Stablecoin

Limits & Escalation

SVA has specific thresholds defined in the policy (§8.3):

Calculation Method

SVA is calculated using Bayesian inference. The prior on P(de-peg) is updated with each new reserve attestation, on-chain depeg event, and issuer credit signal. For example, when Tether’s reserve attestation is 12+ days stale, the Bayesian prior shifts upward (e.g., from 1.5% to 1.8%).

Definition

SCVA quantifies the expected loss from smart contract failure — whether from code exploits, logic errors, upgrade vulnerabilities, or governance attacks. Unlike traditional counterparty credit risk, this is a purely technological risk with fat-tailed loss distributions.

For the TWAP Paradox context, SCVA also has a lag component: SCVA_lag ≈ LGD × P(mismatch) × σ × √(τ), capturing the staleness risk of oracle pricing mismatches over the TWAP window.

Key Inputs

Limits

Warning at 10 bps, hard limit at 25 bps. Escalation to Risk Committee. In the positions prototype, BUIDL carries SCVA of 8 bps (P(exploit) = 0.3%, LGD = 25%).

Definition

LCVA is the valuation adjustment for legal and custody risk — the possibility that regulatory changes, adverse legal interpretations, or custodial failures cause a loss of access to, or value of, digital asset holdings. It compounds over time, reflecting the cumulative exposure to regulatory uncertainty.

Drivers

LCVA is the largest single XVA component on average across positions (18.2 bps portfolio-weighted). Key drivers include:

• Pending regulatory guidance — e.g., SEC guidance on tokenized fund custody under the Investment Company Act
• Custody structure — whether assets are segregated, bankruptcy-remote, and held by regulated custodians
• Jurisdictional variation — different legal treatment across US, EU, Singapore, Hong Kong
• Issuer regulatory status — GENIUS Act compliance, MiCA authorization, state licensing

Limits

Warning at 25 bps, hard limit at 50 bps. Escalation to CFO + Legal. In the positions prototype, BUIDL’s LCVA is at 27 bps (above warning), driven by pending SEC guidance. Outside counsel opinion expected by 18 Apr 2026.

Definition

DPVA applies specifically to tokenized assets like BlackRock BUIDL, Ondo USDY, and Franklin OnChain. It quantifies the expected loss from NAV deviation under stress and redemption delays.

For BUIDL: P(stress) = 20%, E[NAV discount] = 75 bps → DPVA = 15 bps.

Values by Instrument

Definition

OVA quantifies the risk that price oracle feeds are manipulated, stale, or unreliable — leading to mispriced positions. This is the dominant risk factor during crypto stress periods and is central to the TWAP Paradox.

Where τ = TWAP window, n = number of oracle sources, f = update frequency, depth = market depth. The inverse relationship with τ creates the paradox: shorter windows reduce staleness but increase manipulation risk.

Sub-Factors

In the Liquidity Monitor

OVA carries the highest weight (30%) in the Crypto XVA Aggregate formula. In the cascade replay stress scenario, OVA surged more than 6× from baseline — the dominant driver of the aggregate breaching the critical threshold.

Definition

BRVA quantifies the risk unique to cross-chain bridges — the infrastructure that moves assets between blockchains. Bridge exploits have historically been among the largest loss events in DeFi (Wormhole: $320M, Ronin: $625M).

Sub-Factors

Limits & Current Status

Warning at 20 bps, hard limit at 50 bps. Escalation to Treasurer. In the risk positions prototype, Wormhole BRVA has breached at 52 bps after TVL dropped 18% over 48h following a validator set rotation. Auto-pause triggered on new bridge transfers.

Approved bridges: Wormhole, LayerZero, CCIP (Chainlink). Maximum bridge exposure: $5M or 10% of digital portfolio.

Definition

GVA quantifies the expected transaction cost risk — that gas fees spike during periods of high network demand, increasing the cost of executing sweeps, funding operations, or emergency exits.

Typically a small component (0.5–2 bps) for Ethereum mainnet operations, but can spike during network congestion.

Limits

GVA is often combined with OVA for reporting. Combined GVA + QVA warning at 5 bps, hard limit at 15 bps. Escalation to Treasury Ops. Current worst: 2.5 bps combined.

Definition

RWVA quantifies the fair-value discount arising from contractually constrained redemption windows (including T+1 or longer queue delays), capturing the cost of time-to-liquidity impairment relative to instantaneous-redemption benchmark pricing under ASC 820 / IFRS 13. It applies to tokenized assets with defined redemption windows (T+0, T+1, T+2) and quantifies the expected cost of being unable to exit a position within the expected timeframe.

BUIDL: RWVA = 3 bps (T+1 window). Ondo USDY: RWVA = 4 bps (T+2 window).

ASC 820 / IFRS 13 Context

Under ASC 820 / IFRS 13, a contractually constrained redemption window is a valuation input that affects the Level-2 or Level-3 fair-value measurement of the instrument. RWVA prices this constraint explicitly into the risk-adjusted yield deduction, rather than leaving it as an undisclosed liquidity assumption buried in NAV pricing. This is distinct from DPVA, which captures NAV deviation under stress; RWVA captures the time-to-liquidity cost even when NAV is at par.

Definition

OCVA is the catch-all for operational risk in digital asset management — wallet infrastructure outages, key management failures, signing errors, and process breakdowns.

Typically small (0.5–1.3 bps) but can become material during infrastructure incidents. Mitigated by approved service providers (Fireblocks, Coinbase Prime) with SOC 2 Type II attestations.

The Three Competing Risks

The Total Cost Function

CCVA is the correlation/non-additivity term that scales with volatility. The optimal window τ* minimises Φ and is sensitive to four controllable parameters:

• Volatility (σ) — higher volatility shifts τ* shorter
• Market depth — deeper markets allow shorter windows
• Oracle sources (n) — more sources reduce manipulation risk
• Update frequency (f) — faster updates improve freshness

Typical τ* Values

At default parameters (σ=80%, medium depth, 3 sources, 5s updates): τ* ≈ 6–15 minutes with total Φ(τ*) around 55–85 bps. Under stress (σ=200%, shallow depth): τ* compresses to 2–5 minutes.

The Problem

A 3-month T-bill and a USDC stablecoin holding may receive identical accounting classification, but the T-bill carries ~2 bps of XVA (sovereign credit only) while USDC carries ~60 bps (SVA + SCVA + LCVA). The headline yield spread of 5–10 bps in favor of stablecoins is often more than consumed by the XVA deduction.

Risk-Adjusted Comparison

This is why risk-adjusted yield is the correct metric for treasury decision-making, not headline yield.

Formula

This is the central metric of the framework. It answers the question: “What is this instrument actually returning once we account for all the digital-asset-specific risks?”

Portfolio Comparison

DeFi lending has the highest headline yield AND the highest risk-adjusted yield, but also the widest risk band. The portfolio question is how to allocate across these instruments to maximize risk-adjusted return within position limits.

Method Selection Framework

Data Sources

Approved Stablecoins (§7.1)

Current Portfolio ($21.5M total)

USDC: $12.5M (at 25% limit) • USDT: $5.2M (11%) • EURC: $3.8M (8.1%)

Approved Tokenized Assets (§7.2)

Approved Protocols (§7.3)

DeFi Lending Risk Profile

DeFi lending carries the highest XVA at 145 bps (blend) but also the highest gross yield at 7.20%, resulting in a risk-adjusted yield of 5.75%. DeFi exposure is capped at 5% of the digital portfolio per §8.2.

What It Is Not (Boundary Cases)

Roster (Snapshot, July 2026)

Live, single-bank own-issued: JPMorgan (Kinexys Digital Payments in USD/EUR/GBP on a proprietary permissioned ledger, and JPMD, a USD deposit token on public Base, live for institutional clients with Canton Network planned), Citi Token Services (USD, private permissioned, EUR expansion underway), HSBC Tokenised Deposit Service (EUR, GBP, HKD, SGD, USD), DBS Token Services / Treasury Tokens (SGD, multi-currency), Standard Chartered Tokenised Deposits (SGD, USD, HKD, CNH), BNY Tokenized Deposits (USD), and Wells Fargo Digital Cash (USD, legacy and narrow).

Pilot or boundary: UBS Digital Cash (pilot), BBVA via Visa VTAP (pilot), and ANZ A$DC / NZ$DC (institutional; self-branded a "stablecoin," structurally a boundary case here).

Shared rails (not issuers): Partior (live), Regulated Liability Network (pilot), The Clearing House shared network (targeting H1 2027).

This is a fast-moving class. Treat the roster as accurate to within days and verify status before external citation.

XVA Profile

The profile is topology-conditional: the same instrument class carries different components depending on where the token is issued. In every case LCVA leads and SVA is zero.

By Topology

Methodology note: pricing CompVA on a shared bank-deposit network requires generalizing the policy section 5.3 CompVA definition from "protocols" to "network participants." Flagged for the next policy revision.

Accounting Treatment

• Out of scope of ASU 2023-08 (ASC 350-60). A deposit token fails two independent scope gates: it is a direct deposit claim (Condition (b)), and deposits with financial institutions are carved out as financial assets. It is not a crypto-intangible asset.
• Holder-side measurement. Cash equivalent under ASC 305 in the base case (par-redeemable, on demand, original maturity of three months or less). Otherwise an amortized-cost receivable with CECL. Not fair value through income.
• Issuer-side. A deposit liability under ASC 942. The ledger does not change the liability's character.
• Client-electable election. The cash-equivalent versus amortized-cost-receivable branch is a client election with a recommended default of cash equivalent. The out-of-scope conclusion itself is not elective.
• Disclosure. Largely outside the ASC 820 fair-value hierarchy, because the instrument is not carried at fair value. This is a lower disclosure burden than a stablecoin. A CECL allowance disclosure applies on the receivable branch.
• IFRS. No crypto-asset standard applies; the token is treated as a financial asset under IFRS 9. US and IFRS books converge without the "crypto asset" framing.

Why This Is Its Own Category

Three tokenized instrument types that look alike at the wrapper level resolve to three different treatments:

Both the risk decomposition and the accounting reach "distinct fourth category" independently, from different disciplines. A deposit token is not a bank-issued stablecoin, and stating that plainly heads off the first objection a sophisticated reader raises.

XVA-Based Position Limits (§8.1)

Aggregate Exposure Limits (§8.2)

Individual XVA Component Limits (§8.3)

Exception Approval Authority (§13.1)

Sweep Formula (§9.1)

Sweeps execute daily at 16:00 local (after settlement finality). Currency matching: USDC→USD, EURC→EUR.

Funding Trigger (§9.2)

5% safety buffer above projected outflows. Same-day settlement for funding triggered at 08:00.

Regional Sweep Timing

Minimum Balance Thresholds

Operating accounts retain a minimum balance after sweep to cover next-day operational needs. Standard minimum: $50,000 or local currency equivalent. Emergency threshold: if balance exceeds $5M outside scheduled sweep time, an ad-hoc sweep is triggered with Treasurer notification. Funding horizon: maintain 1.05× projected outflows (5% safety buffer).

Exception Handling

Failed sweeps retry up to 3 times with 15-minute intervals. After 3 failures: alert to Treasury Ops + Treasurer. Manual override available for critical funding with dual approval. Weekend/holiday sweeps: pre-positioned on prior business day for known obligations.

Cross-Chain (§9.4)

Treasurer approval required for bridge transfers >$500K. Bridge failure fallback activates if delay >4 hours. BRVA must be <50 bps for bridge execution. See Smart Contract Architecture for the on-chain anchoring of sweep execution proofs.

Tax Impact (§11.3)

Jurisdictional Coverage

United States — Federal Regulatory Landscape

European Union

MiCA (Markets in Crypto-Assets): Full framework effective June 2024. EMT (e-money tokens) and ART (asset-referenced tokens) classifications. CASP licensing for service providers. Reserve requirements for stablecoin issuers. MiFID II / EMIR: Applies when tokenized assets qualify as financial instruments. DLT Pilot Regime: Sandbox for DLT-based market infrastructure. DORA: Digital operational resilience requirements for financial entities.

Asia-Pacific & Other Key Jurisdictions

Global Standards Bodies

BIS / Basel Committee: Prudential treatment of crypto-asset exposures (Group 1a/1b/2). FATF: Travel Rule (Recommendation 16), VASP licensing guidance. IOSCO: 18 policy recommendations for crypto/DeFi markets. FSB: High-level framework for crypto-asset activities (9 recommendations). IMF: Crypto-Asset Reporting Framework (CARF) for cross-border tax transparency.

Restricted Jurisdictions (§11.2)

China: Cross-border crypto prohibited; all crypto trading banned since 2021. India: 30% tax on crypto gains; 1% TDS; restricted but not banned. Venezuela: CADIVI/CENCOEX restrictions; VES-only netting. Capital control jurisdictions require per-transaction regulatory checks.

Approved Service Providers (Appendix C)

All providers must have SOC 2 Type II, segregated custody, and bankruptcy-remote structures: Coinbase Prime (custodian), Fireblocks (wallet infra), Circle (issuer), Anchorage Digital (OCC-chartered custodian).

Roles & Responsibilities (§4)

Reporting Cadence (§12)

Daily: Position report, XVA dashboard, sweep execution, exceptions. Weekly: XVA trends, protocol health, regulatory updates. Monthly: Comprehensive XVA, risk-adjusted returns, counterparty exposure, tax lots, compliance. Quarterly: Board strategy review, model validation, compliance certification.

Policy Review (§14)

Annual review by Finance Committee. This policy is subordinate to the Corporate Treasury Policy and overall Investment Policy. Interim amendments can be proposed by Treasurer for material market or regulatory changes.

Dashboard Metrics (as of 12 Apr 2026)

Position Breakdown (6 Active Positions)

Allocation: Stablecoins $21.5M (45%), Tokenized Treasuries $12.7M (27%), Tokenized MMFs $10.7M (23%), DeFi $2.3M (5%).

XVA Monitor

Portfolio-weighted XVA of 28.4 bps sits in the 25–50 bps enhanced monitoring zone. Largest single component: LCVA averaging 18.2 bps across positions. Two components in warning status: BRVA (Wormhole breached at 52 bps) and USDT SVA approaching 15 bps threshold.

Active Alerts

Prototype Pages

The full risk positions prototype includes 9 operational pages: Dashboard, Position Monitor, XVA Monitor (with heatmap), Sweep & Funding (execution timeline), Limits (utilization bars), Alerts (critical/warning/info), Regulatory (compliance cards), Reports (daily/weekly/monthly/quarterly), Approved Assets (reference table), and Governance (roles & responsibilities).

Three-Domain Architecture

The monitor tracks risk across three domains simultaneously, using a worst-of approach for consolidated status:

Crypto XVA Aggregate Formula

Weights reflect the relative importance: OVA carries the highest weight (30%) as oracle risk is the most dynamic and consequential factor. SCVA and LVA at 25% each, BRVA at 20%.

Design Principles

The stress library calibrates the framework against ten historical and hypothetical scenarios drawn from real crypto-native and cross-market stress events. Each scenario isolates a distinct failure mode:

• Cross-domain correlation — TradFi liquidity stress (unsecured funding spike, FX basis widening) amplified by simultaneous crypto-native stress
• Oracle cascade — oracle staleness and manipulation during high-volatility episodes; OVA as the dominant driver
• Bridge exploit — concentrated bridge exposure combining TVL collapse, validator set changes, and exploit history; BRVA breaching limits
• Stablecoin depeg — reserve opacity combined with a market stress trigger; SVA crossing the hard limit
• Cross-protocol cascade — composability contagion through shared collateral; CompVA SCC and CPBUC sub-factors as early-warning signals

Illustrative Stress Amplification Factors

Across the 10-event calibration set, components exhibit characteristic amplification patterns under stress. The values below are representative of a severe cross-domain scenario in the library:

OVA consistently shows the highest amplification factor — reflecting its role as the most dynamic and consequential component during crypto stress periods.

Monitor Response

For each scenario, the Liquidity Monitor demonstrates the transition path Normal → Warning → Critical with recommended actions at each stage. The cascade replay (April 2026 Aave / Kelp DAO / LayerZero event) is the primary demo scenario; see CompVA for the detailed sub-factor timeline.

Target Hedge Ratios by Maturity

Hedge Ratio Formula

Calculated per currency pair. Reviewed weekly; rebalanced when ratio drifts outside the permitted range by more than 5 percentage points.

Permitted Hedging Instruments

Prohibited: Selling naked options, speculative FX positions, leveraged FX derivatives, binary/exotic options.

Hedge Recommendation Procedure

Step 1: Identify all non-functional currency exposures by entity and currency pair. Step 2: Categorize exposures by maturity bucket. Step 3: Calculate current hedge ratio per bucket. Step 4: Compare to target ratio and determine gap. Step 5: Select appropriate instrument and counterparty. Step 6: Obtain required approvals per Delegation of Authority. Step 7: Execute and confirm. Step 8: Document hedge designation (if hedge accounting applied).

Three-Level Agreement Structure

Hub-and-Spoke Model

Central treasury (HQ) acts as the netting centre. Regional Pool Headers (e.g., EU Pool, APAC Pool, Americas Pool) aggregate subsidiary positions before settling net amounts with HQ. This reduces the number of cross-border payments from O(n²) bilateral to O(n) hub-spoke, cutting transaction costs and FX spread leakage.

Worked Example

Transfer Pricing Addendum

Intercompany FX conversions within the netting cycle must include an arm’s-length markup to satisfy transfer pricing requirements:

Netting Cycle Timing

Standard cycle: Monthly, with cut-off on T-5 business days before month-end. Submission deadline for intercompany invoices: T-7. Dispute resolution window: T-5 to T-3. Net settlement: Last business day of month. Emergency ad-hoc netting available with Treasurer approval for amounts >$1M.

Approved Instruments

Diversification Limits

Prohibited Instruments

Equity securities, structured notes (unless Board-approved), auction-rate securities, inverse floaters, mortgage-backed securities (unless Government agency), and any instrument with embedded leverage.

Five Key Principles

Payment Approval Tiers

Digital Asset Approval Tiers

Digital Asset Compliance Requirements

All digital asset transactions must satisfy: GENIUS Act compliance verification (US entities), SEC custody rule checks, MiCA authorization (EU entities), approved custodian whitelisting (Fireblocks, Coinbase Prime, Anchorage), AML/KYT screening via Chainalysis or equivalent, and OFAC sanctions screening on all wallet addresses.

Americas

Asia-Pacific

EMEA

Policy Engine Rule Syntax

Policy Structure at a Glance

The map below visualises the five interlocking pillars of the policy on one canvas. Read left-to-right: governance sets authority; the XVA framework prices risk per position; limits convert XVA readings into position constraints; sweep & funding operations execute within those constraints; and the regulatory pillar defines external boundary conditions for all of the above.

Purpose, Scope & Objectives (§1–3)

The policy establishes comprehensive guidelines for identifying, measuring, managing, and monitoring risks associated with digital assets, including cryptocurrencies, payment stablecoins, tokenized real-world assets, and DeFi protocol interactions (§1). It applies to all subsidiaries, including regional treasury centers and foreign subsidiaries, covering cross-chain transactions, automated sweep and funding operations, and intercompany settlements denominated in or facilitated by digital assets (§2). The five stated objectives are: preserve principal through XVA-based limits; ensure operational liquidity through coordinated fiat-crypto sweep mechanisms; maximize risk-adjusted return after accounting for all applicable XVA components; maintain full regulatory compliance across all applicable jurisdictions; and provide complete audit trails for all digital asset transactions and risk calculations (§3). The policy operates in conjunction with the Short-Term Investment Policy, FX Risk Management Policy, Treasury Sweep and Funding Policy, and In-House Banking Policy.

Governance Chain (§4)

Authority flows from the Board of Directors (approves policy; sets maximum aggregate exposure limits) to the CFO (approves XVA calculation methodologies and risk tolerance thresholds) to the Treasurer (executes digital asset strategies, monitors XVA metrics, manages sweep and funding operations, maintains counterparty relationships). Risk Management calculates and monitors XVA components, validates model inputs, performs stress testing, and escalates limit breaches. The Compliance Officer ensures adherence to all applicable regulations and maintains AML/KYC compliance. The Tax Department manages transfer pricing documentation for intercompany digital asset flows. The Finance Committee of the Board reviews and approves the policy annually and monitors effectiveness against market developments and regulatory changes (§14).

Digital Asset XVA Framework (§5)

The framework is a systematic methodology for quantifying crypto-native risks, grounded in the SSRN working paper §2.1. The fundamental unit is: XVA Component = Probability of Event × Severity of Loss × Discount Factor. The framework maps each position to the surfaces that apply across three architectural tiers and a policy-only residual cluster — this is an open mapping by instrument, regime, and jurisdiction, not a fixed closed roster.

Tier I — Protocol-Level Adjustments (§5.1): Capture risks endogenous to a single protocol's design and operation. Components active include SCVA (smart contract bugs, exploits, upgrade vulnerabilities; typically Level 2), OVA (price manipulation, stale oracle feeds, liveness failures; the TWAP Paradox is an OVA sub-problem), LRVA (pro-cyclical market depth and liquidity regime shifts during stress), BRVA (bridge exploits, message delays, cross-chain liquidity shortfalls; a leading indicator — feeds CompVA infrastructure overlap), and GVA (gas price spikes, network congestion, failed transaction execution).

Tier II — Asset-Level Adjustments (§5.2): Capture risks attached to the asset itself irrespective of venue. Components include SVA (de-peg events and reserve opacity; example: P(de-peg) = 2%, E[discount] = 50 bps, Exposure = $10M → SVA = $1,000), TVLVA (adoption-decline risk where TVL contraction triggers reverse-flywheel outflows), and LCVA (jurisdictional uncertainty, bankruptcy remoteness, custodian failure; example: P(event) = 2%, LGD = 20% → LCVA = 40 bps — often the largest single component for cross-border tokenized exposures).

Tier III — Cross-Protocol / Network-Level (§5.3): Introduced in SSRN v3 following the April 2026 Aave / Kelp DAO / LayerZero cascade. The component is CompVA, operationalised through three sub-factors with weights that aggregate as: CompVA = 0.40 × SCC + 0.30 × UQL + 0.30 × CPBUC. CompVA is not currently hedgeable; management responses are limited to portfolio rebalancing and SCC reduction below the hard limit (§8.2: SCC ≤ 0.55). Note the distinction from CCVA (Compositional Correlation Valuation Adjustment), which is a within-protocol non-additivity term — a separate concept defined in SSRN v3 §5.5.

Level 3 Residual Adjustments (§5.4): Policy-only by design — operational and capital adjustments retained for institutional implementation completeness but explicitly not part of the SSRN academic taxonomy. These include DPVA (NAV mismatch, stale pricing, redemption gates), RWVA (withdrawal queues and liquidity window gates), FXVA (FX volatility during cross-border settlement), QVA (MEV / sandwich attack exposure), OCVA (custodian downtime, API failures), TXVA (cross-border tax treatment uncertainty), KVA (regulatory capital cost), and MVA (initial margin on on-chain derivatives).

Approved Assets & Instruments (§7)

Approved stablecoins include USDC (Circle; GENIUS Act compliant, MiCA EMT authorized; max 25% of digital asset portfolio; SVA 5–10 bps based on reserve attestation recency), EURC (Circle; MiCA EMT; max 15%; SVA 10–15 bps), USDT (Tether; max 15%; SVA 15–25 bps, reflecting reserve transparency discount), and bank-issued stablecoins (per counterparty limits; SVA 5 bps) (§7.1). Approved tokenized assets include tokenized money market funds (Ondo USDY, Franklin OnChain U.S. Government Money Fund, Superstate funds — apply DPVA + RWVA + LCVA, plus CompVA evaluation if used as DeFi collateral), tokenized treasuries (BlackRock BUIDL, Securitize — apply DPVA + LCVA + SCVA), and bank-issued tokenized deposits (§7.2). DeFi protocol interactions are restricted to Ethereum mainnet, Base (L2), and Solana; DEX protocols Uniswap V3/V4 and Curve (stablecoin swaps only, requiring SCVA < 25 bps); and approved bridges (BRVA < 50 bps; currently Wormhole, LayerZero, CCIP, monitored continuously) (§7.3). Any new protocol must pass a Tier III pre-listing test confirming the addition does not push portfolio-level SCC above 0.45, UQL z-score above 2.0σ, or CPBUC above 0.65 (§8.3 warning thresholds).

Risk Limits & Thresholds (§8)

XVA-based position limits apply as a four-band scale: below 25 bps permits up to 100% of approved limit under standard monitoring; 25–50 bps reduces the limit to 75% with CFO notification and enhanced monitoring; 50–100 bps reduces to 50% and requires Risk Committee review; above 100 bps, the position is prohibited and any existing position must be exited immediately (§8.1). Aggregate caps include: maximum 10% of total cash and short-term investment portfolio in digital assets; maximum 25% of digital asset portfolio per single stablecoin issuer (combined across currencies from the same issuer); maximum 15% per single protocol; maximum 40% per single chain; maximum 5% in DeFi protocols; maximum $5 million or 10% of the digital asset portfolio in cross-chain bridge exposure at any time; dependency-graph density (SCC) ≤ 0.55, with rebalancing required if breached for more than 5 consecutive days (§8.2). Key component hard limits per Table 6 are summarised (abridged — not the full Table 6 roster) in the map above — see the Limits & Thresholds and Escalation Matrix articles for the full escalation-path detail (§8.3).

Sweep & Funding Operations (§9)

Stablecoin balances sweep to fiat concentration accounts daily at 4:00 PM local time following settlement finality confirmation. The minimum sweep threshold is $100,000 USD equivalent; the minimum retained operational float is $50,000 USD equivalent. Sweep Amount = Available Stablecoin Balance − Minimum Retained Balance − Projected 24-hour Outflows. Currency matching applies: USDC sweeps to USD, EURC to EUR; cross-currency sweeps require FX conversion per the FX Risk Management Policy (§9.1). Fiat-to-stablecoin funding is initiated by 8:00 AM when projected payment obligations exceed available stablecoin balance, with a 5% safety buffer: Funding Amount = Projected Outflows × 1.05 − Current Stablecoin Balance (§9.2). Tokenized asset redemptions are triggered by: liquidity needs exceeding available stablecoin and cash balances; DPVA or RWVA exceeding warning thresholds; or a regulatory or compliance requirement; T+1 or T+2 settlement windows apply as disclosed by the fund issuer (§9.3). Cross-chain movements require a BRVA calculation for the specific bridge and transaction size, Treasurer approval for amounts exceeding $500,000, real-time monitoring of bridge status and liquidity, and a documented fallback plan for delays exceeding 4 hours (§9.4). See the Sweep & Funding article for full operational detail.

Regulatory Compliance Framework (§10)

In the United States, payment stablecoins must be from GENIUS Act–permitted issuers meeting: 1:1 reserve backing in high-quality liquid assets (USD, T-bills, repos, government MMFs); monthly reserve attestation by a registered public accounting firm; OCC or substantially similar state license; no interest payments to stablecoin holders (§10.1). BSA/AML/FinCEN compliance requires FinCEN MSB registration for all digital asset service providers, transaction monitoring and SAR filing obligations, Travel Rule compliance for transfers exceeding $3,000, and OFAC sanctions screening for all wallet addresses and counterparties. In the EU, only E-Money Tokens from MiCA-authorized credit institutions or electronic money institutions are permissible; EMT issuers must hold 30–60% of reserves in EU credit institutions; custodians and CASPs must comply with DORA operational resilience requirements including ICT risk management, incident reporting, and third-party risk management (§10.2). Asia-Pacific coverage spans Singapore's PSA / MAS framework for digital payment token services and the Hong Kong Stablecoin Ordinance (2025) for HKMA-licensed HKD-backed stablecoins (§10.3). The jurisdictional basis risk — the valuation differential arising from the substantive divergence between Basel SCO60 (higher capital charges for permissionless infrastructure) and the March 5, 2026 OCC / Federal Reserve / FDIC interagency FAQ position (OCC Bulletin 2026-7) — is a priced risk entering through LCVA at the asset level and CompVA cross-tier correlations at the portfolio level (§10.4). See the Regulatory article for the full jurisdiction-by-jurisdiction breakdown.

Tax, Reporting, Exceptions & Continuity (§11–13)

Digital assets are treated as property for U.S. federal income tax purposes; any exchange for fiat, other digital assets, or goods/services is a taxable event. Cross-border stablecoin pooling requires arm's-length transfer pricing per OECD guidelines, with restricted participation for entities in China (prohibited) and India (verify current regulatory status) (§11). Daily reporting covers the Digital Asset Position Report, XVA Dashboard (current XVA by component with limit utilization indicators), Sweep/Funding Execution Report, and Exception Report. Monthly reporting includes the Comprehensive XVA Report with methodology documentation and uncertainty disclosures per SSRN v3 §8.1.4. Quarterly reports to the Board cover digital asset strategy review, XVA model validation back-testing results, and regulatory compliance certification (§12). Exception approval authority scales with severity: Treasurer alone for XVA threshold exceedances under 48 hours; CFO for extended exceedances; CFO plus Risk Committee for non-approved instruments; Board Finance Committee for aggregate limit breaches and policy amendments (§13.1). Business continuity procedures include manual sweep and funding fallback, backup custodian relationships, alternative bridge paths, emergency liquidation procedures, and annual disaster recovery testing (§13.2).

Use Case 1: Tokenized Treasury Allocation

XVA Analysis: T-Bills carry ~2 bps total XVA vs. BUIDL at 42 bps and Franklin OnChain at 24 bps. The yield pickup of 20–40 bps gross is partially consumed by XVA. Franklin OnChain emerges as optimal: highest risk-adjusted yield (4.81%) despite lower headline yield. Decision: Allocate to Franklin OnChain first, BUIDL second; monitor LCVA as SEC guidance evolves.

Use Case 2: Stablecoin Reserve Optimisation

Treasury holds $25M in stablecoins for operational payments. The XVA framework reveals USDC (SVA 18 bps) vs. USDP (SVA 6 bps) vs. USDT (SVA 30 bps). Optimal blend: 60% USDC (liquidity), 30% USDP (lowest XVA), 10% USDT (counterparty diversification with enhanced monitoring). Total portfolio SVA reduces from 18 bps (all-USDC) to 14.4 bps.

Use Case 3: Cross-Chain Liquidity

Treasury needs USDC on both Ethereum and Solana for different payment rails. BRVA analysis: Wormhole currently at 52 bps (breached), CCIP at 18 bps (within limits). Decision: Route via CCIP; hold native USDC on each chain rather than bridging where possible; cap bridge exposure at $5M total.

Use Case 4: Cross-Border Payments

Use Case 5: Intercompany Optimisation

Group with $150M monthly intercompany flows across 12 entities. Combining multilateral netting (40% payment reduction) with stablecoin settlement (for approved corridors) reduces total treasury costs by an estimated 25–35 bps on netted flows. Key constraint: jurisdictional rules restrict stablecoin netting in Brazil (BRL only), China (CNY only), and India (INR only).

TreasuryAnchor.sol — On-Chain Anchor

Solidity contract (^0.8.19) built on OpenZeppelin AccessControl. Provides immutable audit trails for off-chain treasury operations.

Key Contract Functions

State Transition Validation

Any gap or mismatch in the chain is detectable by auditors using the on-chain record, without needing to trust the off-chain system.

sweep-engine.ts — Off-Chain Policy Engine

TypeScript class (SweepPolicyEngine) implementing Treasury Sweep and Funding Policy §6. Manages evaluation, execution, compliance checks, and audit trail generation.

Compliance Checks (Policy §8)

Every sweep evaluation runs three automated compliance gates: