# xOrbit

The are multiple yield protocols and yield optimisers in the space that facilitate cross-chain interaction through using a decentralised stablecoin, not dissimilar to aUSDC. The challenge is that for cross-chain deposits and withdrawals on these external chains these protocols tend to rely on liquidity pools for swapping. This leads to slippage, the need to bootstrap multiple liquidity pools and less optimal integrations for end users. \
\
xOrbit challenges this, it is the architecture responsible for native cross-chain deposits into Orbit savings vault. We understood that to be able to maximise liquidity and participation in the early stages, both the ability to deposit into Orbit natively and integrate with various DeFi protocols on chains like Solana and EVM chains would be key.\
\
Rather than forcing users to gain access to Orbits yield through swapping into aUSDC in liquidity pool, we designed xOrbit to manage native cross-chain deposits and withdrawals without swapping.

This means composable aUSDC on multiple chains, while still maintaining accessibiliy the the main vault. 

## **How it works** 

The initial function for xOrbit is the the deployment of Orbit Earn in a cross-chain way. Users connect natively from a foreign connected chain and deposit their USDC into the vault.

This USDC is then bridged to the hub chain through hooks and the equivalent aUSDC bridged back to the user, due to the speed of IBC, this is likely to only be a short delay, depending on the finality of the connected chain. 

A router will be added to ensure that users can swap from other stablecoins and variationsof USDC when interacting with Orbit. 

<figure><img src="/files/XSCtYLim7xt0C2hI8Jho" alt=""><figcaption></figcaption></figure>

Streaming will also be made to work in a cross-chain compatible way as the second phase of xOrbit.&#x20;


---

# 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://orbit-16.gitbook.io/orbit-docs/xorbit.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.