Axelar proxy contractId detector#
Name: axelar-proxy-contract-id
The detector detects Axelar proxy and implementation contracts that use the contractId method as an additional check for deploying the contracts and when performing an upgrade.
Proxy contractId shared between multiple contracts#
Two different proxy contracts should not share the same contractId.
Proxy contract without upgradeable contract with the same contractId#
It is expected that a project will have at least one implementation contract with the same contractId as the proxy contract.
Proxy contracts without an implementation contract with the same contractId are reported.
Implementation contract without proxy contract with the same contractId#
It is expected that a project will have exactly one proxy contract with the same contractId as the implementation contract.
Implementation contracts without a proxy contract with the same contractId are reported.
Proxy contract and upgradeable contract with function selector collision#
An implementation contract and a corresponding proxy contract should not define functions with the same function selector. It wouldn't be possible to call the implementation contract function in this case, as the proxy contract function would be called instead.
The implementation() and setup(bytes calldata params) functions are an exception to this rule and are not reported.
- It will never be possible to call the
kindfunction of the implementation contract, as the proxy contract function will be called instead.
Parameters#
The detector does not accept any additional parameters.