Akash Wallet: How to Store, Send and Stake AKT Securely
Updated , 8 minute read
An Akash wallet controls an akash1 address that holds AKT, the token behind Akash Network's decentralized cloud marketplace, and lets you stake it with validators. Keylo generates it on your own device and never sees the keys, and from there you can send, receive and stake AKT. Staked AKT takes 21 days to unbond, so keep what you may need soon unstaked, and always use the memo exchanges give you.
Akash at a glance
- Address format
- Bech32, starts with akash1
- Derivation path
- m/44'/118'/0'/0/0
- Chain ID
- akashnet-2
- Unbonding period
- 21 days
- Active validator cap
- 100 validators
- Smallest unit
- 1 uakt = 0.000001 AKT
On this page
What is Akash Network and what is AKT used for?
Akash Network is a decentralized marketplace for cloud computing. People who need servers, from simple web apps to GPU clusters for AI work, describe what they want, and independent providers around the world bid to host it. The winning bid becomes a lease, paid from an on-chain escrow while the workload runs. The idea is to make spare data-center capacity rentable without a single company in the middle.
The marketplace runs on its own Cosmos SDK blockchain, secured by proof of stake. AKT is that chain's native token: validators and delegators stake it to secure the network, holders vote on governance proposals that set marketplace rules, and it pays transaction fees. Akash connects to other Cosmos chains over IBC.
Most AKT holders never deploy a workload themselves. They hold AKT, stake it to earn rewards and take part in governance through their validator. That is the part Keylo covers: holding, sending and receiving AKT with memos, and staking it with Akash validators from your browser.
Your akash1 address
Your Akash address begins with akash1 and is bech32 encoded, so a mistyped character makes it invalid instead of sending AKT to a stranger. It comes from the path m/44'/118'/0'/0/0, which Keplr and Leap also use for Akash, so an imported phrase shows the same address and any delegations already attached to it.
The underlying key is shared with your other coin type 118 addresses in Keylo, such as cosmos1 on the Cosmos Hub. Each prefix is a separate account on a separate chain, though. Native AKT only lives at your akash1 address, and that is the address to give anyone who is paying you in AKT.
Akash's deployment tools also use akash1 addresses to record who owns a deployment and who pays for it. If you ever fund a workload, the tenant address those tools show is an akash1 address too, which makes it easy to confirm you are sending AKT to the right place before you approve anything.
How to create an Akash wallet with Keylo
Nobody at Keylo can see the phrase, so nobody at Keylo can recover it. If you forget your password and have no phrase backup, the wallet cannot be restored, and that includes any AKT you have staked. Take the two minutes to write the words down before you deposit anything significant.
- 1
Go to Keylo registration in any modern browser on your phone or computer.
- 2
Enter a name, email, phone number and password, then click the link in the confirmation email.
- 3
Your browser generates a 12-word recovery phrase and seals it with encryption derived from your password, so Keylo only ever holds the sealed copy.
- 4
Find Akash in your asset list; the akash1 address there carries the network label.
- 5
Back up the phrase from Settings after re-entering your password. Paper, kept offline, is best.
How to receive AKT
AKT can also exist as an IBC token on other Cosmos chains, such as Osmosis, where it shows up under an ibc/ denomination at your address on that chain. Only native AKT on Akash can be staked with Akash validators, so if staking is your plan, withdraw on the Akash network itself.
- 1
Open AKT and tap Receive.
- 2
Copy the akash1 address or display its QR code.
- 3
Ask the sender or exchange to withdraw on the Akash network.
- 4
Look for the transfer in Activity. It normally confirms within seconds and links to Mintscan.
How to send AKT
Akash blocks are final as soon as they are committed, so a transfer cannot be undone once it lands. Exchanges usually take AKT deposits on a shared address and identify customers by memo; skip the memo and your AKT reaches the exchange but not your exchange balance until support finds it. Between personal wallets, no memo is needed.
- 1
Tap Send on AKT.
- 2
Add the recipient by pasting an akash1 address or scanning a QR code; anything with the wrong prefix is refused.
- 3
For an exchange deposit, copy the exchange's memo into the Memo field.
- 4
Type an amount or press Max.
- 5
Read the summary of recipient, memo, amount and fee, then approve it; signing happens locally on your device.
Akash fees explained
Akash uses the standard Cosmos fee model. Each transaction sets a gas limit and pays that limit multiplied by a gas price in uakt, where 1 AKT is 1,000,000 uakt. Transfers, delegations and reward claims each use a modest amount of gas, so their fees are small fractions of an AKT. Gas that a transaction does not use is not refunded, so wallets aim for accurate estimates. If a transaction ever fails with an out-of-gas error, the fee is still charged, because validators did the work up to that point; retrying with a slightly higher limit usually fixes it.
Workload payments are separate from transaction fees. When someone deploys on Akash, the lease is funded from an escrow deposit and paid to the provider over time, under the marketplace's rules. As a wallet user sending or staking AKT, you only pay the network fee shown in Keylo's summary, and Keylo adds no fee to normal sends.
How to stake AKT
Delegation keeps your AKT in your own account, bonded to the validator's stake. The validator cannot spend it, and only you can sign to change it. Akash currently allows up to 100 active validators, ranked by stake. A validator outside that set, or one that is jailed, earns no rewards for its delegators, so check its status on Mintscan before you delegate and again from time to time.
Because governance shapes the marketplace, your validator's votes matter more than on many chains. Delegators inherit their validator's vote by default, so choosing one whose voting record you agree with is a reasonable part of the decision. Recent votes are visible on Mintscan, and they show whether a validator engages with marketplace proposals or simply abstains.
- 1
Open AKT and select its staking option.
- 2
Review the validators. Favour those with consistent uptime, reasonable commission and an active presence in Akash governance.
- 3
Delegate an amount, leaving some AKT liquid for fees.
- 4
Check the summary and confirm. Rewards start accruing immediately.
- 5
Use the same screen later to claim rewards, redelegate to another validator or undelegate.
The 21-day unbonding period and slashing
Undelegated AKT goes through a 21-day unbonding period. For those three weeks the tokens sit idle, earning nothing, unable to move and still exposed to slashing for anything its validator did while you were bonded. When the period ends, it returns to your balance on its own. If you might need the funds sooner, keep that part unstaked from the start.
Redelegation is the exception: moving stake to another validator is instant, though redelegated AKT cannot be redelegated again for 21 days. Under current parameters, a validator caught double-signing loses 5% of its stake and one that misses too many blocks loses 0.01% and is jailed, with delegators sharing the loss. Splitting stake across a few validators reduces the damage any single one can do.
Moving AKT and paying for deployments
There are no swaps or bridges for Akash inside Keylo, so AKT stays on the Akash chain while it is in Keylo. To exchange it, send it to an exchange that supports Akash deposits, with the memo, and trade there. To rent compute, use Akash's own deployment tools; Keylo is a wallet for holding, sending and staking, not a deployment console. The chains page lists the other networks Keylo supports.
If you want AKT on Osmosis to trade it there, that is an IBC transfer, handled by Osmosis's own app or another IBC-capable interface. Once it arrives, the IBC version appears in Keylo as a token under Osmosis rather than under Akash, and it has to come back over IBC before it can be staked.
Akash safety tips
- Be sceptical of anyone offering cheap GPU access or AKT bonuses in return for your recovery phrase or a test payment.
- Ignore unexpected IBC tokens that appear in your balance with website names attached.
- Include the exchange memo with every AKT deposit and double-check it before confirming.
- Keep some unstaked AKT for fees, so you can always claim or undelegate.
- Enable two-factor authentication and an anti-phishing code; Keylo security explains how.
- Real Keylo support never asks for your password or phrase.
Frequently asked questions
How long does it take to unstake AKT?
21 days. After you undelegate, the AKT stays in unbonding for 21 days without earning rewards and cannot be transferred. Once the period ends, the AKT becomes spendable again without any action from you. If you just want a different validator, redelegate instead, which moves your stake immediately.
Can I deploy workloads on Akash from Keylo?
No. Keylo is a wallet: you can hold, send and receive AKT with memos, and stake it with validators. Creating deployments, bidding and managing leases is done with Akash's own tools. You can fund those tools by sending AKT from Keylo to the address they use.
Is my akash1 address the same as my cosmos1 address?
Both come from one key on coin type 118, so the bytes behind them match, yet each prefix marks a distinct account on its own chain with its own balance. AKT sent on Akash only appears at your akash1 address. Always copy the address from the Akash entry in Keylo.
What does it cost to send or stake AKT?
A small network fee, usually a tiny fraction of an AKT, calculated from the gas the transaction uses and the gas price in uakt. Keylo shows the exact fee in the summary before you confirm, and it adds no fee of its own to sends, delegations or reward claims.
Why are my AKT staking rewards not increasing?
The most common reason is that your validator is jailed or has dropped out of the active set of 100. Only active validators earn rewards. Check its status on Mintscan, and if it is inactive, redelegate to an active validator; redelegation is instant and does not require unbonding.