# February 2026: Contract Removal and Clean-Up Proposal

Full name for this proposal: "\[CIP-050] Add Removal Functionality to Contract Registry and Clean Up Orphaned LayerZero Contracts"

{% hint style="warning" %}
Voting Period Ends Thursday 12th February at 11:00am CET
{% endhint %}

## Description

### Summary

This proposal seeks to upgrade the Contract Registry on Chiliz Chain to include a `removeContract` function. Additionally, it authorizes the immediate removal of two orphaned contract addresses that were added to the registry following a failed deployment. This cleanup is a prerequisite for completing the LayerZero Omnichain integration.

### Background

As part of our Omnichain initiative, Chiliz Chain is integrating with LayerZero. During the initial setup of the registry, two contract addresses were added accidentally due to a deployment failure. Currently, the Contract Registry lacks a native function to remove or "deregister" an address once it has been added.

## Technical Specification

1. Function Addition: Implement a `removeContracts(address[] memory impls)` function within the DeployerProxy Contract.
   1. Access Control: This function will be restricted to `ONLY_GOVERNANCE` to prevent unauthorized removals.
2. State Cleanup: Execute the removal of the following two addresses:
   1. `0x000000000000b361194cfe6312EE3210d53C15AA`
   2. `0x00000000000001E4A82b33373DE1334E7d8F4879`

## Motivation

The presence of these orphaned addresses creates a conflict in the LayerZero integration logic, preventing the successful mapping of Chiliz Chain mainnet.

Removing these entries will:

* Unblock the Omnichain expansion.
* Ensure the Contract Registry remains a "source of truth" without stale or broken data.
* Provide a standard mechanism for governance to rectify future deployment errors.

## Risks

The risk is minimal as the function is protected by governance consensus. Removing these specific addresses is safe because they point to failed/non-functional deployments that are not currently in use by any live services.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.chiliz.com/chiliz-chain-changelog/governance-proposals-and-decisions/february-2026-contract-removal-and-clean-up-proposal.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.