Pages:
Author

Topic: goxgui - a Graphical Bitcoin Trading Tool for MtGox - page 3. (Read 29621 times)

newbie
Activity: 38
Merit: 0
Did you download the pre-packaged binary or the version from the repository?
newbie
Activity: 41
Merit: 0
a bug found in the new version. When I choose EUR in preferences - the order book still displays USD price, just changes the title of asks and bids.
full member
Activity: 137
Merit: 100
I was thinking Stay Puft, but Gozer said Grover
Market dips below 81 nothing happens because the app is waiting for 78, but if the market reverses and goes above the low between 78-81 then the app enters a buy at x$ above the point between 78-81 and if no buy happens because the market reverses so rapidly then it app enters buys at levels the user has defined for x$ more, and x$ more until a buy happens or until a set ceiling is crossed.

So let's take an example for me to understand this. Let's say the price drops to 79, we have entered the buy zone (78 - 81), but it doesn't drop to 78. Instead, it goes up again. The user has defined buy steps at $2, and as soon as the price has reached $81, the bot would place bids at $83, $85, $87 etc. until a buy happens?

Basically yes.

I'll work out stating the logic in a clear fashion.



sebastopol and mrlithium Your work on this is greatly appreciated.  I haven't forgotten I stated i would come up with a better example of what I was on about a few days ago.  Not that yall are holding your breath until I posted again.  Grin

Instead of trying to trade BTC manually I'm working towards a bot application. This is one whack a mole crazy manipulated market.  Penny stocks that are about to be delisted don't even hold a candle to Gox/BTC.

I'm pretty sure I have a sound basic formula designed, of course I would think that I thought it up, though at least one programmer appears to agree.  IDK if this is the place to post this but if anyone wants to work to program a bot then PM me and I can send you my initial premise, or PM me and I'll edit this post to remove the offending text.

newbie
Activity: 46
Merit: 0
I'm working on updating my fork to sebastopols  latest  version. The password stuff should be easier. I still am not sure why your stop loss order didnt work if the rest of normal trades can trade.

Good to see that you still keep an eye on the original repository Smiley This time there have been some major refactorings under the hood, but I think they're worth integrating because they will make future extensions easier for both of us. Also, if you wait till the evening, I should have multi-currency-support ready by then!

OK, I've updated the forked repo. The multi-currency support was just too big of an update for me to include right now. For the stop loss orders, user orders  and ticker tab/ticker title bar, download it from https://github.com/genbtc/goxgui  
Also, the "Total:" Bitcoins column is still present as this is one of the best features that I use goxGUI for. (i usually place my orders about 3000 coins away from the spread, so big whales can hit them Tongue) So in my version it is still there but it is removed in his latest version. (see screenshots)
Also, you can edit the "Fiat" and "Target" currency in the "Various Settings" window, which changes the .ini file for goxtool so it will actually trade in different fiat currencies, and show that currency's wallet. (but the decimals are wrong for JPY and SEK)
The authentication and password tabs have been moved into "Preferences" and you can supply your own password. The "Apply" button will run one final check if everything is valid, and enable the OK button to Write everything to the config file and restart the socket with your new credentials.
sr. member
Activity: 364
Merit: 250
downloading now!
legendary
Activity: 1183
Merit: 1000
goxgui v1.1.0 released!

Download goxgui v1.1.0 on SourceForge.

Changes:

- multi-currency support
- preferences dialog
- various refactorings and unit tests to improve code quality
- fixed bad looking fonts on Windows platform
- fixed annoying QTimer error on application close

The most requested feature in the reddit poll was a close tie between multi currency support and limit / stop orders. I decided to implement multi-currency support first, because it affects the whole application and will be much harder to implement once the application gets more complex. It was already a lot more work than I expected, but I am happy with the result and I believe if MtGox and goxapi support multiple crypto currencies one day, goxgui won't have to be changed much.

P.S.: now vote for the next feature!

This is a great GUI, I think I was first to DL it this morning heh Smiley.

I love your work Sebastopool, best of luck!

Pablo.
newbie
Activity: 38
Merit: 0
goxgui v1.1.0 released!

Download goxgui v1.1.0 on SourceForge.

Changes:

- multi-currency support
- preferences dialog
- various refactorings and unit tests to improve code quality
- fixed bad looking fonts on Windows platform
- fixed annoying QTimer error on application close

The most requested feature in the reddit poll was a close tie between multi currency support and limit / stop orders. I decided to implement multi-currency support first, because it affects the whole application and will be much harder to implement once the application gets more complex. It was already a lot more work than I expected, but I am happy with the result and I believe if MtGox and goxapi support multiple crypto currencies one day, goxgui won't have to be changed much.

P.S.: now vote for the next feature!
newbie
Activity: 21
Merit: 0
I specialize in developing marketplaces, and I want to partner with someone that would like to add a marketplace layer to a wallet.
I don't mean an exchange, I mean a marketplace.

I.e. I want to sell a gold plated fountain pen, I list it for sale at a price of $70.50 + $1.00 shipping. This offer exists on a marketplace, where someone can see it and buy it.

Bitcoiners need a marketplace as much as they need a good wallet system. I aim to combine them.

I helped develop playerauctions.com and have a decade of experience in ecommerce development and management.
If your team is ambition enough to add a marketplace layer, let's talk.
newbie
Activity: 21
Merit: 0
Thanks for your great work

it is really a nice tool i will see what uses i can workout and share with you as iam a bit new to python it wont be very fast but form myself i'm intrested in cross exchange trading

for the stoploss option it would be neat to add this "zone" though there is another possibility to give a trigger for the stoploss option in the way that the bot will be activated once a special value is matched and goes to "sell" mode and then performes his stoploss

idea for on/off trigger

- buy btc with value of 100  you want to gain a small win and want to sell at 102 so you set your stoploss to 102 (if it is under 102 an active bot would have sold so we need the switch)
- the trigger will be set to 102.1  bot goes to "on"
---> bot will sell if market drops below 102

idea hard - soft sell  switch
- buy btc 100  sell at 102.5 and you place a regular order  stoploss at 101.99  (because you don't believe 102 might be reached)  
- the trigger hard sell will be set to 101.99 if anyhow the price will drop bot will sell but only if after 5h trigger soft hasn't been reached
- the trigger soft sell will be set to 102.6  bot goes to "on"
--> bot will sell if market goes below 102.6  but only if in a given time 101.99 hasn't been reached

--- update
as i fumble along can me tell somebody how i "submit" changes to goxgui.exe do i need to compile it with the whol  *.py scripts changes and what is the index used for compiling and what compiler to use  Smiley thx for help
newbie
Activity: 46
Merit: 0
Can anyone help me?
I'm working on updating my fork to sebastopols  latest  version. The password stuff should be easier. I still am not sure why your stop loss order didnt work if the rest of normal trades can trade.

Can you walk me throw how exactly I would go about placing a stop trade. Maybe I did something wrong

Click the stop orders tab. It should say "NO STOP ORDERS     YET" in the box below.
In the size box, enter: 1 (for 1 BTC)
In the price box, enter: 100 (for 100 USD)
This will sell 1 BTC when the price falls below $100.

I have come to the conclusion you maybe are trying to use decimals without the leading 0. If you are using sizes under 1 BTC, you have to include the leading 0 such as: 0.125
newbie
Activity: 38
Merit: 0
I'm working on updating my fork to sebastopols  latest  version. The password stuff should be easier. I still am not sure why your stop loss order didnt work if the rest of normal trades can trade.

Good to see that you still keep an eye on the original repository Smiley This time there have been some major refactorings under the hood, but I think they're worth integrating because they will make future extensions easier for both of us. Also, if you wait till the evening, I should have multi-currency-support ready by then!
legendary
Activity: 1630
Merit: 1000
Can anyone help me?
I'm working on updating my fork to sebastopols  latest  version. The password stuff should be easier. I still am not sure why your stop loss order didnt work if the rest of normal trades can trade.

Can you walk me throw how exactly I would go about placing a stop trade. Maybe I did something wrong
newbie
Activity: 46
Merit: 0
Can anyone help me?
I'm working on updating my fork to sebastopols  latest  version. The password stuff should be easier. I still am not sure why your stop loss order didnt work if the rest of normal trades can trade.
full member
Activity: 137
Merit: 100
I was thinking Stay Puft, but Gozer said Grover
Market dips below 81 nothing happens because the app is waiting for 78, but if the market reverses and goes above the low between 78-81 then the app enters a buy at x$ above the point between 78-81 and if no buy happens because the market reverses so rapidly then it app enters buys at levels the user has defined for x$ more, and x$ more until a buy happens or until a set ceiling is crossed.

So let's take an example for me to understand this. Let's say the price drops to 79, we have entered the buy zone (78 - 81), but it doesn't drop to 78. Instead, it goes up again. The user has defined buy steps at $2, and as soon as the price has reached $81, the bot would place bids at $83, $85, $87 etc. until a buy happens?

Basically yes.

I'll work out stating the logic in a clear fashion.
legendary
Activity: 1630
Merit: 1000
Once you enter the API key and Secret, they are encrypted in the .ini file. Previously the password they were encrypted with was hardcoded, not user-choosable and I found this odd (security hole). So I cobbled together the method that you see in my forked version, therefore the steps to use this functionality are somewhat sub-par in terms of intuitiveness, so heres the instructions.
1) Download the fork from https://github.com/genbtc/goxgui
2) The program will generate a new blank config file on first run. (Don't try to import the old one)
3) Click the "Authentication" Tab, enter your API Key and Secret
4) Click the "Password" Tab, enter a Password of your own choosing.......
5) Go BACK to the "Authentication" Tab, and hit Apply.
6) The program will encrypt the API Key/Secret and store it in the INI file.
7) Each Next time you want to open up the program, you will have to click the password tab, enter your Password, and hit "Decrypt".

I Have just implemented a "lazy-version" of this. Once You have done initial Steps 1-6 above, You can edit the "goxtool.ini" file and add the following:
[goxgui]
password = XXXXXXXXXXXX

This will store your password, and auto-login everytime you launch it next time.

I followed your instructions and all, and it seemed to work as it got my current btc balance and everything, just I did a stop/loss order and activied the bot and it didnt work. it showed it excuted on the program but my balance/account it didnt

Can anyone help me?
newbie
Activity: 38
Merit: 0
Market dips below 81 nothing happens because the app is waiting for 78, but if the market reverses and goes above the low between 78-81 then the app enters a buy at x$ above the point between 78-81 and if no buy happens because the market reverses so rapidly then it app enters buys at levels the user has defined for x$ more, and x$ more until a buy happens or until a set ceiling is crossed.

So let's take an example for me to understand this. Let's say the price drops to 79, we have entered the buy zone (78 - 81), but it doesn't drop to 78. Instead, it goes up again. The user has defined buy steps at $2, and as soon as the price has reached $81, the bot would place bids at $83, $85, $87 etc. until a buy happens?
full member
Activity: 137
Merit: 100
I was thinking Stay Puft, but Gozer said Grover
IDK if this is out of the scope for this project but this seems like a great idea to me.

Is there any way to add a feature that is a trailing stop loss in reverse?

I know it seems like a strange idea.  Why buy above a price you're losing money.  I say are you really?  Same as why sell below the price you buy at, you're losing money if the trend reverses.  I think it's pretty evident this is a highly fluid market with a nice dose of overt manipulation on top.

Say your stop losses are triggered and what was really happening is a trader or group of traders was using their power to cause bots, apps, traders, to dump coins below market with the plan of a quick dump and reverse?  You sell your coins for a loss on a big red candle, but if you're semi-automated when do you buy them back in this scenario when the market rebounds on the next interval or in the same interval?

This is my example since it is easier to explain.

Say I'm tired and fall asleep at the wheel, like this morning when the market was going under 89. I enter buys but my buys are too low so they never execute.

What if when I enter a buy then the app takes the highest buy point and if the prices reaches either a percentage or fixed amount that the user enters (ceiling) but never reaches the highest buy and then rises past the ceiling then the app enters a buy that equals an ask but only does this until a buy is made or until another user defined ceiling is reached.  There is no need for any real automation just some way of using the signals so the user can predefine the conditions.

example. (fictional, but maybe not)

I enter a buy at $78.99.  Gox only dips to $79.  If i was awake I'd be all over buying for $0.01 more.  But I had placed a fixed eyes off order so I miss the buy.  I wake up and bam Gox dipped and rebounds to $92.  What a great trade if I was awake.

So if the app had a feature that worked as a stop loss in reverse I could have bought or tried buying from a range of say $78-$81.  Market dips below 81 nothing happens because the app is waiting for 78, but if the market reverses and goes above the low between 78-81 then the app enters a buy at x$ above the point between 78-81 and if no buy happens because the market reverses so rapidly then it app enters buys at levels the user has defined for x$ more, and x$ more until a buy happens or until a set ceiling is crossed.

For example.  Yes I understand price could not reach my buy during one time period but reach my buy level at a later time.  Same with a stop loss.  A stop loss can be triggered then the price rebound and reach levels far above your stop loss.

You're looking at the charts and can see what looks like a real verifiable no nonsense downturn.  You see that the price is likely to be between $low and $high.  I understand then why not just enter the buy at high range predicted for the bottom?  Why buy something at one price and sell it for a loss with a stop loss?

You enter a range in which you know is comfortable to buy, and the app buys.  I guess to be even more fool proof the app could automatically enter another stop loss that is at the level of the amount of BTC bought plus buy/sell fees.  This way if the market reverses and goes down further then you'd sell in a break even range, or you could elect to hold figuring the market will come back to your buy level.


If this is convoluted blame the rum.  If you have questions please ask and I'll attempt to explain.  The basic idea is a reversed stop loss.  I'm trying to add the hot chick in the passenger seat and the turbo package to an excellent project.
legendary
Activity: 1630
Merit: 1000
sure what is your irc name and what server

Also yes I granted it trade and info access. i can confirm it works as it got my account balance no problem
newbie
Activity: 46
Merit: 0
Did you grant the API key "trade" access in addition to "Get-info" in the mtgox website's security tab?  (did you try to do normal trades?) - it should work...... no errors? contact me on IRC>...
legendary
Activity: 1630
Merit: 1000
Once you enter the API key and Secret, they are encrypted in the .ini file. Previously the password they were encrypted with was hardcoded, not user-choosable and I found this odd (security hole). So I cobbled together the method that you see in my forked version, therefore the steps to use this functionality are somewhat sub-par in terms of intuitiveness, so heres the instructions.
1) Download the fork from https://github.com/genbtc/goxgui
2) The program will generate a new blank config file on first run. (Don't try to import the old one)
3) Click the "Authentication" Tab, enter your API Key and Secret
4) Click the "Password" Tab, enter a Password of your own choosing.......
5) Go BACK to the "Authentication" Tab, and hit Apply.
6) The program will encrypt the API Key/Secret and store it in the INI file.
7) Each Next time you want to open up the program, you will have to click the password tab, enter your Password, and hit "Decrypt".

I Have just implemented a "lazy-version" of this. Once You have done initial Steps 1-6 above, You can edit the "goxtool.ini" file and add the following:
[goxgui]
password = XXXXXXXXXXXX

This will store your password, and auto-login everytime you launch it next time.

I followed your instructions and all, and it seemed to work as it got my current btc balance and everything, just I did a stop/loss order and activied the bot and it didnt work. it showed it excuted on the program but my balance/account it didnt
Pages:
Jump to: