Here is the output from my Nu client:
“version” : “v2.0.1-beta”,
“protocolversion” : 2000000,
“walletversion” : 1,
“walletunit” : “S”,
“balance” : 0,
“newmint” : 0.0,
“stake” : 0,
“parked” : 0.0,
“blocks” : 903260,
“moneysupply” : 822750103.91840005,
“connections” : 12,
“proxy” : “”,
“difficulty” : 0.00021675,
“testnet” : false,
“keypoololdest” : 1409216713,
“keypoolsize” : 501,
“paytxfee” : 1.0,
“unlocked_until” : 0,
“errors” : "
Is is a linux machine or has a bash?
If yes, this command should show the liquidity. It’s broadcast by NuBot.
nud getliquidityinfo B | grep B9gXptkoqAApF3AFrQyhUbhSzvuEudxupt -A 2
Ah, I understand: you’ll find only $400 included in the T1 report, because only the first order is reported as T1. All other orders, even on the order book are reported as T2.
Right, a bit odd, but that explains it.
With the current session ID you’ll find the details - I hope you are on bash 
nud getliquiditydetails B | grep B9gXptkoqAApF3AFrQyhUbhSzvuEudxupt -A 1000 | grep 0.4.1_1464903918569_e146d4 -A 2
"1:NBTBTC:poloniex:0.4.1_1464903918569_e146d4" : {
"buy" : 0.0,
"sell" : 800.0
--
"2:NBTBTC:poloniex:0.4.1_1464903918569_e146d4" : {
"buy" : 0.73,
"sell" : 10233.3128I’ve decided that not being able to track the liquidity of each of my NuBots is bad.
Unfortunately I have only one NBT custodial address to broadcast the liquidty.
If you use getliquidityinfo to track the liquidity, you see the combined liquidity of my three NuBot gateway (2 at Poloniex, 1 at hitBTC).
If you are on a system with a bash (or another shell that’s alike), you can filter it conveniently this way:
nud getliquidityinfo B | grep B9gXptkoqAApF3AFrQyhUbhSzvuEudxupt -A 2
The result of that output is:
nud getliquidityinfo B | grep B9gXptkoqAApF3AFrQyhUbhSzvuEudxupt -A 2
"B9gXptkoqAApF3AFrQyhUbhSzvuEudxupt" : {
"buy" : 21433.12,
"sell" : 25111.0935If you want to have a more precise overview, you need to investigate the output of getliquiditydetails.
This is just a quickly hacked together script that does that on bash:
An output of that would look like this:
status of mOD NuBot session at hitbtc:
"1:NBTBTC:hitbtc:0.4.1_1464952860644_29cdbc" : {
"buy" : 0.0,
"sell" : 500.0
--
"2:NBTBTC:hitbtc:0.4.1_1464952860644_29cdbc" : {
"buy" : 1365.38,
"sell" : 418.265
status of mOD NuBot session at poloniex:
"1:NBTBTC:poloniex:0.4.1_1464943832235_3ba051" : {
"buy" : 500.0,
"sell" : 2000.0
--
"2:NBTBTC:poloniex:0.4.1_1464943832235_3ba051" : {
"buy" : 19622.05,
"sell" : 11160.2103
status of mOD NuBot session at poloniex:
"1:NBTBTC:poloniex:0.4.1_1464903918569_e146d4" : {
"buy" : 400.0,
"sell" : 800.0
--
"2:NBTBTC:poloniex:0.4.1_1464903918569_e146d4" : {
"buy" : 22.2,
"sell" : 9815.3268
status of zoro NuBot session at poloniex:
"1:NBTBTC:poloniex:0.3.2a_1464953175077_595d35" : {
"buy" : 750.0,
"sell" : 1500.0
--
"2:NBTBTC:poloniex:0.3.2a_1464953175077_595d35" : {
"buy" : 16556.52,
"sell" : 17929.8288Unfortunately I don’t know how to tell my two NuBots at Poloniex apart.
The one that was started after the other always has the latest broadcast session.
I fear, they can only be told apart by the order sizes.
The one with
the closer spread has the buy order size 400, sell order size 800, the one with
the bigger spread has the buy order size 500, sell order size 2,000
The one with the tight spread is currently out of buyside funds. There’s no BTC on the order book.
T2 is partially on the order book, but only the first orders (the ones with the tightest offset) are reported as T1 by NuBot.
I guess you cannot use my latest grand address which i don’t use to report liquidity.
do you want to send you the private key?
No, I don’t want that.
You’ve been trusted with it. You need to keep it confidential.
But thank you for your confidence.
Could you post data for the last 24hrs?
To make it one more post, that needs to be moved:
don’t I interfer with the NuBot at 0.35% sellside, 2% buyside offset?
OK, so the problem is: I have 10K in NBT right now. And I really want to sell 1500, but I can’t. So while price stability looks good…there is no liquidity.
How do we get back liquidity when BTC is on a run?
We need more USD/NBT gateways.
The low liqudity is a direct result of the big buyside offset.
If it were lower, we had liquidity, but would soon run out of BTC.
The demand for NBT is low, because BTC is on the rise.
That would of course help; if they were really used they’d be even more helpful.
https://alix.coinerella.com/volume/gui_index.php doesn’t show much trades in fiat pairs.
But the NBT/USD pair is very important - after all NBT is pegged to USD! Supporting a tight peg on that pair without volatility risk is easy as pie.
So the question remains: I have NBT & I want BTC, but how do I get it?
There’s more than 1.5k NBT on the buy side on polo. It’s just at a spread you have no taste for.
T6 leveraging is an intentionally slow process. If we want more reserves we should make a motion like:
“Every week, increase the target reserve by 0.25% of outstanding NBT until it reaches 30%.”
This will leverage the market more rapidly.
Option 1) put them on order for sale and wait until the orders get filled. Can be automated by using NuBot and afaik you are able to run it; NuOwned operations rarely made NBT sale in the last 7 days, though.
Option 2) buy from the buy orders, that are on the orde books; the byuside offset can be significant - depending on where and how fast you want to get rid of the NBT
SouthXchange has some BTC on order at a not so big offset - the orders are within the spread within orders get reported by ALix:
“Every week, increase the target reserve by 0.25% of outstanding NBT until it reaches 30%.”
This I like.
My NuBot with tight offsets sold 24 NBT!
Sellside balance went from 9,815 NBT to 9,791 NBT.
…maybe not worth mentioning it, but as it’s a kind of good news…
Fri Jun 3 17:12:46 UTC 2016
status of mOD NuBot session at hitbtc:
"1:NBTBTC:hitbtc:0.4.1_1464952860644_29cdbc" : {
"buy" : 0.0,
"sell" : 500.0
--
"2:NBTBTC:hitbtc:0.4.1_1464952860644_29cdbc" : {
"buy" : 1413.66,
"sell" : 418.263
status of mOD NuBot session at poloniex:
"1:NBTBTC:poloniex:0.4.1_1464943832235_3ba051" : {
"buy" : 500.0,
"sell" : 2000.0
--
"2:NBTBTC:poloniex:0.4.1_1464943832235_3ba051" : {
"buy" : 20338.09,
"sell" : 11160.2103
status of mOD NuBot session at poloniex:
"1:NBTBTC:poloniex:0.4.1_1464903918569_e146d4" : {
"buy" : 400.0,
"sell" : 800.0
--
"2:NBTBTC:poloniex:0.4.1_1464903918569_e146d4" : {
"buy" : 61.78,
"sell" : 9791.227
status of zoro NuBot session at poloniex:
"1:NBTBTC:poloniex:0.3.2a_1464953175077_595d35" : {
"buy" : 750.0,
"sell" : 1500.0
--
"2:NBTBTC:poloniex:0.3.2a_1464953175077_595d35" : {
"buy" : 17172.37,
"sell" : 17929.8288btc price has just fallen from 590 to 565 on bitfinex.
on polo nbt price is
Polo NBT last : 0.00174088 lowestAsk : 0.00174556 highestBid : 0.00173214
polo nbt 574.422 572.882 577.321
that is 0.9% spread BEFORE fee
I see $1100 buy orders on nbt/btc. But why alix is giving 0 buyside? @willy
The buy offset should be a function of BTC’s increasing velocity!
But then again the speculation remains. Can this offset be covered with a future BTC increase?
That makes the function dynamic and very complicated!
@zoro, it might be time to increase the buyside offset.
You start running out of BTC:
Mon Jun 6 08:11:54 UTC 2016
status of zoro dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
"BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
"buy" : 7204.24,
"sell" : 30719.8262