[Passed] NuPond Term 5 Grant

[Nagalim]

I’m not sure I understand what you’re implying. That the CNY pairs are all higher priced than the USD pairs?

[huafei]

yes , so we can buy nbt as usd to buy BTC and sell BTC to cny .

[Nagalim]

I’ll have to think about this. You’re essentially saying that I’m providing an arbitrage route for the whole cryptoeconomy of china, which is definitely a valid point. Whether that’s a good thing or a bad thing, however, I’ll have to think about, and if there is a reasonable solution to this.

[Cybnate]

This grant passed.

[Cybnate]

[zoro]

@Nagalim,
too late to change it to fixed cost? It could solve the balance issue in this btc/cny pair

[Nagalim]

I’m not done troubleshooting fixed cost.

[zoro]

i am seeing this error continuasly for NBT/CNY pair

and i think this is the reason that my balance (payout) is always zero although orders are indeed set !
For other pairs this error is less frequent.

[Nagalim]

This shouldn’t cause your balance to be zero. I’m pretty sure this is a bter issue, my mobile app (bitcoin checker) also has issues updating price feeds from Bter, occasionally throwing errors out while other exchanges don’t do anything of the sort. Of course, that app is completely third party and has nothing to do with Nu, so I’m reasonably convinced this is a Bter issue. Again, it shouldn’t be failing to credit you, that is probably another issue.

I could be completely wrong, but this issue didn’t come about until recently and I actually haven’t changed the CNY server software in a very long time.

[zoro]

yes, you are right. it should be BTER’s issue. i see those messages also in BTC/NBT pair but my balance payout is correct for this pair!
Strange!

[huafei]

Is that cny pool and btc pool payout together when i set the same NBT address?

[Nagalim]

They shouldn’t be, they’re separate instances of the script.

[Nagalim]

I don’t want to make this official because I’d really rather keep the deviation up, but you can use this for now:

Determines window of allowed price deviation

deviation = 0.0005

Determines market spread

offset = 0.005

[zoro]

what this means and what is the purpose?

[masterOfDisaster]

The smaller deviation makes cancelling and placing orders more agile - if I understood that part right.

[Nagalim]

I’m abusing the parameters to squeeze out 0.1% more offset. These parameters are for the cny bot not the btc bot.

[masterOfDisaster]

I’m abusing the parameters to squeeze out 0.1% more offset.

…compared to the standard settings for the bter cny operation.

I wouldn’t call it abusing - it’s still within the limits of the operation, right?
It makes adjusting orders to changed price more agile and the increased offset reduces the loss for liquidity providers - or even allows them to make money with this offset!
This is necessary to make the LPs keep up the walls.

edit:
To make it clear:

Spread After Fees: 0.4%

With an offset of 0.004 and a fee of 0.2% (0.002) the deviation of 0.0015 is small enough to keep the orders within the spread after fees: 0.004-0.002+0.0015=0.0035.
With an offset of 0.005, a fee of 0.002 and a deviation of 0.0005 the result is the same: 0.005-0.002+0.0005=0.0035.

I only wonder about one thing:
isn’t the “spread after fees” twice the [offset - fee + deviation]?
In that case both settings would be outside the 0.4%

[Nagalim]

SAF is purely 2*(offset-fees). Deviation will not ever decrease your spread, but only allow your price to drift some from the server price. This is an abuse of the parameters because it will most likely cause more bugs in the long term but we’re getting killed by the arbitrage on Bter (i.e. the pools are getting out of balance). The CNY bitcoin exchanges have been very pumpy these last few days.

[Nagalim]

Ok, new update: https://github.com/Nagalim/alp-collection

I’ll change the tolerance later, and maybe do some other things, but here’s how you use this update. Basically, strategically you have nothing to do from the default parameters but decrease the spread, so this method will decrease SAF. Try parameters like these (SAF = 0.2%):

Determines window of allowed price deviation

deviation = 0.0005

Determines market spread

offset = 0.003
shift = 0.002

[Nagalim]

NBT are getting eaten on the CNY orderbook at high prices. I plan to increase the tolerance to 3%, possibly even 5%. I will either suggest or automate a reasonable shift parameter for use with that high a tolerance.