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

Nud connectivity issues again?
Liquidity broadcast is stuck at

nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 19759.3,
            "sell" : 6000.0

It is ok. I don’t see a problem.

Strange. I see it moving now as well, but the last time I looked, the “buy” of my NuBot moved (while the “sell” stayed the same) and yours didn’t.
Maybe I just didn’t look right.
Sorry for the inconvenience!

Do you still have

 "wallchangeThreshold": 0.1,

in your config?
It looks like your NuBot is more “lazy” with moving orders and reporting adjusted liquidity for some reason. A different setting for "wallchangeThreshold" could be a reason. I have it at 0.1 and have

  "bypassStreaming": false,

This is what I mean:
###My buy side moved from 14470.03 to 14440.26. Yours didn’t move:

Tue Mar  8 07:55:47 UTC 2016
status of mOD dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
        "BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
            "buy" : 14470.03,
            "sell" : 5700.9277
status of zoro dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 19557.04,
            "sell" : 6084.7662
Tue Mar  8 08:22:47 UTC 2016
status of mOD dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
        "BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
            "buy" : 14440.26,
            "sell" : 5700.9277
status of zoro dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 19557.04,
            "sell" : 6084.7662

###My buy side moved from 14466.53 to 14405.23. Yours didn’t move:

Tue Mar  8 08:37:39 UTC 2016
status of mOD dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
        "BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
            "buy" : 14466.53,
            "sell" : 5700.9277
status of zoro dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 19509.65,
            "sell" : 6084.7662
Tue Mar  8 08:58:21 UTC 2016
status of mOD dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
        "BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
            "buy" : 14405.23,
            "sell" : 5700.9277
status of zoro dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 19509.65,
            "sell" : 6084.7662


I am using nubot v0.3.2a
Are you using the new RC2 version?

[BTC] Bitcoin 34.39800505
On orders: 12.99003185
BTC value: 47.38803690

[NBT] NuBits 84.76621963
On orders: 6000.00000000
BTC value: 14.76675405

I switched to 0.4.1-RC2 only recently.

@zoro, your NuBot stopped broadcasting liquidity:

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

Yes, API connection issues. i am checking it now.

Looks fixed.
The liquidity situation immediately looks better:

I didn’t do anything else than a few restarts. It seems it was a connection issue between me and Polo :slight_smile:

Today, the 30 running days of Nubot from grant:


are over.
I believe that FLOT + Nubot had a great performance keeping the peg in Poloniex :slight_smile:
According to above grant i will kindly ask from FLOT to sent me 249 NBT as payment in the same grant
address: BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo

Nubot will keep running unless the following motion (for Nubot term 2) will not pass in due time.

1 Like

[BTC] Bitcoin 34.44525463
On orders: 12.94278227
BTC value: 47.38803690

[NBT] NuBits 84.76621963
On orders: 6000.00000000
BTC value: 14.75221146

[BTC] Bitcoin 29.69843368
On orders: 12.82233293
BTC value: 42.52076661

[NBT] NuBits 2108.87497096
On orders: 6000.00000000
BTC value: 19.38791461

[BTC] Bitcoin 23.60863926
On orders: 12.68031352
BTC value: 36.28895278

[NBT] NuBits 4756.48548275
On orders: 6000.00000000
BTC value: 25.46823824

@zoro, keep your NuBot running!
Your NuBot, @Cybnate’s PyBot and my NuBot are the only defense for the peg on buy side at the moment at Poloniex!

ALP failed and NuLagoon has no orders there:

nud getliquiditydetails B | grep "BTRnV9uLSPVJw4jn1JMV2Ki2cfFqPYip9o" -A 100 | grep polo -A 2
        "1:NBTBTC:poloniex:0.3.2a_1454163803748_1106ef" : {
            "buy" : 0.0,
            "sell" : 0.0
--
        "1:NBTBTC:poloniex:0.3.2a_1454167693921_6457fb" : {
            "buy" : 0.0,
            "sell" : 0.0
3 Likes

sadly, this is the norm!

Under the circumstances i am going to alter the “Buy Orderbook Offset” from 0.01 --> 0.014
for as long as the buy wall has low liquidity.

Edit: Done.
Now Alix will probably show zero or very low buy wall but don’t be afraid :wink:

1 Like

Thank you!
This makes the importance of the gateways even more visible, by making the failure of ALP more visible!
…keep yours running! :wink:

[BTC] Bitcoin 22.51613765
On orders: 12.97339828
BTC value: 35.48953593

[NBT] NuBits 5094.32064847
On orders: 6000.00000000
BTC value: 26.96474633

configuration is kept the same

[BTC] Bitcoin 22.60981194
On orders: 12.87972399
BTC value: 35.48953593

[NBT] NuBits 5094.32064847
On orders: 6000.00000000
BTC value: 26.70979884