Handling proxy contracts with implementation abi missing proxy abi about eth-sdk HOT 2 OPEN

Two thoughts:

1. "global" settings like noFollowProxies is not enough. Instead of specifying raw addresses in config, it should be possible to specify small config objects.

Instead of:

export default defineConfig({
  contracts: {
    mainnet: {
      dai: '0x6b175474e89094c44da98b954eedeac495271d0f',
    },
  },
})

This should be supported as well:

export default defineConfig({
  contracts: {
    mainnet: {
      dai: { 
           address:	'0x6b175474e89094c44da98b954eedeac495271d0f',
           proxyHandling: "do-not-follow-proxy"
			// this could be a place for many other things like for example providing implementation address manually
      },
    },
  },
})

2. noFollowProxies needs to be replaced with a more granular setting. Some ideas:

• follow proxies (default)
• do not follow proxies
• merge proxy with implementation (this is what you need).

Merging proxies should be generally easy because TypeChain and Ethers will use full method signatures if there is a conflict. (but I guess two methods with exactly the same signatures will have to be filtered out...).

from eth-sdk.

There's any update on this?
Seems having a more granular setting a reasonable solution

from eth-sdk.