When I wrote that, there was no liquidity provision by Nu.
That’s what I wanted to achieve with this thread/announcement without the need of going through a motion.
A lot of NSR holders are lazy!
May they create a motion to steer FLOT away from being responsible, or acting based on discretion, repectively.
FLOT needs to do a lot from monitoring the liquidity situation over crafting and signing tx to fill gateways and balance liquidity to trying to improve the situation.
If NSR holders are too lazy to craft a motion, FLOT can take care.
It’s not about taking power aways from NSR holders.
It’s about involving them beyond configuring votes!
Maybe I just lean back for a while and look what happens.
Shareholders are shareholders and mostly passive even though they are supposed to be active to some extent.
Besides that some won’t have the knowledge or experience or time to obtain it to craft a meaningful motion.
I’m more than happy to have FLOT craft motions, I’m concerned about taking away voting power from Shareholders.
Maybe we need to revisit the governance model again. Look at the Swiss, referenda are mostly crafted by professionals paid for doing so and voted in once in I believe 4 years (can’t find a source quickly), but even individuals can still submit proposals when at a certain threshold. Either way both types of proposals are voted for by all citizens.
In my opinion this is a truly democratic model and Nu should take it as an example. Maybe this needs a separate thread…
Nobody can take away voting power from NSR holders and I say FLOT will always follow passed motions.
This was never my intention and I didn’t propose it that way.
It’s silly that FLOT needs to craft motions to improve things, while NSR holders can stay passive.
NSR holders are in charge, they are responsible!
If we compare Nu to a standard share corporation, we might say that FLOT has been elected to act - in parts - on behalf of NSR holders.
Unfortunately these parts are not strictly defined to leave room for discretion, to keep FLOT able to react in case of unforeseen circumstances.
Is it really up to the FLOT to define what they are responsible for?
Anyway, I’ll stop here.
Don’t expect motions regarding this topic in near future from me.
May the NSR holders do the work.
It’s about their property.
It is time for NU to have an elected board of directors making decisions that need immediate action.
Could FLOT be this board?
Don’t expect NSR holders to govern every “little” aspect of NU.
Just in case it’ll be used, I’ll finish the gateway.
At the moment it’s not online, although testing is complete.
I will change the status of the gateway soon and update this thread.
I don’t know why NuBot has trouble broadcasting liquidity, but this isn’t working like expected:
20:10:39.185 [checkOrders] WARN - Liquidity is not being sent : orders are not yet initialized [c.n.n.t.CheckOrdersTask:145]
20:12:49.186 [checkOrders] WARN - Liquidity is not being sent : orders are not yet initialized [c.n.n.t.CheckOrdersTask:145]
20:14:59.186 [checkOrders] WARN - Liquidity is not being sent : orders are not yet initialized [c.n.n.t.CheckOrdersTask:145]
20:17:09.186 [checkOrders] WARN - Liquidity is not being sent : orders are not yet initialized [c.n.n.t.CheckOrdersTask:145]
The order (9.99 NBT) is on the book - I checked on Bittrex.
Checking the health status and the liquidity isn’t possible without the broadcast.
Will keep you updated.
edit:
restarted NuBot, issue fixed:
Wed Mar 16 23:59:01 UTC 2016
status of Bittrex sell side gateway by mOD:
nud getliquidityinfo B | grep BETwD8nSjtj9ADSvej2na34xmsMYwPRymv -A 2
"BETwD8nSjtj9ADSvej2na34xmsMYwPRymv" : {
"buy" : 0.0,
"sell" : 9.99
At the moment there are issues at Bittrex.
From NuBot:
10:45:47.486 [checkOrders] WARN - Liquidity is not being sent : orders are not yet initialized [c.n.n.t.CheckOrdersTask:145]
10:46:01.675 [priceTriggerTask] WARN - Shift needed on **bittrex** - Reason : BTC price changed more than 0.1 % [c.n.n.s.S.StrategySecondaryPegTask:199]
10:46:01.681 [priceTriggerTask] WARN - Cannot shift walls, orders are being reinitiated. Price is already adjusted. [c.n.n.s.S.StrategySecondaryPegUtils:297]
10:46:01.687 [priceTriggerTask] ERROR - Wall shift failed [c.n.n.s.S.StrategySecondaryPegTask:208]
10:46:01.698 [priceTriggerTask] INFO - New price computed [Thu Mar 17 10:46:01 UTC 2016,bitcoinaverage,BTC,422.1,USD,0.00244681,0.00229211,] [com.nubits.nubot.tasks.PriceMonitorTriggerTask:483]
10:46:01.715 [priceTriggerTask] ERROR - The Fetched Exchange rate data has remained outside of the required price band for 61seconds.
The bot will notify and restart in 183.0seconds. [c.n.n.t.PriceMonitorTriggerTask:249]
10:46:01.722 [priceTriggerTask] ERROR - Notifying HipChat [c.n.n.t.PriceMonitorTriggerTask:250]
I still have trouble broadcasting liquidity, but the bot itself is running.
I had to switch back to nud 2.0.3 because of trouble with nud 2.1.1 and NuBot…
I agree there’s demand for some liquidity at Bittrex, and altough this gateway will only support the sell side, it’s very useful.
But like I stated in the OP:
The current order related settings are:
Here’s an excerpt from the current run:
23:59:29.176 [Strategy Secondary Task] WARN - Initializing strategy [c.n.n.s.S.StrategySecondaryPegTask:137]
23:59:29.184 [Strategy Secondary Task] INFO - setting up ordermanager [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegTask:138]
23:59:29.189 [pool-1-thread-1] WARN - Subscribing to websocket push updates from streamer @ tcp://stream.tradingbot.nu:5561 [c.n.n.s.Subscriber:103]
23:59:29.204 [Strategy Secondary Task] INFO - Sell-Wall size : : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:539]
23:59:29.214 [Strategy Secondary Task] INFO - Buy-Wall size : : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:544]
23:59:33.702 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
23:59:34.835 [Strategy Secondary Task] INFO - initOrders SELL [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:178]
23:59:35.238 [Strategy Secondary Task] INFO - The current balance equivalent 9.99 NBT is not enought to place the full SELL wall defined in the liquidity model (500.0).
Resizing the size of the order [com.nubits.nubot.trading.LiquidityDistribution.LiquidityDistributionModel:153]
23:59:35.248 [Strategy Secondary Task] WARN - The balance is not enought to place the tier2 liquidity. (Balance is entirely on tier1 wall) 9.99 [c.n.n.t.L.LiquidityDistributionModel:241]
23:59:35.258 [Strategy Secondary Task] INFO - The current balance equivalent 9.99 NBT is not enought to place the full SELL wall defined in the liquidity model (500.0).
Resizing the size of the order [com.nubits.nubot.trading.LiquidityDistribution.LiquidityDistributionModel:153]
23:59:35.275 [Strategy Secondary Task] INFO - SELL- OrderBook : ----- SELL-side order book :
1.017501,0.0024291,9.99
SELL wall volume : 9.99
SELL tier2 volume = 0.0 NBT
Total SELL volume = 9.99 NBT
Best price :0.0024291 (1.017501408$)
SELL balance left = 0.0 NBT----- [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:228]
23:59:35.282 [Strategy Secondary Task] INFO - Trying to place 1 orders... [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:229]
23:59:36.027 [Strategy Secondary Task] INFO - SELL wall order updated. ID : f5974fdb-75cf-4551-88b3-a23aaebbdcf1 size: 9.99 [com.nubits.nubot.trading.TradeUtils:232]
23:59:36.048 [Strategy Secondary Task] WARN - **SELL** orders re-initialized on **bittrex** : 1/1 placed successfully
total amount placed : 9.99
Tier1 order size : 9.99
Tier2 cumulative order size : 0.0 (0 orders)
[c.n.n.s.S.StrategySecondaryPegUtils:247]
00:00:03.702 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
00:00:29.509 [checkOrders] WARN - Liquidity is not being sent : orders are not yet initialized [c.n.n.t.CheckOrdersTask:145]
00:00:33.702 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
00:00:47.256 [Strategy Secondary Task] INFO - Order placed = OrderToPlace{type=SELL, pair=nbtbtc, size=9.99, price=0.0024291} [com.nubits.nubot.models.MultipleOrdersResponse:88]
00:00:47.263 [Strategy Secondary Task] INFO - Order ID = f5974fdb-75cf-4551-88b3-a23aaebbdcf1
[com.nubits.nubot.models.MultipleOrdersResponse:89]
00:00:47.275 [Strategy Secondary Task] INFO - initOrders BUY [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:178]
Exception in thread "Strategy Secondary Task" java.lang.NullPointerException
at com.nubits.nubot.utils.Utils.getDouble(Utils.java:224)
at com.nubits.nubot.trading.wrappers.BittrexWrapper.getAvailableBalance(BittrexWrapper.java:218)
at com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils.initOrders(StrategySecondaryPegUtils.java:185)
at com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils.placeInitialWalls(StrategySecondaryPegUtils.java:142)
at com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils.reInitiateOrders(StrategySecondaryPegUtils.java:120)
at com.nubits.nubot.strategy.Secondary.StrategySecondaryPegTask.initStrategy(StrategySecondaryPegTask.java:144)
at com.nubits.nubot.strategy.Secondary.StrategySecondaryPegTask.run(StrategySecondaryPegTask.java:70)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
00:01:03.702 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
00:01:33.703 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
00:02:03.702 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
Unfortunately you are wrong.
I’m trying to tackle two issues which are not related to the type of machine NuBot is running on.
I have a fix for one issue, but not the other.
nud uses IPv6, although I compiled it without IPv6 support; NuBot doesn’t connect to the IPv6 address and the RPC port isn’t open on IPv4
Bittrex has trouble with the API stuff that prevents orders from entering the “initialized” state:
I can fix 1. using a RPC connection to a remote nu client (2.0.3) with IPv4 only support
But the Bittrex issue seems to be a general issue
If you can run NuBot at Bittrex and have NuBot broadcast the liquidity, I’m all ears!
