> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/empe-blockchain/overview/install-prebuild-binary.md).
# Install prebuild binary
> **CRITICAL NOTICE:** Snapshots and state sync require version 0.4.0. The v0.1.0 binary on this page does not support them.
>
> To run snapshots or state sync, follow the [Migration to v0.4.0 guide](/empe-blockchain/overview/migration-to-v0.4.0.md).
The emped binary serves as the node client and the application client. In other words, the emped binary can be used to both run a node and interact with it.
### Pre-Built Package
#### For Linux Distributions
Download the tar.gz file:
```
curl -LO https://github.com/empe-io/empe-chain-releases/raw/master/v0.1.0/emped_linux_amd64.tar.gz
```
Verify the checksum:
```
sha256sum emped_linux_amd64.tar.gz
```
You should see the following:
```
5353de7004bbacc516d6fc89d7bbcbde251fbba8c4bdccb2a58f8376e47ab753 emped_linux_amd64.tar.gz
```
Unpack the tar.gz file:
```
tar -xvf emped_linux_amd64.tar.gz
```
Move the binary to your local bin directory and make it executable:
```
mkdir -p ~/go/bin
sudo mv emped ~/go/bin
chmod u+x ~/go/bin/emped
```
Open a new terminal window and check if the installation was successful:
```
emped version
```
You should see the following:
```
v0.1.0
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.empe.io/empe-blockchain/overview/install-prebuild-binary.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.