# [GIP-295] Allow Credit Facade v3.1.1 in the Bytecode Repository

- Space: [Gearbox](https://snapshot.box/s:gearbox.eth.md)
- Author: 0xab025D1Cb886D8464f6aECfC7144C6c4D07aa6D8
- State: Active
- Voting type: Basic
- Start: 2026-11-20 13:39 UTC
- End: 2026-11-23 13:39 UTC
- Votes: 10
- Quorum: 200,000,000 voting power
- Open in Snapshot: https://snapshot.box/#/s:gearbox.eth/proposal/0x66766f584a79fa5ce64cfb215032152f1e3576c10466c75b5620e054159657fc

## Results

- For: 34,098,562.51 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

## Summary

Authorize the Technical Multisig to submit the cross-chain governance batch **“Allow Credit Facade v3.1.1”**. Once approved and executed, the batch allows this implementation to be deployed through the Gearbox Bytecode Repository.

## Motivation

Credit Facade v3.1.1 adds support for `SignatureDegenNFT`, which lets curators protect their markets by requiring external signer approval for every new Credit Account. Curators can integrate offchain monitoring and other protective measures into the signing process. Each signed approval is valid for one opening by a specific borrower on a specific Credit Manager and expires if unused by its deadline. [SignatureDegenNFT implementation](https://github.com/Gearbox-protocol/permissionless/blob/9b74e7b8c483b8bca0b97813de899675d346006e/contracts/helpers/SignatureDegenNFT.sol)

The existing account-opening function can consume an approval already recorded on-chain. With v3.1.1, the borrower can include the signatures in the opening transaction itself. The facade forwards them to `SignatureDegenNFT`, so the borrower can present approval and open the Credit Account in one transaction. [Credit Facade implementation](https://github.com/Gearbox-protocol/core-v3/blob/ae03efa578ec45feca4a5e5829873cfec503f09e/contracts/credit/CreditFacadeV3.sol)

## Proposed change

Allow the following implementation as a system contract across Gearbox instances.

| Contract type | Version | Bytecode hash |
| --- | --- | --- |
| `CREDIT_FACADE` | 3.1.1 | [`0xb4dcb113180304e3d0357e83238bcc7b6980936c4ed0e0bdd3cd469f41fe5cb0`](https://bcr.gearbox.finance/hash/0xb4dcb113180304e3d0357e83238bcc7b6980936c4ed0e0bdd3cd469f41fe5cb0) |

## Execution

The [Technical Multisig](https://etherscan.io/address/0xA7D5DDc1b8557914F158076b228AA91eF613f1D5) submits the batch to the [CrossChainMultisig](https://etherscan.io/address/0xcCCCCcCc42B7DA9fdEc1761698Fb55fdD41CDF55) on Ethereum. After cross-chain governance approval, execution routes a single all-chain call through `InstanceManager.configureGlobal` to `BytecodeRepository.allowSystemContract` with the bytecode hash above.

# Transaction log
The json can be found [here](https://gearboxprotocol.notion.site/GIP-295-41e145c1622480c6b552c3b2d75643e5?source=copy_link)
Transaction file MD5: `f8d16f2386f6b0ff3f5a12f3869ec307`

---

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

