Kaspa & Layer-2s
Kache is built around Kaspa and its growing layer-2 ecosystem. One wallet, one set of keys, every network.
The networks
| Network | Type | Native asset | Address format |
|---|---|---|---|
| Kaspa | Layer 1 (BlockDAG) | KAS | kaspa:… |
| Kasplex | zkEVM Layer 2 | wKAS | 0x… |
| Igra | EVM Layer 2 | iKAS | 0x… |
On Layer 1 you also hold KRC-20 tokens and KRC-721 NFTs. On the L2s you hold the wrapped native asset plus any ERC-20 tokens.
One address per layer
- Your Kaspa (L1) address begins with
kaspa:. - Your EVM address is a single
0x…address, shared across Kasplex and Igra (they use the same coin type), just like MetaMask and other EVM wallets.
Because the two L2s share one 0x address, an asset you receive on Kasplex and one on Igra both land at the same
address, just on different chains. Always confirm the network, not just the address.
Derivation paths
Kache derives your keys from your recovery phrase using standard BIP-44 paths, so the same phrase restores the same addresses in any compatible wallet:
| Layer | Path | Coin type |
|---|---|---|
| Kaspa (L1) | m/44'/111111'/0'/0/i | 111111 |
| EVM (Kasplex / Igra) | m/44'/60'/0'/0/i | 60 |
The EVM path uses coin type 60, the standard Ethereum coin type, which is why one 0x address works across every
EVM chain. The index i increases for each additional receive address.
Moving between layers
Use Bridging to move value between Kaspa and its L2s, and Swapping to trade tokens on an L2.
Testnet
Kache supports testnet-10 for development and testing. Switch networks from the settings menu.