> For the complete documentation index, see [llms.txt](https://gitbook.mor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.mor.org/mrc/closed/mrc19.md).

# MRC 19: Cosmos & Thorchain Expansion of Morpheus

***

## Status:

**April 1st, 2024: PENDING**

**Comments:**\
Technical dependencies on Thorchain upgrade

***

## History

The original Morpheus whitepaper proposed using Thorchain yield as the means for Capital Providers to contribute to Morpheus.

## Tech Problem

While the Smart Contracts were in development the open source devs notes that there was a feature missing from Thorchain that would make this possible.

## Dependency

This missing feature is support for multi-outputs from yield generated from a Thorchain Saver. Currently when a Thorchain Saver vault is set up the yield can only be returned to the same address as the that contributed the crypto to the Saver Vault.

## Solution

When Thorchain adds support for Multiple addresses to be rewarded yield, then the Morpheus Capital Provider can be extended to Thorchain yield types.

## Value

This would be a substaintial upgrade as Thorchain create sustainable native yield in BTC, ETH, AVAX, USDT, BCH, USDC, BNB, LTC, DOGE & ATOM. This represents yield from many of the most active chains and would add a great deal of the most active crypto communities to the ranks of Morpheus Capital Providers.

## Link to Source of Yield Available

<https://thorchain.net/thorfi/savers>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.mor.org/mrc/closed/mrc19.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
