> 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/kernel-deprecated/smart-contracts/roles.md).

# Roles

A timelock with an exclusive proposer governs all Kernel smart contracts. Three other roles namely an admin, manager and pauser share multiple responsibilities necessary to successfully configure and operate the Kernel protocol. Here are all the multisigs and signers.\
\
**Timelock Contract** - [0xc34C665264DAC8a589F240684aFd18f52d98C602](https://bscscan.com/address/0xc34C665264DAC8a589F240684aFd18f52d98C602)\
Currently, the timelock delay is set to 3 days to provide transparency and notify the broader ecosystem of upcoming changes. 

 **Timelock Proposer** - [0x845c3dB355f7bEcA27Ac8b4652517f8594369261](https://app.safe.global/home?safe=bnb:0x845c3dB355f7bEcA27Ac8b4652517f8594369261)\
The timelock proposer is a 8 signer multisig and needs 5 signatures to upgrade any contracts ( additionally has to pass timelock) formed by prominent community members from the BNB ecosystem. The signers of this multisig are as follows -

1. Igal Bini (Partner & Head of Partnerships, Israeli Blockchain Association) \
   [LinkedIn](https://www.linkedin.com/in/igal-bini-b33b701bb/), [Twitter/X](https://twitter.com/igalb77) (@igalb77) \
   Wallet: 0x3FCAEeafC0f9Ec1FD8e2AEAe1276935c636b0dAF
2. Lars Rensing (CEO, Protokol, Core Team at Cluster Capital) \
   [LinkedIn](https://www.linkedin.com/in/larsrensing/), [Twitter/X](https://twitter.com/l_rensing?lang=en) (@l\_rensing) \
   Wallet: 0x2198A3188A0dc5526567A5D17b06e466C042D702
3. Michael Kam (Investment Partner, Avid VC) \
   [Link](https://www.avid3.xyz/) \
   Wallet: 0x61f45F63e06aa0DAE039BcFDa2c4Aab017441Ee7
4. Amrit Kumar (COO, AltLayer) \
   [LinkedIn](https://www.linkedin.com/in/amrit-kumar-6aa66151/), [Twitter/X](https://twitter.com/maqstik?lang=en) (@maqstik) \
   Wallet: 0x7Da5A697980E53Ecc137c0f7E96F4Cb656130098
5. Ramani Ramachandran (CEO, Router Protocol & Dfyn.network) \
   [LinkedIn](https://www.linkedin.com/in/ramaniram/), [Twitter/X](https://twitter.com/CryptoMan_Ram) (@CryptoMan\_Ram) \
   Wallet: 0xd4C9d49bBda1F074ba8363bfc5D72Fd2a9dFC77F
6. Dheeraj Borra (Co-Founder of KernelDAO)\
   [LinkedIn](https://www.linkedin.com/in/dheeraj-borra/) \
   Wallet: 0x7AAd74b7f0d60D5867B59dbD377a71783425af47
7. Emanuele (KernelDAO member)\
   [Website](https://www.linkedin.com/in/emanuelegaspari/) \
   Wallet: 0xa9De8755FaCD88Fd82894afD2C014C860993042f
8. Manoj Patra (KernelDAO member)\
   [LinkedIn](https://www.linkedin.com/in/defi-wind) \
   Wallet: 0x0e4B97563723eF7f0a7FDe4c7bD3B17a5bF63fBf

Admin Multisig - [0x40f5f0f5e78289b33e450fbca1cbd8700098cd23](https://app.safe.global/home?safe=bnb:0x40f5f0f5E78289B33E450fBCA1cbD8700098cd23)\
This role is used for admin related operations on Kernel contracts.

Manager Multisig - [0x85dfbf5a7c26da08406b792e673d847755498bc8](https://app.safe.global/home?safe=bnb:0x85dfbf5a7c26da08406b792e673d847755498bc8)\
This role is used for manager level low-impact operations on Kernel contracts.

Pauser Multisig - [0x762966a8f4f4ed9016f8651b352e9435ce733b67](https://app.safe.global/home?safe=bnb:0x762966a8f4f4ed9016f8651b352e9435ce733b67)\
This role is explicity used for pausing contracts as a response to emergencies.


---

# 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/kernel-deprecated/smart-contracts/roles.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.