> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/anchors/anchor-types/asset-movement/ethereum-vm-anchors.md).

# Ethereum VM Anchors

Ethereum VM (EVM) based Asset Movement Anchors enable transfers between Keeta and EVM-compatible blockchain networks like Ethereum, Base etc.

### **What's Unique About EVM Anchors**

EVM Anchors have special characteristics:

1. **Smart Contract Integration**: Uses smart contracts for secure custody and forwarding
2. **Multi-Chain Support**: Works across all EVM-compatible chains using the same interface
3. **Gas Management**: Handles gas fees transparently
4. **ERC-20 Tokens**: Supports any ERC-20 token with contract address
5. **Native Asset Support**: Can handle ETH, USDC, EURC, etc.

#### **EVM-Specific Rails**

* **EVM\_SEND**: Standard token transfers (like sending ETH or ERC-20)
* **EVM\_CALL**: Smart contract calls for more complex operations

#### **Example: Moving USDC from Keeta to Base**

{% @github-files/github-code-block url="<https://github.com/KeetaNetwork/keetanet-examples/blob/main/src/anchor/asset-movement-evm-inbound.ts>" %}

#### **Example: Moving USDC from Base to Keeta using Persistent Addresses**

{% @github-files/github-code-block url="<https://github.com/KeetaNetwork/keetanet-examples/blob/main/src/anchor/asset-movement-persistent-address.ts>" %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeta.com/anchors/anchor-types/asset-movement/ethereum-vm-anchors.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 `build a script that syncs our docs to a CMS` 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.