feat(platform)!: contests on testnet/devnet/local should take less time #2115
Conversation
This file contains 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 network field in Drive config will be filled from the NETWORK env. We already pass it in dashmate |
|
Ivan had reviewed, merging in. |
QuantumExplorer
deleted the
feat/ContestsOnTestnetShouldTakeLessTime
branch
shumkov
changed the title
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.
Issue being fixed or feature implemented
Contests on Testnet took 2 weeks to resolve. This was bad for testing
What was done?
Contests on Testnet/Devnet/Local now will take 90 mins to resolve.
How Has This Been Tested?
Breaking Changes
This is a breaking change for testnet. It can only be activated with V2 of protocol.
Checklist:
For repository code-owners and collaborators only