img width: 750px; iframe.movie width: 750px; height: 450px;

Kaia wallet extension setup and usage guide

Download the KASWARE build specifically for Chromium-based browsers. Navigate to the official repository page on the Chrome Web Store; avoid third-party mirrors offering modified builds. Click “Add to Chrome” and confirm the permission request for data exchange with *kaia*[dot]io. The small popup confirming installation appears in the upper-right corner of your browser window.

Upon first launch, you must select the preferred network environment. For testing tokens and contracts, choose the *Baobab* testnet option. For live asset management, select *Cypress* mainnet. The interface presents a dropdown menu with these two specific selections; there is no default. After choosing, immediately generate your 12-word recovery phrase. Write these words on paper with a pencil. Do not store them in a text file, screenshot, or cloud note service. The next screen will ask you to confirm a random sequence of three words from that phrase to verify you recorded them correctly.

Set your local access PIN, which is a four-to-six digit code required to unlock the interface each time you open it. This differs from your mnemonic phrase. The module will then display your public deposit address, a string starting with *0x*. Click the “Copy Address” icon next to it. Open a faucet interface for the network you selected (e.g., the official *Kaia* faucet for Baobab), paste that address, and request test funds. The first transaction should appear in the activity log within 30 seconds.

Kaia Wallet Extension Setup and Usage Guide

Download the official companion tool solely from the project’s GitHub repository or its listed Chrome Web Store page, not from random search ads. After installation, click the puzzle icon in your browser toolbar, pin the new icon, and select “Create a new vault.” Write down the 12-word recovery phrase on paper only–never screenshot it, store it in cloud notes, or type it into any website. Store this paper in a fireproof safe; losing it means permanent loss of all assets.

1. Funding Your Account
   Go to the “Receive” tab and copy the public address (a string starting with “0x”). Transfer native tokens from a centralized exchange or another self-custody tool to this address. Use a small test transaction first–send $1 worth to confirm the address works. Confirm the balance appears in the interface within 60 seconds; if it takes longer, check the block explorer using your address.

2. Executing a Transfer
   Click “Send,” paste the recipient’s public address, enter the amount in native tokens (not USD), and set the gas limit to 21000 for simple coin transfers. The system will auto-calculate the gas price, but you can increase the priority fee by 10% during network congestion. Double-check the last 4 characters of the address twice before confirming–malware often swaps clipboard data to a scam address.

3. Connecting to dApps
   Open a decentralized application (like a marketplace or lending platform) and click “Connect” or “Sign In.” Approve only read-request permissions initially–reject any popup asking for unlimited spending approval unless you explicitly trust the app. For NFTs or token swaps, approve each transaction individually; never use “Approve all” on unfamiliar sites.

4. Security and Recovery
   If you must log in on another device, enter your 12-word phrase directly into the tool’s import interface–ignore any other website that requests it. Enable “Show test networks” in settings only if you use a faucet for development. Disconnect idle sessions by clicking the tool icon, selecting “Connected sites,” and removing all unrecognized domains. Test your recovery phrase once a year by importing it into a temporary browser profile, then immediately delete that profile after verification.

Downloading the Official Kaia Wallet Extension from the Chrome Web Store

Only Install Kaia wallet on Chrome the browser tool from the official Chrome Web Store listing titled “Kaia” by “Kaia Blockchain”. Search directly in the Chrome Web Store; do not click sponsored ads or third-party download sites. The official publisher ID should be verified against the Kaia Foundation’s official website.

Before clicking “Add to Chrome”, verify the total user count and recent review dates. A legitimate listing will have thousands of users and consistent, recent updates. Check the “Developer” section for a verified email and website link matching kaia.io. If the listing lacks contact information or shows a suspicious domain, abort immediately.

The download process is identical to any other Chrome Web Store item: click the blue “Add to Chrome” button, then confirm the permissions prompt. The tool requests access to read and change data on specific websites–this is standard for interacting with dApps. Granting these permissions enables direct blockchain transactions without exposing your private keys to the page.

After installation, locate the hexagonal icon pinned to your browser toolbar or in the extensions menu. Right-click the symbol and select “Manage extension” to enable “Allow access to file URLs” if you plan to test local development sites. Disable the “Pin to toolbar” option if the icon clutters your interface; you can access it via the puzzle piece icon later.

Once added, the tool automatically generates a unique 12-word seed phrase–this is written exactly once. Write these words on paper, store them in a fireproof safe, and never photograph, screenshot, or save them digitally. Anyone holding this phrase controls all assets. The tool will not show the phrase again.

Finally, close all browser tabs that were open during installation. Reopen your browser and navigate to any supported dApp to trigger the connection prompt. If the icon remains grayed out or unresponsive, check Chrome’s extension manager for an “Errors” button under the listing; a red banner indicates a corruption or version mismatch that requires re-downloading the official package.

Creating a New Wallet and Securing Your Seed Phrase Offline

Begin the account creation process on the device you intend to use for transactions. The interface will present a randomly generated mnemonic phrase, typically 12 or 24 words. Do not take a screenshot, type it into any online document, or transmit it over a network. Write the sequence down exclusively on paper using a pen–this is the only non-digital record acceptable for security.

Each word in the mnemonic is drawn from a specific BIP39 standard list, placing the total entropy at 128 to 256 bits. The order of these terms is non-negotiable; a single misplacement renders the entire phrase invalid for recovery. Verify your handwriting immediately after writing them, checking for legibility, correct spelling, and sequential numbering. A missing article or a smudged character can lock you out permanently.

Store the written backup in a fireproof safe, ideally waterproof, buried or secured in a location separate from your computer. Do not laminate paper with heat, as it can degrade the ink over time. Use a metal stamping kit on a titanium or steel plate (e.g., Billfodl or Cryptosteel) for physical resilience against fire, flood, and physical impact. This elevates your redundancy beyond a simple slip of paper.

Generate a second, identical copy of the mnemonic on a different physical medium. Place this duplicate in a secondary secured location, such as a bank safety deposit box or a trusted family member’s lockbox. This mitigates the risk of a single point of failure, such as a house fire or a lost safe. The copies must be verified against each other for exactness before distribution.

Test the recovery procedure immediately after creating the account. Enter the seed phrase into the recovery interface of a clean, offline device to confirm full restoration of access. Do this before storing any significant value. This confirms your human transcription is correct and that the software interprets the words precisely as written. Failure at this stage means your backup is useless.

Never store the mnemonic digitally, in a password manager, on a cloud service, or in a photo. All digital storage mechanisms are vulnerable to malware, keyloggers, and remote access. The offline paper or metal copy is the only form that guarantees the cryptographic private keys remain air-gapped from any connecting network, preserving sovereign control over the assets.

Importing an Existing Wallet Using a Private Key or Mnemonic Phrase

Restore access to a self-custodial vault by using the 12 or 24-word mnemonic sequence directly. This method reconstructs the entire key hierarchy, granting full control over all derived addresses associated with that recovery phrase. For single-account imports, the private key–a 66-character hexadecimal string (0x + 64 hex digits)–is the faster, isolated option, but it does not recover linked token approvals or multi-chain configurations.

Open the interface and locate the “Import” or “Restore” option, typically found below the “Create New” selection. You must manually enter each word of the mnemonic exactly as generated, preserving the original order and case sensitivity. Any misplacement of a single term–like “abandon” instead of “abandon”–will generate a checksum error and prevent import. Use a hardware keyboard when possible to avoid autocorrect mistakes on mobile devices.

Private key import requires copying the full key, including the “0x” prefix, into the designated field. Do not share the screen or clipboard with untrusted apps during this operation. If the key originates from a hardware signer or a cold storage file, verify the character set matches the expected format (secp256k1 elliptical curve keys are standard). The system will reject keys with stray spaces, missing characters, or wrong encoding.

After submitting the credentials, the interface will scan the blockchain for transaction history and nonce data for the first 10 derived addresses by default. This scan may take 2–5 minutes depending on network latency. Do not close the tab or refresh during this process, as it can reset the derivation index and force a rescan. The application will display a balance snapshot once the scan completes.

Security practices before import:

Imported accounts will appear in the management list alongside any existing ones. You can rename each entry for clarity–for example, “Vault A” or “Old Ledger.” Note that importing a phrase with 24 words activates HD path m/44’/60’/0’/0/0 by default; software using a different derivation path (like m/44’/60’/0’/0/1 for a legacy contract) will not show the correct address. Check the derivation path in the advanced settings if the balance shows zero despite correct seed entry.

Cross-verify the first derived address against a block explorer before transferring funds. Use a read-only script or a second device to confirm the address matches the one shown in the interface. If the balance appears lower than expected, increment the derivation index manually (e.g., change account 0 to account 5) to reveal additional funded addresses. Do not rely solely on the automatic scan for assets held in deeply nested derivation indices.

Q&A: