[BTC] Bitcoin 11.69517441
On orders: 3.52885500
BTC value: 15.22402941
[NBT] NuBits 6932.36501214
On orders: 1500.00000000
BTC value: 20.06683631
[BTC] Bitcoin 11.68354941
On orders: 3.54048000
BTC value: 15.22402941
[NBT] NuBits 6932.36501214
On orders: 1500.00000000
BTC value: 20.11355161
[BTC] Bitcoin 11.67352941
On orders: 3.55050000
BTC value: 15.22402941
[NBT] NuBits 6932.36501214
On orders: 1500.00000000
BTC value: 20.14289624
2 Likes
[BTC] Bitcoin 7.08703690
On orders: 3.36510000
BTC value: 10.45213690
[NBT] NuBits 9037.74667405
On orders: 1500.00000000
BTC value: 23.81952258
5000 NBT have been sent back to FLOT.
10 BTC are expected at buy side.
BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
“buy” : 14.4238,
“sell” : 10128.6432
I encourage you to keep some more funds on your NuBot account.
I don’t know how the other FLOT members see that, but I’d rather have some more buffer in this last line of peg defence at Poloniex.
The motion on which this operation is based on doesn’t deal with thresholds at which you withdraw funds.
I recommend to try having approximately $10,000 on buy side and sell side at average, but leave it up to the FLOT to decide what they consider wise.
Remark: when I ran the previous NuBot operation at Poloniex there were up to $50,000 in total for an extended time in the accounts on which I ran the two NuBots. While that was quite high and due to the very bad experience with ALP, I consider in total below $20,000 insufficient.
Waiting until the FLOT requests withdrawal might be an option. I think a “forum consensus” could be sufficient for that.
Comments are welcome.
ok. I would prefer though to have those funds in more than one nubots with different operators 
My contract has me send back half of each side once a week, at my discretion.
I think I’m in the condition to ramp up my NuBot operation from “active standby” to “active”, soon.
My current NuBot motion at Poloniex was rather meant for emergencies and to provide incentives to create additional operations (due to the high fees which kick in with delay).
So I consider applying for a new operation with moderate fees to replace that emergency version.
Based on the current motion a second NuBot operation is available basically for free for the first 45 days.
As soon as I feel comfortable operating a NuBot again, the account can be funded while the motion for a regular NuBot operation is still running.
I’ll keep you updated.
2 Likes
The NuBot is already down to a bit over $1,000 on buy side:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
"BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
"buy" : 1399.902,
"sell" : 13122.6432I’m going to prepare another BTC deposit by FLOT.
The strange thing is that the ALP doesn’t show recent “outages”:
How can NuBot orders at 1% offset be traded under these circumstance? Recently there have been over $4,000 in the NuBot account after the last deposit by FLOT.
I know, it is strange! But now the situation is changed. We don’t have sell side, only nubot has 10K NBT there.
Moreover the ALPs can reach 1% offset as well. Sometimes nubot’s orders are below ALP and sometimes are above!
And I think that should change soon or the rates needs to be adjusted significantly. With over 1% offset you can earn money with the volumes on Poloniex. And you can earn even more when BTC goes up. We are paying too much for the liquidity at Poloniex and we are not getting the walls when we need them. Good to have the NuBots! Although a topup might be needed.
2 Likes
And don’t forget the famous pybot bug, placing orders of 0.5 NBT (in both sides) when recalculates new prices!
It will adjust, give it some time.
Ok, it didn’t fast enough. Gave it a kick and tweaked some parameters. Might create a hard reset of the bots with some clever batching to circumvent this problems the soft reset doesn’t always work. See if I can get Linux or some tool to set jobs on a timer…
Edit; Made something quickly, will have this experimental script running resetting Pybot every 15 minutes for a while. That will solve the problem.
What repo are you using? I switched from a soft reset to a hard reset in the latest main repo pull of alp-collection for just this reason.
The deposit arrived and was credited. Funds are on order:
nud getliquidityinfo B | grep BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo -A 2
"BJs4YbtaqCmxeHLiR6zzjnZEotYVFAPfMo" : {
"buy" : 10040.08,
"sell" : 9855.7689
1 Like
[BTC] Bitcoin 19.40582032
On orders: 3.36906000
BTC value: 22.77488032
[NBT] NuBits 8355.76893059
On orders: 1500.00000000
BTC value: 22.36234547
nearly perfect balance
2 Likes
Used yours for this, but I believe it came with newly introduced bugs. The NBT/USD pair really misbehaves with your repo for some reason, so I’m running bots from two different repos at times. They both work with the script below.
For anyone interested in the bash script I’m using to restart the bot;
#!/bin/bash
COUNTER=0
cd /
while [ $COUNTER -lt 50000 ]; do
echo The counter is $COUNTER
let COUNTER=COUNTER+1
timeout -s10 900s /root/nu-pool-1.31lb/unix/client-poloniex-btc &
sleep 901
done
echo Script ended counter max reached
I’m sure this can be done better and smarter, but it may help someone. 900s stand for a reset every 15 minutes. The counter is on 50,000 just because I don’t like infinite loops This is not a solution, just removing symptoms.
2 Likes
[BTC] Bitcoin 19.25957032
On orders: 3.51531000
BTC value: 22.77488032
[NBT] NuBits 8355.76893059
On orders: 1500.00000000
BTC value: 23.38271323
1 Like
[BTC] Bitcoin 19.29584032
On orders: 3.47904000
BTC value: 22.77488032
[NBT] NuBits 8355.76893059
On orders: 1500.00000000
BTC value: 23.10300650
1 Like