Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

More realistic Compound v2 deployment on testnet #130

Closed
mhluongo opened this issue May 19, 2019 · 2 comments
Closed

More realistic Compound v2 deployment on testnet #130

mhluongo opened this issue May 19, 2019 · 2 comments

Comments

@mhluongo
Copy link
Member

In #105, we agreed to stub out Uniswap behavior for development purposes. #117 suggests we'll have a similar solution for Compound in the short term.

Before mainnet, we should switch out the stubs for actual Compound contracts.

@mhluongo mhluongo added this to the Pre-audit milestone May 19, 2019
@mhluongo mhluongo modified the milestones: Pre-audit, Post-mainnet Jan 17, 2020
@mhluongo
Copy link
Member Author

Moved to post-mainnet since this supports #117

@Shadowfiend
Copy link
Contributor

Closing this as there's no approach here, we're not deploying any Compound contracts currently (stub or otherwise), and this is about deployment of in use contracts. Some form of this may come back as #117 plays out post-mainnet, though #270 at least covers how we would link to it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants