Sorry for the late reply, I went back through git revisions and couldn't reproduce the error.
That is weird that the log would show requests but no responses. I suppose I'll move the internal logging points around bit so in the future I'll know if replies are being received but dropped internally, which seem the most plausible explanation.

That is odd, first check that MtGox works in a browser and shows that SSL is verified. I would think that you are using some sort of network that hijacks web traffic like a coffe shop or a college. If that's not that it could be that somewhere on your system the chain of certificates for signing is screwed up. On my box I have this package:
which contains known certificates for signing SSL certificates, of which contains the Verisign certificate that signs the MtGox certificate.

So I would try it the MtGox site in a browser, then try and find the certificates package in your package manager and reinstall that.

Yes sudo'ing because someone from some forums told you to is bad, I put a note in the README about installs with user permissions.
will install to ~/.local . That's how I install it actually, but you'll need some $PATH foolery or do a to run the thing.

About the no debug output, I put in a -d debug flag, -h will explain the options.
I think I know what is going on, the MtGox API takes amounts and prices in integers, so a 1.00000000 bitcoin order amount is requested as 100000000. This is to prevent rounding errors because of the incompatibility of decimal division and binary hardware. So, rather than hardcode these multiplication factors for each market pair, they are requested from MtGox when the program starts. This way a change on MtGox's end doesn't make your ask prices ten times smaller than you thought.

To compound that, MtGox specifies 10 seconds between API requests. I've set the minimum request period to 5 seconds because 10 is a little ridiculous if you are trying to do interactive stuff. So, when the program starts you have an API request for the bitcoin multiplication factor, a request for your counter currency multiplication factor, a request for your account balance, and probably a request for the ticker. That means 10 or 15 seconds before your bid/ask buttons are enabled and 20 seconds before the tickers register prices. So I would try it again and wait and see what happens.

Refresh rate is in seconds, and if I were looking over the code I would start by looking at all the import statements to see which libraries and capabilities get pulled in and where.

No, north america. Originally I thought I'd try and make a program that would multiplex exchange accounts and dwolla accounts, so the thing was going to be called dreiklene.

I think it'd be cool to have a little interpreter and a set of predefined variables and functions to implement stop-loss and bot logic, which could be stored as scripts. That is easier said than done but I'm working on charting for now which should any statistical analysis readily available.

MtGox API authentication uses a key and secret, the key identifies you, and the secret is for signing requests. You only see the secret when you create the key/secret pair, so you'll probably need to create a new pair.

As for the SSL handshake error, I would think that would only happen if MtGox's SSL certificate couldn't be verified.

That extraneous QtSql dependency has been removed, and that precision problem is fixed. Pull from git and reinstall and that should fix it.



You will have to enable the market, the exchange, and the account from the two settings dialogs and then restart the program, I'm working on having the settings change the display dynamically right now.

It should be fully cross-platform but I have not tested it on windows or OSX yet. I don't know what is involved in getting it running on windows but I plan on looking into it.

I should note that passwords and API key/secrets are stored plaintext, so keep that in mind if you run one of those crappy backdoored OSes or don't encrypt to disk.

Are you tired of in-browser trading? Garish graphic designs got your inter-pipes clogged with cookies? Should you hit refresh or wait for that trade page to load? Is hand formating API calls because you lost your yubikey becoming tedious?

Then for you I present tulpenmanie, a multi-market exchange client: https://github.com/3M3RY/tulpenmanie

It displays tickers, makes limit and market orders, cancels orders, and can initiate bitcoin transfers between exchanges.

Right now I'm working on supporting streaming exchange APIs which looks like I'll be overhauling the exchange module system. I get that done and I can move on to things like charts and depth tables.

Supported exchanges:

• Bitstamp
• BTC-e
• CambBX
• MtGox

I'll be adding more, queued by volume.

Requires Python-2.7 and PyQt4.
Unless you're on Gentoo it's manual install only for now.
Gentoo install instructions

I've got it to run on windows, and I plan to make an installer. Please be patient, I don't have a windows install anywhere. Rest assured that I am making every effort to maintain cross-platform compatibility. First I need to stabilize what I have before I can deal with OS's that I never use.

Getting it to work on pre-intel OSx is almost impossible. As for later versions I don't know.

Consider it in beta for now.
If there are questions or problems I lurk in the #bitcoin channel when I can, nick EM3RY.
If it seems like there questions below that are answered above, it is because I previously didn't address those questions in this message and have made an edit.

If only it were that simple. You see they replaced mine at no cost to me, then said they couldn't send one at all. One way or another, they did not follow their terms of services, but instead made stuff up as they went along.
First they told me they'd send it to a new address, it gets refused at my old address, then they wont send it back again to the old address.

My point is it's really not safe to assume MtGox's inconsistencies in services and policies will work out in your favor.

What does MtGox's terms of service say about yubikeys?
So what happens if you lose one?

The fact is MtGox has no clear policy on accounts with yubikeys. The terms of service do not seem to clarify the meaning of "inactive", "cancel account", or "termination of account". If you lose your yubikey, MtGox might be nice and violate their own terms of service, or they might repeat "We apologize for any inconvenience caused" until your six months are up.

If you do have an account with a yubikey take your money someplace with competitive service policies in place as fast a possible, lest you get robbed like me.

Early adopters are making a risky investment and doing work that if successful, later participants will benefit from at little or no cost to themselves. Keep in mind this is all voluntary, if the central banks of prevailing currencies want alter the money supply, participants don't have much say or much of an exit. With bitcoin the inflation is known to participants from the offset, and no one has to use bitcoin.

I want out of here, please.

https://github.com/3M3RY/python-mtgox