Current Liquidity

4005 NBT has been purchased with 10.2 BTC.


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

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?

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

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

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
1 Like

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

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

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.

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 :
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 []
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)

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

@woolly_sammoth @willy

NuBot related issues -> forwarding my ping to @desrever


I don’t see an issue.
It’s just like it was when I did the tests during creation of the gateways:
as long as the price doesn’t move enough to make NuBot cancel the orders and place them anew, NuBot doesn’t use funds that arrive at the account.

I restarted NuBot and the order was placed like intended. Have a look at the edited version of my last post.

Ok, feature request: some way to force fund placement when new funds arrive on exchange.

1 Like

Then you have a fill factor of 1000NBT for T1?
The rest are in T2?

you’re thinking the alp bot. This is Nubot, it works differently.

ok, then we have a problem when checking Alix’s T1 report!
It’s not “trustful” any more!

Yah, the nubot is using the parametric order book so the funds look spread out on the buy side and concentrated on the sell side.

I limited the order size to 1,000 USD value in the config to limit risk for Nu funds due to device or internet access issues.
If I’d let NuBot place all funds on orders, and my RaspberrPi crashed, or my internet access had an outage, the orders wouldn’t be shifted when the price moves, posing a risk to the funds.

Approximately 6.5 BTC have already been sold.
I’m going to withdraw the NBT to the T4 FLOT sell side address (BqyRzFtWXDmjxrYpyJD42MLE5xc8FrB4js), if there are no objections.

@JordanLee, would you prefer receiving the NBT instead to have some funds for propping up sell side on demand?
It has become quite obvious that the decentralized design of the FLOT doesn’t make it the ideal role to balance T1 liquidity…

1 Like