Skip to content
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

Weekly Scope unified-auctions-ui KW 39+40 #470

Open
8 of 13 tasks
LukSteib opened this issue Sep 23, 2022 · 4 comments
Open
8 of 13 tasks

Weekly Scope unified-auctions-ui KW 39+40 #470

LukSteib opened this issue Sep 23, 2022 · 4 comments
Labels

Comments

@LukSteib
Copy link
Contributor

LukSteib commented Sep 23, 2022

@LukSteib
Copy link
Contributor Author

Re-check the profit calculation

Had another look. The discrepancy between actual profit and calculated profit during test runs is related to the estimated transaction fees on the fork being higher than actual.
Other than that the calculation is accurate. So for me no need to investigate further at this point in time

@LukSteib
Copy link
Contributor Author

rETH onboarding

based on the discussion with PE yesterday work on rETH is pushed out until the 12.10 when there is a PR for the mainnet spell to onboard it.

Suggestions on the current sprint:

#464 (also relevant for rETH onboarding)

I would suggest to keep on working on this PR, since we already made quite some progress and a generic simulation for vault creation + liquidation will help us in all of the future onboarding processes (including rETH). @valiafetisov what is your take on that?

https://github.com/sidestream-tech/auction-ui/issues/430

I would for now stop further investigation on that front and wait for the pair programming session scheduled on the 12.10 for a complete walk through of existing simulations by PE.

Instead my proposal:
Put more resources on the liquidity sources stream. See the two relevant issues in the top level comment. Besides that I'd suppose to proceed with 1inch as well. Currently I see two tasks:

  • check wether API can be called from frontend
  • include 1inch quoter information to the /dashboard table to compare prices

@valiafetisov what is your take?

@valiafetisov
Copy link
Contributor

I would suggest to keep on working on #464

Agree

https://github.com/sidestream-tech/auction-ui/issues/430

I would for now stop further investigation on that front and wait for the pair programming session scheduled on the 12.10 for a complete walk through of existing simulations by PE.

In order to execute the spell, we need their cli tools working on our side. I would still push this PR at least to the state where we have a robust setup. But based on what we learned yesterday, we can also move forward with spell execution.

Put more resources on the liquidity sources stream.

Yes, we can further investigate 1inch or/and set the goal to conceptualise multi-callee support. Or set the goal to release the auto router for unswapv3 callee(s) even before multi-callee support (even if it's not optimal order).

@LukSteib
Copy link
Contributor Author

In order to execute the spell, we need their cli tools working on our side. I would still push this PR at least to the state where we have a robust setup

Fine to push it up until the point where we have a robust setup. As this will minimise the risk of unknown unknowns for the meeting on the 12th. Although I would not proceed further than that.

Yes, we can further investigate 1inch or/and set the goal to conceptualise multi-callee support.

Yes, let's include both parts into the scope.

Or set the goal to release the auto router for unswapv3 callee(s) even before multi-callee support (even if it's not optimal order)

I would stick to the original order of having multi-callee support first. For me the risk of having a buggy auto router implementation without fallback outweighs its upside.

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

No branches or pull requests

2 participants