Documentation

Installation, wallet basics, network context, releases, verification, and safety.

Getting started

Kaspa Wallet is a desktop self-custody wallet for Kaspa. Your first priorities are simple: obtain the software from the project source, protect recovery material, and understand that network transactions can be irreversible.

Never share

Seed phrases, recovery words, private keys, passwords, or wallet files should never be sent through forms, email, social messages, or support chats.

Installation

  • Choose the build intended for macOS, Windows, or Linux.
  • Read release notes before installing, especially for pre-release software.
  • Verify signatures or checksums when they are provided.
  • Do not use downloads from unverified mirrors or direct-message links.

Download for macOS · Download for Windows · Download for Linux

Wallet basics

Send

Confirm the destination address and amount before broadcasting a transaction. For important transfers, verify the receiving address through a second trusted channel when possible.

Receive

Use the receiving address generated or shown by your wallet. Check the address carefully before sharing it.

Activity

The activity view helps you read recent wallet movement. For independent confirmation, inspect the transaction on a Kaspa block explorer.

Accounts

Accounts help separate wallet context. Keep clear records of which account is intended for which purpose.

Network context

Kaspa uses Proof of Work with kHeavyHash and a BlockDAG structure. The network launched on November 7, 2021 without a premine or pre-allocation. Its ticker is KAS and maximum supply is approximately 28.7 billion KAS.

The wallet is an interface to that public network. A local display can help you understand activity, but the network record is the independent reference for transaction verification.

Read the Kaspa Wiki ↗

Releases & verification

Release quality and signing status can vary. Before relying on a new build, inspect its release notes, source context, and any published verification information.

  • Prefer stable releases for routine use when available.
  • Treat pre-release software as testing software.
  • Unsigned software requires additional caution.
  • Verify important transactions with an independent explorer.

Safety

  • Keep recovery material offline.
  • Do not paste recovery words into websites or support chats.
  • Keep backups separate from the everyday device.
  • Verify addresses before sending.
  • Review the transaction on an explorer when independent confirmation matters.
  • Do not assume a person contacting you is a contributor or support representative.

Troubleshooting

A transaction is not visible yet

Check connectivity, then verify the transaction or address in the Kaspa explorer. Distinguish between a wallet display issue and the state recorded by the network.

A build behaves unexpectedly

Review the release notes and repository issues. Do not expose recovery material while asking for help.

You are unsure about a download

Do not run it. Return to the official repository, compare the release information, and verify any signatures or checksums that are provided.