fix(notional): Fix contract name and bytecode shadowing issues for temp Notional contracts #255
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.
DO NOT MERGE.
(These are small adjustments to get a NotionalTradeModule staging deployment working, published at the
notional
tag as version 0.11.1-notional. (See deployments-v2 PR 208). They affect contracts that will be removed when IC returns to finalize the NotionalTradeModule after audit)As part of #251, several contracts that will be published/deployed by Notional in future have been temporarily brought into the repo to enable NotionalTradeModule development and staging_mainnet testing
Unfortunately the way these contracts are imported results in duplicate hardhat artifacts being generated and two problems in the downstream deployments repo:
This PR renames WrappedfCashFactory root-level contract and makes other Notional contract bytecodes slightly different (in an irrelevant way) to get around these.