> For the complete documentation index, see [llms.txt](https://doc.tryethernal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.tryethernal.com/dashboard-pages/contracts/import-mainnet-contracts.md).

# Importing mainnet contracts

{% hint style="warning" %}
This feature will only work on workspaces connected to a mainnet fork
{% endhint %}

![Importing and interacting with the mainnet Uniswap contract](/files/-MZm2sa7lcvkhgrpD8H3)

This feature lets you import mainnet contracts that have been verified on Etherscan, Polygonscan or Bscscan (depending on the chain set for the workspace). Once the contract has been imported, it will appear in your contracts list, you'll be able to see transactions sent to it on your fork, and to interact with all read & write methods.

To get started, go to the "Contracts" page, click on "Import Contract", enter the address, and click "Import". This will pull the name and the ABI from the explorer, and populate your contracts list.

Once this is done, go to the contract page, and from there you'll be able to see the list of transactions sent to this address on your fork, and, on the "Contract" tab, to interact with all the read & write methods.

{% hint style="info" %}
The "Storage" tab is not available yet for this feature, if you need it, you'll have to redeploy the contract with Truffle or Hardhat
{% endhint %}

{% hint style="info" %}
This feature is currently available for Ethereum, Polygon & BSC mainnet forks. If you'd like to request compatibility with other networks, please reach out to @antoinedc on Discord
{% endhint %}


---

# 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://doc.tryethernal.com/dashboard-pages/contracts/import-mainnet-contracts.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.