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"
Voting Period Ends Thursday 12th February at 11:00am CET
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.
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.
Function Addition: Implement a removeContracts(address[] memory impls) function within the DeployerProxy Contract.
Access Control: This function will be restricted to ONLY_GOVERNANCE to prevent unauthorized removals.
State Cleanup: Execute the removal of the following two addresses:
0x000000000000b361194cfe6312EE3210d53C15AA
0x00000000000001E4A82b33373DE1334E7d8F4879
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.
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.
Last updated
Was this helpful?
Was this helpful?
