# Kaspa Networks Integration

### 🌐 Kaspa Network Integration

#### Overview

[Kastle](https://kastle.cc/) supports multiple networks within the **Kaspa ecosystem**, including both **Layer 1** and **Layer 2**.

This allows users to interact with a variety of assets — from native $KAS, KRC tokens to EVM-based assets (ERC20, ERC721) — all within one wallet.

This section provides an overview of the networks currently supported in Kastle and explains how to switch between mainnet and testnet environments.

***

#### 🧱 Kaspa Layer 1

The **Kaspa Layer 1 (L1)** network is the core blockchain that powers all native transactions and on-chain data.

* **Mainnet:** The live network where $KAS, **KRC-20**, **KRC-721**, and **KNS** assets exist.
* **TN10 Testnet:** A public test network where users and developers can experiment with Kaspa transactions, token minting, and name services without using real $KAS.

> KRC-based assets are built on Kasplex’s **data insertion protocol** and indexed by third-party APIs that Kastle monitors for display.

***

#### ⚙️ Kasplex Layer 2 (EVM-Based)

**Kasplex L2** extends the Kaspa ecosystem with **EVM compatibility**, supporting assets and dApps built using Ethereum standards.\
Kastle currently supports:

* **Kasplex L2 Mainnet** – For real EVM-based tokens and smart contract interactions (ERC-20, ERC-721).
* **Kasplex L2 Testnet** – For developers to test EVM-based integrations before deploying to mainnet.

This means you can interact with familiar **EVM-style dApps and tokens** directly from your Kastle wallet while benefiting from Kaspa’s high-speed, PoW-secured foundation.

***

#### 🔧 Igra Layer 2 (EVM-Based)

**Igra** is an experimental **Layer-2 protocol** being developed on top of Kaspa. Its objective is to combine **Bitcoin-grade Proof-of-Work security** with the **programmability of modern virtual machines**.

The project explores how Kaspa’s BlockDAG architecture can be used to support **EVM-based smart contracts** with **high throughput** and **low latency**, while maintaining strong decentralization and MEV resistance.

Kastle currently supports the **Igra Testnet**, **Caravel**, allowing developers to experiment with its early implementation and test EVM-compatible transactions before mainnet release.

***

#### 🔁 Switching Between Networks

Switching between supported networks in Kastle is simple:

1. Open your **Kastle wallet**.
2. Tap on the ⚙️ icon.
3. Tap or click the **Network** selector.
4. Choose your desired network (mainnet or testnet).

<div align="center"><figure><img src="/files/C8oKiiTM3RNiLu0tjOcF" alt="Screenshot of Kastle switch network setting Page" width="375"><figcaption></figcaption></figure></div>

**Kastle automatically handles all the different mainnet and testnet**, you won't need to deal with switching between L1 and L2 and so on.

If you connect to a dApp that operates on a different network, Kastle will automatically prompt you to switch.

***

#### 🧠 Tip

When using any **testnet**, remember that tokens there have **no real value** — they’re for experimentation and development purposes only.

***

#### ✅ Summary of Supported Networks

| Layer  | Network     | Supported Environments | Supported Assets           |
| ------ | ----------- | ---------------------- | -------------------------- |
| **L1** | **Kaspa**   | Mainnet + TN10 Testnet | $KAS, KRC-20, KRC-721, KNS |
| **L2** | **Kasplex** | Mainnet + Testnet      | ERC-20, ERC-721            |
| **L2** | **Igra**    | Testnet                | ERC-20, ERC-721            |

***

As the Kaspa ecosystem continues to evolve, Kastle will expand support for additional networks and Layer-2 integrations, ensuring a seamless experience across all Kaspa environments.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kastle.cc/kastle-wallet-help-center/advanced-features/kaspa-networks-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.