It's because the Total column is not the cumulate sum of the column Count but of the column Amount. In your example, at the line for price 1612, Total=6.0 and indeed if you do the sum of all amount of the price above 1612 it gives you : 0.3+1.2+1.7+2.8 = 6
I emailed them about this:
The limit is measured per IP address and per account. So for one
account (regardless of the number of key/secret pairs) 60 requests per
minute can be made via our API. When you are using multiple
connections (IP addresses), the combined sum of all request for the
account in question will used to determine if you are ...
You are submitting a float value. Float values are not totaly accurate:
Thats why the specification requires a Decimal datatype:
>>> from decimal import Decimal
The problem is not with the timestamp, it's with your method of converting the timestamp to local time.
As this SO question describes, convert it this way:
var dt = new Date(0);
Which prints Sun Feb 07 2016 07:03:52 GMT-0500 (EST).
I have posted an answer regarding the code in the stackoverflow question, but if you just want the raw (or sample) data for either BTC/ETH/LTC from Bitfinex or HitBtc, you can head over to my website at www.cryptodatasets.com.
All the data is free, and gets updated every day.
It is fairly common for exchanges to only provide a limited amount of historical data. Tradingview and other sites that have more historical data store it themselves on a database. With 2 hours of data you could ping the exchange API once every 2 hours adding the new data to your database each time.
What you fund your account with is irrelevant to this question.
If you take a long position against a USD pair, you'll borrow USD and pay USD interest. If you short a Coin you will borrow that coin and pay its interest.
Eg. Open long position on BTC/USD for $1000, you'll be borrowing $1000 for your position and would have to pay back $1000 + Interest.
This is not really a bitcoin related issue. As long as the exchanges have 100% reserves, they can always pay. This means they need to have the sum of all balances of all customers on their own account.
The problem is that some exchanges apply a fractional reserve. Using part of the users money to make investments or to cover operating costs. You are ...
until the BTG fork is complete, sending bitcoin to a 3rd party might risk your access to BTG.
that said, sending anything to bitfinex might be a risk in itself, given that there is accusations public that bitfinex has no bank accounts and may be involved in multiple accounts of fraud.
always do your due diligence.
never trust random strangers (me included)....
The documentation of the authenticated side of the API from where these orders are created states the following:
After a te message you receive shortly a tu message that contains
the real trade id (TRD_ID) and additional/updated fields.
These updated fields are for example fees that are charged afterwards.
Although from the public side of the API this ...
This is a shortcoming of the Bitfinex API. For example, say you have 0.5 BTC and you'd like to buy as much ETH as you can with it, you need to calculate how much ETH it might work out to and then pray the order book doesn't change between the time of your calculation and the time of the order. The feature to use all available funds isn't a good solution. ...
Its the return rate. So instead of just setting a return rate at lets say 0.019%, you're return rate is the market rate. It updates once an hour. It makes it easier for you so you don't have to log in all the time to adjust you're rate.
Imagine. You set a rate to the current market rate of 0.049%. Then you get a few loans but the market rate drops to 0.019%....
This is the total number of orders at that level. A count of 1 means that 1 order is at that price point. A count of 6 would mean that there are 6 orders at that price point.
The problem might be, that the JSON data does not contain line breaks. I was facing the same issue. My 'subscribe' call had no effect until I added line breaks to the JSON data. I haven't even gotten an error message back from the API.
You could use JSON library for Java which will handle the correct formatting for you.
Please note, there are some existing ...
This is possible. It also may sound good on paper, but the implications are horrible.
Think of it. 100 thousand bitcoin. 0.5% of all coins will be rejected. This is out of 21 million. Out of the current 15 million, maybe 0.65%. That's hugel
If a hacker also wanted, he could move the coins into multiple mixers and deposit them in and out of Exchanges, as ...
My finding for bitfinex rate limit is this: 1 second is divided up in milliseconds. 60 requests must span the entire second.
For example, if you have a foreach loop you'll get a rate limit error in less than 15 requests, because you are querying too fast. So add usleep (microsecond sleep in PHP) to span your requests for the entire second and or have ...
In well regulated markets (Bitfinex's aim) traders should have the ability to profit from movements in both directions.
Shorting also assists in the formation of price bottoms. The only way a short seller can capitalize after a down move is by buying back the shorted BTC. This has the net effect of creating buyers after a down move which helps bouy the BTC ...
Shorting is normal trading transaction on real financial markets. Without shorting you would not be able to speculate and profit on price decline. Assume that btc price is 400 USD and you think that the price will go down. By shorting one bitcoin you simply borrow one bitcoin from some lender and sell the bitcoin for 400 USD. If your assumption is correct ...