Project title: Kelp as a Service Summary: SDEX markets need liquidity. Spinning up Kelp is tough. I'd like to help with both. Goals: Provide a quick and easy way for people to use kelp. Increase SDEX market liquidity. Timeline: Initial design review (~ 2 weeks) Alpha task definitions & release (~ 1 month) Beta task definitions & release (~ 1 month) General release (~ 1 month) Description: From a high level, I plan on spinning up simple servers running Kelp instances in docker that are configured from a web app UI (NodeJS/React). The UI will provide the ability to select the tradeable asset pair and spread. I'd also use the stellar from the community fund to get them started.

StellarZac I could get started on the design review and maybe spin up a very, very alpha example frontend. Some more details on the various stages: Initial Design Review: I'd create a google slide deck with the proposed infrastructure and basic wireframe design/walkthrough of the front-end. I imagine I'd get that done in a day or two, but would appreciate feedback from stellar (and other community) devs. Alpha task definitions & Release: From the initial design review, I'd create a Github roadmap with associated issues for each task. I've spun up similar services in the past, so I guesstimated approximately 1 month of time to: a. Spin up the underlying infrastructure in AWS. b. Build out the very premature service with: i. Authentication ii. New Stellar account generation (I don't want to request/store people's other private keys) iii. Basic ability to spin up/shut down kelp (only testnet, hardcoded asset pairs) Beta task definitions & Release: Again, based on the initial design review and any new tasks which have surfaced from the Alpha release, I guessed around another month for: a. Creating pre-baked configurations for people to use (XLM -> LTC, XLM -> USD, etc) b. Building out the front-end for user's to select custom configurations, and getting docker startup to utilize these configurations. c. Creating a feed the user's Stellar account's trades and such. i. Possibly providing some sort of view into the (soon to be released) Kelp front-end for each docker container. General Release: a. Fix bugs found in Alpha & Beta b. Continue adding new functionality suggested in Github Issues c. Develop some sort of system for XLM matching for deposits? ("We will give you 100 XLM if you deposit 10000!") That's about all I've brainstormed so far. Let me know if I need to clarify, but it's all still very early stage

hello i really need help with the kelp trading bot. I don't know how to install and used it. Its level of complexity do not allow me to provide the market with liquidity. If someone could help me with that I will be greatly appreciates it. My public address is GDIQN3BCIF52R5WDMTPWUSN7IM3ZNQYYRWEWR2I7QX7BQUTKYNU2ISDY.

Kelp as a Service

alexgandy

Project title:
Kelp as a Service

Summary:
SDEX markets need liquidity. Spinning up Kelp is tough. I'd like to help with both.

Goals:

Provide a quick and easy way for people to use kelp.
Increase SDEX market liquidity.

Timeline:

Initial design review (~ 2 weeks)
Alpha task definitions & release (~ 1 month)
Beta task definitions & release (~ 1 month)
General release (~ 1 month)

Description:
From a high level, I plan on spinning up simple servers running Kelp instances in docker that are configured from a web app UI (NodeJS/React). The UI will provide the ability to select the tradeable asset pair and spread. I'd also use the stellar from the community fund to get them started.

BGold

Yes, I want this!

StellarZac

Could you flesh this proposal out with more details on how you plan to accomplish this timeline. Will you have a live element for review before voting begins?

alexgandy

StellarZac I could get started on the design review and maybe spin up a very, very alpha example frontend.

Some more details on the various stages:

Initial Design Review: I'd create a google slide deck with the proposed infrastructure and basic wireframe design/walkthrough of the front-end. I imagine I'd get that done in a day or two, but would appreciate feedback from stellar (and other community) devs.
Alpha task definitions & Release: From the initial design review, I'd create a Github roadmap with associated issues for each task. I've spun up similar services in the past, so I guesstimated approximately 1 month of time to:
a. Spin up the underlying infrastructure in AWS.
b. Build out the very premature service with:
i. Authentication
ii. New Stellar account generation (I don't want to request/store people's other private keys)
iii. Basic ability to spin up/shut down kelp (only testnet, hardcoded asset pairs)
Beta task definitions & Release: Again, based on the initial design review and any new tasks which have surfaced from the Alpha release, I guessed around another month for:
a. Creating pre-baked configurations for people to use (XLM -> LTC, XLM -> USD, etc)
b. Building out the front-end for user's to select custom configurations, and getting docker startup to utilize these configurations.
c. Creating a feed the user's Stellar account's trades and such.
i. Possibly providing some sort of view into the (soon to be released) Kelp front-end for each docker container.
General Release:
a. Fix bugs found in Alpha & Beta
b. Continue adding new functionality suggested in Github Issues
c. Develop some sort of system for XLM matching for deposits? ("We will give you 100 XLM if you deposit 10000!")

That's about all I've brainstormed so far. Let me know if I need to clarify, but it's all still very early stage

alexgandy

^ See what I mean?

@NoelMartialNguemechieu Sorry, this isn't the right place for help with Kelp, but good luck.

DrewPalmer

You might want to think hard about 4c. I'm now an extra two months behind on development because anything like that probably requires a Money Services provider license if anyone involved is in the U.S. and that's taking me awhile to get approved even with clean records and 3 attorneys. There is zero chance that Paypal could start today, or even blue chip stamps or frequent flyer programs without years of red tape. I do like 2(b)(ii) and hate 2(b)(iii) - though I assume the latter is just for the test phase. Add XMC to 3(a) even just for testing and I'll send you 100K XMC to use and keep for testing. We won't be on IDAX until October or CoinMarketCap until November-ish, but at least you can play around. drew@marscoin.com

alexgandy

DrewPalmer Thanks for the response.

4c: I'm totally willing to scratch the idea and use the funds for infrastructure costs. I really appreciate the input and insight.

2iii. I meant more from a development stand-point. The ability to start/stop docker containers from the UI, without diving into the weeds of passing custom configs from the UI. But yes, definitely just a test phase thing.