> For the complete documentation index, see [llms.txt](https://learn.qanplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.qanplatform.com/technology/technology-features/ethereum-evm-compatibility.md).

# Ethereum EVM Compatibility

<figure><img src="/files/gpOVL2J1o5CdmGMadO8b" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
💡\[Definition] **Ethereum EVM**

The Ethereum Virtual Machine (EVM) is a computation engine that acts like a decentralized computer with millions of executable applications called smart contracts. It is part of the Ethereum blockchain on which smart contracts can be deployed and executed.
{% endhint %}

{% hint style="warning" %}
\[Market problem]: **Most of the new blockchains are not Ethereum EVM compatible**

Projects currently running on the Ethereum network can only leave Ethereum at significant compromises for a more reliable, cost-predictable, cost-efficient, and secure blockchain platform alternative, since they would need to rewrite all their smart contracts in a different programming language resulting in a re-audit requirement as well.&#x20;
{% endhint %}

## **QANplatform will be Ethereum EVM compatible**

The whole blockchain ecosystem owes a lot to the Ethereum team, as Ethereum was the first smart contract platform to run decentralized applications (DApps). As the smart contract pioneer, Ethereum took a market advantage which is still held, since most blockchain projects and solutions are running on Ethereum.

90% of current enterprise blockchain platform implementations will require replacement within 18 months to remain competitive, secure, and avoid obsolescence, according to [Gartner](https://www.gartner.com/en/newsroom/press-releases/2019-07-03-gartner-predicts-90--of-current-enterprise-blockchain). There are signs that projects are already leaving first-generation blockchain platforms are already visible. Many projects are realising that Ethereum Layer 2 solutions are not the cure to all problems. However projects currently running on the Ethereum network could only leave Ethereum at significant compromises for a more reliable, cost-predictable, cost-efficient, and secure blockchain platform alternative.&#x20;

### **Move your code from Ethereum to QANplatform**

Thanks to QANplatform’s Ethereum EVM (Ethereum Virtual Machine) compatibility, developers can write, deploy, and run smart contracts as they would on Ethereum, but on top of that they and their users can enjoy all the benefits of QANplatform, such as the [Quantum-resistant security](/technology/technology-features/quantum-resistant-security.md), Proof-of-Randomness (PoR) consensus mechanism, Multi-language smart contract development, Developer Royalty Fees, Low and predictable transaction costs fixed in USD — to name a few.&#x20;

{% hint style="success" %}
**Key Takeaways — \[Ethereum EVM Compatibility]:**&#x20;

* QANplatform is Ethereum EVM compatible blockchain.
* Projects currently running on the Ethereum network can move their operation to QANplatform.&#x20;
* Thanks to Ethereum EVM compatibility, the QANplatform can win market share from Ethereum.
* Also all tooling like wallets, SDKs, etc. people already use with Ethereum remain compatible not forcing users to leave their favored toolkit behind.&#x20;
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://learn.qanplatform.com/technology/technology-features/ethereum-evm-compatibility.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.