Learning, and improving, the Coinbase tutorial.
I could find these bugs in the Coinbase Python library (pip install coinbase), and/or their server code:
- client.get_notifications() - the official code creates a
TypeError: unhashable type: 'dict' - verify_callback() - key missing in their package, lack of documentation, and a bug.
- invalid (empty) HOST header - Django refuses your POST requests (RFC 1034/1035). [Fixed - but do read how!]
- "Do you want to add it?" (a fee) when small amounts - but no way to answer. Clicking "Pay" doesn't work.
Additional to those:
- In my .py code below ... I have caught most of the exceptions caused by your wrong syntax, or implementation - while I was working through your introduction. If you are really interested to improve your tutorial, then you can find them either in the source code or in the output.
- Read my ideas what else could be useful extensions, for future versions of your API.
I would have found more bugs, and suggestions - but I want to be appreciated too. Stopping this working-for-free now. Simply donate (below) - and I might continue.
The main purpose of all my .py code here ... was to try out all explained functions once, so that I better understand the whole coinbase system. Mission accomplished. But I am publishing it now, because it might help others. Intended for:
- Coinbase newbies: Run these one by one, to learn how coinbase works.
- Coinbase devs: Which inconsistencies & typos I have found in the official Python tutorial.
Chapter by chapter:
- output of cbWallet.py = testing: Guides ... Create a wallet
- output of cbSendRequest.py = testing: Guides ... Send and Receive BTC
- output of cbBuySellBtc.py = testing: Guides ... Buy and Sell BTC
- output of cbPriceData.py = testing: Guides ... Price Data (*)
- output of cbAuthenticationBasics.py - Custom authentication for Coinbase API = Guides ... API Key Authentication
- output of cbNotificationsBug.py - uses that custom authentication to get the provoking data. I hope that helps you to debug your erroneous code.
Do all this with a sandbox account!
- cbPersonal.py = your API key goes here.
(*) This produces (among other things) a neat table of all the currencies (In non-fantasy exchange rates only when not on sandbox but on real api.).
All this is work in progress, perhaps more to come ... current version: v09
Using my new tool FiledatePunchcard to give a rough estimate of the time that I have invested into this.
Each 'x' represents a 30 minute block:
Filling up blocks of size 6, i.e. approx 180 minutes.
2016-01-10|-----------------------------------------------x|
2016-01-11|x |
2016-01-12| xxxxx|
2016-01-13|xx xxxxxxx x x |
2016-01-14| |
2016-01-15| x |
2016-01-16| |
2016-01-17| x |
2016-01-18| xx |
2016-01-19| xxxxxxxxx |
2016-01-20| x |
2016-01-21| xxxxxx |
2016-01-22| x |
2016-01-23| |
2016-01-24| |
2016-01-25| |
2016-01-26| xxxxxxxxxxxx|
2016-01-27|xxxxxxx |
2016-01-28| |
2016-01-29| |
2016-01-30| |
2016-01-31| |
2016-02-01| x |
2016-02-02| |
2016-02-03| |
2016-02-04| |
2016-02-05| |
2016-02-06| |
2016-02-07| |
2016-02-08| |
2016-02-09| |
2016-02-10| xxxxxxxx |
2016-02-11| |
2016-02-12| |
2016-02-13| |
2016-02-14| |
2016-02-15| |
2016-02-16| |
2016-02-17| |
2016-02-18| |
2016-02-19| xxxx------|
With 30-minute blocks, the number of hours is approx 35.5
Probably more, because the above is heuristics, and only registering filedates, which are overwritten with each (non-committed) file saving. And additional to that approx. 15 hours on January 8th-10th (before I made a git committed version of this).
(C) 2016 Andreas Krueger
If you like this, show it: [BTC] 1NvfRSDzXmwUdTjeqN8MAfmPCNHgwB8eiC
And if you do not show it - then ask yourself: Aren't you showing that you don't like this?
No Coinbase account yet? Then use my referral, to give me and you 10$ bonus.
hire (at) andreaskrueger (dot) de