Repository navigation
feat(chains): add Multicall3 to Tempo chains - #5405
Merged
Merged
Conversation
|
@gakonst is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
🦋 Changeset detectedLatest commit: 9398ac6 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 |
This was referenced Nov 3, 2026
Merged
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
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.
Tempo Mainnet (4217), Moderato (42431) and Devnet (31318) deploy Multicall3 at
0xcA11bde05977b3631167028862bE2a173976CA11at genesis.eth_getCodefor that address at block0x0returns the Multicall3 bytecode onrpc.tempo.xyz,rpc.moderato.tempo.xyzandrpc.devnet.tempoxyz.dev, soblockCreatedis0.Without
contracts.multicall3, clients on these chains have to batch withbatch: { multicall: { deployless: true } }, which sends Multicall3's ~6.6 KB of bytecode with every batchedeth_call, or fail withChainDoesNotSupportContract. The Tempo Accounts SDK relay works around this today (tempoxyz/accounts#952); this makes the workaround unnecessary.tempoLocalnetis left as is. The currentghcr.io/tempoxyz/tempodev node also has it, but a localnet's genesis is up to whoever runs it.