> For the complete documentation index, see [llms.txt](https://kerneldao.gitbook.io/kernel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerneldao.gitbook.io/kernel/getting-started/kelp/smart-contracts/access-control-and-multisigs.md).

# Access Control & Multisigs

All authorities are Gnosis Safe multisigs. Every safe is staffed by team members or external signers, all signing with hardware wallets and operating under strict signer discipline — every transaction is checked through a thorough internal verification process and simulated (e.g. via Tenderly) before it is signed.

\
Ethereum Mainnet:

| Safe           | Address                                    | Threshold                        | Role                                        |
| -------------- | ------------------------------------------ | -------------------------------- | ------------------------------------------- |
| External Admin | 0xb3696a817D01C8623E66D156B6798291fa10a46d | 6-of-11 (incl. external signers) | Core DEFAULT\_ADMIN\_ROLE; recovery custody |
| Admin          | 0xb9577E83a6d9A6DE35047aa066E3758221FE0DA2 | 3-of-6                           | Owns the Admin-Safe ProxyAdmin              |
| Manager        | 0xCbcdd778AA25476F203814214dD3E9b9c46829A1 | 3-of-6                           | Day-to-day operations                       |
| Pauser         | 0xb6AbB489aCA4583833230F10B3A7670114D09559 | 1-of-5                           | Pause only (unpause needs admin)            |

\
 L2s: Each with 2 multisigs —  an Admin multisig (3-of-6) and the Pauser multisig (1-of-5):

| Network  | Admin multisig (3-of-6)                    | Pauser multisig (1-of-5)                   |
| -------- | ------------------------------------------ | ------------------------------------------ |
| Arbitrum | 0x96D97D66d4290C9182A09470a5775FF90DAf922c | 0xb6AbB489aCA4583833230F10B3A7670114D09559 |
| Base     | 0x7Da95539762Dd11005889F6B72a6674A4888B56d | 0xb6AbB489aCA4583833230F10B3A7670114D09559 |
| Linea    | 0xEe68dF9f661da6ED968Ea4cbF7EC68fcFE375bc6 | 0xb6AbB489aCA4583833230F10B3A7670114D09559 |
| Ink      | 0x7a1112494843d0228BFFBa13eF3Ce57f4c35a461 | 0xb6AbB489aCA4583833230F10B3A7670114D09559 |
| Mantle   | 0xfa3bA682f2210d05D087b331c71F5b34F16Cd3e9 | 0xb6AbB489aCA4583833230F10B3A7670114D09559 |

Note: The ProxyAdmins on Ethereum mainnet and L2s are owned by their timelocks, whose proposers are the respective admin multisigs. 

<br>


---

# 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://kerneldao.gitbook.io/kernel/getting-started/kelp/smart-contracts/access-control-and-multisigs.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.