Someone would have to write a wrapper for alp and nubot. For ALP it currently looks like that someone will be @thecrema and it will be next when southx is completely finished and reviewed.
NuBot and pybot are running along on poloniex pretty well. More than one pybot is the usual situation with an ALP. Syncing the clients on start is one of the measures to prohibit discrepancies.
If you’re planing to run more than one alp server on one pair, I would have to tell you that this something I am not a fan of. It’s quite untested and users can easily cheat by submitting to all servers on the pool.
definately not running multiple ALP operators. That’s not currently doable with integrity. Multiple MLPs though is a very real possibility.
We should talk to HitBTC about getting rewarded for our ALP pool. If HitBTC could enter contract with us to burn a certain amount of NBT every month that our ALP pool is successful (by most measures it tends to do very well) it would certainly draw shareholder interest. @tomjoad what’s the best way to aim for that? We might want to wait to get a wrapper going and be listed with MLPs before we try to bargain with them, but it might not be bad to reach out from the start.
I have even less experience (=0) with NuBot, but hey, others did that before and I’m sure there are some manuals and maybe even someone offering some guidance.
NuBot does run fine on a RaspberryPi(2), right?
…because I wouldn’t want to run that on a virtual server (only if RPI2 is no option).
I’d be willing to be either LP in an ALP, ALP operator if necessary or trying to get a grant passed for being NuBot operator on HitBTC (as soon as wrappers are available).
After all you best learn things if you try…
…and with BCE it will be necessary to get familiar with NuBot!
Update: The exchange is in contact with me and has confirmed that NBT has been added internally on their exchange. We’re discussing when the announcement can occur. I’ve seen some good guesses recently and hope it will be announced very soon.
It’d be best to wait until you see what the exchange is and then make a proposal.
Even if HitBTC is not the exchange that is (already) planning to include NBT it’s an interesting looking exchange.
So whether or not it will be HitBTC to list NBT next, I’ll keep an eye on it and consider getting in contact with them regarding NBT
I had problem with the wrappers (poorly documented API in some case), been waiting for a reply for their engineers . Now I have all I need to complete it.
It runs on a raspberry and I am sure you can operate it very easily: minimal configuration just require you to set five parameters and be reassured I can help anytime
I suggest you read the complete SETUP.md tutorial anyway (will change soon to this) .
As willy was saying, there’s no way to stop people from cheating and submitting to all operators on a single pair. To fix that we’d need the operators to talk to each other and that gets complicated. The only reason we don’t have this with MLP / ALP combo is because MLP’s are trusted not to cheat. Theoretically they could though.
Maybe we could make some competitive ALP motions and let shareholders decide? If you’d rather not do that I can take btc cause it’s already up. I’d be offering a 1.2% SAF I think because the fee is only 0.1% instead of 0.2%. It’d be fun to try fixed cost on this pool and bter at the same time. Otherwise, I could do something like 0.25%/day with 2,000 NBT targets for starters.
Anyway, the wrapper won’t even be started until the one for southx is finished and reviewed, so we have time for discussion for sure.
Welcome @HitBTC! I’ve had the pleasure of communicating with them the past couple weeks and they are indeed the mystery exchange in question. I’m looking forward to a productive partnership emerging with HitBTC, starting with the introduction of liquidity operations when NuShareholders make a decision on a provider.
