Add one-command RISE Testnet V2 deployment - #12
Merged
Conversation
CryptoMickle
marked this pull request as ready for review
August 24, 2026 18:23
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.
Summary
DeployRiseTestnet.s.soldeployment scriptLegacyVRFAdapteragainst the existing RISE VRF coordinatorDelveworncore against that adapterIntended rollout
The helper reads
RISE_EXISTING_DUNGEON_ADDRESSor../frontend/.env.local, callscoordinator()on the existing RISE deployment, then deploys the new adapter and V2 dungeon. The new Delveworn address can then replaceNEXT_PUBLIC_DUNGEON_ADDRESSin Vercel/frontend configuration.Validation
forge fmt --check✅forge build --sizes✅forge test -vvvsuite ✅script/DeployRiseTestnet.s.solandscripts/deploy-rise-testnet.shReady to merge.