# [GIP-293] Allow KillSwitch Deployment through the Bytecode Repository

- Space: [Gearbox](https://snapshot.box/s:gearbox.eth.md)
- Author: 0xab025D1Cb886D8464f6aECfC7144C6c4D07aa6D8
- State: Passed
- Voting type: Basic
- Start: 2026-11-16 14:06 UTC
- End: 2026-11-19 14:06 UTC
- Votes: 15
- Quorum: 200,000,000 voting power
- Open in Snapshot: https://snapshot.box/#/s:gearbox.eth/proposal/0xd408cac97373c636ce9ef5f0176eccf2a3dfdac3f2e5eddd8e589c58f2b193ff

## Results

- For: 247,467,158.48 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

# Summary

This proposal authorizes the Technical Multisig to submit the prepared cross-chain governance batch allowing the KillSwitch implementation as a system contract in the Bytecode Repository.

This enables its subsequent deployment and configuration for use in Gearbox markets.

# Motivation

Emergency administrators need to act quickly, but curators also need a way to disable their access if an emergency administrator is compromised or behaves unexpectedly.

The [KillSwitch implementation](https://github.com/Gearbox-protocol/permissionless/blob/12fec541c297c18387331ee3817a38da0ae0e03d/contracts/helpers/KillSwitchProxy.sol) separates these responsibilities. A designated caller can forward calls through the proxy, while a separate owner can permanently disable that forwarding capability. The owner and caller must be different addresses.

When configured as part of a market’s emergency administration, this provides an independent way to revoke that execution path without waiting for a timelocked replacement. Disabling the proxy is irreversible; restoring that path requires a replacement and the appropriate configuration.

# Proposed change

Allow the following bytecode as a system contract in the Bytecode Repository:

- Contract type: `KILL_SWITCH_PROXY`
- Version: `310`
- Bytecode hash: [`0xda04386097337332550e6486e198a3ddf4cc980d07975e70a67a6e07c95458ad`](https://bcr.gearbox.finance/hash/0xda04386097337332550e6486e198a3ddf4cc980d07975e70a67a6e07c95458ad)

# Execution

Authorize the [Technical Multisig](https://etherscan.io/address/0xA7D5DDc1b8557914F158076b228AA91eF613f1D5) to submit the batch **“Allow KillSwitch as system contract”** to the [CrossChainMultisig](https://etherscan.io/address/0xcCCCCcCc42B7DA9fdEc1761698Fb55fdD41CDF55), followed by approval and execution through the cross-chain governance process.

The batch calls `allowSystemContract` for the specified bytecode through `InstanceManager.configureGlobal`, using the all-chain scope.

This action allows the implementation in the Bytecode Repository. Deployment, assignment of owner and caller, and market configuration remain separate steps.

# Transactions
Md5 checksum of the transaction is 42905c4165fc076945e1224819bb742c. Transaction json is available [here](https://gearboxprotocol.notion.site/GIP-293-41a145c16224801185a0d45691cd0546?source=copy_link)

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

