> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/16.-best-practices-security-and-production-readiness/16.2-key-management-and-wallet-security.md).

# 16.2 Key Management and Wallet Security

Private keys represent full control over assets and contract interactions. Improper handling of keys can lead to irreversible loss of funds.

Developers must never expose private keys in client-side code or public repositories. All sensitive operations should be performed in secure environments, such as backend services or hardware-secured systems.

For production systems, it is recommended to use:

* hardware wallets or secure key vaults
* environment-based key management systems
* multi-signature wallets for critical operations

Access to keys should be strictly controlled, and all transactions should be logged and monitored.


---

# 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.frequencychain.org/16.-best-practices-security-and-production-readiness/16.2-key-management-and-wallet-security.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.