A Kaspa address starts with the prefix kaspa: followed by a character string such as kaspa:qr0โฆ โ the prefix is part of the address and should be copied with it. You find it on the Receive screen of Kaspa NG, Kaspium, KasWare or another Kaspa wallet. Kaspa needs no memo, and the same address can receive repeatedly; some wallets show a fresh address for each receive, all belonging to the same wallet.
Anatomy of a Kaspa address
Kaspa uses a Bech32-style encoding with the network as a human-readable prefix: kaspa: on mainnet, kaspatest: on testnet. The first character after the colon indicates the type: q for the standard Schnorr public-key addresses most wallets create, p for script-hash addresses. A checksum protects against typos. Wallets and exchanges that strip the prefix usually add it back, but pasting the full string avoids surprises.
Where to find it
- Kaspa NG (desktop and web, maintained by the Kaspa community): open the account and the receive section; the address is shown with a QR code.
- Kaspium (mobile): tap Receive; the app shows the address and QR, with an option to share.
- KasWare (browser extension): the address is under the account name; KasWare also handles KRC-20 tokens.
- Hardware wallets: Tangem cards support Kaspa directly; Ledger devices are used through the community KasVault interface. Verify the address on the device when offered.
Kaspa wallets use BIP39-style recovery phrases (12 or 24 words), but derivation paths differ between some older and newer wallets. If a restored wallet shows an empty balance, try another wallet or derivation option before assuming the funds are gone.
Why deposits wait for 1,000 confirmations
Kaspa is a proof-of-work blockDAG: many blocks are created in parallel and ordered by the GHOSTDAG protocol. Since the Crescendo hard fork in 2025 the network produces about 10 blocks per second. A "confirmation" therefore means much less time than on Bitcoin, and services ask for many of them. The liquidity provider's list for KAS shows 1,000 confirmations for deposits โ roughly 100 seconds at 10 blocks per second, plus processing.
Why very small transfers fail
Kaspa limits how much storage a transaction may consume relative to the value it moves (the "storage mass" rule introduced with KIP-9). In practice, sending tiny outputs โ fractions of a KAS โ or splitting into many small outputs can make a transaction too heavy to be accepted, and wallets show a mass or fee error. Send larger amounts, or consolidate many small UTXOs first; wallets such as Kaspa NG handle consolidation automatically when needed.
Selling or buying KAS
KAS is supported on KOT.CASH through the liquidity provider. Minimums depend on network costs: on 21 October 2026 the minimum for KAS to USDT TRC20 was about 802 KAS, while buying KAS with USDC needed at least about 30 USDC. For a KAS payout paste your full kaspa: address; for a KAS deposit, send from your wallet to the address on the order page โ no memo. Compare confirmation times on other networks with the deposit confirmations lookup or estimate any network's wait with the confirmation time estimator.
Checking a transaction
Kaspa explorers show a transaction by its ID together with the accepting block and the number of confirmations ("blue score" difference). If an exchange or swap has not credited your deposit yet, look the transaction up: when it is accepted and the confirmation count is rising, the deposit is simply waiting for the required depth.
FAQ
Do I need to include kaspa: when I paste the address?
Yes, copy the full address with the prefix. Most services accept it with the prefix and some require it.
Does Kaspa need a memo?
No. Kaspa deposits are identified by address alone.
Why does my KAS deposit need 1,000 confirmations?
Kaspa produces about 10 blocks per second, so 1,000 confirmations take only about 100 seconds.
Why did my small KAS transfer fail?
Kaspa's storage mass rule makes very small outputs too expensive to include. Send a larger amount or consolidate UTXOs.
Can I use my Kaspa phrase in another wallet?
Usually, but derivation paths differ between some wallets. Check that the first address matches after restoring.