Deployment walkthrough

The Reserve Yield Protocol allows anyone to permissionlessly create Yield DTFs backed 1:1 by collateral assets of their choosing. The options for governance design and operational parameters available to deployers are essentially limitless.

This guide walks through the main steps to deploying a Yield DTF using the Reserve app.

Getting Started

Step 1: Getting Started

1. Navigate to the Yield DTF deployer UI
2. Connect your wallet using the Connect button in the top right
   
   
   

Define your DTF

Step 2: Define your DTF

A DTF's name, ticker, and mandate are important as unique identifiers which serve to convey its core purpose and set it apart from other products in the marketplace.

• Network - The DTF's native blockchain
• Token Name - The DTF's full name
• Ticker - The DTF's abbreviated symbol (Staking token names and tickers are auto-generated)
• Mandate - Description of the goals the DTF's governors should try to achieve. By briefly explaining the DTF’s purpose and what the RToken is intended to do, it provides common ground for the governors to decide upon priorities and how to weigh tradeoffs.

Configure Basket

Step 3: Configure Basket

Now it’s time to define what collateral assets back your DTF, and in what proportions. Emergency collateral can also be defined as fallbacks in the event any primary collateral defaults.

A number of collateral plugins can be employed “out-of-the-box.” If a desired collateral plugin doesn’t already exist, developers may create and deploy custom plugins.

• Under “Primary Basket,” click the “Add to basket” button
• Select your desired collateral assets. In this example, a number of yield bearing stablecoin positions will be used.
  
  
  

Note: In order to mint the DTF after it’s created, deployers must either have the selected collateral assets in their wallet, or use the “Zap Minting” utility, which enables minting using just 1 asset (e.g., mint eUSD using just USDC).

• Once satisfied with the selected assets, click “Add to basket”.
• Select your asset distributions, as well as the number of target units (e.g. USD, BTC, ETH) your “Target Basket” comprises.
  
  
  

Configure Backup Basket

Step 4: Configure Backup Basket

1. It’s generally recommended to configure Emergency Collateral in a backup basket. These are defined separately for each target unit.
2. The ‘Diversity factor’ of your backups dictates the number of backup assets the DTF will scale into when exiting defaulted collateral (split evenly if there are multiple backups).
   
   
   

Configure Parameters

Step 5: Configure Parameters

This section discusses what each configuration parameter does, and why it’s important. For more information on each parameter, see Advanced Parameters.

Note that the Reserve app provides sensible defaults and unless you’re an advanced user, you can deploy your RToken using the defaults and skip this section.

Backing Manager Parameters

Other Parameters

Deploy

Step 6: Deploy

Once you’re satisfied with your DTF’s name, basket composition, and other parameters, you can click “Deploy” button which will prompt you to sign a transaction (“Tx1”).

Congratulations! You have successfully deployed your Yield DTF. However, no governance system has yet been configured. Continue reading to learn how to set up decentralized governance on your DTF using Governor Anastasius.

Note that if you aren’t yet ready to set up governance, you can leave your RToken paused and return later to finish.

Set up Governance

Step 7: Set up Governance

1. If you wish to use Governor Anastasius (default; recommended by Reserve), ensure the following toggle is active
   
   
   
2. Carefully select addresses for Guardian, Pauser, and Freezer roles. See here for more details on system roles.

Addresses for each role are separate from each other and from the Guardian. However, often, the Guardian address is also included in the other three roles.

Next, configure the ‘Governance parameters’

Note that the Reserve app provides sensible defaults and unless you’re an advanced user, you can deploy Governance using the defaults and skip this section

Governance parameters

Select whether your DTF will be left in a paused state or whether it will be functional after configuring governance (In other words, the deployer decides whether the DTF should be active immediately post-deployment, or whether governors should decide to start in a paused state.)

Once you’ve made a selection, click “Deploy Governance”. Once that transaction confirms, the DTF is live onchain with the live state parameters you chose above.

Closing

All of the DTF’s relevant contracts can be viewed under the “Related Contracts” section of the UI. The DTF is now ready to accept collateral assets and be used throughout the ecosystem.

The deployment process is complete! That said, your new DTF’s journey has just begun — ongoing attention and marketing are required for DTFs to distinguish themselves in a crowded marketplace and truly flourish. Check out the post‑launch playbook for helpful tips.

Join the Reserve Discord server to share knowledge with and learn from other DTF deployers in the ecosystem.

Appendix

How to create custom RToken collateral plugins

Deployers have the option to create and use custom collateral plugins for an RToken by adding a custom plugin contract address in the Primary Basket or Emergency Collateral during the deployment process.

The following resources will be of use to those wishing to create custom collateral plugins:

• Collateral Plugin Overview describes what a developer needs to know to begin writing and contributing collateral plugins. Familiarity with this material is crucial before jumping into writing a plugin.
• Writing Collateral Plugins describes the general process a developer should follow when writing a new collateral plugin. Filling this out accomplishes 90% of the work necessary before any coding is required.
• Reserve’s Solidity Style details practices and conventions relevant to reading and writing Solidity source code in the Reserve house style.

Troubleshooting questions and feedback are always welcome in the Reserve Discord server. The #🔧|technical-discussions channel is actively monitored by core team engineers.

Non-compatible ERC-20 assets

The following types of ERC-20s are not supported to be used directly in a Yield DTF system:

These tokens should be wrapped into a compatible ERC-20 token to be used within the protocol. A concrete example is the use of Static ATokens for Aave V2.

Yield DTF deployer video tutorial