# Ecosystem

### Compatible with Ethereum tools

Since Zeltra is an EVM, all existing tools in the Ethereum ecosystem work natively with the network without any modifications required.

| Tool      | Category    | Status       |
| --------- | ----------- | ------------ |
| MetaMask  | Wallet      | ✅ Compatible |
| Hardhat   | Development | ✅ Compatible |
| Foundry   | Development | ✅ Compatible |
| Remix IDE | Deployment  | ✅ Compatible |
| Ethers.js | Integration | ✅ Compatible |
| Web3.js   | Integration | ✅ Compatible |
| The Graph | Indexing    | ✅ Compatible |

### Network connection

To connect any EVM-compatible tool to the Zeltra network:

| Setting      | Value  |
| ------------ | ------ |
| Network name | Zeltra |
| ChainId      | 271017 |
| Symbol       | ZLA    |
| RPC URL      |        |
| Explore      |        |

### Smart contracts

Any contract written in Solidity for Ethereum can be deployed on Zeltra without modification. EVM opcodes are fully supported.

This means that the ERC-20 and ERC-721 standards, as well as all existing DeFi primitives, are immediately available on Zeltra.

### Target applications

Zeltra can host any type of decentralized application:

* **DeFi**: decentralized exchanges, lending protocols, stablecoins
* **NFTs**: creation, exchange, and management of digital assets
* **Payments**: integration of ZLA payments on third-party platforms
* **Identity**: on-chain identity and reputation management
* **Governance**: decentralized voting and decision-making systems

{% hint style="success" %}
If you've already deployed it on Ethereum, you can deploy it on Zeltra. Same code. Same tools.
{% endhint %}


---

# Agent Instructions: 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://zeltra.gitbook.io/zeltra-docs/basics/ecosystem.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.