Skip to content

Conversation

@maxime-oe
Copy link
Contributor

@maxime-oe maxime-oe commented Jan 29, 2026

Explanation

This PR adds support for the HyperEVM blockchain network across the PreferencesController and TransactionController packages. The changes enable HyperEVM network integration by adding chain ID definitions, API support, and default configurations.

Change

  • Add HyperEVM chain ID constant (0x3e7) and swaps token configuration
  • Enable incoming transactions and account relationship API support for HyperEVM
  • Configure default preferences to show incoming transactions for HyperEVM network

API:

V4 MultiAccount - URL

V1 Account relationship - URL

V1 Account tx history - URL

Jira

https://consensyssoftware.atlassian.net/browse/NEB-331

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

Medium Risk
Adds a new supported chain across preferences defaults and transaction-related Accounts API/swaps logic; incorrect chain ID mapping or API assumptions could affect transaction history/relationship queries and swaps defaults on that network.

Overview
Adds HyperEVM (0x3e7 / 999) as a supported chain across preferences-controller and transaction-controller.

PreferencesController now includes HYPEREVM in ETHERSCAN_SUPPORTED_CHAIN_IDS and enables it by default in showIncomingTransactions (tests updated accordingly). transaction-controller adds HyperEVM to Accounts API supported chain lists (relationship + incoming transactions), introduces CHAIN_IDS.HYPEREVM, and maps a default swaps token for HyperEVM. Changelogs are updated to reflect the new network support.

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

@maxime-oe maxime-oe force-pushed the feat/add-hyperevm-to-tx-preference branch 2 times, most recently from c863186 to 194255c Compare January 29, 2026 08:20
@maxime-oe maxime-oe marked this pull request as ready for review January 29, 2026 08:20
@maxime-oe maxime-oe requested review from a team as code owners January 29, 2026 08:20
@maxime-oe maxime-oe force-pushed the feat/add-hyperevm-to-tx-preference branch 2 times, most recently from 245aa34 to 4abe5bf Compare January 29, 2026 08:30
@stanleyyconsensys stanleyyconsensys changed the title feat: add HyperEVM preferences and transactions feat: add HyperEVM support in PreferenceController and TransactionController Jan 30, 2026
Copy link
Contributor

@stanleyyconsensys stanleyyconsensys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 nit comment on the change log

OGPoyraz
OGPoyraz previously approved these changes Jan 30, 2026
@maxime-oe maxime-oe force-pushed the feat/add-hyperevm-to-tx-preference branch 2 times, most recently from b1e8ea6 to d03e4b0 Compare January 30, 2026 08:23
@maxime-oe maxime-oe force-pushed the feat/add-hyperevm-to-tx-preference branch from d03e4b0 to 5b9fbdf Compare January 30, 2026 08:24
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Copy link
Contributor

@stanleyyconsensys stanleyyconsensys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@maxime-oe maxime-oe requested a review from OGPoyraz January 30, 2026 11:31
@maxime-oe
Copy link
Contributor Author

@OGPoyraz I had to force-push a CHANGELOG edit, is it possible to reapprove ? 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants