16:35:21.197 [priceTriggerTask] INFO - Price Updated. bitfinex:1 BTC = 422.99 USD [com.nubits.nubot.tasks.PriceMonitorTriggerTask:359]
16:35:36.668 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
16:35:58.290 [Strategy Secondary Task] INFO - Sell-Wall size : : 500.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:539]
16:35:58.300 [Strategy Secondary Task] INFO - Buy-Wall size : : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:544]
16:36:06.668 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
16:36:36.668 [checkNud] INFO - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
16:36:39.707 [Strategy Secondary Task] INFO - Sell-Wall size : : 500.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:539]
16:36:39.718 [Strategy Secondary Task] INFO - Buy-Wall size : : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:544]
16:36:42.176 [checkOrders] WARN - Liquidity info submitted:
tier=1 buy=0.0 sell=500.0 identifier=1:NBTBTC:hitbtc:0.4.1_1458757219123_4f225b response=true
tier=2 buy=0.07 sell=1499.936 identifier=2:NBTBTC:hitbtc:0.4.1_1458757219123_4f225b response=true [c.n.n.t.CheckOrdersTask:142]
Based on the trading volume I don’t see a reason for sending another 1,000 NBT there.
But I’m a fan of redundancy.
Is that redundancy currently worth 100 NBT per 60 days? If yes, I’d withdraw 1,000 NBT to FLOT to keep the exchange default risk the same as it is now.
I’d like to hear opinions from other FLOT members before I’m going to sign it.
Putting money on the buy side as well provides an incentive for using NBT as BTC volatility hedge.
Do we really want to provide incentives for that?
Or do we want to offer NBT for sale for people who want to actually use them (for more than just hedging BTC volatility risk…)?
From the trading volume on hitBTC you can make a guess what NBT traders are after!
In fact NBT on sell side only supported exchanges still can still be used to hedge BTC volatility, but not as convenient as at dual side supported exchanges: the NBT must be sent to an exchange with a supported buy side,
Well, given the current situation it isn’t urgent but nmei’s gateway has also starved for a while. The formal activation is going to be triggered by FLOT deposit so there’s no hurry, but seeing no discussion on e.g. the amount of funds to send I had to raise this before start.
Right, but then @nmei put the operation on hold, because of absence and I took the liberty to step in with an offer that was accepted.
So currently there’s sell side liquidity at hitBTC:
##2) Rationale for signing this tx @zoro’s gateway has an empty buy side while a 13.2 BTC deposit (approx 6,000 NBT value) is withheld.
This tx helps moving BTC from NuLagoon to @zoro’s gateway without creating imbalance in the sides.
After this tx went through there’s little reason in the field of balancing that can stop from depositing 13.2 BTC to @zoro’s gateway.
It is because the external data could not be loaded due to connection problems with the blockexplorer (as always) and cointoolkit only show the tx data (output amount). Not knowing the input, it can not compute the fee.