refactor: rename hardhat network "test" to "custom" #502
+1
−1
Conversation
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
The name "test" was misleading as it implied a specific testnet, but the network's RPC URL is entirely user-defined via RPC_URL env var. Rename to "custom" to better reflect its purpose.
kvinwang
added a commit
to Phala-Network/dstack-cloud-deployment-guide
that referenced
this pull request
Feb 13, 2026
- Replace all --network test with --network custom to match upstream hardhat config rename (Dstack-TEE/dstack#502) - Expand prerequisite sections with detailed setup instructions - Add example outputs for contract deployment and authorization steps - Add troubleshooting sections for common issues - Improve deployment instructions with prelaunch.sh approach
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
testnetwork in hardhat config tocustomRPC_URLenv varTest plan
--network customresolves correctly withRPC_URLset