> For the complete documentation index, see [llms.txt](https://docs.harmony.one/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.one/home/developers/deploying-on-harmony/truffle/deploying-an-ethereum-smart-contract-onto-harmony.md).

# Demo: Deploying an Ethereum Smart Contract on Harmony

Since Harmony is fully EVM-compatible (Ethereum Virtual Machine), it makes it really easy to port existing contracts to Harmony. Here's a short demo on how to port an existing Ethereum smart contract to the Harmony testnet:

{% embed url="<https://www.youtube.com/watch?v=HeJZwDa4a3A&feature=youtu.be>" %}

If you have an idea that you'd like to deploy on the Harmony Protocol, you might be interested in learning about the [Harmony Grant Program](https://docs.harmony.one/home/developers/grant-proposals).


---

# 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://docs.harmony.one/home/developers/deploying-on-harmony/truffle/deploying-an-ethereum-smart-contract-onto-harmony.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.