-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make pool & addresses provider immutable #81
Conversation
afb042d
to
26a0cac
Compare
26a0cac
to
46f9cba
Compare
I'm just wondering as I've never been clear on this point. Is there no way that we can do this without having to store our own rebase index? This asset should only be supplied as collateral, so it should only ever be on pool. In that case, what is stopping us from just imitating the pool logic? |
I agree this asset is only supposed to be supplied as collateral, because:
Then we could only store it as collateral, but we need to have a way to prevent users from supplying it for anything else than collateral.
What do you think? |
I prefer solution 2 for now, since this is really just a very special case that the matching parts of the protocol are not built for. |
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.
One thing to remember is that Aave V3 is deployed yet so the only way to test it is on an L2 where the stETH is not there.
Can we try to think about something which is more scalable? I'll reflect on this too
46f9cba
to
598827e
Compare
598827e
to
773c74b
Compare
773c74b
to
365ec8d
Compare
78a8e1e
to
18414ad
Compare
Pull Request
Issue(s) fixed
This pull request fixes nothing