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)
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.
1 Like
can set it to true now!
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.0ninjaedit: 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
1 Like
I see the deposits in my account.
Thus the Nubot operation is officially started.
Liquidity:
“BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo” : {
“buy” : 5302.185,
“sell” : 5000.0
2 Likes
Right.
I decommissioned mine:
I hope that you will be back sooner. We will miss you 
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.6294Either 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.8147You 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.
2 Likes
Done! Thanks.
that was a “nice” bug
1 Like
All is good.
“BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo” : {
“buy” : 5324.775,
“sell” : 4999.8147
9 BTC are traded so far.
Deposit of 10 BTC by FLOT to nubot’s buywall.
BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
“buy” : 5550.105,
“sell” : 8530.9513
5000NBT have been sent back to FLOT.
BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
“buy” : 1248.3625,
“sell” : 7941.1504
Deposit of 13 BTC by FLOT.
BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
“buy” : 7600.495,
“sell” : 6441.1504
@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.1504I 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.
1 Like
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:
1 Like
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
2 Likes
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.0Now 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
1 Like
Poloniex seems to have solved the issues today.
[BTC] Bitcoin 12.52134310
On orders: 3.81117000
BTC value: 16.33251310
[NBT] NuBits 6438.15044906
On orders: 1500.00000000
BTC value: 20.35889507
[BTC] Bitcoin 12.62208310
On orders: 3.71043000
BTC value: 16.33251310
[NBT] NuBits 6438.15044906
On orders: 1500.00000000
BTC value: 19.79115855
1 Like