good job, thank you for patch
|
|
|
kraken adds multiple currency pairs for NMC, please add.
|
|
|
Lol Bitstamp,
Are you frikkin kidding me?
Params: time - time frame for transaction export ("minute" - 1 minute, "hour" - 1 hour). Default: hour.
Sneakily remove the day param after denying us full historical data?
This is a joke...
Think who is the architect of current solution, who accept it, who is not fixing it, who did not officially notify users about the chance - which may results charting services to multiplied volume of transaction!
|
|
|
are you going to be listed on bitcoincharts.com? it could be the best advertise I believe.
|
|
|
any chance for kind of newsletter for your API updates? I'm interested to go back to bitstamp when you will fix transaction method.
|
|
|
what with transaction api method? This one current api method is not acceptable for production use. How long do you think we will wait before moving our assets to other place?
|
|
|
I am wondering if you can add code to convert the date and time to GMT time. I am trying to do some analysis on BTC price and its correlation and some more analysis with stock market index and some other index. Once we can figure out those stuffs, maybe we can publish a R package for BTC analysis.
The dates field in data from script should be in GMT already. To have the same TZ during the processing I'm using adjusted globally for whole project in RStudio. It would be great to have a R package related to bitcoin, I have already a lot of code for that (which include mtgox/bitstamp private api calls with authorization (also v2 for mtgox) and it is possible to add new markets). The blocker currently for me is a lack of documentation for that code. If anybody with experience of publishing R package would be interested to create one I would be happy to contribute. I would need to simplify some codes, drop some dependencies (example. RpostgreSQL), but I wanted to create package from my codes so it is on my todo list someday.
|
|
|
Attention, Bitstamp transaction api no longer works with offset parameter ( https://www.bitstamp.net/api). This means that any charts which will not handle that change might be affected! Bitstamp just changed that without any notification! Dear bitstamp, We need to have an argument to pass to transaction method which indicates not time to fetch (day/hour), but to get trades after particular tid. Please leave DEFAULT behavior as it is currently but extend method for such thing as offset/tid param! I already contact the bitstamp support, tried to rise priority, but after 2 days, no reply so far.
|
|
|
good to see any feedback I put your comment in the instruction.
|
|
|
now it's working fine, was the whole pastebin offline or only this one link?
|
|
|
2. buy btc at 999999 price, sell btc at 0.01 price - how to calculate the amount to put in POST request?
This seems like the best solution. It looks like a cheap hack, but I don't see how it can go wrong. yeah but for such price you probably could buy a very small amount of BTC, if you have 100000 USD you can only place order at 99999 for 0.01 btc, right? you buy only 0.01, looping again until you sellout all fiat?
|
|
|
I don't believe there is no solution/workaround for that, anybody?
|
|
|
anybody used it? any experience, feedback?
|
|
|
you need to wait for ltc on mtgox, currently they are trading only credits not moneys. I'm working on my bot and going to open source it some day, but currently some coding and setup skills would be required but I don't have time make a doc.
|
|
|
there are more issues with their data/doc info. There is a threshold in the TID field, 4 of the past trades are with 0 amount. It needs to be handled in the volume weighting process. I recommend my scripts described above to fetch it's full and up to date archive.
|
|
|
Hi,
Bitstamp API does not offer instant/market order placement through API, only via UI. I've tried ask support with no success. Can anybody recommend me the most efficient way to achieve such order placement?
Some possibilities: 1. as on mtgox I tried to place an order with no 'price' argument - api call returns error caused by lack of this param 2. buy btc at 999999 price, sell btc at 0.01 price - how to calculate the amount to put in POST request? 3. buy at ask depth price, sell at bid depth price - orders might be not completed, should be put in loop, can be difficult to achieve when there is lag on market 5. any other way?
Thanks in advance
|
|
|
I'm interested. I think you need to write requirements point by point. ex. compare prices in expected depth and market fee, check lag, perform buy/sell, conditional buy on successful sell, transfer btc, transfer fiat, etc. You are quite new user so escrow the bounty to some well known person on the forum would be good idea.
|
|
|
But if you think you have a different approach and want to do it, feel free to create your own script I think I will try MtGox trades history download R script - https://bitcointalk.org/index.php?topic=286755no bigquery, no middle hosts, simple logic, opensource, output to csv/sqlite
|
|
|
|