# Orb Labs

## 1. Problems/Challenges it aims to solve

***

Multichain account fragmentation - assets that sit in users' accounts to be seamlessly accessed on another. Other main problems are data fragmentation (data from one chain to be accessed on/from another chain), and liquidity fragmentation (liquidity that sits on one chain be to be accessed on/from another chain).

architecture difference between cross-chain apps and single-chain apps makes their interop needs very different

Cross-chain apps primarily need solutions that address data and liquidity fragmentation, while single-chain apps need solutions that tackle account fragmentation.

## 2. Solutions

***

**Orb Stack:**  multi-chain  interop solution that specifically caters to the needs of single-chain apps, improving multi-chain UX. Orb Stack is a set of modular protocols that work together to enable users to issue cross-domain intents. It consists of 5 layers.

**Orby:** an intent engine which is embed into frontend of any application, enabling users from any chain to access the app. Embed into wallets, enabling users to interact with any app on any chain without fragmenting user accounts Orby takes in a multi-chain interaction and converts it into an intent that can be executed on any chain via the Orb Stack.

A layer between users and apps where funds can be swiftly and seamlessly moved between accounts to interact with apps without significant changes to the security of user accounts&#x20;

## 3. Target Customers

***

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

***

## 5. People

***

## 6. Resources

***


---

# Agent Instructions: 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:

```
GET https://qualitax.gitbook.io/interop/protocol-providers/orb-labs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
