# PortalOS: Overview
The Portal Network constitutes a collection of PortalOS nodes actively running and executing network-level protocols in a trustless manner. PortalOS acts as an operating system configured to run a set of services required to enable various functions in the Portal Network. In essence, PortalOS serves as a protocol that facilitates the coordination of activities across multiple blockchains. It ensures smooth communication of events between these chains, playing a crucial role in keeping the entire network operational and cohesive.
## Components
PortalOS consists of several components that collectively form the Portal Network. One of the main components of PortalOS is the Notary Chain built utilizing the EVMOS. The Network consists of validators called Portal Guardians, which serve as validators. A description of various components that form the PortalOS follows.
### Notary Chain
The Notary Chain serves as the core database for all activity occurring in the Portal Network protocol. This chain is designed to efficiently manage a substantial volume of cross-chain swap transactions. All protocol events are recorded and broadcast by the Notary Chain. This covers almost everything, including, but not limited to:
* Registering trading pairs
* Auctions for Validators
* Slashing management
* Tracking asset balances on liquidity pools
* Tracking contributions from LPs
* Consensus Validation
* Facilitating Native Protocol Swaps via the Automated Dynamic Market Maker
* Emission Management and Fee Collection
### Peer
* Peers manage native blockchains nodes necessary for network operation.
* Acts as a proxy agent for the end-user
* Relays a user’s orders to the Coordinator
* Manages atomic swaps
* Interfaces with one or more L1/L2 daemons, as needed
* Relays updates to the web and mobile clients
The schematic below shows how 2 Peers interact with the coordinator
### Coordinator
* A protocol designed to enable coordination between different blockchains.
* Maintains state level information and event passing between peers, clients etc.
### SDK
* A library that encapsulates all the common functionality to enable implementation of Portal cross-chain swaps. The Portal Swap SDK is built to empower other wallets, exchanges with the Portal's instant swaps.
* IOSClient, AndroidClient, and WebClient will import the Client library to implement their respective functionalities.
* May operate without a Peer, though Peer would remain relevant for Liquidity Providers and power-users.
### Client (App)
* A browser-based application hosted by the peer to enable the user to set up and operate the peer. This is accomplished by two separate applications:
* **The Portal Peer Setup Wizard**, used to set up the peer. This process involves configuring the Portal Peer to use new or existing L1/L2 network daemons, load and unload any credentials necessary for regular operation.
* **The Portal Peer App**, that may be used by the Peer operator to use the services provided by the Portal network, including:
* Trading assets
* Settling trades by atomically swapping the assets with the counterparty
* Interface for Liquidity Providers for staking and management
* Interface for Validators to participate in the Auction process and keygen ceremonies etc.
---
# 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://docs.portaldefi.com/portalos/portalos-overview.md?ask=
```
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.