> For the complete documentation index, see [llms.txt](https://archive-ko.docs.klaytn.foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archive-ko.docs.klaytn.foundation/misc/klaytn2/ethereum-compatibility.md).

# 이더리움 호환성

## 이더리움 동일성을 지원합니다

![](/files/NI4ESFC3NGamC3UaxsYI)

### 1. 개발 도구 <a href="#finality-and-improvements" id="finality-and-improvements"></a>

클레이튼 기술 스택의 인터페이스와 실행 방식을 이더리움과 호환시킴으로써, 이더리움에서 동작하는 도구라면 클레이튼 생태계에서도 문제없이 동작힐 수 있습니다. New tooling created in the Klaytn ecosystem could be reciprocally adopted within the Ethereum ecosystem.

### 2. EVM과 API <a href="#evm-and-api" id="evm-and-api"></a>

기존 이더리움 스택을 이용함으로써 EVM과 라이브러리 오픈소스 코드 베이스에 추가된 모든 개선 사항들을 상속합니다. 클레이튼 EVM 환경과 동일한 옵코드와 스택 로직을 지원함으로써 실행 동작도 호환됩니다. 또한 동일한 엔드포인트 페이로드 구문을 지닌 JSON-RPC API를 지원하여 완전한 이더리움 인터페이스 호환성이 보장됩니다.

### 3. 코어 개발 기여 <a href="#core-development-contribution" id="core-development-contribution"></a>

이더리움 동일성을 지원함으로써 클레이튼과 이더리움 생태계 간 호혜적 관계가 가능해집니다. The majority of Ethereum Improvement Proposals (EIPs) could be migrated and adopted to the Klaytn core development agenda, and in turn Klaytn Improvement Proposals (KIPs) could contribute to the advancement of Ethereum and EVM. When the development community contributes to one ecosystem, they are indeed contributing to both.


---

# 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:

```
GET https://archive-ko.docs.klaytn.foundation/misc/klaytn2/ethereum-compatibility.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.