-
Notifications
You must be signed in to change notification settings - Fork 4
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
Bump support for RP4 #136
Comments
necessary changes for bot, are pretty minimal, we just need to point to rp4 route builder fn, instead of rp3.2, thats it all for bot side to be able to run thing on rp4, ofc we need the rp4 contract deployed on the supported chains, most of them have official deployments that are available in sushi lib as literals, but for mising chains, we can just deploy and update the literals on sushi lib with them so it be accessible by the bot, since it gets RP contract addresses from literal that are in sushi lib |
here is the list of all RP4 deployments: in our case missing chains include:
|
after this, we would need new Arb contracts deployed with RP4 address of their chain, and used as bot ENVs, so that bot can operate normally |
todo:
|
|
We are trying to arb against PancakeSwap V3, but it appears that the RouteProcessor contract we're using isn't compatible.
It looks like RouteProcessor4 is compatible (pending a passing test by @Siddharth2207), this issue is to track the necessary changes to the bot.
The text was updated successfully, but these errors were encountered: