[Nubot Gateway] Poloniex @zoro (sell offset:0.25% , buy offset:5% ) - stand by

[zoro]

This is the thread in order to make available the details about the passive Nubot gateway in Poloniex and to report the status and other information.
A level 3 account is created in Poloniex connected with my main account and secured by 2FA.

The Poloniex addresses that FLOT may use to send funds are:

BTC: 1FVEuU6FeUL7HyVq73gkBdVxN1AJGV7QVd

NBT: BEDJCrAZA9P7cvUm2vvSgkmEebVtKhZZ5V

[zoro]

I will use the config i see in MoD’s thread but i am not sure about the ‘priceincrement’

Moreover, the nubot will run with -skipCredential key since i have trouble with it! Liquidity will be reported though.

[masterOfDisaster]

A level 3 account is created in Poloniex connected with my main account and secured by 2FA.

The API credentials are “can trade” only, right? This is rather important.

I will use the config i see in MoD’s thread

The config you pasted is rather outdated. I could enable the parametric order book again, etc.
This assumes a Nu wallet in server mode is running on the same machine.
But I think that part of the setup is already complete, right?

I recommend to lean on this config:

{
“exchangename”:“poloniex”,
“apikey”: “redacted”,
“apisecret”: “redacted”,
“txfee”: 0.1,
“pair”:“nbt_btc”,

“dualside”: true,
“multiplecustodians”:true,
“executeorders”:true,
“verbosity”:“normal”,
“gitter”:true,
“mailnotifications”:“severe”,
“mailrecipient”:“redacted”,
“emergencytimeout”:60,
“keepproceeds”:0,
“priceincrement”: 0.002,
“bypassStreaming”: false,
“streamingServer” : “stream.tradingbot.nu:5556”,
“webport”:6667,

“submitliquidity”: true,
“nubitaddress”: “BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo”,
“nudip”: “127.0.0.1”,
“nudport”: 9091,
“rpcuser”: “redacted”,
“rpcpass”: “redacted”,

“wallchangeThreshold”: 0.1,

“bookDisabletier2”: false,

“bookSellwall”: 1500.0,
“bookSellOffset”: 0.01,
“bookSellInterval”: 0.002,
“bookSellMaxVolumeCumulative” : 6000,
“bookSellType”: “exp”,
“bookSellSteepness”: “high”,

“bookBuywall”: 1500.0,
“bookBuyOffset”: 0.01,
“bookBuyInterval”: 0.002,
“bookBuyMaxVolumeCumulative” : 6000,
“bookBuyType”: “exp”,
“bookBuySteepness”: “high”
}

The priceincrement seems to be effective only in sellside mode.

[zoro]

The API credentials are “can trade” only, right?

Exactly
Thanks for the new configuration.

[masterOfDisaster]

There was a recent issue with the strea server. I don’t know whether that’s been fixed.
@desrever, is
"bypassStreaming": false,
ok at the moment?

[zoro]

“multiplecustodians”:true,

This i needed as ‘true’? I have it ‘false’

[masterOfDisaster]

This is a requirement to use the stream server as far as I understand it. There might be more than one custodian running NuBot on the same exchange and order collisions can be prevented using the stream server and
"multiplecustodians":true,

[zoro]

“streamingServer” : “stream.tradingbot.nu:5556”,
“webport”:8889,

These are working for me.

[masterOfDisaster]

You can choose whatever webport you like.
Are you sure that the stream server is working? Does your NuBot move orders, if the BTC price moves?
That was the issue that made me bypass the stream server: the orders didn’t get moved…
Have you tested it?

Make your account empty as soon as you have finished the testing (or note the funds you had there). This will make accounting much easier. I only had $5 or so from testing on the accounts (because of the minimum to have NuBot place orders).

[zoro]

No, i haven’t. I have to sent some funds in order to test it!
the stream.tradingbot.nu:8889 is not working indeed.

[masterOfDisaster]

the stream.tradingbot.nu:8889 is not working indeed.

I think it’s for one the wrong port and totally not working at the moment in addition.
Try
"bypassStreaming": true,

[zoro]

Well, this is very strange!
stream.tradingbot.nu:5556 reports that connection is OK
but nubot is not placing any order!

stream.tradingbot.nu:8889 reports that it is NOT OK
but order are placed and liquidity is reported!

BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
“buy” : 0.0,
“sell” : 20.0

[masterOfDisaster]

“bypassStreaming”: true,

[zoro]

Now it is working

[zoro]

Isn’t better to lower the bookSellwall and bookSellMaxVolumeCumulative
in order to minimize the risk of funds after a nubot failure?
Considering that more nubots and ALPs exist in the field.
I am thinking of 500 and 2000.

[masterOfDisaster]

There are two risks:

• not deleted walls due to NuBot failure can cost some percent
• too small walls increase the risk for damaging Nu’s brand image

NuBot orders being filled means, the ALP before that failed.
I’d rather have some more funds than $500 in that line of peg defence at 1% offset (or 1.6% SAF).

That’s why I ended up with $1,000 from ine NuBot at 0.9% offset and additional $1,500 at 1.0% offset from the other one.
So in total $2,500 have been (and are still until my NuBots take a break) at approximately 1% offset most of the time after 2016-01-23.

The NuBots ran remarkably stable.
Each time their orders were traded, they made Nu money from the offset.
That could compensate parts of the hedging risks.

So my conclusion is: more funds on T1.1!
The parametric order book will make adjacent orders even more expensive

[zoro]

The main risk i see is a power and internet outage (during sleeping, Murphy’s law)
The orders will remain and in a big BTC volatility, NU’s funds will take a hit!
This can be reduced with small walls and a lot of different nubots.
Even different nubots (from different IPs) managing the same account will reduce this risk (i just made a feature issue in bitbucket)

[masterOfDisaster]

The orders will remain and in a big BTC volatility, NU’s funds will take a hit!

That’s the few percent I was speaking of. Not worth thinking about that for too long.
Even if you have in total $5,000 on orders on both sides and lose 1% or 2% of that by trading them too cheap, that’s just $50 or $100.

During volatile times you’ll likely lose more by being used for hedging if the NuBots are running properly.
So if the NuBots fail in such a time, it will be cheaper for Nu in terms of direct loss, although the peg might receive a dint.

[desrever]

There was a recent issue with the strea server. I don’t know whether that’s been fixed.

can set it to true now!

[masterOfDisaster]

The NBT already arrived on the account. I’m waiting for the BTC to arrive as well and withdraw funds from my accounts to FLOT afterwards:

Sun Feb  7 17:06:52 UTC 2016
status of zoro dual side gateway:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 57.505,
            "sell" : 5000.0

ninjaedit: that went fast:

Sun Feb  7 17:10:23 UTC 2016
status of zoro dual side gateway:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 5312.125,
            "sell" : 5000.0