Add Multicall3 contract to EDU Chain mainnet

[matt-opencampus]

Summary

Added Multicall3 contract details to EDU Chain mainnet configuration.

Changes

• Updated src/chains/definitions/eduChain.ts to include multicall3 contract configuration
• Added contract address: 0xcA11bde05977b3631167028862bE2a173976CA11
• Added deployment block: 16410660

Verification

• Contract deployed today on EDU Chain mainnet
• Uses standard Multicall3 address consistent with other chains
• Can be verified on EDU Chain Explorer

Testing

• Follows established pattern used by other chains in the repository
• Changeset created for proper versioning

Resolves the missing multicall3 functionality for EDU Chain users.

[matt-opencampus]

Hi @jxom , I saw that you reverted the PR.

Multicall3 was just deployed yesterday on EDU Chain and so we have this PR open to update the official list: mds1/multicall3#394

Do we need to wait for this PR to be approved first before we can add the details to viem (not sure how long that's going to take unfortunately—last commits in the multicall3 repo were over 3 months ago)? Or can we simply compare the bytecode deployed on EDU Chain to what's deployed on other chains (that are on the official list, e.g., Base) and verify that it's the same?

Also, the contract was verified automatically by Blockscout via their bytecode database too: https://educhain.blockscout.com/address/0xcA11bde05977b3631167028862bE2a173976CA11?tab=contract

[matt-opencampus]

Hi @jxom, quick follow up on my comment above. Let us know if there's a good way to proceed, given the lack of activity on the multicall3 repo these days.

[jxom]

Try out the new Deployless Multicall in 2.36.0! No multicall contract required.

[matt-opencampus]

Thanks for sharing, @jxom! But given that we've already gotten Multicall3 deployed, are we able to just confirm that it is indeed the same bytecode as the official deployment (and also at the same address) and just also update the settings for EDU Chain?