> 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/wallet.md).

# Wallet

The `SeismicWallet` is the signing component of `seismic-alloy`. It manages one or more private key signers and provides the `NetworkWallet` implementation that the provider's filler pipeline uses to sign transactions.

## Overview

In Alloy's architecture, a wallet is responsible for:

1. Holding one or more signers (private keys, hardware wallets, etc.)
2. Providing a default signer address for transactions that do not specify `from`
3. Signing transactions when the `WalletFiller` requests it

`SeismicWallet` extends this pattern for Seismic networks. It is generic over `N: SeismicNetwork`, meaning the same wallet type works with both `SeismicReth` (production) and `SeismicFoundry` (local development).

## Quick Start

```rust
use seismic_prelude::client::*;
use seismic_alloy_network::reth::SeismicReth;

// Create a wallet from a single private key
let signer: PrivateKeySigner = "0xYOUR_PRIVATE_KEY".parse()?;
let wallet = SeismicWallet::<SeismicReth>::from(signer);

// Use it to create a provider
let url = "https://testnet-1.seismictest.net/rpc".parse()?;
let provider = SeismicProviderBuilder::new()
    .wallet(wallet)
    .connect_http(url)
    .await?;
```

## Multi-Signer Support

`SeismicWallet` supports multiple signers. This is useful when your application needs to send transactions from different accounts:

```rust
use seismic_prelude::client::*;
use seismic_alloy_network::reth::SeismicReth;

let signer_a: PrivateKeySigner = "0xKEY_A".parse()?;
let signer_b: PrivateKeySigner = "0xKEY_B".parse()?;

// Create wallet with signer_a as default
let mut wallet = SeismicWallet::<SeismicReth>::new(signer_a);

// Register an additional signer
wallet.register_signer(signer_b);

// Or register and set as new default
// wallet.register_default_signer(signer_b);
```

## Pages

| Page                                                     | Description                                                 |
| -------------------------------------------------------- | ----------------------------------------------------------- |
| [SeismicWallet](/clients/alloy/wallet/seismic-wallet.md) | Full API reference with all methods, generics, and examples |

## See Also

* [SeismicSignedProvider](/clients/alloy/provider/seismic-signed-provider.md) - Provider that uses the wallet
* [Network Overview](/clients/alloy/network.md) - Network types the wallet is generic over
* [Fillers](/clients/alloy/fillers.md) - The filler pipeline that invokes wallet signing
* [Installation](/clients/alloy/installation.md) - Cargo setup and prerequisites


---

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