Pages:
Author

Topic: Qt Bitcoin Trader [Open Source secure trading client for Mac/Windows/Linux] - page 62. (Read 383297 times)

legendary
Activity: 1035
Merit: 1065
Hey IGHOR, got any ideas why i can't connect to btcchina API? i would really love to be able to use your software with that exchange!

Press Alt+Shift+D and see debug viewer.
Send debug info to my email from About dialog.
sr. member
Activity: 363
Merit: 250
Hey IGHOR, got any ideas why i can't connect to btcchina API? i would really love to be able to use your software with that exchange!
sr. member
Activity: 266
Merit: 250
legendary
Activity: 2114
Merit: 1002
A couple of question. I mostly develop in C# but if i wanted to modify the code to use ltc instead say in btce i would need replace the btc calls with ltc while leaving the rest of the logic intact no?

Since the keys are encrypted, would you say its safe to it running 24/7 on a VPS running X and VNC?



PPC and Mastercoin (MSC) traders will love your platform.
Time to port in PPC and MSC quickly.

PPC:
https://bitcointalksearch.org/topic/ann-ppc-ppcoin-released-first-long-term-energy-efficient-crypto-currency-101820

MSC:
https://bitcointalk.org/index.php?topic=292628.0;topicseen
brand new
Activity: 0
Merit: 0
I love this IGHOR! I've shown all my trading friends and donated some coin.  What a great job you've done.  If you're considering additional features a trailing stop loss and normal stop loss would be most welcome.
sr. member
Activity: 365
Merit: 250
Nice platform!

I was messing with the rules and couldn't find one to create market sell order if price goes below a certain point. The classic stop loss.

I only found options that define limit orders which is dangerous in case of a fast movement. You can get your order not executed and trapped.

Am Im missing something or for now it is not possible to create rules with market orders?
newbie
Activity: 3
Merit: 0
A couple of question. I mostly develop in C# but if i wanted to modify the code to use ltc instead say in btce i would need replace the btc calls with ltc while leaving the rest of the logic intact no?

Since the keys are encrypted, would you say its safe to it running 24/7 on a VPS running X and VNC?

member
Activity: 76
Merit: 10
...and the BitcoinKid
does anyone have any rule sets they wanna share with the community? For instance, the stop loss or trailing jammies?
sr. member
Activity: 363
Merit: 250
I followed your advice and I am still stuck.  I looked for about, but i didn't see it in the mac version so i can't email you the debug long.  I'm 100% sure i am inputing the keys without any whitespace.  Is it possible this is only a bug in the mac version?  I have not tried the windows version.

I have a debug log, if you let me know what your email is i can send it.

This is what i see in the regular log (not debug)

[email protected]

Sent!
hero member
Activity: 981
Merit: 500
DIV - Your "Virtual Life" Secured and Decentralize
I really wish I would have setup a good stop loss system. Go me. Anyways the above post got me to thinking again about a oversight I see.

For most of my range trading if I use rules for it I would want them done sequentially similar but not identical to the above post. It works great.

The problem as I see it is I need at least 1 rule to run concurrently for a proper stop loss. Ironically I can't rely on every rule before it to get used. Especially if I setup one rule just to restart the previous rules. I could run a separate instance with its own API key pair per currency I am range trading. Currently one so it wouldn't be that much more. That having been said in some cases prudence might indicate a rule or 3 that would ideally run concurrently while most can run sequentially.
full member
Activity: 195
Merit: 100
Or I'm wrong or the stop-loss orders can be already done creating a stop-loss rule.

I'm tested that kind of rule and it works pretty fine on BTC-e.

By the way IGHOR, the program is outstanding. Very good work. I've improved Spanish translation and sent it to U.

Thank you for fixes!
Stop loss rule is can be configured manually.
But they want to use percentage of price to create rule.
And I'll add this soon.

Thank you so much for this program I'm going to throw a donation now.  Thanks to this program I was able to sell at 800 during the flashcrash the other night so I definitely owe you.

As I mentioned in my post, I can configure stoploss manually, but for short traders it requires punching in numbers and changing rules extremely quickly.  More then once I've made a mistake (mistyping), and it requires at least 3 separate rules to make work properly so I think it would be prudent to have an entirely separate stop loss function that would do these things.

Set a percentage trailing the market price that would move up with current market conditions but not move down (IE execute function at 10% below highest value since entry)
Cancel all orders if market price falls below stoploss price
Execute a sell order at last market price
If sell order doesn't execute immediately reattempt to sell at last market price


using the setup I had that saved me by selling at 800 this would look like

Sequential mode

If sell price (goes below) 800 (cancel all orders)
If sell price (goes below) 800 (sell all) at last market price
If sell price (goes below) 790 enable all rules

Its set up like this so that if the market falls to quickly to sell at first it will reset itself and try again to sell at the last market price.

So excited to see the now version now that I know your working on stoploss!!! Really great work!!!:D:D:D
legendary
Activity: 1035
Merit: 1065
As soon as this volatility is over and I've bought back in, I will be sending you some coins Ighor. Your program saved my ass the other night from what could have been a very expensive mistake!

Love the rules!

Glad to help you Smiley
maz
full member
Activity: 140
Merit: 100
As soon as this volatility is over and I've bought back in, I will be sending you some coins Ighor. Your program saved my ass the other night from what could have been a very expensive mistake!

Love the rules!
legendary
Activity: 1035
Merit: 1065
Or I'm wrong or the stop-loss orders can be already done creating a stop-loss rule.

I'm tested that kind of rule and it works pretty fine on BTC-e.

By the way IGHOR, the program is outstanding. Very good work. I've improved Spanish translation and sent it to U.

Thank you for fixes!
Stop loss rule is can be configured manually.
But they want to use percentage of price to create rule.
And I'll add this soon.
legendary
Activity: 1212
Merit: 1052
Or I'm wrong or the stop-loss orders can be already done creating a stop-loss rule.

I'm tested that kind of rule and it works pretty fine on BTC-e.

By the way IGHOR, the program is outstanding. Very good work. I've improved Spanish translation and sent it to U.
legendary
Activity: 1035
Merit: 1065
I would love to see stoploss added.

It would really probably be pretty easy and an essential feature for trading apps imo.  Maybe some little tickbox under buy order that says "enable stoploss" with an input for percentage.  It could generate a subsequent rule to cancel all orders and sell at market last price maybe?  This is how I have been doing it in the passed but its kind of risky in fast moving markets to have to talk the time to manually enter those numbers into 2-3 different rules everytime.

I'll add this soon.
full member
Activity: 195
Merit: 100
I would love to see stoploss added.

It would really probably be pretty easy and an essential feature for trading apps imo.  Maybe some little tickbox under buy order that says "enable stoploss" with an input for percentage.  It could generate a subsequent rule to cancel all orders and sell at market last price maybe?  This is how I have been doing it in the passed but its kind of risky in fast moving markets to have to talk the time to manually enter those numbers into 2-3 different rules everytime.
sr. member
Activity: 407
Merit: 250
Hey Ighor, great program!!
Thank you
legendary
Activity: 1035
Merit: 1065
I followed your advice and I am still stuck.  I looked for about, but i didn't see it in the mac version so i can't email you the debug long.  I'm 100% sure i am inputing the keys without any whitespace.  Is it possible this is only a bug in the mac version?  I have not tried the windows version.

I have a debug log, if you let me know what your email is i can send it.

This is what i see in the regular log (not debug)

[email protected]
sr. member
Activity: 363
Merit: 250
I am using the latest version of the software from sourceforge, version 1.07.95.
I have entered brand new BTCChina API key and secret in. But everytime i try to use it i get:
Login: Offline
in the top right corner and this error:
Code:
Identification required to access private API.
Please enter valid API key and Secret.
Please try to enable "Trade" and "Info" righs for this API pair.
If it not helps. Please generate new API keys and recreate profile.

401 Unauthorized
208

Try to type API keys manually, or copy/paste it to notepad first.
There maybe space in the end or beginning.
If it not helps press Alt+Shift+D and switch to Debug mode.
Send me 1 minute debug log to my email. (email in about window).

I followed your advice and I am still stuck.  I looked for about, but i didn't see it in the mac version so i can't email you the debug long.  I'm 100% sure i am inputing the keys without any whitespace.  Is it possible this is only a bug in the mac version?  I have not tried the windows version.

I have a debug log, if you let me know what your email is i can send it.

This is what i see in the regular log (not debug)
Quote
------------------
2013-11-19 10:39:04 LVL:2
API Error: 401 Unauthorized
 ReqType:202
------------------


------------------
2013-11-19 10:39:05 LVL:2
API Error: 401 Unauthorized
 ReqType:208
------------------


------------------
2013-11-19 10:39:06 LVL:2
Invalid depth data:401 Unauthorized

------------------


------------------
2013-11-19 10:39:09 LVL:2
API Error: 401 Unauthorized
 ReqType:202
------------------


------------------
2013-11-19 10:39:10 LVL:2
API Error: 401 Unauthorized
 ReqType:208
------------------


------------------
2013-11-19 10:39:11 LVL:2
Invalid depth data:401 Unauthorized

------------------



Thank you!
Pages:
Jump to: