> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/hyperchains/hyperchains-bridge.md).
# Hyperchains Bridge
## Hyperchains Bridge for Developers
The Hyperchains Bridge provides a complete development solution for enabling secure token transfers between æternity and Hyperchain networks. Built with TypeScript, Bun.js, and Sophia smart contracts, it includes pre-deployed contracts, deployment scripts, API endpoints, and a monitoring backend that automatically tracks cross-chain transactions.
Developers can easily deploy bridge contracts to custom Hyperchains, integrate the bridge API into their applications, and leverage smart contract interfaces for seamless asset transfers. The architecture supports both mainnet and testnet environments, with built-in indexing and PostgreSQL storage for transaction tracking.
The bridge enables developers to build scalable applications requiring asset mobility between æternity's main chain and specialized Hyperchains, with comprehensive tooling for testing, deployment, and integration workflows.
### Quick Start
Deploy bridge contracts for custom Hyperchains using the included deployment scripts, integrate the bridge API into applications, and leverage provided smart contract interfaces for seamless cross-chain functionality. Complete documentation and deployment guides are available in the Hyperchains developer documentation.
---
# 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.aeternity.com/hyperchains/hyperchains-bridge.md?ask=&goal=
```
`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.