Skip to content

chore: add tempo mainnet multicall contract address#8346

Open
Julink-eth wants to merge 2 commits intomainfrom
chore/support-tempo-mainnet-multicall
Open

chore: add tempo mainnet multicall contract address#8346
Julink-eth wants to merge 2 commits intomainfrom
chore/support-tempo-mainnet-multicall

Conversation

@Julink-eth
Copy link
Copy Markdown
Contributor

@Julink-eth Julink-eth commented Mar 31, 2026

Explanation

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Low Risk
Low risk: this only extends the MULTICALL_CONTRACT_BY_CHAINID mapping to enable multicall batching on an additional chain, with no behavioral changes for existing networks.

Overview
Adds Tempo Mainnet support to multicall-based RPC batching by registering chain 0x1079 in MULTICALL_CONTRACT_BY_CHAINID.

Updates the assets-controllers changelog to note the newly supported Tempo Mainnet multicall contract.

Written by Cursor Bugbot for commit c271bfd. This will update automatically on new commits. Configure here.

@Julink-eth Julink-eth requested a review from a team as a code owner March 31, 2026 08:11
@github-project-automation github-project-automation bot moved this to Needs dev review in PR review queue Mar 31, 2026
@Julink-eth Julink-eth requested a review from a team as a code owner March 31, 2026 08:15
@github-project-automation github-project-automation bot moved this from Needs dev review to Review finalised - Ready to be merged in PR review queue Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Review finalised - Ready to be merged

Development

Successfully merging this pull request may close these issues.

3 participants