# Intro to AppChain

{% hint style="danger" %}
**Note:** The Immu3 Testnet AppChain was deployed to support the Tanssi LFD campaign. It will be decommissioned by the end of September 2024.
{% endhint %}

### Let's Start

Immu3 AppChain was built on the Tansii AppChain infrastructure protocol. It inherits block finality (consensus) from Polkadot RelayChain. Consequently, it acts as a Layer 1 blockchain like Moonbeam, not Layer 2 solutions on top of another Layer 1. It is a public EVM smart contract platform that offers reliability, scalability and security needed within use cases of on-chain communication. 

{% hint style="success" %}
**Explainer:** Built on the Rust-based Substrate framework, [Tanssi](https://www.tanssi.network/) offers high performance, flexibility, and rapid deployment via its library of pre-built pallets. Substrate's modular structure eases appchain creation and deployment.
{% endhint %}

### Baseline EVM (i.e. Ethereum Virtual Machine) Template <a href="#baseline-evm-template" id="baseline-evm-template"></a>

Extending the *Baseline AppChain template*, this template provides not only Immu3 AppChain support but also an EVM and full Ethereum compatibility. It enables an Ethereum compatibility layer for Immu3 ContainerChain to allow running unmodified Ethereum dApps while using tools and infrastructure like MetaMask out of the box.

### Features

* Transaction execution reliability
* Robust security and decentralisation inherited from Polkadot RelayChain
* Congestion resistant
* On-chain communication-specific
* Native apps: BlockCommunicator, W3XShare, PX Storage NFTs and PX Drive

### Resources

{% embed url="<https://chainlist.org/chain/3100>" %}


---

# 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://wiki.immu3.io/immu3-appchain/intro-to-appchain.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.