> For the complete documentation index, see [llms.txt](https://docs.switchboard.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.switchboard.xyz/how-it-works/technical-architecture/oracle-queues.md).

# Oracle Queues

An Oracle Queue (often just called a "Queue") is a core component of Switchboard, designed to manage and secure data feeds by creating a structured and secure environment that facilitates efficient management, isolation, and reliable data delivery.

Think of a Queue as:

* **A Dedicated Subnetwork of the larger Switchboard Protocol:** A whitelisted environment within the Switchboard protocol, controlling which software can be executed and which oracles are authorised to respond in its network.
* **An Oracle Registry:** A list of on-chain oracle accounts, each linked to a physical machine that fetches and publishes data.
* **A Security Boundary**: Oracles within a Queue must run verified code. This ensures that only trusted nodes contribute to the data feeds.
* **A Multi-Chain Entity**: Defined on Solana and synchronised across all Switchboard deployments on different blockchains.

Queues have an important key characteristic:

* Each data feed *must* belong to **one**, and only **one**, Queue.


---

# 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.switchboard.xyz/how-it-works/technical-architecture/oracle-queues.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.