# Asset Whitelist

**Overview**

Yuzu Money maintains a curated [**Asset Whitelist**](https://app.yuzu.money/asset-whitelist) that defines where backing assets for yzUSD may be deployed.

Only assets and protocols on this list are eligible for deployment of the [Backing Assets](https://yuzu-money.gitbook.io/yuzu-money/yuzu-stablecoin/collateral-pool-backing-assets). When a new protocol is added, it is subject to a 7-day activation period before any funds are deployed. This allows users to observe the boundaries of Yuzu Money’s mandate instead of “trusting the strategist”.

You can verify live positions and exposures at our [Transparency dashboard ](https://yuzu.accountable.capital/)(Accountable) under the Strategy Breakdown view.

*Note: The page reflects only Yuzu Money’s whitelisted underlying asset exposures and does not include additional smart contract surfaces (e.g. DEXes, routers, bridges, aggregators, etc.) that the protocol may interact with in the course of deployment.*

**What Gets Whitelisted?**

For an asset or venue to be whitelisted, it must pass Yuzu Money's internal risk framework, which includes but is not limited to:

* Oracle and price-feed design
* Smart contract risk
* Economic / liquidity risk
* Counterparty and governance risk
* Alignment with our capital-preservation mandate

**Status Labels & Activation Rules**

For each asset / venue combination, we display a **status**:

* **Active** –

  > It is within Yuzu Money’s mandate to deploy backing assets into this asset / venue combination. Positions may already be live.
* **Activating** –

  > Approved by risk, but subject to an activation countdown. Yuzu Money will only deploy backing assets after the activation window elapses.
* **Paused** –

  > Temporarily disabled for new allocations. Existing positions are being monitored and, where appropriate, unwound.

**Governance, Reviews & Pauses**

* New assets/venues go through a risk review and require collective sign-off by the asset allocation team&#x20;
* Material changes (e.g. protocol upgrade, oracle change, governance incident) may trigger a **re-review** and may result in a downgrade to *Paused* or *Removed*.
* Changes to the whitelist are timestamped and visible in the dashboard history, so users can see *when* mandate changes happened.
