# Zeknd Superchain

Amidst the evolving blockchain landscape, scalability remains a crucial hurdle. Introducing opZEKND, a revolutionary Layer 2 scaling solution that addresses the limitations of Layer 1 networks. With its robust EVM-compatible platform, opZEKND empowers developers to build open ecosystems, migrate applications to Zeknd Superchain, and extend their user reach.

<figure><img src="/files/2wSOyzqbbJdo26JVYV0U" alt=""><figcaption></figcaption></figure>

**Zeknd Network** operates on several networks each operating with their own independent validators and unique state. These networks are as follows:

* [`mainnet`](https://docs.near.org/concepts/basics/networks#mainnet)
* [`testnet`](https://docs.near.org/concepts/basics/networks#testnet)
* [`betanet`](https://docs.near.org/concepts/basics/networks#betanet)
* [`localnet`](https://docs.near.org/concepts/basics/networks#localnet)

### Mainnet[​](https://docs.near.org/concepts/basics/networks#mainnet) <a href="#mainnet" id="mainnet"></a>

`mainnet` is for production-ready smart contracts and live token transfers. Contracts ready for `mainnet` should have gone through rigorous testing and independent security reviews if necessary. `mainnet` is the only network where state is guaranteed to persist over time *(subject to the typical security guarantees of the network's validation process)*.

* Name: Zeknd Superchain
* RPC: <https://dataseed.opzeknd.xyz>
* Chain ID: 6289
* Block Explore: <http://explorer.opzeknd.xyz>

### Testnet[​](https://docs.near.org/concepts/basics/networks#testnet) <a href="#testnet" id="testnet"></a>

`testnet` is a public network and the final testing network for `zekndnetwork` changes before deployment to `mainnet`. `testnet` is intended for testing all aspects of the Zeknd Network platform prior to `mainnet` deployment. From account creation, mock token transfers, development tooling, and smart contract development, the `testnet` environment closely resembles `mainnet` behavior. All `zekndnetwork` changes are deployed as release candidates on first testnet, before the changes are released on `mainnet`. A number of `testnet` validators validate transactions and create new blocks. dApp developers deploy their applications on `testnet` before deploying on `mainnet`. It is important to note that `testnet` has its own transactions and states.

* Name: Zeknd Superchain ( Testnet)
* RPC: <https://testnet-dataseed.opzeknd.xyz/>
* Chain ID: 6162
* Block Explore: <https://testnet-explorer.opzeknd.xyz/>

### Betanet[​](https://docs.near.org/concepts/basics/networks#betanet) <a href="#betanet" id="betanet"></a>

`betanet` is a public network, where `zekndsuperchain` is run to test its stability and backward compatibility. Validators on `betanet` are participants in the Betanet Analysis Group, where they engage in active discussions, submit bug reports, and participate in issue resolution. On `betanet`  changes, there are automated hard forks, where the state is compressed into a new genesis. As such, new genesis exists frequently on `betanet`, and there are no historical data snapshots. `betanet` usually has daily releases with protocol features that are not yet stabilized. State is maintained as much as possible but there is no guarantees with its high volatility.

### Localnet[​](https://docs.near.org/concepts/basics/networks#localnet) <a href="#localnet" id="localnet"></a>

`localnet` is intended for developers who want to work with the Zeknd Superchain platform independent of the public blockchain. You will need to generate nodes yourself. `localnet` gives you total control over accounts, economics, and other factors for more advanced use cases (including making changes to `zekndnetwork`). For developers, `localnet` is the right choice if you prefer to avoid leaking information about your work during the development process.


---

# 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://documentation.opzeknd.xyz/on-chain/zeknd-superchain.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.