We don’t have a reply yet by woolly_sammoth. It could be an error!
It can’t be very bad to keep some distance from mid price with this last resort.
@Cybnate’s PyBot will keep a tighter offset, because the PyBot runs within limits of the ALP server.
So there will be a “tiered” offset scheme, sorted by offset:
ALP -> @Cybnate’s PyBot -> your NuBot -> my NuBot
The pybot cybnate is running is off her personal server script. She can make the tolerance anything she wants. Shes not trying to get compensated via alp.
let me change it a little
Cybnate’s PyBot -> zoro NuBot -> ALP -> MoD NuBot
And we also have to take the new Poloniex’s fee model into consideration.
https://poloniex.com/fees/
Yes, we do.
At first glance it’s for the benefit of Nu, because Nu is with the liquidity provision scheme on the “maker” side (for which fees were reduced by 0.05%).
It’s good to make “takers” aware (by increasing the fee by 0.05%) that they need to pay for the “service” of others who provide liquidity.
Maybe I should increase the bot offset to 0.025
My bot is the ideal playground as I expect it to be discontinued quite soon - no later than 2016-04-19
15 BTC have been withdrawn to FLOT:
This was done by my discretion to balance the liquidity situation:
I recommend an appropriate deposit of NBT in turn. Maybe I can craft a tx later.
Would be good to deposit NBT to @zoro’s and my gateway in the same tx as he followed the recommendation to balance as well.
2 Likes
The funds arrived and are used by NuBot to support the peg:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
"BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
"buy" : 15070.68,
"sell" : 15727.2174I’ve received 5 BTC on Poloniex, which were automatically recognized by NuBot and included in the liquidity broadcast (without NuBot restart):
Mon Apr 11 10:04:25 UTC 2016
status of mOD dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
"BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
"buy" : 15857.27,
"sell" : 16850.23422,100 NBT have been withdrawn to BqyRzFtWXDmjxrYpyJD42MLE5xc8FrB4js with tx ID a87a496d5bb7da4792937668c7b542ed69288854bc726e2562d0133df4dc5b7d (that withdrawal went through very fast - almost instantly! Poloniex seems to have reworked the withdrawal system and not only the web interface…).
Coinpayments link
http://blockexplorer.nu/ offline; I might update the link later
New liquidity status of the gateway:
Mon Apr 11 10:16:24 UTC 2016
status of mOD dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
"BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
"buy" : 15857.27,
"sell" : 14750.2242
2 Likes
7,000 withdrawn to FLOT NBT address. Tx ID 03120193798906607c694ad4f1c1bb9565d0b151e0eedb75180c99e64666746d
blockexplorer.nu
coinpayments.net
Request for deposit of 16.5 BTC in exchange (based on an exchange rate of 424 NBT/BTC follows).
edit:
16.5 BTC credited by Poloniex and automatically put on order by NuBot.
Results:
Thu Apr 14 17:44:20 UTC 2016
status of mOD dual side NuBot at Poloniex:
nud getliquidityinfo B | grep BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP -A 2
"BFGMPykfKxXZ1otrCZcsbnTwJjKHPP9dsP" : {
"buy" : 15525.63,
"sell" : 15463.67282016-04-25
Decommissioning of the gateway has been initiated:
The funds on the account exceed my daily withdrawal limit.
I’ve requested a withdrawal of all BTC funds and 10,000 NBT:
30.35 BTC to FLOT multisig address 3HikFkS2Zinab1TJq7dqp6wSPyLu7i7bhe; tx ID 019e9bf9e4bd93444192a3a31326af75c43c63719f589d81d4f61f9142ff0e67
10,000 NBT to FLOT multisig address BqyRzFtWXDmjxrYpyJD42MLE5xc8FrB4js; tx ID 5cf7ccc3f856a4ccf786c1ad1bb95fddd79131c66bf37194944f21486a7b5809
8,354 NBT wait for the reset of the withdrawal limit to be withdrawn.
The gateway operation ended on day 6 after the grace period was over.
Based on a daily fee of 15 NBT
I’ll create a grant for 90 NBT.
I could have taken the fee from the account funds in compliance with the motion, but as I need a new liquidity broadcast address in a few weeks anyway (my current one is soon 6 months old), making a grant seems to be the clean way.
2 Likes
2016-04-26
8,354 NBT to FLOT multisig address BqyRzFtWXDmjxrYpyJD42MLE5xc8FrB4js; tx ID f8a5d428eee000a2ba7f28b236178fc3ea749261fca40a716cf23100215f0d54
The gateway is on unattended standby from now on.
2 Likes
This gateway is one of the last lines of defence (currently operating at 7.5% buyside offset) since 2016-05-27.
But liquidity broadcasting has been disabled to make tracking the liquidity status of the NuBot gateway, that tries to tighten the spread and revive trading on Poloniex, easier.
I thought I might give a quick report here.
Unfortunately I only have one NBT address, that can be used to broadcast liquidity at the moment (“B9gXptkoqAApF3AFrQyhUbhSzvuEudxupt”), otherwise I’d just let the two NuBots just use two different ones.
It would have been useful to track all activity related to this account here right from the start. I didn’t think of that earlier. I’m sorry for that.
07:32:39.461 WARN - Putting a cap on SELL liquidity available. [Total Balance : 13160.21030798 NBT ; capped @ 6000.0 NBT] - [c.n.n.t.L.LiquidityDistributionModel:82]
07:32:39.509 INFO - SELL- OrderBook : ----- SELL-side order book :
1.007099,0.00187818,2000.0
1.009099,0.00188191,4000.0
SELL wall volume : 2000.0
SELL tier2 volume = 4000.0 NBT
Total SELL volume = 6000.0 NBT
Best price :0.00187818 (1.0070988978$)
SELL balance left = 7160.21030798 NBT----- - [c.n.n.s.S.StrategySecondaryPegUtils:228]
07:32:39.511 INFO - Trying to place 2 orders... - [c.n.n.s.S.StrategySecondaryPegUtils:229]
07:32:39.764 INFO - SELL wall order updated. ID : 2624987447 size: 2000.0 - [c.n.n.t.TradeUtils:232]
07:32:40.009 WARN - **SELL** orders re-initialized on **poloniex** : 2/2 placed successfully
total amount placed : 6000.0
Tier1 order size : 2000.0
Tier2 cumulative order size : 4000.0 (1 orders)
- [c.n.n.s.S.StrategySecondaryPegUtils:247]
07:32:41.786 INFO - Order placed = OrderToPlace{type=SELL, pair=nbtbtc, size=2000.0, price=0.00187818} - [c.n.n.m.MultipleOrdersResponse:88]
07:32:41.789 INFO - Order ID = 2624987447
- [c.n.n.m.MultipleOrdersResponse:89]
07:32:41.791 INFO - Order placed = OrderToPlace{type=SELL, pair=nbtbtc, size=4000.0, price=0.00188191} - [c.n.n.m.MultipleOrdersResponse:88]
07:32:41.792 INFO - Order ID = 2624988446
- [c.n.n.m.MultipleOrdersResponse:89]
07:32:41.795 [Strategy Secondary Task] INFO - initOrders BUY [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:178]
07:32:42.453 [Strategy Secondary Task] WARN - Putting a cap on BUY liquidity available. [Total Balance : 36.36537239 BTC ; capped @ 3.72988195 BTC] [c.n.n.t.L.LiquidityDistributionModel:82]
07:32:42.462 [Strategy Secondary Task] INFO - BUY- OrderBook : ----- BUY-side order book :
0.924898,0.00172488,500.0
0.9099,0.00169691,537.49448425
0.715921,0.00133515,962.50551616
BUY wall volume : 500.0
BUY tier2 volume = 1500.0000004099998 NBT
Total BUY volume = 2000.0000004099998 NBT
Best price :0.00172488 (0.9248979048000001$)
BUY balance left = 17499.47632883 NBT----- [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:228]
07:32:42.464 [Strategy Secondary Task] INFO - Trying to place 3 orders... [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:229]
07:32:42.709 [Strategy Secondary Task] INFO - BUY wall order updated. ID : 2624989445 size: 500.0 [com.nubits.nubot.trading.TradeUtils:232]
07:32:43.900 [Strategy Secondary Task] WARN - **BUY** orders re-initialized on **poloniex** : 3/3 placed successfully
total amount placed : 2000.0000004099998
Tier1 order size : 500.0
Tier2 cumulative order size : 1500.0000004099998 (2 orders)
[c.n.n.s.S.StrategySecondaryPegUtils:247]
07:32:47.075 [Strategy Secondary Task] INFO - Order placed = OrderToPlace{type=BUY, pair=nbtbtc, size=500.0, price=0.00172488} [com.nubits.nubot.models.MultipleOrdersResponse:88]
07:32:47.077 [Strategy Secondary Task] INFO - Order ID = 2624989445
[com.nubits.nubot.models.MultipleOrdersResponse:89]
07:32:47.079 [Strategy Secondary Task] INFO - Order placed = OrderToPlace{type=BUY, pair=nbtbtc, size=537.49448425, price=0.00169691} [com.nubits.nubot.models.MultipleOrdersResponse:88]
07:32:47.081 [Strategy Secondary Task] INFO - Order ID = 2624990444
[com.nubits.nubot.models.MultipleOrdersResponse:89]
07:32:47.083 [Strategy Secondary Task] INFO - Order placed = OrderToPlace{type=BUY, pair=nbtbtc, size=962.50551616, price=0.00133515} [com.nubits.nubot.models.MultipleOrdersResponse:88]
07:32:47.084 [Strategy Secondary Task] INFO - Order ID = 2624991443
[com.nubits.nubot.models.MultipleOrdersResponse:89]
07:32:47.086 [Strategy Secondary Task] INFO - Strategy initialization completed [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:148]
07:33:21.110 [Strategy Secondary Task] INFO - Sell-Wall size : : 2000.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:539]
07:33:21.414 [Strategy Secondary Task] INFO - Buy-Wall size : : 500.0 NBT [com.nubits.nubot.strategy.Secondary.StrategySecondaryPegUtils:544]In a nutshell:
13,160 NBT and
36.36 BTC are in this gateway.
Current order related parameters:
1 Like
@desrever, I’ve found a behaviour of NuBot, which I consider a bug.
I tried to prepare the future use of this gateway account: place orders at the book at a huuuuge offset 90% and beyond.
It doesn’t work like I wanted it to work.
I wanted to have a 50,000 NBT order at $0.10.
It did only place much less.
NuBot calculates the total amount of NBT that can be placed on the buy side of the order book based on the current BTC exchange rate.
It doesn’t consider the offset.
So I can only place 10,000 on the order book, if I have 20 BTC at an exchange rate of $500/BTC.
Although at an offset of 0.9 there would be enough BTC for 100,000 NBT.
At these offsets I could of course place the orders manually, but as I want to provide the sell side with orders, I need NuBot to move them according to the BTC price.
Is it much effort to adjust that in NuBot?
Basically you need to divide the Dollar value of the BTC by (1-offset; per order that is about to get placed), if you want to calculate the NBT amount that is available at these offsets.
I hope it’s just this one calculation.
Do you know what I mean?
2016-06-04
Current status:
nud getliquiditydetails B | grep 0.4.1_1465062836601_5e33b3 -A 2
"1:NBTBTC:poloniex:0.4.1_1465062836601_5e33b3" : {
"buy" : 20776.4411,
"sell" : 2000.0
--
"2:NBTBTC:poloniex:0.4.1_1465062836601_5e33b3" : {
"buy" : 47.64,
"sell" : 11160.0278Remark: the BTC are on order with an offset of 90%
I try to have NuBot manage only the sell orders, while placing buy orders manually.
The buy side currently has 3 orders at 90%, 95% and 97.5% offset, each with a volume of 50,000 NBT.
Total NBT required for those orders: 15ish
Let’s see whether the manually placed orders stay, when NuBot moves the sell orders.
The next attempt will be to have a NuBot placing the buy side orders with different API credentials.
When using the
"multiplecustodians":true,
setting, they should move the orders at the same point of time.
I’ll keep you updated.
Btw.
20 BTC withdrawn to 3HikFkS2Zinab1TJq7dqp6wSPyLu7i7bhe to reduce exchange risk; tx ID 4c0fbef2d16555d092ee2ec7b2f14b9b6752828eeca1ada0a1f1185350ea8ef4
ninjaedit: well, I need to fiddle with a buy side only NuBot on that account. The sell side only NuBot deleted the manually placed orders. Damn!
If it is, I can run another PyBot to emulate this and running with another offset. Just let me know. It is not that hard to open 2 or 3 accounts more on Poloniex.
You know that you have to associate the accounts with each other?
Dealing with the accounts and the OTP, backing them up safely, getting the API credentials with all that email verification stuff in between and not loosing the overview is indeed the hardest part
Yes, no problem.
Yes, my accounts are still at the lowest level. Can’t be bothered to provide every identity document I have to them to even get to the second level. Don’t like them scattered everywhere, too many breaches and hacks these days.