Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

{'result': None, 'success': False, 'message': 'INVALID_SIGNATURE'} #136

Open
karthikdhanusu opened this issue Feb 8, 2018 · 9 comments
Open

Comments

@karthikdhanusu
Copy link

I made the following changes in bittrex code still I am getting invalid signature error

request_url += urllib.parse.urlencode(options)
signature = hmac.new(self.api_secret.encode('utf-8'), request_url.encode('utf-8'), hashlib.sha512).hexdigest()

can someone help me ?

@karthikdhanusu
Copy link
Author

It works with python 2.7 not on python 3

@FullKickProductions
Copy link

I'm also running into this error!

@FullKickProductions
Copy link

Is there no workaround? I have to stick with python 3 to support some of the other libraries I'm using! Any help will be hugely appreciated.

@cryptobeaver
Copy link

You can run Python 2.7 and 3 in separate install folders (i'm on mac) and then when running python 2.7 you just call it with python2.7 if my memory serves me right.

@FullKickProductions
Copy link

Thanks for the response @cryptobeaver, The trouble is that my application has to use python 3.6 in order to support some of the other libraries. I don't want to drop support for any of them, but I would like to support bittrex trading. Unless I can call the bittrex methods from python 3.6, I'm going to have to find another exchange to work with :(

@forgetso
Copy link
Contributor

forgetso commented Dec 2, 2018

Bump

@hpr0009
Copy link

hpr0009 commented Dec 5, 2018

Bump again

@forgetso
Copy link
Contributor

I have fixed this in a fork: forgetso@6d0cb93

@g0tzz
Copy link

g0tzz commented Mar 25, 2019

I have fixed this in a fork: forgetso@6d0cb93

I'm still getting this error even with your fix. Anyone still having this issue? Or are you using V1.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants