> For the complete documentation index, see [llms.txt](https://docs.sia.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sia.tech/legacy/your-sia-wallet/for-advanced-users/verify-the-sia-release-signature.md).

# Verify the Sia release signature

All Sia release binaries are signed, which allows you to confirm that the version you've downloaded is indeed the exact version that we've released. This is an extra security check to ensure you're using legit, unmodified software, which can be pretty important when the app also handles money like Siacoins.

{% hint style="info" %}
These instructions are also available on the [official downloads page](https://sia.tech/get-started), just under the download links.
{% endhint %}

You can download the signing key [here](https://sia.tech/releases/sia-signing-key.asc), and the signed hashes for the current release [here](https://sia.tech/releases/Sia-v1.5.0-SHA256SUMS.txt.asc).

1. Download and import the Sia signing key. `wget -c https://sia.tech/releases/sia-signing-key.asc` `gpg --import sia-signing-key.asc`
2. Download the signed hash file, and verify the signature. `wget -c https://sia.tech/releases/Sia-v1.5.0-SHA256SUMS.txt.asc` `gpg --verify Sia-v1.5.0-SHA256SUMS.txt.asc`
3. If you downloaded a zip file, unzip that first. `unzip Sia-v1.5.0-linux-amd64.zip`
4. Check that the files you downloaded were signed. `sha256sum --check --ignore-missing Sia-v1.5.0-SHA256SUMS.txt.asc`

You should see "OK" next to the files you did download and errors for the files you have not downloaded.


---

# 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.sia.tech/legacy/your-sia-wallet/for-advanced-users/verify-the-sia-release-signature.md?ask=<question>&goal=<user_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.