fix(chains): correct xdcTestnet (XDC Apothem) multicall3 address#4753
Open
AnilChinchawale wants to merge 1 commit into
Open
fix(chains): correct xdcTestnet (XDC Apothem) multicall3 address#4753AnilChinchawale wants to merge 1 commit into
AnilChinchawale wants to merge 1 commit into
Conversation
The xdcTestnet (chainId 51) multicall3 pointed to the canonical 0xca11…ca11, which has no deployed code on Apothem (verified via eth_getCode on rpc.apothem.network, erpc.apothem.network and apothem.xdcrpc.com), so multicall() failed there. Updated to a deployed Multicall3 (standard bytecode) at 0x7937b3878860eb3CDA14360cEaaa11a9646d941B, block 83401816.
🦋 Changeset detectedLatest commit: 5003cb2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@AnilChinchawale is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the
multicall3contract address onxdcTestnet(XDC Apothem, chainId 51). The current entry points to the canonical0xca11…ca11, but Multicall3 is not deployed at that address on Apothem, soclient.multicall/useReadContractsfail on this chain.Evidence
eth_getCodefor the currently-listed address returns0x(no code) on three independent Apothem RPCs:eth_getCode(0xca11…ca11)https://rpc.apothem.network0x(no code)https://erpc.apothem.network0x(no code)https://apothem.xdcrpc.com0x(no code)(For contrast, the
xdcmainnet entry's multicall30x0B1795cc…is correct and has code — only the testnet entry is wrong.)Fix
Points
xdcTestnet.contracts.multicall3at a deployed Multicall3 instance:0x7937b3878860eb3CDA14360cEaaa11a9646d941B83401816This is the standard Multicall3 creation bytecode (from the canonical mds1/multicall deployment transaction), deployed via a normal contract creation since the canonical keyless deployer cannot be used on new chains (its key is compromised, per the mds1/multicall README). The deployed runtime is the standard Multicall3 (3808 bytes) and is functional —
getBlockNumber()andgetCurrentBlockTimestamp()return correct values on Apothem.Notes
Address is checksummed. Changeset (
patch) included.