-
Notifications
You must be signed in to change notification settings - Fork 229
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
Arbitrage Bot #4656
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 264 years, 7 months from now. 1) arnab11917676 has applied to start work (Funders only: approve worker | reject worker). We are a group of web3 devs having expertise in building applications regarding web3 interaction. We saw your project and have figured out a plan to execute it with precision. We have been building a similar kind of product with the help of the rest API, Node.js and Python. We would really like to work with you if the opportunity is provided. I am experienced with arbitrage bots, and I have been working on the same project, and I would definitely completely on time. I have professional experience in building defi arbitrage bots at a arbitrage hedge fund. agoric17sv2y69mxympe69vecpk8h7ahmk5tjmsfsn7pj I have some experience with Agroic, this is an interesting project for me, so I come up with an initial idea:
Learn more on the Gitcoin Issue Details page. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 9600.0 USD (9598.08 USD @ $1.0/USD) has been submitted by: @jeetraut please take a look at the submitted work:
|
p.s. I (@dckc) suppose we reviewed |
Description
Build a bot which is able to arbitrage prices between a pool on Osmosis and a pool on the Agoric AMM.
To complete this bounty, you must demonstrate an off-chain bot which can make nearly simultaneous off-setting trades on the Agoric AMM and Osmosis DEX given a divergence in price.
Context
A goal of the Agoric AMM is to maintain prices that are inline with the external market. A tight coupling to external DEXes like Osmosis through arbitrage bots will help achieve this goal.
Acceptance Criteria
Approach validated by the Agoric team
Bot can recognize and act on a price deviation between its target pools simultaneously
Target pools are on unique L1 Cosmos chains connected by IBC (e.g., Agoric’s AMM and Osmosis)
Demonstration of arbitrage bot in local environment to the Agoric team
Time Estimation
3 weeks
Reward
$9,600
Payment will be made in USD (fiat currency) via wire transfer. The developer is responsible for providing their completed tax documents (W9 for US based developers and/or W8 or W8-BEN-E for non-US based developers) and providing their banking details in order to receive payment.
Applicant Assessment Criteria
Important: Please provide a clear workplan for how you will approach this bounty. Use the work plan as an initial demonstration that you would be a good candidate. Bounties will require coordination with the Agoric team, so unfortunately only plans submitted in English will be considered.
Applicants will be assessed based on the following criteria:
##Experience Write-up
As part of completing the bounty, we ask that you write up a short (or long!) summary of your experience building on Agoric. This is important feedback for us as we evolve the platform.
##Review Process
Agoric team reviews your submitted workplan on Gitcoin
It is best to join our Discord and post your gitcoin name in the bounties channel, so that we can follow up with you. Otherwise, we will write on your gitcoin profile wall and say hello!
Agoric contacts you to provide reference projects / sample code for engineering review
Introductory call to discuss your plans and expected timeline
You join the Agoric Discord bounties channel (if you haven’t done so already)
Agoric accepts you on Gitcoin and you get started!
References
Agoric.com/documentation
#bounties channel in Discord for general questions and your specific bounty channel for direct questions to the Agoric team
The text was updated successfully, but these errors were encountered: