updated Hiperliquid Chain

[alfredolopez80]

Update Data, logo, chain info and RPC of Chain Id: 999, that corresponding to Hyperliquid EVM L1: more details: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/evm

[github-actions[bot]]

You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review.

[alfredolopez80]

Hey guys, fixed the imagen

[ChiTimesChi]

@alfredolopez80 are you planning to add "redFlags": ["reusedChainId"] as required by this repo chain management?

[Alkhatri77]

Thanks my friend

في الأربعاء، ١٩ فبراير ٢٠٢٥, ٧:٢٠ م ALFREDO J LOPEZ H (alfredolopez80.eth) < @.***> كتب:

Update Data, logo, chain info and RPC of Chain Id: 999, that corresponding to Hyperliquid EVM L1: more details: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/evm

You can view, comment on, or merge this pull request online at:

https://github.com/ethereum-lists/chains/pull/6840 Commit Summary

• 1694ce9 https://github.com/ethereum-lists/chains/pull/6840/commits/1694ce949964ca6845028eedb7fed48771d46f7f updated Hiperliquid Chain

File Changes

(2 files https://github.com/ethereum-lists/chains/pull/6840/files)

• M _data/chains/eip155-999.json https://github.com/ethereum-lists/chains/pull/6840/files#diff-2f8d2a881ddec137e3c198b652edc90b1ed3d9351d7f044e49a15bd8eec65f37 (32)
• A _data/icons/hyperliquid.json https://github.com/ethereum-lists/chains/pull/6840/files#diff-4d278607254aca817da38b0705534652473a5e024200e3b38e436151600eaa15 (8)

Patch Links:

• https://github.com/ethereum-lists/chains/pull/6840.patch
• https://github.com/ethereum-lists/chains/pull/6840.diff

— Reply to this email directly, view it on GitHub https://github.com/ethereum-lists/chains/pull/6840, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFTTIUPEXD3PAGMD4BZRZ2D2QSVNHAVCNFSM6AAAAABXOTORRKVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA3DGOBSGA3DKNY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[ChiTimesChi]

@ligi do you mind reviewing #7204 that completes the requested changes? Don't think this PR is going to be updated any time soon.

[github-actions[bot]]

This PR has no activity in a while - it will be closed soon.

[PaulRBerg]

HyperEVM should switch to using another chain ID.

[usame-algan]

HyperEVM should switch to using another chain ID.

@PaulRBerg @ligi Who is the right person to ping for this in order to move it forward? How important is it to keep the wanchain testnet vs. having HyperEVM support?

[pmerkleplant]

How important is it to keep the wanchain testnet vs. having HyperEVM support?

The issue is the risk of replaying txs between the two chains. It's a well understood security risk and with the possible chain id space big enough, an unnecessary one too.