> For the complete documentation index, see [llms.txt](https://docs.portaldefi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.portaldefi.com/network-overview/portal-network.md).
# Portal Network
The Portal Network consists of swap clients and PortalOS nodes running to make the cross-chain ADMM a reality. A core enabler for multi-blockchain interoperability is exchanging assets held by mutually untrusting owners on different ledgers atomically. Since the Portal Network is non-custodial, assets are held on the native chains (like Ethereum and Bitcoin). However, the accounting occurs on a State Chain (Notary Chain), enabling highly customized AMMs on each chain.
The main components of the network are AMMs designed on each chain. Since EVM chains are Turing Complete, this involves developing smart contracts similar to Uniswap on these networks. On Bitcoin, Portal leverages a secure and highly decentralized AMM built using a multi-party HTLC. This eliminates some centralization in other protocols that manage shared key wallets. To facilitate swaps and ensure transactions are processed promptly and appropriately, a set of validators controls the transaction flow. These validators track balances across chains, process events, and execute instructions. They maintain the Notary layer, which tracks transactions and the flow of funds.
---
# 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.portaldefi.com/network-overview/portal-network.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.