> 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/4.-wallet-and-network-access.md).

# 4. Wallet and Network Access

Interacting with the FreCx blockchain requires a wallet, which acts as the primary interface between the user and the network. A wallet is not merely a storage mechanism for tokens, but a cryptographic identity layer that enables users to authenticate transactions, deploy smart contracts, and interact with decentralized applications.

For developers and users who are new to blockchain systems, it is important to understand that a wallet does not hold funds in a traditional sense. Instead, it manages a pair of cryptographic keys:

* a public address, which is used to receive assets and interact with applications
* a private key, which is used to authorize transactions and must remain strictly confidential

Every interaction with the FreCx network whether deploying a contract, sending tokens, or calling a function  is executed through this wallet interface.


---

# 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/4.-wallet-and-network-access.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.