MoD-bot, you are becoming a “single point of failure”
Failing at NBT sell side only exchanges isn’t that bad.
Poloniex as one of the dual side exchanges has 3 bot operators!
I have sent some NBT in sell side (as ALP) although i don’t trust it
NuBot ia running.
I’ll post a contract soon.
sorry , have a big work to do , i wll set up nubot right now
@Nagalim, if you consider the situation dire, you might consider depositing T3 custodian funds.
Although that’d put me in some trouble as it wouldn’t per definition activate the contract…
…and for you it could mean trouble as well, as your accounting would be messed up - you’d proxy NBT through my NuBot to BTC at FLOT address…
On second thought, I’m fine with receiving funds from a T3 custodian.
I consider you a “Nu representative” although not having listed T3 custodians explicitly.
It’s only you who’d get in trouble
Yah im not doing that. My contract is basically just for ALPs and MLPs, gateways are a T4 game.
You are talking about BTER?
Not in a thousand years
ALP gives me 0.67% now
(where are you people?)
I’m all turn to CNY pool…
And why do you think you get that rate at a FC pool?
I give you a hint: there’s only very little liquidity
sorry i have this error when i running the nubot .
08:51:12.425 [main] ERROR - could not launch bot com.nubits.nubot.bot.NuBotRunException: Problems while validating communication with exchange : [ ApiError [4 : Null Return] ] [c.n.n.l.MainLaunch:173]
i do’t know what the error come from… get a new API to test
setting about exchange , Is that right ?
“exchangename”:“bter”,
“apikey”: “xxx”,
“apisecret”: “xxx”,
“txfee”: 0.2,
“pair”:“NBT_BTC”,
Did you actually put in an apikey and secret, or did you leave it as xxx?
yes i am , not show API here
My config looks similar:
"exchangename":"bter",
"apikey": "obfuscated",
"apisecret": "obfuscated",
"txfee": 0.01,
"pair":"nbt_btc",
I don’t know whether “pair” is case sensitive. You might want to change the capital letters.
Which NuBot version do you use? I run 0.4.1, which works fine:
nud getliquiditydetails B | grep BETwD8nSjtj9ADSvej2na34xmsMYwPRymv -A 500 | grep 0.4.1_1458818581316_919b81 -A 2
"1:NBTBTC:bter:0.4.1_1458818581316_919b81" : {
"buy" : 0.0,
"sell" : 0.0
--
"2:NBTBTC:bter:0.4.1_1458818581316_919b81" : {
"buy" : 0.08,
"sell" : 0.3135
try 0.4.1 and 0.3.2a both , same error , try to use polo to find out the netwrok error or client error.
Will add this to my datafeed, despite the high 2% spread. Would be interesting to see whether it is still used at those high spreads.
Nu can test the waters, if Nu deposits funds at my sell side gateway:
The current offset is 1.5%, but can be lowered to close to 1% as stated in the terms.
If FLOT plans to deposit funds there, I should say that this is another deposit, which I’m not going to sign - just like I did with the hitBTC gateway.
hello guys , can i send liquidityinfo that without passed?
No, you need a custodial address to submit liquidity. Once you have one though, if you hold on to the private keys you can always reuse it in an emergency or just convenience. They expire every 6 months.
cheaper BTC at BTC/CNY, Don’t know what happen with BTER