# Onboarding Yield-bearing Assets

This guide outlines the process of onboarding yield-bearing assets to Balancer v2. To fully leverage Balancer's technology, you'll need to complete several key steps including token setup, rate provider implementation, pool creation, and optional gauge setup for BAL rewards.

# Step-by-Step Onboarding Process

# 1. Token Setup

First, ensure your token is properly whitelisted on Balancer. See our token whitelisting guide for detailed instructions.

# 2. Rate Provider Implementation

For yield-bearing asset stable pairs using a stable pool, you must provide a vetted rate provider during pool creation:

1. Review existing rate providers in our registryopen in new window
2. If needed, submit your rate provider for review hereopen in new window

# 3. Pool Creation and Initialization

Use the community pool creator toolopen in new window to create your pool:

1. Select ComposableStable Pool type
2. Set Yield Protocol Fee Exempt to false
3. Add your token and approved rate provider
4. Add additional tokens (up to 5) with their rate providers
5. Create the pool
6. Perform an init join to seed initial liquidity

# 4. APR Data Integration

To ensure accurate yield metrics display:

1. Provide an API endpoint for your yield-bearing token
   • Format: api-yourtoken
   • Include APR in return values
2. Register your endpoint in the yield token registryopen in new window
3. This ensures correct APR display across Balancer frontend deployments

# 5. BAL Rewards Setup (Optional)

If you want to receive BAL rewards, you'll need to set up a gauge and apply through governance.

# Gauge Creation

# Governance Application Timeline

1. Submit proposal following the instruction setopen in new window
2. Contributor review by Thursday
3. Voting period: Thursday 8PM CET to Monday 8PM CET
4. On-chain gauge controller transaction by Tuesday evening CET
5. Gauge appears on veBAL voting pageopen in new window

# Additional Resources

• Gauge Onboarding Guide
• Rate Provider Documentation
• Core Pool Framework
• Protocol Fees Documentation