Hyperevm infrastructure - #397
Merged
Merged
Conversation
9 tasks
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.
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)
npx hardhat hl-deposit --amount 5 --network arbitrumhyperevm-big-blocks (scripts/hyperevm-big-blocks.ts)
npx hardhat hyperevm-big-blocks --enable --network hyperevm(and optionally --disable after).Workflow
For a brand-new deployer EOA targeting HyperEVM:
Type of change
Checklist:
master, or there's a description of how to mergeIssue Resolution