ALix Panel

Liquidity
#1

Hey,

at the request of the community (mainly @nagalim and @masterOfDisaster) I’ve created a new page that shows NuBits liquidity calculated with reported liquidity from the client and gathered liquidity from ALix Walls.

Give it a go and tell me what you think about it:

https://alix.coinerella.com/panel

The two left buttons at the bottom let you chose whether you want the totals to be calculated with ALix Walls T1 or T1 reported in the client.

Development costs are currently 350 NBT. I’ll post a custodial grant request when the community is satisfied with the software.

Thanks

Willy

6 Likes
[Passed] ALix Panel fee request
#2

One step further towards convenient control of the liquidity situation.
This control needs to be available to anyone interested in the well-being of Nu and mustn’t be put on the shoulders of few.
Thank you very much for your efforts!

#3

To include a part of a private conversation:
I’d really appreciate if it’d be possible to have another option next to

  • “Use ALix Walls data for T1” and
  • “Use reported liquidity for T1”
    :arrow_right: " Use ALix Walls for T1 PLUS include Nu gateway funds at T1.2"

###My reasoning is this:
while the gateway funds are ideally not really T1 (at best T1.2), the orders provided by the gateways get automatically replenished when consumed (even when only in parts).
So the T1.2 (and even T2) from the gateways should be included in the calculation, because these funds are automatically promoted to T1.2 and availabe to support the peg.

###Problems identified for doing that:
There’s no easy way to gather liquidity information from the gateways.
At the moment there are 3 in operation, all at Poloniex.
This status will change over time.

To include this liquidity information (just in case somebody finds it useful…), there are some things that should be considered:

  • the information should be provided via json to make including it by ALix easy
  • ideally each gateway uses a broadcast address that is only used for reporting the gateway liquidity
  • the gateway addresses need to be kept up-to-date
  • updating the script/addresses needs to be possible by several people

This leads me to the question:
can this be done by hosting and automatically updating a repo at github?
The idea would be to have a script run the evaluation locally and automatically upload the data json formatted to github - e.g. by crontab.

Data according to ALix (“Use ALix Walls data for T1”):

Pasted image829×652 46.9 KB

Data according to my script:

Fri Mar 11 09:30:18 UTC 2016

status of the gateways in total:
bid total 31752 USD, bid side ratio 65%
ask total 16578 USD, ask side ratio 34%

status of the ALP last 15 minutes:
bid total 34050 USD, bid side ratio 38%
ask total 55529 USD, ask side ratio 61%

status of the ALP last 4 hours:
bid total 37436 USD, bid side ratio 42%
ask total 51147 USD, ask side ratio 57%

status of the total liquidity; gateways and ALP (last 15 minutes):
bid total 65802 USD, bid side ratio 47%
ask total 72107 USD, ask side ratio 52%

status of the total liquidity; gateways and ALP (last 4 hours):
bid total 69188 USD, bid side ratio 50%
ask total 67725 USD, ask side ratio 49%
[/quote]

2 Likes
[Passed] Sell side Nubot gateway (BTC/NBT) on SouthXchange @zoro
#4

You forgot 2 more in Hitbtc, one in operation and the other idle :slight_smile:
eidt:
and i forgot the nubot’s by Nulaggon :stuck_out_tongue:
1 in Poloniex and 1 in Hitbtc

#5

That’s why distributed updating it is necessary :wink:
Can you please provide me with the NBT address and the thread?

Currently included:

Fri Mar 11 09:45:15 UTC 2016
status of mOD dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
        "BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
            "buy" : 14647.34,
            "sell" : 5809.8706
status of zoro dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
        "BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
            "buy" : 17119.25,
            "sell" : 8903.8829
status of Cybnate dual side PyBot at Poloniex:
nud getliquiditydetails B | grep B954pkUEdkeT1G5Lq14Cisij5no3RVxHYe -A 20 | grep poloniex -A 2
        "1:NBTBTC:poloniex:LiquidBits" : {
            "buy" : 0.0,
            "sell" : 266.6667
#6

as you wish:


#7

Do you use “BA8di3FFBADAFQmRwEqiAocrkBoMDPBQQu” to broadcast liquidity for HitBTC?
It doesn’t appear in the output of getliquidityinfo B

#8

Not yet. My bot is idle atm. Zero funds.

#9

Is it idle meaning not running, or just not able to place orders?
Not seeing a liqudity broadcast leads me to the assumption the NuBot isn’t running.

When I had NuBots on standby, I funded them with a few USD and let them run. This way you can more or less track the function of the NuBots in “active standby” by looking at the broadcast liquidity (and changes of the values).

Having a NuBot in “active standby” is less important for hitBTC as it is for Poloniex in my opinion, because sell side only operations are less important for the peg than the dual side ones.

But Nu still needs to advertise that:
“Folks, be aware that Nu doesn’t ensure a peg at exchanges except for place A, place B and maybe place C, but will offer NBT for sale as long as supply lasts at place D, place E, etc.!”

I think there’s not yet consensus about what I consider an evolution of the liquidity provision scheme.

2 Likes
#10

this

#11

that :wink:

#12

@nagalim recently asked for a custodian / motion list as a backup for blockexplorer.nu.

I could include that into ALix Panel, but not with those fancy trending arrows that blockexplorer.nu has, as I’m not planning to record a history database for this.

It would be a list of the last 10k blocks, ordered by voting percentage.

This data would also be provided as JSON.

I suppose this would require 3-4 hours of work.

Any comments?

#13

Much more accurate than Coinmarketcap.com

Thx

#14

That should be sufficient to track progress.

One type of historic information is useful, though:
I’d be happy to find a motion/grant that passed listed together with the block number in which the majority of votes was reached.

That is something blockexporer.nu offers as well and which makes it easy to verify motions/grants with
getmotions [<block height>] [<block quantity>]
`getcustodianvotes [] []``

#15

Do I get that information out of the client or do I have to track those separately?

I never played much with the getmotions RPC call.

#16

How do you calculate

if not by issuing getmotions or getcustodianvotes RPC calls?

As soon as a percentage is above 50%, note the block height at which the 50% were surpassed.

#17

That’s not what I meant, I mean getting a history list of passed motions. Does the getmotions RPC call provide that till infinity or only for the last 10k blocks?

#18

Ah, got it!
With getmotions and getcustodianvotes you should be able to search for a rolling window of any size beginning at any block

#19

I’ll play with that in the coming days, thanks.

#20

voting panel.png1893×930 121 KB

last 10k

1 Like