> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/chiliz-chain-changelog/governance-proposals-and-decisions/february-2026-contract-removal-and-clean-up-proposal.md).

# February 2026: Contract Removal and Clean-Up Proposal

CIP-050 proposal to add a removeContract function to the Chiliz Chain Contract Registry and remove orphaned LayerZero contracts as a prerequisite for Omnichain integration.

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

## 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
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://docs.chiliz.com/chiliz-chain-changelog/governance-proposals-and-decisions/february-2026-contract-removal-and-clean-up-proposal.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.