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

[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

[zoro]

I see the deposits in my account.
Thus the Nubot operation is officially started.

Liquidity:
“BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo” : {
“buy” : 5302.185,
“sell” : 5000.0

[masterOfDisaster]

Right.
I decommissioned mine:

[Accounting] (Former) NBT entry/EXIT gateway (now dual side)

Status of the former gateways at 2016-02-07, 17:54 UTC I started the decommissioning of my NuBots, because @zoro’s NuBot is operational and funded and I will be away for two weeks. Important notice: The NuBots I operated are out of order as I can’t monitor them until further notice. I will try to have one on active standby for emergencies only. If I manage that, there will be an update in the respective thread. BTC rate: $376 Sun Feb 7 17:54:56 UTC 2016 Account activity (former) sell s…

[zoro]

I hope that you will be back sooner. We will miss you

[masterOfDisaster]

Is it possible that you had to restart NuBot after a non-graceful shutdown?
The broadcast liquidity seems to be derailed (double of your funds):

nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 10536.885,
            "sell" : 9999.6294

Either the session 0.3.2a_1454879153200_c90bc9 or 0.3.2a_1454882815146_effce8 is erroneously still broadcasting liquidity.

nud getliquiditydetails  B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 200 | grep 0.3.2a_1454879153200_c90bc9 -A 2
        "1:NBTBTC:poloniex:0.3.2a_1454879153200_c90bc9" : {
            "buy" : 1500.0,
            "sell" : 1500.0
--
        "2:NBTBTC:poloniex:0.3.2a_1454879153200_c90bc9" : {
            "buy" : 3747.95,
            "sell" : 3499.8147
-----------------
nud getliquiditydetails  B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 200 | grep 0.3.2a_1454882815146_effce8  -A 2
        "1:NBTBTC:poloniex:0.3.2a_1454882815146_effce8" : {
            "buy" : 1500.0,
            "sell" : 1500.0
--
        "2:NBTBTC:poloniex:0.3.2a_1454882815146_effce8" : {
            "buy" : 3738.99,
            "sell" : 3499.8147

You can reset the wrong session with

nud liquidityinfo B 0 0 BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo $nubot_session

if you replace $nubot_session with the session you want to reset.

[zoro]

Done! Thanks.
that was a “nice” bug

[zoro]

All is good.

“BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo” : {
“buy” : 5324.775,
“sell” : 4999.8147

[zoro]

9 BTC are traded so far.
Deposit of 10 BTC by FLOT to nubot’s buywall.

BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
“buy” : 5550.105,
“sell” : 8530.9513

[zoro]

5000NBT have been sent back to FLOT.

BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
“buy” : 1248.3625,
“sell” : 7941.1504

[zoro]

Deposit of 13 BTC by FLOT.

BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
“buy” : 7600.495,
“sell” : 6441.1504

[masterOfDisaster]

@zoro, please have an eye on the Poloniex situation.
The ALP buy side is quite thin (between only $2k and $4k for more than 12 hours) and the BTC price might be moving upwards creating more pressure on the buy side.
The reported liquidity of your NuBot is balanced, but the buy side has only a few $k:

nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 7712.995,
            "sell" : 6441.1504

I can’t keep a close eye on it where I am and I’m not sure whether the other FLOT members who hold BTC keys do.

So I beg you to keep an eye on it.

Without NuLagoon being active on Poloniex (the T1 buy side orders reported here
https://alix.coinerella.com/walls/?4h are ALP only; no MLP buy side support from NuLagoon) the funds on your NuBot are an important defence layer for the peg on Poloniex.

[zoro]

I have some API connection issues and i have to keep restarting the bot today to avoid hanging orders.
I monitor especially the buy side closely.
I am also providing some ALP funds there as a first layer of defence
But ALP has the same connection issues! These days are hell
We need another nubot!
please vote for it:

[Passed] Passive Liquidity Source on Poloniex: @Nagalim

Reference: Proposal RIPEMD160 hash: 92263daf3b89a605f9302ad212d12799c0c7bcee =##=##=##=##=##=## Custodian Hash starts with this line ##=##=##=##=##=##= Custodial Address: BN3XDdiNQw858WWpPEZ3kVr5WsgwYjMRy3 Amount Requested: 1 NBT Intro @Nagalim - below called "the operator" - will run a NuBot on Poloniex. The liquidity is being broadcast using a custodial address to allow tracking the liquidity situation of the bot. The operator promises to send all withdrawn funds to a FLOT multisig…

[huafei]

news from polo

We are under heavy loads at this time. We are addressing the issue and working on resolving this as soon as possible. Thank you for your understanding and apologies for the inconvenience.Posted by InfiniteJest at 2016-02-12 11:57:21

[masterOfDisaster]

ALP volume almost zero according to
https://alix.coinerella.com/charts/?select=48_hours_nupool_poloniex#

What about your NuBot, @zoro?
The broadcast liquidity doesn’t make sense:

nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 57.505,
            "sell" : 0.0

[zoro]

Now they start working again. But Polo is very unstable.
Funds are safe, i hope.

[BTC] Bitcoin 16.25497896
On orders: 3.88167000
BTC value: 20.13664896

[NBT] NuBits 4941.15044905
On orders: 1500.00000000
BTC value: 16.88347914

we are fine