I don’t put advanced trading parameters in the guide. They’re in the config file, is that not verbose enough? These are advanced strategies, and they actually don’t really work if literally everyone does them. The idea is that these strategies only work if some custodians behave differently than others.
Btw, these strategies are also totally applicable to any other pool, not just nupond. This particular one is taking advantage of the fixed cost deal, but shifts and fillfactor are totally applicable on any other pool.
This is really twisted. Lasttime when I tried shift I didn’t understand all its behavior, part of the reason being no clear document partly might be that the version of software i checked out didn’t work. I never knew. It was frustrating to be a lab rat. Do you want people to use your s/w or do you not?
Did fillfactor work out alright? I haven’t wired shift out to all the config files properly, so you are right that it is undocumented. I’ll do some updates to the github. Sorry that you got frustrated.
There actually has been an update that makes it work on both sell and buy side and I should probably have documented that as such. With numbers it would be like: if you have a fill factor of 20 and you have 100 NBT in your account it will put up 20 NBT. If you have a billion NBT in your account, it will still only put up 20 NBT. If those 20 NBT are sold, it will put up another 20. Nubot will make this feature completely obsolete, but it’s useful in the current ALP incarnation for running multiple pools on one account at the very least. At the best, it’s a T2 strategy.
What would be the best way to explain this to users?
So what I really need to do is one last complicated updated. In this update I should upgrade shift and the fill parameter into a list or something. I want to have buy fill and sell fill separately controllable and I want to allow users to have both auto and manual shifts with individual magnitude for each. Then I’ll get on the documentation for real.
thanks!
I am trying this fillfactor, it is working great!
I have an idea about this fillfactor. What if we can make it work between our NBT wallet and the exchange?
I guess it could be like transferring from T3 --> T1 thus eliminate T1+T2 fund risks due to exchange’s hack!
The downside will be the time refilling sell side (some minutes due to transferring) and some other risks i cannot think of.
I’m still updating. I pushed an update, but the config files didn’t update properly. Still, the trading.py and client.py should now support the above parameters.
I pushed this update about a minute ago. I’ll work on a patch tomorrow morning for the config files and double check a couple things. Download at your own risk or whatever.
Only the Bter config files are properly formatted, all other pools won’t work properly (I think the program probably crashes) because the fill factor needs to be a dictionary. I suppose I probably should have made it support the old style, but I didn’t. Anyway, this update is basically feature complete as far as my efforts on this software go. I will still debug and what have you, but I’m not going to be adding any additional config parameters beyond these.
This is not correct. Deviation is complicated and I’d rather the custodian just use the numbers I provided. The example would be 0.0025 would mean a change in price of 0.25% would cause the bot to replace the orders at the new price.
Shift causes the ‘price’ that orders are placed at to be different from the ‘price feed’.
I’m going to go ahead and call it a requirement, but it’s actually written incorrectly. Honestly, it should just be:
Missed it in t he notification area due to flot activities.