---
# System prepended metadata

title: Info Architcture

---

# Info Architcture

## Problem
Language use and implementations are changing fast. It's hard for many users to maintain a clear mental model of the yearn products. As the documentation process moves forward, it's evident we need to clarify naming conventions and our product structure.

**yUSD Example:**
We talk about `yUSD`, which is either the same as, or a wrapper of, `yyCRV`, which is actually `yyDAI+yUSDC+yUSDT+yTUSD` and also `yearn Curve.fi yDAI/yUSDC/yUSDT/yTUSD` on [etherscan](https://etherscan.io/token/0x5dbcF33D8c2E976c6b560249878e6F1491Bca25c). 

**yUSDC Example:** 
You can deposit into the **yEarn** USDC contract and get **yUSDC**, that contract yields ~3%.
![](https://i.imgur.com/dFBxqwS.png =500x)

You can deposit into the **yVault** USDC contract and get **yUSDC**, that contract yields ~22%.
![](https://i.imgur.com/6VVluUn.png =500x)


## Solution Requirements
Let's develop what requirements a solution in this space requires. Here is an initial list, please suggest modifications:
- Product and Token names need to be matched and unique, eg the name of the yToken received via a specific yVault should match the name of the vault and be unique from other products
- Product names and branding need to be clearly differentiated
- Branding should help new users understand the differing services (eg yEarn vs yVault) and their associated risk


