> For the complete documentation index, see [llms.txt](https://docs.seismic.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seismic.systems/clients/alloy/guides.md).

# Guides

Step-by-step guides for common workflows

Comprehensive guides for working with the Seismic Alloy (Rust) SDK.

## Available Guides

### [Shielded Write](https://docs.seismic.systems/clients/alloy/guides/shielded-write.md)

Complete guide to sending shielded transactions with encrypted calldata. Covers:

* Setting up a signed provider
* Defining contract interfaces with the `sol!` macro
* Encoding calldata and building transactions
* Auto-encryption for functions with shielded parameters, and `.seismic()` for others
* Sending and confirming transactions
* Security parameters and expiration windows

### [Signed Reads](https://docs.seismic.systems/clients/alloy/guides/signed-reads.md)

Guide to executing signed reads (encrypted `eth_call`). Covers:

* Why signed reads exist and when you need them
* Using `seismic_call()` for encrypted requests and responses
* Decoding decrypted return data
* Comparison with transparent reads

## Quick Navigation

| Topic                     | Description                                      | Guide                                                                                 |
| ------------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------- |
| **Shielded Transactions** | Send encrypted writes to modify on-chain state   | [Shielded Write](https://docs.seismic.systems/clients/alloy/guides/shielded-write.md) |
| **Signed Reads**          | Execute encrypted `eth_call` with identity proof | [Signed Reads](https://docs.seismic.systems/clients/alloy/guides/signed-reads.md)     |

## Related Documentation

* [Contract Interaction](https://docs.seismic.systems/clients/alloy/contract-interaction.md) - Shielded and transparent call patterns
* [Examples](https://docs.seismic.systems/clients/alloy/examples.md) - Runnable code examples
* [Provider](https://docs.seismic.systems/clients/alloy/provider.md) - Provider setup and configuration
* [Installation](https://docs.seismic.systems/clients/alloy/installation.md) - Cargo setup and dependencies


---

# 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.seismic.systems/clients/alloy/guides.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.
