> For the complete documentation index, see [llms.txt](https://docs.kyberswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyberswap.com/reference/kyberswap-operator-multisig.md).

# KyberSwap Operator MultiSig

## Overview

To facilitate the smooth running of campaigns and liquidity mining programs, KyberSwap maintains an Operator MultiSig address. This address is managed by the KyberSwap Operations team and is only used to facilitate the transfer of funds related to KyberSwap's operations across the platform. The MultiSig address acts as both a safeguard against malicious actors as well as validation process against any possible input errors when funds are managed by a single actor.

The KyberSwap Operator MultiSig has been deployed at the same address across all chains that have or previously had active campaigns and liquidity mining programs. For your convenience, the full list of contracts can be found below:

<details open>

<summary>Ethereum (ChainID: 1)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://etherscan.io/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>BSC (ChainID: 56)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://bscscan.com/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Arbitrum (ChainID: 42161)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://arbiscan.io/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Polygon PoS (ChainID: 137)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://polygonscan.com/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Optimism (ChainID: 10)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://optimistic.etherscan.io/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Avalanche (ChainID: 43114)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://snowtrace.io/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Base (ChainID: 8453)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://basescan.org/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Linea (ChainID: 59144)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://lineascan.build/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Berachain (ChainID: 80094)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://berascan.com/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Sonic (ChainID: 146)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://sonicscan.org/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>HyperEVM (ChainID: 999)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://hyperevmscan.io/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Plasma (ChainID: 9745)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://plasmascan.to/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Monad (ChainID: 143)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://monadvision.com/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Unichain (ChainID: 130)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://unichain.blockscout.com/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>

<details open>

<summary>Robinhood (ChainID: 4663)</summary>

* **MultiSigWalletWithDailyLimit:** [`0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C`](https://robinhoodchain.blockscout.com/address/0xeB28e1C4c47b471a88B00bA93163a3a44AE65D9C)

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kyberswap.com/reference/kyberswap-operator-multisig.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 `automate deployments from our CI pipeline` 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.