Topic: [ANN] Bittrex / Poloniex / Cryptsy All Coin Trading Software, Quatloo Trader. - page 87. (Read 236688 times)

Can anything be done for the users of older operating systems 32 bit Windows XP?

There is a lot of people in developing countries who can not get the new ones, and can not install the .NET Framework 4.5.

I'd pay 10 BTC for a bot that did this

It says both because there are 2 versions.  Where in the OP are you referring?

Nevermind, I see it in red at top.  It does go on to explain that 1.1.2.5 , which is only bittrex trading only requires 100 QTL for main functionality.

A few more suggestions in addition to the ones I listed here: https://bitcointalksearch.org/topic/m.8550849

█ After filling the BUY side of a ping pong order the Bot will not SELL until e.g. 1% Gain is achieved on the price if e.g. the price does not reach that level within e.g. 60 minutes, the Bot will SELL at e.g. 1 satoshis below the top ask. I would suggest implementing this before anything else, I got this idea from the Cryptsy.Automated.Trading bot.

█ Advanced automated trading using data scraped from bitcoinwisdom & cryptrader
>> 1. Using one indicator, examples:
BUY when the price is close to or has touched the lower Bollinger band.
BUY when the 21/50 EMA  has just diverged to the upside on a chosen time frame (The Magic Cross signal).
BUY when the StochRSI OR MACD is low and has just diverged to the upside.
BUY when the RSI is low.

The SELL signal would be to sell after a specified % gain in price.

>> 2. Combining multiple indicators: Take into consideration multiple indicators such as RSI, MACD, EMA crossings and combine them into a weighted score index which the bot will generate its own BUY and SELL signals from. Quite a challenge to code this I imagine. 

how come the OP says 100 qtl to use it, but then the program says 1000!

The more contribution that comes forward, the stronger QTL gets. 

No not yet.  And its not going to be easy to track down.  Most likely is code security measures.

(3) Sell order: Sell 80 QTL at 102%

(5) If repeat-switch is True, then goto (6)
(6) wait xx seconden / random timeframe , then goto(1)

Dev, please update the thread title to: (not sure if it'll fit)

[ANN] Bittrex / Poloniex / Cryptsy Windows Automated Trading Application for ALL coins , Quatloo-Trader

Would anyone be interested in trading 3,000 QTL for 40 Mhs make that 50 Mhs (500 Asic shares) on ltcgear.com  

*Edit: Upped my offer to 50 Mhs (>")>

This "Buy Low - Sell High" idea in particular is fantastic! It's exactly what I'm looking for!

Did you manage to get the new version 2.0.0.7 running with mono? I'm unable to get it working :/ either something changed that my mono does not like :/

Upon reflection, I do think that the QTL holdings requirement to use the trader is beneficial to support the value of QTL overall.

Fantastic. It's so cool to see you develop this tool in front of us!

I had a long look at 2.0.0.6. Here are some of my suggestions (extension to my first list of ideas):

Common Markets ... Bittrex-Poloniex ... Price difference
to sort by absolute values does not make much sense to me,
--> show difference to last price as percentage


(Market) ... Trader ... Buying / Selling tables:
Show a fourth column where all orders UP TO THIS PRICE (or DOWN TO THIS PRICE for bids) are summed up.
It helps a lot, to see the big stepsizes in the order book.


(Market) ... Trader ... Main Auto Tasks ... PingPong ...
What is 'Scalp Mode' ?

What about a general approach to an on-the-spot 'manual':
Adding hover-over bubble help texts for the most important switches.


(Market) ... Trader ... Buy/Sell ... Quantity and Rate
--> auto-calculate the Quantity/Rate (or Quantity*Rate) so that we see the purchase total
--> allow reverse quantity=total*Rate (or total/Rate) so that we can choose how much to spend/earn in total, and the quantity is then calculated for us


(Market) ... Trader ... Buy/Sell ... Book total
Do not only show BTC amounts, but both currencies!
Why? The BTC total of the 'asks' is often pure fiction
(Imagine I ask for 1000 BTC for 1 QTL, and my order gets counted it, then I completely manipulate that total)


(Market) ... Trader ... Buy/Sell ... Book total
Most order books are truncated nowadays, so only the first 50 order levels are shown.
So the totals become quite irrelevant.
But imagine you now invent a new type of totals:
Only for those orders within an intervall of 1%, 2%, 5% (or a choosable percentage) around the last price, or around the middle of the spread. Then you can make 'totals' relevant again.


(Market) ... OpenOrders
Idea: Give a percentage how far I am still away with my targeted order from the last price.
i.e. want to sell at 0.00035, last price was 0.00025 --> show plus  40% ( = my wish is at 140% of last price)
i.e. want to  buy at 0.00020, last price was 0.00025 --> show minus 20% ( = my wish is at 80% of last price)


(Market) ... Accounts
rename that to 'Balances'


(Cryptsy/Poloniex) ... Accounts
a new switch 'hide all zero balances',
and for poloniex a nonzero threshold, because there are 1 Satoshi leftovers sometimes


New function: Buy low - Sell high
A bit similar to PingPong, but with given rates:
(1) Buy order: Buy 100 QTL at 20000 Sat
(2) Wait until that purchase has happened
(3) Sell order: Sell 80 QTL at 25000 Sat
(4) Wait until that purchase has happened
(5) If repeat-switch is True, then goto (1)


I might have more ideas if you are interested. I send you a PM now.

What a great tool. Thanks a million for all your work.

Enjoy!

:-)

Removing the old config files will mean the old versions need the keys again!  I thought i'd let you all know where the keys were stored so you'd feel better about removing them eventually

well i released 2.0.0.7... got rid of sqlite and all dlls  that aren't necessary anymore.  Went with storing the keys encrypted in a xml file. Should have done that from the start.

Now you have to enter your password every time you open the program..other wise there's no point in encrypting them.

I realize some of you may not care about that and ill add an option to save the password on closing!
.

I have done some testing:

I filled in the API's and saved it, all went well.
Then I removed the full folder : AppData/Local/QuatlooTrader2/
Now I need to enter the API's on every run.
I thing I doesn't check the existance of the folder

Q: adding a trim function on the api, or a check on the format, so people are forced to enter the correct length + format for the api would be a cosmetic plus.

bug: the comparison between tradeplatforms is not correctly formated.

I think the introduction of the extra dll's for sqlite is just going to cause more trouble that its worth.. I'll keep the encrypton paradigm.. add an option save pass  for those who don't care.. and it'll save the encrypted keys in flat file or xml file.

I'll look over the source. I've had a crash.. maybe something unhanded when network connection is lost.  And 2.0.0.6 is having problems in mono for linux.. i'll check what that is about.. prob the sqlite interop dll.

Any chance you can provide the checksums for the archives in the first post as well or on the site for that matter?