> For the complete documentation index, see [llms.txt](https://docs.unirouter.io/dataroom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unirouter.io/dataroom/background-why-unirouter/why-is-unirouter-needed.md).

# Why is UniRouter needed?

`UniRouter makes Bitcoin greater as ever. A boost-up of asset liquidity and use cases.` 

As Bitcoin ecosystem involves with fast user acquisition, we have found out some pain-points holding back the development. 

**I. Assets insufficient of liquidity.** 

Inscriptions assets on both BRC20 and ARC20 lack in trading liquidity as the current marketplaces for such assets are unable to offer the depth and trading experience. Bitcoin inscription assets need better liquidity in order to onboard more users and grow into a much bigger ecosystem. 

**II. A Broader World is yet to Exploit**

Strong as the Bitcoin ecosystem is, while there are still a broader world that it needs to exploit and expand more. EVM chains comparably have a larger ecosystem as of now and will continue to be so in a foreseeable future. The access to EVM ecosystems is essential for fast and sustainable growth of the Bitcoin ecosystem. 

**III. Use Cases are more needed**

For an ecosystem to enjoy continuous growth, use cases are essential. Applications affiliated are the gateway for users who maintain the sound engagement and contributions. FOMO sentiment can boost up the fast growth in the short run, while in the long run, applications and use cases are the key to huge success. 

`UniRouter goes beyond Bitcoin & EVM bridge`

By offering a secure and reliable cross-chain bridge solution, connecting the Bitcoin Inscription Assets to EVM ecosystems, bridging Atomicals and Ordinals to EVM will be the first stage that UniRouter builds. Besides cross-chain asset transfers, data communications will also be enabled. More use cases will be brought into Bitcoin ecosystem. 


---

# 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://docs.unirouter.io/dataroom/background-why-unirouter/why-is-unirouter-needed.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.