Skip to content

Hyperevm infrastructure - #397

Merged
EndymionJkb merged 2 commits into
masterfrom
hyperevm-infrastructure
May 14, 2026
Merged

EndymionJkb merged 2 commits into
masterfrom
hyperevm-infrastructure

Conversation

@EndymionJkb

Copy link
Copy Markdown
Collaborator

Description

Adds two Hardhat tasks to support deploying from a fresh deployer EOA on HyperEVM. Without these, a new account can't deploy because (a) the standard path to credit HyperCore goes through the Hyperliquid website's T&C / geo gate (a problem if you're from a heavily restricted country that's blocked everywhere: i.e., the US - and it detects VPNs), and (b) HyperEVM's default small blocks (~2M gas) reject deployment of larger contracts, which most of ours are.

  • hl-deposit (scripts/hyperliquid-bridge.ts)

    • Sends native USDC on Arbitrum to Hyperliquid's Bridge2 contract. Validators credit HyperCore for the sender's address in under a minute, no UI flow needed.
    • Enforces the 5 USDC minimum and refuses to run if you only hold USDC.e (the old bridged token, which is silently lost by the bridge).
    • Run as: npx hardhat hl-deposit --amount 5 --network arbitrum
  • hyperevm-big-blocks (scripts/hyperevm-big-blocks.ts)

    • Toggles the deployer EOA's "big blocks" mode (~60s, 30M gas) via a Hyperliquid L1 evmUserModify action, which is necessary for any deploy whose constructor exceeds the default 2M-gas block limit.
    • Run as: npx hardhat hyperevm-big-blocks --enable --network hyperevm (and optionally --disable after).

Workflow

For a brand-new deployer EOA targeting HyperEVM:

  1. Fund the EOA with native USDC on Arbitrum
  2. hl-deposit to credit HyperCore
  3. hyperevm-big-blocks --enable
  4. Run the deployment task as usual against --network hyperevm
  5. optionally set it back to small blocks if you use the account for other things: hyperevm-big-blocks --disable

Type of change

  • Bug fix
  • New feature
  • Breaking change
  • Dependency changes
  • Code refactor / cleanup
  • Documentation or wording changes
  • Other

Checklist:

  • The diff is legible and has no extraneous changes
  • Complex code has been commented, including external interfaces
  • [N/A] Tests are included for all code paths
  • The base branch is either master, or there's a description of how to merge

Issue Resolution

@joaobrunoah joaobrunoah left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM!

@EndymionJkb
EndymionJkb merged commit 0785412 into master May 14, 2026
49 checks passed
@EndymionJkb
EndymionJkb deleted the hyperevm-infrastructure branch May 14, 2026 14:37
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.

2 participants