> For the complete documentation index, see [llms.txt](https://qualitax.gitbook.io/interop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qualitax.gitbook.io/interop/solutions-providers/datachain.md).

# Datachain

## 1. Problems/Challenges it aims to solve

***

## 2. Solutions

***

Cross-chain digital securities settlement with Stablecoin using IBC and LCP

**Cross Framework:** Cross is a framework that enables distributed transactions over multiple blockchains. It is implemented as Cosmos module.

IBC Module for Hyperledger Fabric IBC Module for Hyperledger Besu IBC Module for Corda

## 3. Target Customers

***

**Traditional backends/Institutional players:** That wish to interact with various blockchain networks without building separate in-house solutions for each interaction. 

**dApp developers:** To leverage cross-chain functionalities and create dApps with enhanced features and services. 

**Web3 entrepreneurs**: Looking to securely meet all their cross-chain needs.

## 4. Key Points <a href="#id-4.-key-points" id="id-4.-key-points"></a>

***

## 5. People

***

## 6. Resources

***

{% embed url="<https://www.datachain.jp/>" %}


---

# 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://qualitax.gitbook.io/interop/solutions-providers/datachain.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.