You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today there is a "contract interaction" flow for multisig signers but ABIs are only loaded directly from the contract itself. This makes it hard to interact with proxy contracts, and in reality most production smart contract deployments are performed with proxies to allow for upgrades. This feature request is about making it easier to interact with proxy + implementation contract by displaying methods from the implementation contract when a proxy contract address is loaded.
Goals
Detect when a provided contract address is a proxy address (see how Blockscout does this)
Load methods from ABI of implementation contract in proxy
Requirements
We can start by just supporting Blockscout for now and look to support other block explorers like Celoscan later
Overview
Today there is a "contract interaction" flow for multisig signers but ABIs are only loaded directly from the contract itself. This makes it hard to interact with proxy contracts, and in reality most production smart contract deployments are performed with proxies to allow for upgrades. This feature request is about making it easier to interact with proxy + implementation contract by displaying methods from the implementation contract when a proxy contract address is loaded.
Goals
Requirements
Screens
https://explorer.celo.org/address/0x6180F059986cF55Bb2b46A14B21A7b8F9aF999a7/read-proxy
The text was updated successfully, but these errors were encountered: