Kaspire

The Kaspa wallet that makes no compromises. First wallet with encrypted deeplinks, passphrases, Argon2id backups, and support for all L1 assets, including KCC20

[Kaspire @kaspirewallet]

@CryptoEndeavr Hey! Kaspire is a HUB21 development. We have been around the Kaspa space since 2 years now, started with simple Telegram bots and later on expanded further with bigger builds. You can checkout our track record here: https://t.co/BT2Q11T35F

[Kaspire @kaspirewallet]

We are excited to announce the peak of Kaspa wallets finally arrived: Kaspire Wallet, a covenant-ready, fully open-source and secure Kaspa wallet built without compromises.

Designed from the ground up for security and usability, Kaspire gives you complete control over your assets while supporting everything the Kaspa ecosystem has to offer. Kaspire is the first covenant-ready Kaspa wallet to support all L1 assets, encrypted WalletConnect v2 (which leading crypto wallets like MetaMask utilize) for mobile and desktop (for the app), BIP39 passphrases and Argon2id-encryption for industry-leading protection of your wallet data. The entire project is open source because in crypto, trust should always be earned through verification, not promises.

Kaspire is available as an Android app and as a browser extension for Chrome and Chromium-based browsers.

Kaspire in the Chrome extension store: https://t.co/gi4LSKITIS

Kaspire APK for Android: https://t.co/zR9gjhx7wt

GitHub: https://t.co/tNyIQqvGYl

Security deepdive: https://t.co/9wkjb0obTm

***
Roadmap: During our beta test we collected feedback and advanced Kaspire Wallet even further to deliver the best wallet for the best crypto. In an upcoming update we will add Kasplex and Igra L2 support. Android app store release is on the pipeline. In the meantime you can already download and install the APK from our website. Apple iOS support depanding on demand.
***

A quick deepdive into Kaspire:

Privacy and usability
Kaspire includes:
- optional balance hiding
- a main-screen privacy toggle
- configurable fiat currencies
- configurable automatic locking
- an address book
- recipient allowlisting
- a list of the user’s own wallets when choosing recipients
- UTXO count and consolidation
- editable wallet and contact names
- multiple visual themes
- built-in QR scanning
- flashlight controls for QR scanners
- detailed network diagnostics
- dApp session management
- in-app update notifications

The interface is designed to make advanced Kaspa functionality understandable without hiding critical security information.

Fully open source
Kaspire is fully open source because trust in cryptocurrency software should be earned through verification, not promises.

Users and developers can inspect:
- wallet derivation
- entropy generation
- native Rust signing
- transaction policies
- covenant validation
- backup encryption
- Android integration
- WalletConnect handling
- extension-provider methods
- build and release metadata

One wallet for the complete Kaspa L1 ecosystem. Kaspire supports:
- KAS
- KRC20 tokens
- KRC721 NFTs
- KNS domains
- Legacy KCC20 covenant tokens
- KRON-native KCC20 tokens
- PSKT flows
- Direct browser dApp connections
- Encrypted WalletConnect v2 connections for mobile and desktop

Kaspire for Android
The Android application offers a complete native mobile-wallet experience, including encrypted WalletConnect sessions. Mobile websites can open Kaspire directly through verified Android App Links. Desktop dApps can display a Kaspire-specific WalletConnect QR code, which users scan from inside the app. Every connection and signing request still requires explicit approval.

Kaspire Browser Extension
The browser extension provides the same wallet ecosystem through a traditional injected provider.
Websites can connect directly to the extension without WalletConnect, QR codes or relay infrastructure. Permissions are bound to the exact requesting web origin, and unknown or unauthorized methods are rejected.

Wallet creation and recovery
Kaspire supports:
- 12- and 24-word wallets
- Optional BIP39 passphrases
- Private-key imports
- Watch-only wallets
- Multiple independent wallets
- Multiple BIP44 accounts
- Address-index subwallets for Kasware-compatible wallet support
- Modern Kaspa derivation paths
- Legacy web wallet derivation paths

The wallet distinguishes correctly between separate BIP44 accounts and address-index subwallets.

Secure entropy generation
New wallets are generated using cryptographically secure operating-system randomness. Kaspire does not derive entropy from:
- timestamps
- device identifiers
- serial numbers
- application-level pseudo-random generators
- predictable hardware values

The resulting entropy is processed inside Kaspire’s Rust security core and converted into a checksum-protected BIP39 recovery phrase.

Native Rust security boundary
Kaspire is designed around a central rule: Network services may provide data, but they are never trusted to decide what the wallet signs.

Sensitive wallet and transaction operations are handled by a native Rust security core based on pinned Rusty Kaspa components.

The Flutter interface does not construct arbitrary signed transactions. Instead, it sends a typed request to the native core. The core reconstructs the transaction, validates it and produces a deterministic review containing the information the user is expected to approve.

Depending on the operation, this includes:
- sender
- recipient
- asset
- amount
- network fee
- inputs and outputs
- change
- transaction mass
- token operation
- covenant ID
- covenant template hash
- covenant inputs and outputs
- reserve top-up
- KAS held in token cells

The resulting review is cryptographically bound to the signing operation. If the transaction changes after review, the authorization no longer matches and signing fails.

Kaspire does not expose a generic unrestricted signing endpoint. Supported operations use typed policies for:
- KAS payments
- KRC20 transfers
- KRC721 transfers
- KNS transfers
- KCC20 covenant transfers
- KIP-5 personal messages
- reviewed PSKT transactions

Unknown operations and unsupported transaction structures fail closed. This makes Kaspire suitable for more advanced applications such as marketplaces, covenant vaults and other dApps without turning the wallet into a blind signer.

KCC20 and covenant security
Kaspire supports both legacy KCC20 assets and KRON-native covenant tokens. KCC20 signing requires complete cell information. Indexer data alone is not trusted. Before signing, Kaspire verifies the referenced covenant cells against its own Kaspa node.

Checks include:
- covenant identity
- unique transaction outpoints
- cell value
- token balance conservation
- script public key
- redeem script where required
- current UTXO existence
- current spendability
- ownership transition
- template requirements
- KAS reserve requirements

If an indexer reports an outdated cell that the node no longer considers spendable, Kaspire refuses to sign.

Kaspire validates network responses before using them for signing. The wallet checks:
- UTXO ownership
- duplicate outpoints
- malformed UTXOs
- impossible or negative values
- sender scripts
- recipient outputs
- change outputs
- fees
- transaction mass
- token quantities
- covenant transitions
- locally calculated transaction IDs

After signing, the locally calculated transaction ID is compared with the broadcaster’s response. A mismatching result is rejected. This security model helps protect users against outdated, defective or manipulated RPC and indexer responses.

Hardware-backed encrypted storage
On Android, secret wallet material is encrypted using AES-256-GCM with keys protected through Android Keystore. Where supported by the device, Kaspire can use hardware-backed storage or StrongBox. The application reports the available protection level instead of silently claiming hardware protection when the device cannot provide it. Sensitive material is kept behind the native Android and Rust boundary wherever possible.

Sensitive operations require fresh user authorization through:
- strong biometrics
- device credentials
- or a dedicated Kaspire PIN

Argon2id-encrypted backups
Kaspire backups use the versioned kaspire-backup-v2format. The backup password is processed using Argon2id v1.3 with:
- 32 MiB of memory
- three passes
- parallelism of one
- a random 32-byte salt
- a 256-bit derived key

The resulting key encrypts and authenticates the backup using AES-256-GCM.

Argon2id is memory-hard. Its iteration count should not be compared directly with PBKDF2 because every Argon2id pass processes the configured memory region.

Encrypted backups preserve the information required to restore registered wallets, accounts, subwallets and individual derivation paths.

Official website and documentation:
https://t.co/Sa4tLLYETA

Source code and release APKs:
https://t.co/tNyIQqvGYl

Official Telegram community for quick support: https://t.co/jSbnBXEHkJ

Your Kaspa universe. One secure wallet.

[Kaspire @kaspirewallet]

As Kaspire is free to use software without any income this depends on if we are able to gather funds for an independent audit. It's also worth to mention that no Kaspa wallet currently has any independent audit. Kastle, Kasware, Kaspium, Kurncy, Kasanova and Kaspa NG are all without any audit.

[Kaspire @kaspirewallet]

@KrexToken One of the legendary builders who are already integrating Kaspire ⚡

[Kaspire @kaspirewallet]

Kaspire Wallet further made big progress. We received awesome feedback during our beta test over at Telegram and evolved Kaspire even further based on the community wishes. The goal is simple: do not just make the best Kaspa wallet but even better than best.

Today we are announcing Kaspire will not just launch as a mobile app but also as a browser extension. Mostly the same features (encrypted WalletConnect v2 is only needed for mobile), same security.

Argon2id encryption for industry-leading protection of your wallet data. BIP39 passphrases. Every L1 asset. Covenant-ready. Open source. And more. The Kaspa wallet that makes no compromises. Your $KAS. Your control. Soon.

[Kaspire @kaspirewallet]

@PoppaSmurfRides @Hidalgo68 You can join our Telegram group to get earlier insights and links to release buids: https://t.co/qIeAjRFU5Z

[Kaspire @kaspirewallet]

@thekaspaonion Yes and no. Kaspire is covenant-ready but creating vaults is currently not enabled inside the app but via another HUB21 development from us that releases very soon as well. We might integrate it directly inside the app at some point.

[Kaspire @kaspirewallet]

Welcome to Kaspire ⚡

The Kaspa wallet that makes no compromises. Designed from the ground up for security and usability, Kaspire gives you complete control over your assets while supporting everything the Kaspa ecosystem has to offer.

Kaspire is the first mobile Kaspa wallet to support all L1 assets, including KCC20, encrypted WalletConnect v2 for mobile and desktop which leading crypto wallets like MetaMask use, BIP39 passphrases, covenant vault support, and Argon2id-encrypted backups for industry-leading protection of your wallet data.

With the encrypted WalletConnect v2 we also fix Kaspa's biggest flaw when it comes to wallets: most people use their phone today, not their PC. With Kaspire it's finally possible to do everything from your phone.

Kaspire is also the first Kaspa wallet with covenant support for KCC20 and vaults, enabling next-generation smart asset functionality.

The entire project is open source because in crypto, trust should always be earned through verification, not promises.

Built by trusted developers in the Kaspa space under the HUB21 brand. GitHub und public wallet release open this week.

[Kaspire @kaspirewallet]

@thePodKAS @KastleWallet @KaChat_ Yes. You can export any private key, no matter if main wallet or sub wallet. You can also use the Argon2id backups on any sub wallet.

[Kaspire @kaspirewallet]

@shimadonia Public GitHub und wallet release later this week