# Overview ## **TLDR:** Orbit protocol was designed to make depositing and withdrawing assets super easy and cross-chain compatible. The heavy lifting and complexity is abstracted from the front end and behind the scenes, leveraging powerful cross-chain yield optimiser that regularly rebalances and allocates funds across top DeFi and RWA yield sources. Yield streaming is layered on top to allow users to maximise their earning by automatically allocating their interest to assets they desire to accumulate, the protocol automatically swaps their earned interest every 8 hours as it comes in. ## Components of Orbit: The Orbit protocol is made up of various components, these include: * **The Earn Vault:** This is the interface for the savings vault that governs deposits and withdrawals. Users can deposit and withdraw without lockups, track their savings growth and claim their earned rewards. * **Yield-bearing aUSDC:** aUSDC is the receipt token received for depositing in the earn vault, it is abstracted from the front-end for a cleaner user experience. It appreciates as yield is generated and can be transferred cross-chain or used to redeem a position and its yield. * **The Yield Aggregator:** The yield aggregator/optimiser powers the yield in the earn vault, is allocates deposited funds to various cross-chain protocols and yield sources. It also monitors risk, yields, market conditions and regularly rebalances allocations to maximise earning and manage risk. * **Asset Streaming:** The asset or yield streaming function is a Orbit module that enables users to select assets they would like the accumulate with their earned yield. It then dollar-cost-averages into these assets on behalf of the user every 8 hours using their accumulated yield. * **xOrbit:** xOrbit is the front end instructure responsible for native cross-chain deposits and withdrawals into the earn vault. It enables users to access the vault without the need to manually bridge assets to a different network.
## Designed to be Cross-chain at Both Ends Orbit protocol is designed to be cross-chain on both ends of the protocol. As the space evolves, there is more fracturing of yields and also native userbases, so it's important to both give people the best of yields no matter the ecosystem, but also ensure that the user experience is natively accessible to users no matter their chain preference. This also opens up a wider range of potential integrations. \ Beyond the cross-chain element, Orbit aims to abstract much of the blockchain elements in the app from the users for a seamless experience. Orbit is built on top of the IBC v2 network which benefits from trustless bridging across Cosmos SDK chains and soon the expansion to EVM and Solana, this allows Orbits yield aggregator to access yields across every IBC connected chain without sacrificing security, and broader access to yields means greater returns on the savings vault. At the front end, native deposits and withdrawals is also enabled a across a wide range of IBC connected chains, this ensures deep integration into a wide range of DeFi ecosystems and userbases. Many yield protocols rely on yield-bearing stablecoins to support their cross-chain expansion but rely on liquidity pools for deposit and redemption, which are sub-optimal due to the need to bootstrap multiple liquidity pools and swap fees/slippage.
--- # 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/orbit-protocol/overview.md?ask= ``` 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.