> For the complete documentation index, see [llms.txt](https://docs.reserve.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reserve.org/core-components/yield-dtfs/deployment-guide/designing-your-yield-dtf.md).

# Designing your Yield DTF

Before deploying, it’s important to consider what goes into creating a successful Yield DTF. Each DTF will have its own ecosystem use cases, community, and unique go-to-market strategies.

Just because anyone can deploy and/or mint a DTF does not mean adoption is guaranteed. Consider the following points to help ensure success.

## Key questions

{% stepper %}
{% step %}

### Collateral mix

Is the basket diverse and attractive?

* See our [basket design guide](https://blog.reserve.org/rtoken-basket-design-1d20ae03bf89) for key considerations
* Find collateral plugins in the [deployer UI](https://app.reserve.org/deploy/yield-dtf) or [write your own](/core-components/yield-dtfs/deployment-guide/yield-dtf-deployment-walkthrough.md#appendix)
* Specify emergency backup assets in case of default
  {% endstep %}

{% step %}

### Target yield

What are the yield targets (if any) for your DTF?

* Consider risk/reward trade-offs and the DTF's target market
* Check out [DefiLlama](https://defillama.com/yields) for inspiration and market rates
* Fork [this spreadsheet](https://docs.google.com/spreadsheets/d/1nipH_G0lKQeaXItatDeAGju-4smkYeaIpUl3Pxnz3iU/edit) to model blended APY and revenue share
  {% endstep %}

{% step %}

### Revenue split

What share goes to holders, RSR stakers, and other addresses?

* **DTF holders**: incentivize minting and holding as a savings vehicle
* **RSR stakers**: incentivize decentralized governance and overcollateralization
* **Other addresses**: fund marketing, liquidity, research, DAO management, etc.
  {% endstep %}

{% step %}

### Branding

What is the name, ticker, and one-line marketing hook for your DTF?

* Use unique & memorable branding to convey the DTF's unique features
* Keep the ticker short & avoid overlap with other major assets
  {% endstep %}

{% step %}

### Mandate

What will the DTF's mandate be?

* The mandate is a 256‑character compass for governance
* Specify the DTF's goals, constraints, and priorities
  {% endstep %}
  {% endstepper %}

If you’re unsure how to answer any or all of these questions, the Reserve community is welcoming and willing to help! [Jump in the Reserve Telegram channel here.](https://t.me/reservecurrency)

## Pre-launch checklist

Before deployment, make sure each of the following has been specified:

* ✅ Deployment network (Ethereum / Base / Arbitrum)
* ✅ Primary & backup collateral baskets
* ✅ Revenue split (DTF holders / RSR stakers / others)
* ✅ Name, ticker, & mandate
* ✅ DTF parameters (use presets or tweak [advanced parameters](/core-components/yield-dtfs/deployment-guide/advanced-parameters.md))

Once each has been chosen, the Yield DTF is ready for launch.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.reserve.org/core-components/yield-dtfs/deployment-guide/designing-your-yield-dtf.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.