Current Liquidity

Liquidity
#783

Fixing the flow is the solution.
Having 2 or 3 of 8 addresses with some funds on them should be a viable workaround.

#784

I imagine FLOT will usually be a lot quicker than 24–48 hours, but the delay concerns stated should be addressed anyway.

I have to say I’m uncomfortable with only 2-of-8 if that approach would go forward. Can you motivate it? 3-of-8 seems much safer with only one more, which I hope wouldn’t affect response time very negatively. Not that I think anyone is about to run away with funds, but I’d plan around the possibility whenever feasible.

I didn’t catch how those times would be applied. What should happen if FLOT takes 30 minutes, and when it takes 30 hours?

Procedure

  1. Establish terms between FLOT and @zoro (does your role have a title?).
  2. FLOT receives NBT corresponding to the amount of BTC agreed to trade.
  3. FLOT sends BTC to @zoro (plus compensation for volatility during signing delay?).
  4. @zoro applies liquidity.

Anything more?

At how many confirmations should we consider a transaction secured?

Proposals

There was an alternative suggestion at 10 BTC, but it’s better they explain it themselves.

1 Like
#785

The procedure is ok.
(1) and (2) could be very fast, matter of minutes.
(3) needs the most time since it needs 5 FLOT members to sign the transaction
but by the time the transaction is signed, BTC could have been changed and thus one side
would gain and the other would loose, probably. More time, bigger the risk.
(4) is lighting fast, since the addresses i use is polo’s and thus the bot take care of liquidity.
Polo needs one confirmation for BTC and 10 for NBT. We can keep the same scheme :wink:
This procedure could be applicable with every ALP and MLP custodian.

#786

no buy fund inject to polo?

#787

Share that nervousness, a little less risk given the fund sizes would be better. 3-8 at least, maybe we need to add more FLOT members in order to end up with more ‘quick’ signers?

1 Like
#788

While the overall liquidity (T1-3) accross all exchanges still is ok:

 nud getliquidityinfo B
{
    "total" : {
        "buy" : 69398.9089,
        "sell" : 60111.108
    },
    "tier" : {
        "1" : {
            "buy" : 16292.832,
            "sell" : 15043.2682
        },
        "2" : {
            "buy" : 8974.59,
            "sell" : 5759.4757
        },
        "3" : {
            "buy" : 41807.8606,
            "sell" : 31556.0
        }
    },

The situation at Poloniex isn’t looking very well:

Pasted image916×439 55.5 KB

Pasted image1410×745 78.1 KB

However the spiking BTC price emptied the buy side (T1) on Poloniex to a level that calls for action. Is anybody willing to trade funds with FLOT or @JordanLee to put them in a liquidity operation on Poloniex’ buy side? @zoro maybe?
@henry any chance to balance walls at Poloniex? The buy side really needs some funds.

update:

Pasted image917×431 56.5 KB

There’s almost no volume on buy side within the spread left on Poloniex. There might be in total 34 BTC on buy side, but at rates way beyond what Nu considers pegged to USD.

2 Likes
[Discussion] Tier 7 liquidity: Volume-dependent transaction fees and "Restricted Network Access" status
#789

I am currently serving as a backup to FLOT’s tier 4 buy side support, and I plan to activate in that role when buy side drops below 35%, as it is currently. I see FLOT is in the process of trying to negotiate a trade, and that ought to continue. I will start with buying 4,000 NBT where the BTC proceeds will show up on the Bter buy wall. I will leave all other balancing efforts up to FLOT.

2 Likes
#790

NuLagoon will be promoting 20 BTC to Poloniex soon.

We also suggest the community have some try on other exchanges, such as HitBTC, so we can avoid letting the most NBT trading depending on one exchange.

2 Likes
#791

and bter.com

2 Likes
#792

4005 NBT has been purchased with 10.2 BTC.

2 Likes
FLOT BTC Operations (buy side)
#793

Glad to see some action :smile:
BTER has rebalanced itself, somehow :wink:

#794

Once again Polo’s buy side has problem. i have sent a pm to Jordan to do something about it ASAP :wink:
We need to introduce a pay scheme in Poloniex to pay ALPs depending on the liquidity.
I guess a “special” fixed cost scheme?

FLOT BTC Operations (buy side)
#795

So other than paying more to the weaker side (already covered under fixed cost) what other modifications would you make?

#796

I was thinking for an unbalanced payout depending on the sell/buy liquidity amounts.
Fixed cost has fix payouts for either side, correct?

#797

The amount is fixed while the rate is not. Basically, if you provide on the buy side when it’s at 10% and the sell side is at 90%, you’re getting 9x higher rate than those on the sell side.

If you’re looking to compensate the heavy side more (so the above situation is only 4.5x instead of 9x) we would be moving back toward fixed reward. If you’re looking to compensate the weak side more (so the above situation becomes 18x instead of 9x) that would indeed need a specialized and exaggerated implementation of fixed cost.

I think for now we should just try the normal fixed cost and see what happens. Currently, polo is operating under fixed reward still.

1 Like
#798
1 Like
#799

25 BTC just arrived at @masterOfDisaster’s NBT exit gateway.

[Passed] NBT entry gateway on Poloniex provided by @masterOfDisaster
#800

What happened to it? Did it get sold?
There is now a 31 BTC sell wall…

#801

It hasn’t gone up on the pool yet. That’s a shame, MoD is using nubot I think so it shouldn’t be a software error.

#802

I can confirm that the funds arrived.
I just checked NuBot. It’s running:


20:05:20.259 [checkNud] INFO  - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
20:05:50.259 [checkNud] INFO  - Executing class com.nubits.nubot.tasks.CheckNudTask [com.nubits.nubot.tasks.CheckNudTask:37]
20:05:52.842 [Strategy Secondary Task] INFO  - Sell-Wall size :  : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:538]
20:05:52.847 [Strategy Secondary Task] INFO  - Buy-Wall size :  : 0.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:543]

It looks like the BTC have not been placed in orders, because the price didn’t move.
I will restart NuBot…

edit - restarted:

20:11:45.917 [Strategy Secondary Task] INFO  - BUY- OrderBook : ----- BUY-side order book :
0.993996,0.00250062,1000.0
BUY wall volume : 1000.0
BUY tier2 volume = 0.0 NBT
Total BUY volume = 1000.0 NBT
Best price :0.00250062 (0.9939964499999999$)
BUY balance left = 8937.78576275 NBT-----  [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:227]
20:11:45.925 [Strategy Secondary Task] INFO  - Trying to place 1 orders... [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:228]
20:11:46.265 [Strategy Secondary Task] INFO  - BUY wall order updated. ID : 766461833 size: 1000.0 [com.nubits.nubot.trading.TradeUtils:231]
20:11:46.281 [Strategy Secondary Task] WARN  - **BUY** orders re-initialized on  **poloniex** :  1/1 placed successfully
total amount placed : 1000.0
Tier1 order size : 1000.0
Tier2 cumulative order size : 0.0 (0 orders)
 [c.n.n.s.S.StrategySecondaryPegUtils:246]

The liquidity is being broadcast:

 nud getliquiditydetails B | grep "BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" -A 17
    "BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
        "1:NBTBTC:poloniex:0.3.2a_1449088964364_c6087a" : {
            "buy" : 0.0,
            "sell" : 0.0
        },
        "1:NBTBTC:poloniex:0.3.2a_1449605416734_d024e4" : {
            "buy" : 1000.0,
            "sell" : 0.0
        },
        "2:NBTBTC:poloniex:0.3.2a_1449088964364_c6087a" : {
            "buy" : 0.0,
            "sell" : 0.0
        },
        "2:NBTBTC:poloniex:0.3.2a_1449605416734_d024e4" : {
            "buy" : 8937.79,
            "sell" : 0.0998
        }
    },

poloniex:0.3.2a_1449088964364_c6087a is the previous session

NuBot development roadmap - From 0.1 to 1.0