Please add properties for Wagmi compatibility

[hskang9]

I saw CAIP-25 was applied for betterment for the wallet experience, but the recent CaipNetwork type is making a huge friction for building an app.

By switching to CaipNetwork type, App developers cannot:

1. Specify Multicall3 address to call multiple view function in smart contracts. App crashes whenever it tries to use multicall3, because it cannot even use it.
2. Add ENS contract address to interact with ENS stack or other name system contracts in other chains
3. Make their app prepare for worst case when specified RPC is not responding
4. Add websocket connection on RPC when it is required(e.g. Polkadot) for different specification, I just don't understand what CaipNetwork type is doing when it is not considering the default connection is happening in websocket in Polkadot.

Can we remove CaipNetwork type and use Chain type by Wagmi?

I don't understand why CaipNetwork is used when Chain type after just comparing the code itself.

This is the Chain type code

export const StoryIliad = defineChain({
  id: 1513,
  name: "Story Public Testnet",
  nativeCurrency: { name: "IP", symbol: "IP", decimals: 18 },
  rpcUrls: {
    public: { http: ["https://testnet.storyrpc.io/"] },
    default: {
      http: ["https://testnet.storyrpc.io/"],
    },
  },
  blockExplorers: {
    etherscan: {
      name: "Story Testnet Scan",
      url: "https://testnet.storyscan.xyz",
    },
    default: {
      name: "Story Testnet Scan",
      url: "https://testnet.storyscan.xyz",
    },
  },
  testnet: true,
  contracts: {
    multicall3: {
      address: "0xcA11bde05977b3631167028862bE2a173976CA11",
      blockCreated: 1566,
    },
  },
});

This is the current CaipNetwork type code.

export type ChainNamespace = 'eip155' | 'solana' | 'polkadot'

export type CaipNetwork = {
  id: CaipNetworkId
  chainId: ChainId
  chainNamespace: ChainNamespace
  name: string
  currency: string
  explorerUrl: string
  rpcUrl: string
  imageUrl?: string
  imageId?: string
}

The type is just vague as it can be, and it never considers agnostic connection when each of them can require different ways to connect.

I wonder which CAIP author proposed this specification to make app devs report for guidance in this month now. I cannot find anywhere for this CaipNetwork type specification in the proposal repository.

Can Reown team just add extra interface for CaipNetworkId, imageUrl, imageId, and Namespace on top of Chain type by Wagmi?

Why is the team rebuilding the wheel when they could just make app devs add extra properties on the existing type?