# 1.2 Multi-Asset Blockchain

Token economies of blockchain projects are mostly comprised of Ethereum-based cryptocurrencies.  These cryptocurrencies serve as a transaction fee on the chain, and also as a vital part of Governance.  Other assets exist on ERC20 chains in different formats, and their usage varies as well. Orbit Chain allows all assets to exists on its chain in the same format, even the ones that exists in different forms outside of Orbit Chain.

Orbit Chain aims to work as a hub for various public blockchains, making possible fluid asset movement and interaction within a single blockchain network.  Every blockchain has a different set of constituents and protocols, such as UTXO and Balance-state. Connecting these blockchains together is no easy feat, but through Orbit Chain, all of these chains can be linked and utilized in the same fashion, with the same amount of liquidity.  To this purpose, Orbit Chain provides a system that will use a singular method of transaction to build DApps, which will then be able to use various assets in the same manner. In doing so, the previous liquidity problem of traditional blockchain systems is eliminated with the standardization of multi-asset usage.

Orbit will also include, in addition to cryptocurrencies, more traditional forms of assets within Orbit Chain.  This connection will be made in a different formats than cryptocurrencies, yet will still be connected to all in a similar fashion.


---

# 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-1.gitbook.io/orbitchainwhitepaper/1.-introduction/1.2-multi-asset-blockchain.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.