> For the complete documentation index, see [llms.txt](https://lita.gitbook.io/lita-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lita.gitbook.io/lita-documentation/advanced-usage/using-the-rust-toolchain.md).

# Using the Rust Toolchain

For basic instructions on using the Rust to Valida compiler toolchain, see [QUICK START: Valida Compiler Toolchain](/lita-documentation/quick-start/valida-compiler-toolchain.md). This page covers more advanced usage instructions for the Rust to Valida toolchain.

## Keccak acceleration

The Valida VM has the capability of accelerated Keccak hash proving. To use this capability in Rust, you can simply import `sha3::Keccak256` and use the Keccak hasher in the `sha3` crate in the usual way. The `keccak-crate` example located at `/valida-toolchain/examples/rust/keccak-crate` exemplifies this usage. You must use Lita's forked version of the Keccak crate, using a line in your `Cargo.toml` such as:

```
[dependencies]
sha3 = { git = "https://github.com/lita-xyz/hashes", default-features = false }
```


---

# 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://lita.gitbook.io/lita-documentation/advanced-usage/using-the-rust-toolchain.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.