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

# Introduction to Wallets

Introduction to wallets on Arweave

### What is a wallet for blockchains?

A wallet on a blockchain is a device, program or service that stores public and private keys which in turn enable transactions with the blockchain.

The public key can be thought of as the username and the private key is like a password that must be kept safe at all times.

Any change to the state of the blockchain (information stored on chain) is considered a transaction and requires a wallet to complete.

### Wallets on Arweave

Arweave is a blockchain-like system that focuses on permanent and decentralised low-cost storage solutions. It can be thought of as a blockchain database.

All kinds of data like images, videos, documents, JSON objects, even web applications, among other types, can be stored on Arweave.

For uploading this data on Arweave we need a wallet. Additionally, a wallet is needed for interacting with applications that rely on Arweave.

### Wallets from a development perspective

As developers, we need to handle wallets for various uses right from providing users the ability to create transactions using these wallets on Arweave to interacting with other applications built on Arweave.

### Libraries used

The functions associated with wallets leverage the following libraries:

* [Arweave JS](https://github.com/ArweaveTeam/arweave-js)

### Wallet based functions

In this section, we will look at the following functions:

* creating a new wallet
* getting a wallet address using the private key
* getting the balance of a wallet address

###


---

# 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.arweavekit.com/wallets/introduction.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.