> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/blockchain/build/web3-development.md).

# Web3 Development

Welcome to the **Web3 Developer Guide** for IoTeX!

The IoTeX Blockchain is fully compatible with the Ethereum RPC API and the Ethereum Virtual Machine (EVM). This guide is designed to help Web3 developers seamlessly transition to IoTeX development and leverage the powerful features of the IoTeX blockchain.

{% hint style="info" %}
IoTeX compatibility with the Ethereum RPC API means that you can use familiar tools like [Web3.js](https://web3js.org/), [Ethers.js](https://ethers.org/), and [Hardhat](https://hardhat.com) to interact with the IoTeX chain. 
{% endhint %}

By supporting the latest EVM, IoTeX ensures that your Solidity smart contracts will run without modification, enabling you to port existing applications and develop new ones with ease.

{% hint style="info" %}
IoTeX currently supports the **Shangai** EVM release and the **Solidity** compiler **0.8.20**
{% endhint %}

This document will guide you through the necessary steps to get started, including setting up your development environment, deploying smart contracts, and connecting to IoTeX using popular Ethereum tools. 

Let's dive in and explore the possibilities of building on IoTeX!


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.iotex.io/blockchain/build/web3-development.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.