Skip to content

Commit ba3c8d2

Browse files
committed
➕ Add HyperEVM Test and Main Networks
Signed-off-by: Pascal Marco Caversaccio <[email protected]>
1 parent 76c8ce9 commit ba3c8d2

File tree

7 files changed

+61
-48
lines changed

7 files changed

+61
-48
lines changed

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -266,6 +266,7 @@ The current available networks are:
266266
- `zkSyncTestnet`
267267
- `immutableZkEVMTestnet`
268268
- `abstractTestnet`
269+
- `hyperevmTestnet`
269270
- **EVM-Based Production Networks:**
270271
- `ethMain`
271272
- `bscMain`
@@ -343,6 +344,7 @@ The current available networks are:
343344
- `zkSyncMain`
344345
- `immutableZkEVMMain`
345346
- `abstractMain`
347+
- `hyperevmMain`
346348

347349
> [!IMPORTANT]
348350
> Note that you must ensure that your deployment account has sufficient funds on **all** target networks.
@@ -399,6 +401,9 @@ The contract creation transaction is displayed on Etherscan (or any other block
399401
> [!WARNING]
400402
> Solidity version [`0.8.25`](https://github.com/ethereum/solidity/releases/tag/v0.8.25) defaults to EVM version [`cancun`](https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/cancun.md), which features a number of new opcodes. Prior to running a deployment with a `>=0.8.25`-compiled bytecode (using the EVM version `cancun`), please verify that _all_ targeted EVM networks support the new `cancun` opcodes. Otherwise, a deployment attempt on an EVM chain without `cancun` support may result in deployment or runtime failure(s).
401403
404+
> [!WARNING]
405+
> Solidity version [`0.8.30`](https://github.com/ethereum/solidity/releases/tag/v0.8.30) defaults to EVM version [`prague`](https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/prague.md), which introduces _no new opcodes_ but includes a few new precompiled contracts (see [EIP-2537](https://eips.ethereum.org/EIPS/eip-2537)). If your contract(s) make use of these new precompiled contracts, ensure that _all_ targeted EVM networks support the `prague` precompiled contracts. Otherwise, deployed contracts may encounter runtime failure(s).
406+
402407
## Usage
403408

404409
```console

package.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "xdeployer",
3-
"version": "3.1.14",
3+
"version": "3.1.15",
44
"description": "Hardhat plugin to deploy your smart contracts across multiple EVM chains with the same deterministic address.",
55
"author": "Pascal Marco Caversaccio <[email protected]>",
66
"license": "MIT",
@@ -25,7 +25,7 @@
2525
"engines": {
2626
"node": ">=14.0.0"
2727
},
28-
"packageManager": "pnpm@10.10.0",
28+
"packageManager": "pnpm@10.11.0",
2929
"scripts": {
3030
"prettier:check": "npx prettier -c \"**/*.{js,ts,md,sol,json,yml,yaml}\"",
3131
"prettier:fix": "npx prettier -w \"**/*.{js,ts,md,sol,json,yml,yaml}\"",
@@ -48,7 +48,7 @@
4848
"@types/chai": "^4.3.20",
4949
"@types/fs-extra": "^11.0.4",
5050
"@types/mocha": "^10.0.10",
51-
"@types/node": "^22.15.17",
51+
"@types/node": "^22.15.18",
5252
"chai": "^4.5.0",
5353
"eslint": "^9.26.0",
5454
"eslint-config-prettier": "^10.1.5",

pnpm-lock.yaml

Lines changed: 42 additions & 42 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)