Updated config file to comply with new Bitstamp API version. Simple erro...

[willeeklund]

Updated config file to comply with new Bitstamp API version.

Please also consider creating a new release of the npm module. The 0.0.3 release today does not take the new version of npm module "bitstamp" into consideration, making it uncompliant with new updated Bitstamp API.

Thanks for a great repo!

[askmike]

Thanks, I will merge this in even though the current dataprovider for bitstamp (bitcoincharts) is not recommended ( see #77 ).

We are working hard on a new version which keeps a local database for historical data so we can leverage the Bitstamp's own API. Check it out here (note you should consider it alpha). Here you can read up about the discussion (it started out as a problem with CEX.io, but the same goes for bitstamp).

When that branch is nearing a stable release we'll make sure that the Bitstamp trader is updated to work again.

Please also consider creating a new release of the npm module.

I am the author of the module and it's already updated for a month or so, however due this new API we couldn't get Gekko running on it anymore reliably. Because the module changed to much updating the required one for Gekko would break Gekko.

[askmike]

This has been fixed since 0.1.0.