> For the complete documentation index, see [llms.txt](https://docs.esprezzo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esprezzo.io/smart-contract-activity/add-smart-contracts.md).

# Add smart contracts

Whether you want to stream data for specific contract events and functions to your apps, or use smart contract event emissions and function calls to trigger alerts and automated workflows, you'll need to add the contracts to Dispatch.

There are 2 ways to add smart contracts to Dispatch:

1. Add contract during Patch creation ([Patch Builder](https://dispatch.esprezzo.io/patches/create))
2. Add contract on the [Contracts](https://dispatch.esprezzo.io/contracts/overview) page

{% hint style="info" %}
Currently Dispatch supports smart contracts on Ethereum, Polygon, Arbitrum One, Base, and Optimism.

Request support for other networks [here](https://info.esprezzo.io/dispatch-network-request).
{% endhint %}

See how to add contracts during Patch creation in the [contract activity monitor example](/introduction/contract-activity-monitor-example.md#step-2-set-the-trigger-conditions).

## Adding a smart contract from the Contracts page

Navigate to the [Contracts](https://dispatch.esprezzo.io/contracts/overview) page.

Click the "Add contract" button:

<figure><img src="/files/P98NzhWlwQd4tLK5KiRH" alt=""><figcaption></figcaption></figure>

In the modal, add the

1. **Network**: the network that the smart contract is on
2. **Contract address**: the address of the smart contract you want alerts/automations from
3. **Contract nickname**: an easy-to-remember, descriptive name for the contract that will distinguish it from other contracts you might add later

Click the "Add contract" button.

### Adding unverified contracts

If the contract you want to monitor is unverified, there are a few extra steps.

Namely, you'll need to provide the [contract ABI](https://dev.to/sadiqful/understanding-smart-contract-abi-31km) in JSON format.

<figure><img src="/files/GeDeprNddMz9QLwQbJcZ" alt="How to add an unverified contract to Dispatch so you can get alerts from it" width="563"><figcaption></figcaption></figure>

#### Proxy contracts

If the contract you're adding is a proxy, Dispatch provides the option to add the associated implementation contract at the same time, so you can monitor activity in both the proxy and implementation contracts.

To monitor activity in both the proxy and implementation contracts, you'll need to provide the ABIs for both contracts.

<figure><img src="/files/qO3iqi6Mmr4q9Z3ODu0i" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
At this time Dispatch does not auto-update monitoring of new implementation contracts when proxy contracts are updated with new implementation contract addresses.
{% endhint %}

Once you add a contract, you should see it in the top row of the table in [Contracts Overview](https://dispatch.esprezzo.io/contracts/overview).


---

# 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.esprezzo.io/smart-contract-activity/add-smart-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.
