-
Notifications
You must be signed in to change notification settings - Fork 591
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
[Epic] v8 tracking issue #1141
Comments
It feels like to me like we're hitting scope creep on v8 / when that'd go into an on-chain proposal. I propose making a new issue for planning a v9 release, and moving some v8 items into there. The goal would be to target a v8 proposal going on-chain April 8th or April 11th. Items that I think we should move to v9:
|
Kicked off a branch: |
Hey @ValarDragon, Hope your doing well mate :) Curious if this Epic will be ready by end of this week. I see @faddat has kicked off a branch which is exciting. I also see the GAMM Work still needs sometime to properly address as well! |
Hey @ValarDragon following up here again if possible to see if there is any update. Thank you so much and enjoy the remainder of your week |
Hey, this will definitely not be ready by end of week unfortunately. Would appreciate any help in documenting & improving any of the relevant changes! |
Hi yes, of course, I think I can help with documentation if need be. Improving the relevant changes I am unaware of where to help. For instance, stable swap is clearly out of my scope/capability to help :/ |
Looking at the additional work, it looks like this v8 release will actually take 3-4 more weeks until pushed. Let me know how I can help your team push it out further from a documentation stance. Thanks |
Closing this issue in replacement of V10 |
TWAPsThe text was updated successfully, but these errors were encountered: