This repository has been archived by the owner on Oct 6, 2023. It is now read-only.
Makes tenderly verification optional, defaults to off #394
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Explanation of the solution
We are in flux right now with our tenderly integration -- our account type has a hard cap on the limit of contracts that can be monitored and verifying a contract implicitly monitors it. The desired behavior is to only verify a subset of contracts related to the most "bleeding edge"; i.e. yield sources. In the meantime, we should disable "verify by default" behavior. When needed, we can manually verify contracts on tenderly to assist in debug efforts.
This PR makes tenderly verification optional when calling
verify()and defaults to "off".Instructions on making this work
yarnoryarn installto install npm dependencies