Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 16 2015 10:14

    sammoth-wazoku on master

    changes to southx in light of s… (compare)

  • Oct 20 2015 08:38

    sammoth-wazoku on cybnate_logging

    add more logging to determine w… (compare)

  • Oct 17 2015 09:05

    sammoth-wazoku on master

    add traceback for debugging exc… (compare)

  • Oct 17 2015 09:00

    sammoth-wazoku on master

    add soutXchange wrapper added exception logging at end … change string formattnig in sou… (compare)

  • Sep 28 2015 07:14

    sammoth-wazoku on extra-cryptsy-logging

    add auto replace order for Cryp… (compare)

  • Sep 27 2015 18:43

    inuitwallet on extra-cryptsy-logging

    Update exchanges.py (compare)

  • Sep 27 2015 10:08

    inuitwallet on extra-cryptsy-logging

    Update client.py (compare)

  • Sep 26 2015 19:43

    sammoth-wazoku on extra-cryptsy-logging

    Add logging for Cryptsy orders (compare)

  • Sep 26 2015 19:43
    sammoth-wazoku added as member
  • Sep 24 2015 09:36

    inuitwallet on 0.121

    (compare)

  • Sep 24 2015 09:34

    inuitwallet on master

    alter server consditional (compare)

  • Sep 24 2015 07:51

    inuitwallet on 1.22

    (compare)

  • Sep 17 2015 18:50

    inuitwallet on master

    update gitignore file (compare)

  • Sep 05 2015 21:43

    inuitwallet on master

    update logging around sendinng … update example_config with pool… (compare)

  • Sep 05 2015 21:36

    inuitwallet on master

    added cryptsy wrapper as well a… addecd Cryptsy as wrapper in se… updated run_clent.py to allow f… and 8 more (compare)

  • Sep 05 2015 20:17

    inuitwallet on 1.3.0

    (compare)

  • Aug 29 2015 20:19

    inuitwallet on cryptsy_wrapper

    add method to interact with 'ca… tested cryptsy fees ethod again… (compare)

  • Aug 24 2015 19:13

    inuitwallet on cryptsy_wrapper

    update to allow setting reset_t… added offset as config paramter (compare)

  • Aug 18 2015 21:11

    inuitwallet on cryptsy_wrapper

    update place_orders method in c… (compare)

  • Aug 17 2015 21:29

    inuitwallet on cryptsy_wrapper

    updated cryptsy wrapper to veri… (compare)

inuitwallet
@inuitwallet
To get the branches merged for the nu-pool software, could you create a pull request? Then I can see what changes have been made and try and make it as smooth as possible to merge them.
Nagalim
@Nagalim
They aren't mergeab
They aren't mergeable. There are several key differences, but the ones that are the most interesting are fixed cost, shift, and fillfactor.
inuitwallet
@inuitwallet
cool. I will take a look at what youve done and see which ideas can be used in ALPv2
Nagalim
@Nagalim
Fixed cost is literally like a 2 line change, just changing the units of rate to nbt/day and dividing by liquidity provided
inuitwallet
@inuitwallet
sure. I have that in the new server already
Nagalim
@Nagalim
Shift trie to locally shift the price based on a custodian's personal buy/sell ratio
inuitwallet
@inuitwallet
I'm hooking into the price streamer server sao that NuBot and server are using the same price always
Nagalim
@Nagalim
And fillfactor simply limits the total funds put up, allowing people to run multiple nbt bots on one account for different units.
inuitwallet
@inuitwallet
that's pretty cool. the idea is to let NuBot handle all the order placing. NuBot already has params like that I would imagine.
Nagalim
@Nagalim
It's an intentional price shift that the client applies themselves. Basically, the custodian willingly reduces the spread to allow their average price to float more.
inuitwallet
@inuitwallet
it sounds like you've been actively developing the nu-pool software. I'm happy for your branch to take precedence over mine if that works for you?
Nagalim
@Nagalim
My stuff is soooo hacky. But yes, I would guess most LPs are currently using MoD's repository or mine.
O
How does the server credit? Is it based on threshold like the current servers? Like anything under 1.5% tolerance gets paid?
inuitwallet
@inuitwallet
yes. you set a threshold for the pair/side and anything that close to the peg is credited anything under isn;t
example config
Nagalim
@Nagalim
So a shift parameter is something where if you have 75% buy liquidity your buy orders will be closer to the price feed and your sell orders will be farther away.
Nagalim
@Nagalim
So if I'm not mistaken that config file is allowing for multiple ranks of liquidity provision? Like you get paid one rate at rank 1 and a different rate at rank 2?
If no one is in rank 2, does rank 2's money go to rank 1?
You could do it like this: Each rank has a different weighting factor
person A provides in rank 1 with $100 with weight 1, person B provides in rank 2 with $500 with weight 0.5. The normalization coefficient is therefore 1001+5000.5 = 350. Therefore, if the server is paying out 10 NBT/day, person A gets 101001/350 = 2.86 NBT and person B gets 105000.5/350 = 7.14 NBT
blech, stupid formatting
person A provides in rank 1 with $100 with weight 1, person B provides in rank 2 with $500 with weight 0.5. The normalization coefficient is therefore 100x1+500x0.5 = 350. Therefore, if the server is paying out 10 NBT/day, person A gets 10x100x1/350 = 2.86 NBT and person B gets 10x500x0.5/350 = 7.14 NBT
the idea being that rank 1 is at a closer spread than rank 2
CoinGame
@CoinGame
loving all the comments wooly
:thumbsup:
inuitwallet
@inuitwallet
I like the idea around weighting. I'd not originally intended for rank 2 to get any compensation but then thought that it may be beneficial and added it to th e config file.
Remember that this is intended for use with NuBot and the parametric order book so generally the user won't have total control over amounts placed in ranks 1 and 2. They can influence it though through the parameter they choose for their order book.
My rank 1 is just to compensate those funds directly supporting the peg. The rank 2 compensation does need more work. At the very least it needs a range rather than just being "anything outside of rank 1"
Nagalim
@Nagalim
Oh it's like that. I was hoping we'd have a large number of ranks, like 10 or 100
inuitwallet
@inuitwallet
Potentially we will. I'd like to get it working properly with 1 first though.
Nagalim
@Nagalim
Yah, for sure. So then the server can tell the client what the weight and price is for each rank, then the server can optimize to find the best slot using order books and histories and complex stuff
Then changes in the actual liquidity provided can feed back to the server and change the weights of each rank
inuitwallet
@inuitwallet
Potentially. The data is already there, it'll just be a matter of getting NuBot to consume it and Act upon it coreectly
Nagalim
@Nagalim
Specifically, increasing the weighting of the rank that gained provision and all ranks less than it and decreasing and higher ranks.
*decreasing any higher ranks
inuitwallet
@inuitwallet
Yup. Beyond that it will hark back to the original intent of balancing the liquidity across markets too. It in the road map for NuBot.
Nagalim
@Nagalim
Also, having some ranks at negative tolerance would not be amiss
Thanks for being awesome Sam, it sounds like the potential for alp 2.0 is vast.
inuitwallet
@inuitwallet
:) you're kind. I hope it works as planned. The system can already handle dynamically updating the parameters on the fly without needing a restart so we are making steps I the right direction.
Cybnate
@Cybnate
Awesome ^
JZA
@Jzarecta
How can someone copy their NuDroid address?
Willy
@bananenwilly
This is the nupool channel, are you sure you mean NuDroid?
Nagalim
@Nagalim
@inuitwallet can you kick assistant bot please?
inuitwallet
@inuitwallet
I'll give it a prod in a moment
Cybnate
@Cybnate
@inuitwallet, seeing that you are still around here. Can you please enlighten us on the situation here: https://discuss.nubits.com/t/passed-nupool-6/2781/45
Getting a bit worried