> For the complete documentation index, see [llms.txt](https://elysia.gitbook.io/elysia-whitepaper-v2-0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elysia.gitbook.io/elysia-whitepaper-v2-0/ecosystem/overview.md).

# Overview

![\[ELYSIA Protocol Ecosystem\]](/files/-MjFza4pkKqoX8AuvbMV)

The Elysia Protocol consists of four core components: issuance, distribution, liquidation, and price oracles. The technology and mechanism behind each component are open source and can be used to develop applications for other assets. For example,

1. A project may issue other real-world assets using the Onboarding Dapp 
2. Subsequently, the project may distribute asset tokens issued by using the protocol’s distribution components. This will allow other Defi services to create underlying assets.
3. If the distributed asset token is transferred to a third party for liquidation, it can be carried out through a Dapp on the liquidation core component.
4. Price information on real assets is reflected in the ELYSIA Protocol with price oracle core components, which are utilized by all other components. In addition, price matching derivatives Dapps can be developed using the oracle itself.

If a project is looking to issue bond-type tokens, they can work directly with the Elysia DAO for the following reasons: 

1. An asset token issuer (a collateral entity) can issue an asset token (an asset bond token) through the Onboarding Dapp.
2. ELYFI DAO can lend funds using the asset tokens as collateral.
3. If the asset token becomes insolvent, the liquidation process is carried out through the NPL Openmarket Dapp.


---

# 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://elysia.gitbook.io/elysia-whitepaper-v2-0/ecosystem/overview.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.