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

# Getting started

This section will guide the reader to install, deploy, and interact with the Panacea blockchain.

### Table of contents <a href="#table-of-contents" id="table-of-contents"></a>

* **Installation**: Instructions on how to install *panacead*, the server daemon for nodes, the cli tool to interact with panacead.
* **How to Join the network**: Panacea is the first official public network running the Panacea Blockchain. This section outlines step by step instructions on how to start operating a node on Panacea.
* **How to deploy own Panacea testnet**: How to setup and deploy one's own testnet of the Panacea blockchain, in a single-node local, multi-node local, and remote network context.
* **Introduction to panacead**: Using the `panacead` to interact with the Panacea blockchain.
* **Clients**: How to spin up a light client daemon, that stores partial state and responds to REST API queries.
* **Use the Ledger Nano**: How to interact with the Panacea blockchain using the Ledger Nano S.


---

# 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.gopanacea.org/guide/getting-started.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.