-
Notifications
You must be signed in to change notification settings - Fork 0
Nialexsan/wbtc weth #108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Nialexsan/wbtc weth #108
Conversation
This reverts commit 7d6c2bb.
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
| strategy: Type, | ||
| collateral: Type | ||
| ): Bool { | ||
| let composerConfig = self.configs[composer]! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested fix: The hasConfig function uses force-unwrap (!) on optional values which can panic. Should be changed to use optional binding:
access(all) view fun hasConfig(
composer: Type,
strategy: Type,
collateral: Type
): Bool {
if let composerConfig = self.configs[composer] {
if let strategyConfig = composerConfig[strategy] {
return strategyConfig[collateral] != nil
}
}
return false
}|
Additional changes needed:
These changes are staged locally and can be reviewed. |
local/setup_mainnet.sh
Outdated
|
|
||
|
|
||
| # Setup UniV3 path tauUSDFv -> USDF -> WFLOW | ||
| flow transactions send ../cadence/transactions/flow-yield-vaults/admin/upsert_musdf_config.cdc \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix relative path: This should be ./cadence/transactions/flow-yield-vaults/admin/upsert_musdf_config.cdc instead of ../cadence/... since the script runs from the repo root.
Kay-Zee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How easy is it to add new strategies to this setup? We will likely need to add a few more strategies compared to just the one mUSDF strategy, so if it's easy, then i'd almost want to "reset" the versioning, and go onto a new account, rather than having v1_1.
| let composerType = Type<@FlowYieldVaultsStrategiesV1_1.mUSDFStrategyComposer>() | ||
| let strategyType = Type<@FlowYieldVaultsStrategiesV1_1.mUSDFStrategy>() | ||
|
|
||
| //issuer.purgeConfig() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not, if not needed, let's removed, if leaving, mentioned why with additional comments
|
|
||
| //issuer.purgeConfig() | ||
| // === FLOW collateral === |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?? only flow?
Closes: #???
Description
testnet txns for vaults with the collaterals:
https://testnet.flowscan.io/tx/2e3bf1756651d81fbf638d74faaf2685d26c474b7f4373ee995e0189b7d75d2f
https://testnet.flowscan.io/tx/b9154993f550dc85b1361cf59a2f3a5b0f1b8595c79e2f3e9a0350526cbe15e9
FlowYieldVaultsStrategies diff:
main...2d4e129#diff-3ca82892e3f3687d53c4df502a69e2b07e6f5a0038466d9792121979b51d2f32
For contributor use:
masterbranchFiles changedin the Github PR explorer