> 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/python/api-reference/types/private-key.md).

# PrivateKey

32-byte secp256k1 private key

32-byte secp256k1 private key used for transaction signing and ECDH key derivation.

## Definition

```python
class PrivateKey(Bytes32):
    @staticmethod
    def from_hex_str(hex_string: str) -> PrivateKey:
        ...
```

## Construction

| Parameter | Type                  | Required | Description                       |
| --------- | --------------------- | -------- | --------------------------------- |
| `val`     | `bytes \| str \| int` | Yes      | Hex string, raw bytes, or integer |

Raises `ValueError` if length is not exactly 32 bytes.

## Methods

### from\_hex\_str()

Create a `PrivateKey` from a hex string, with or without `0x` prefix. Shorthand for `PrivateKey(hex_to_bytes(hex_string))`.

```python
@staticmethod
def from_hex_str(hex_string: str) -> PrivateKey
```

## Example

```python
import os
from seismic_web3 import PrivateKey

pk = PrivateKey.from_hex_str(os.environ["PRIVATE_KEY"])
```

## Notes

* Subclass of [`Bytes32`](/clients/python/api-reference/types/bytes32.md) — inherits immutability, hashability, `.to_0x_hex()`
* Compatible with `eth_keys.PrivateKey` via `eth_keys.PrivateKey(bytes(pk))`
* No validation on mathematical validity (i.e., no check that `0 < key < n`)

## See Also

* [Bytes32](/clients/python/api-reference/types/bytes32.md) — parent type
* [CompressedPublicKey](/clients/python/api-reference/types/compressed-public-key.md) — corresponding public key type
* [hex\_to\_bytes](/clients/python/api-reference/types/hex-to-bytes.md) — general-purpose hex decoding
* [sign\_seismic\_tx\_eip712](/clients/python/api-reference/eip712/sign-seismic-tx-eip712.md) — sign transactions with private key


---

# 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/python/api-reference/types/private-key.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.