Collateral eligibility
Reserve assets are onboarded by class, source, liquidity depth, custody model, valuation availability, legal clarity, and governance approval.
Control frameworkRisk Controls
USDV risk controls are built to keep synthetic dollar issuance inside defined collateral, liquidity, oracle, chain, and governance limits. The goal is not maximum speed. It is controlled growth with transparent parameters.
CollateralEligibility
MintingCaps
ReviewGovernance
Control matrix
Rules before scale
Every USDV expansion path should pass through conservative limits before minting or routing capacity is increased across the settlement networks.
Haircut policy
Each collateral class receives a conservative risk adjustment so volatile, opaque, or less liquid assets contribute less to minting capacity.
Oracle freshness
Pricing inputs must remain inside freshness windows. Stale or divergent oracle data can reduce mint capacity or trigger manual review.
Chain supply caps
XRPL, Stellar, Solana, Sui, and Ethereum can carry separate supply ceilings, deployment states, and operational monitoring thresholds.
Mint throttles
Minting can be limited by reserve coverage, liquidity availability, chain-specific exposure, pending attestations, or governance-defined launch stages.
Escalation path
Material deviations should move through governance review before parameters are expanded, restarted, or changed in production.
XRPL
Stellar
Sui
Solana
EthereumRisk lifecycle
Detect, limit, reconcile, resume
Detect
Monitor coverage, asset allocation drift, oracle freshness, chain supply, liquidity depth, and operational events.
Limit
Apply caps, throttles, reserve-ratio buffers, and chain-level constraints before risk becomes system-wide.
Escalate
Route exceptions to governance contributors and operational reviewers with the data needed to act quickly.
Resume
Restore normal parameters only after reserve, oracle, chain, and reporting conditions return inside policy.
Risk register
Key risk buckets
The control framework is designed around observable risks that can be monitored, limited, and governed over time.
| Risk | Control objective | Example mitigation |
|---|---|---|
| Reserve risk | Ensure USDV is supported by eligible, valued, and documented collateral. | Asset limits, haircuts, custody reporting, attestation review. |
| Oracle risk | Reduce dependency on stale or manipulated price data. | Freshness windows, source comparison, fallback policy, governance review. |
| Liquidity risk | Keep usable reserve liquidity aligned with redemption and market-stability needs. | Liquidity buckets, stablecoin buffers, pool depth monitoring. |
| Chain risk | Limit exposure to chain-specific operational, bridge, issuer, or contract issues. | Supply caps, deployment stages, chain monitoring, incident throttles. |
| Governance risk | Prevent unreviewed parameter changes from increasing systemic exposure. | Proposal process, parameter registry, role separation, reporting trail. |
Risk Controls define the intended operating discipline for USDV. They are not a promise that every risk can be eliminated; they define how risk should be measured, limited, escalated, and communicated.