Search content
Sort by
Showing 12 of 12 results by martinkou
I can't spot any errors apart from that you seem to be mixing up Python 2.x with Python 3.x syntax (the u"" thing belongs to 2.x, all strings are automatically unicode in 3.x). The HMAC and the post data should be all correct. I thought the chr(0) might mess up Python's encode("utf-8") but it didn't.
What are you using to submit your request with? urllib.request.Request? Unlink Python 2.x, the urlopen() in Python 3.x doesn't submit your headers, you'd need to use the Request constructor instead. So if you're copying code from people using Python 2.x, you may end up not submitting your headers at all.
What are you using to submit your request with? urllib.request.Request? Unlink Python 2.x, the urlopen() in Python 3.x doesn't submit your headers, you'd need to use the Request constructor instead. So if you're copying code from people using Python 2.x, you may end up not submitting your headers at all.
Does anyone see a problem with deflation and massive hoarding after all of them have been printed out?
Yes, you are right. Why would I sell my bitcoins, knowing the price will always go up. A market can only exist with a bid-ask side.
Well, simple - it doesn't *always* go up. It dropped to $55 last week and rose back to ~$135 today. And if you look at the charts the price can fluctuate by 3%+ in a single minute a few times per day. The real world isn't as simple as some economic model you see..
Stash your wallet files inside encrypted files (via TrueCrypt, for example) in a Google Drive and a Dropbox. If your computer burnt down, you'd still be able to access them on another computer. If one of the services corrupted your encrypted file, you'd still have another service.
The other guy is most probably using Python 2.7 (or lower), where the str means byte string, not Unicode string as in Python 3.3.
If I were you I'd try changing the str() into a bytes() and remove the encode() at the end.
There're other parts of the auth logic that you haven't shown in your code though (and those might be wrong) - e.g. do you have a monotonically increasing nonce in the post message? Is the post message url-encoded?
If I were you I'd try changing the str() into a bytes() and remove the encode() at the end.
There're other parts of the auth logic that you haven't shown in your code though (and those might be wrong) - e.g. do you have a monotonically increasing nonce in the post message? Is the post message url-encoded?