The release we are currently working on turned out to be a major release rather than a small plugin.
Changed 0.2.0.5 ----> 0.3.0, and adapted overall roadmap.
Stay tuned
1 Like
This is so cool. I would really like to look a bit further again into using the NuBot in the TLLP client. The greatest problem here is that events that the TLLP client recognizes cannot be communicated with the NuBot (except killing it, changing the config, and starting it again).
Is it planned to implement some interface to modify the config parameters interactively? In particular we would need to specify the fund limits on the fly, since this can happen every 15 seconds.
2 Likes
Wow, the GUI is amazing. The things that are being done here are absolutely MASSIVE and so many people have yet to discover it.
2 Likes
Definetly a feature of parametric order books, can be implemented earlier if needed. how would you imagine it working from TLLP perspective?
However you prefer 
Give me a socket, a memory map, a ProcessQueue or simply reparse the config file from time to time. I just need to tell the nubot that it must not place more than X NBT on the buy or sell side right now.
That s impressive, to say the leastā¦
If nu shareholders can find a way to make liquidity provision a predictably profitable business (which i believe they will), your GUI will definitively democratize it.
Comment here and Iāll try to squeeze it into 0.3.1 : https://bitbucket.org/JordanLeePeershares/nubottrading/issue/707/make-an-entry-point-to-change-maxsell-and
The GUI in NuBot is very nice and highly desirable to attract new users. The merge of NuBot and TLLP would be awesome, but I can see that there are many hurdles to overcome given the different architectures of the two. Happy to be surprised though.
Looks impressive
Updated roadmap in view of recent changes and imminent release of 0.3.1
1 Like
Iām curious is @benjyz still part of NuBot development team?
Is http://metaexchange.io project related to Nu, where @benjyz put his efforts lately?
Hi @Mark. Iām not on the NuBot team anymore. The collaboration in form of my contributing to NuBot ended 1 month ago. I was happy to be able to work on NuBot. Metaexchange.io is my private commerical project unrelated to Nubits. It is a centralised exchange which I have been working on and off for almost 2 years. Iāve used some of my code and experience for NuBot, e.g. a Bitcoin API in Java. Also centralised exchanges can learn some things from NuBits. Happy to discuss if there a other ways to collaborate in a new thread.
1 Like
I am wondering about the current status of NuBotās development fundingā¦and how it will be funded over the next months because this piece of software developed mainly by @desrever is essential to Nu.
Also, is book mirroring still on the agenda?
Hi @cryptog, after a 1 month break I am resuming works on NuBot today.
I have a strict agenda now where high priority is given to Parametric order books (aka 0.3.2) : there is a list of open issues approved for work you can filter on bitbucket : https://bitbucket.org/JordanLeePeershares/nubottrading/issues?milestone=0.3.2+-+Liquidity+distribution+model+(t2)&status=open&status=new
Letās get to work
3 Likes
By the way, though it should be in another thread, how does NuBotās development get funding?
The same way as coredev and marketing I guess
1 Like
Good to see that the NuBot development goes on.
Is this idea still being followed[quote=ācreon, post:28, topic:1175ā]
I would really like to look a bit further again into using the NuBot in the TLLP client.
[/quote]
or did the approaches stop with @creon leaving?
Iām asking because of the tier 3 management options that are planned to be made available with version 0.3.4.
It would increase the security of funds by far if they could be held in tier 3 in times where the bot canāt place orders for a reward (or less reward than the taste of the liquidity provider requires).
To decrease the reward that is paid for liquidity providing by making liquidity providing less risky, that function would need to be included in the TLLP bot as well and not only in NuBot.
Ideally both bots would be merged (if technically feasible).
Nu assumes that B&C Exchange will mitigate the exchange default risk by far and reduce the costs of liquidity providing.
I think that assumption is valid.
But I also think that Nu should offer the tools for the safest possible way of providing liquidity at other exchanges as well - or shall Nu solely rely on B&C Exchange?
Liquidity providing at centralized exchanges might be necessary for some more time, I think.
1 Like