> For the complete documentation index, see [llms.txt](https://docs.69.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.69.finance/introduction.md).

# Introduction

As the blockchain ecosystem rapidly evolves, the crypto world is no longer centered around a single network. Each blockchain — such as Ethereum, Arbitrum, Optimism, Base, and various Layer2 solutions — offers unique technical advantages and active communities. However, this diversity also brings a major challenge: assets and liquidity are fragmented across different networks that cannot communicate directly with one another.

In this context, *cross-chain bridges* have become a fundamental component of the Web3 ecosystem. Bridges enable users to transfer assets seamlessly across chains, connecting previously isolated environments. Without such interoperability, the growth and innovation of DeFi, NFTs, and decentralized applications (dApps) would remain confined within individual ecosystems.

69 Finance aims to solve this fragmentation by building a secure, efficient, and user-friendly cross-chain bridge — empowering users to move assets freely and experience a truly connected blockchain 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:

```
GET https://docs.69.finance/introduction.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.
