# Our Contracts

Our contracts allows users to execute onchain actions by sending funds to an address or ENS name.

### Benefits

* **Removes Phishing Risk:** Users can use our contracts directly in their wallets instead of User Interfaces (UIs) to perform onchain actions. This removes the risk of phishing scams, which are most prevalent on the UI side.
* **Increases Efficiency:** Our contracts combine multiple actions into one, which is simply sending ETH to an address or ENS domain. This saves the user time and helps them capture market opportunities in an instant.
* **Mobile Friendly:** Using multiple UIs on mobile is a nightmare. Our contracts are easy to use on mobile.
* **No Geofencing:** There is no UI, therefore a user can use any protocol in any country.

<div align="center" data-full-width="true"><figure><img src="/files/TLNJTB7Rh8FJQCHUAffX" alt="" width="563"><figcaption></figcaption></figure></div>

### Acceptable Assets

| Input Token | Accepted      |
| ----------- | ------------- |
| **ETH**     | ✅             |
| **USDC**    | Coming soon.. |

### Types of Contracts

* **Bridge** - Bridge ETH from one network to another.
* **Swap** - Swap ETH into another token.
* **Bridge + Swap** - Send ETH from one network to another. Once the ETH arrives to the desired network it is then instantly swapped into another token.
* **Bridge + Pool** - Send ETH from one network to another. Once the ETH arrives to the desired network it is then instantly deposited into a liquidity pool.
* **Stake** - Deposits ETH into liquidity pools.
* **Deposit (AAVE) -** Deposits ETH sent as collateral on your AAVE vault.
* **Bundle -** Swaps ETH sent proportionally into a basket of tokens.


---

# 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://docs.onthis.xyz/overview/users/our-contracts.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.