The hashrate can be calculated from the expected rate of finding a block (144 a day), the actual rate of finding a block and the current difficulty.
So let's calculate the average hash_rate for a single day:
expected_blocks = 144
difficulty = 11187257.461361 # this is on May 22nd 2013
blocks_found = 155 # Also May 22nd 2013
hash_rate = (blocks_found/...
I've not touched a large part of my online wallet (two weeks), nor the paper wallets under my sink (two years), but they are by no means disappeared, idle or lost. There's really no way of telling, no matter how much thought is put into it.
Some coins can be called lost, that is they don't have any associated private keys known, but there's no way of ...
This chart can answer that question for any period you choose:
Measured in BTC, the average transaction value was naturally the highest in the early days of bitcoin when its value was much less in fiat terms
The network hash rate can be statistically inferred from the difficulty and the rate at which blocks are found. It's just a more complex version of the fact that if you know that someone is flipping coins and heads comes up 800 times an hour, they're flipping about 1,600 coins an hour.
The ledger chain stores all transactions. So yes, you can rebuild the transaction history.
But the validators don't need to store or serve the whole chain to operate. A new validator only needs the last closed ledger to validate new transactions.
This is different from bitcoin, where nodes need the last output of the relevant public key to validate a new ...
It is impossible to tell lost coins from stored coins, because there is not way to tell if anyone has the private key associated with a foreign address.
The only coins that can realiably be declared lost are those that have been assigned to invalid recipient addresses.
not sure what you mean by logarithmic graph. The time in a logarithmic scale, or the value? On both, there is a "log" button below the graph. And you can export as CSV or JSON:
As mentioned, raw transactions are incredibly easy to screw up since you must explicitly pay yourself if you want change.
Here's a few scenarios besides unbalanced outputs which will produce huge transaction (Tx) fees:
forgetting to pay change
forgetting to convert to Satoshis in your code
misplacing the decimal (perhaps due to rounding errors)
The blue bars indicate the transaction volume in that period, this is how many bitcoins have been traded. Use the blue numbers at the left axis to see how many bitcoins were traded.
The yellow line is the average weighted price in that period. Use the yellow numbers on the right to see what the price is.
The green and red parts show the fluctuations (high &...
In my opinion, you should not use Mt. Gox as an indication of the price of Bitcoin. The price on Mt. Gox is significantly higher than the other exchanges, because sellers must be compensated for the difficulty of getting their money off the site. Instead, you might use BTC-e for pricing info. Here is the chart you ask for:
There's a start and an end that can be quoted, and only one is required although both can be used.
If you want US$ per BTC data from a 24th April until now until now, use:
If you want all US$ per BTC data until now, use:
I wrote a bitcoin price theory is about a correlation of number of bitcoin addresses
(from blockchain) and the bitcoin price, with a law of networking use like the metcalfe law.
here I posted my study about your question
How to determine the Software (Core, Classic, XT, etc.) and quantity
on the whole network?
connect to host and take the 'user-agent' string from 'version' packet
How to determine the last 1k blocks and their Miner Software?
the miner can be determined by analyzing coinbase transaction.
the software can not be determined
It would seem using a large Tx fee is an attack vector in that miners will all realign to try and solve the block at height n, which is quite different to the normal situation where it's usually two chains competing for length. The outcome requires 100% "rational actors" trying to mine the block height n and the ability of the nodes to detect the errantly/...
It simply is someone with a lot of coins, who sold on the open market and depressed the price (temporarily). It was an economically unwise decision, since they missed out on the fair market value as you saw.
This is one example of how the Powerful Elite can Thwart Cryptocurrencies.
At the end of the Day this is a very trader specific questions. Trading with a moving average system is dependent on the traders preference. If you do not understand the best way you personally should be trading, you are likely setting yourself up for failure from the beginning. I recommend you read "Trading for a Living" Dr. Van K Tharpe
There are hundreds ...
List of all sites I know of
http://www.coinorama.net/ (only graphical order book)
http://bitjoy.org/~ (order book in "to do" list)
Speaking as a programmer, it's VERY easy to screw up the transaction fee. If you're not using a known bitcoin client and are making your own, it's quite easy to accidentally leave out an output or calculate things wrong. The blockchain won't accept your transaction if you're spending more than the inputs, but will happily accept transactions if you're ...
EDIT: perhaps what I am seeing is due to different graph scales for the two values?
Yes, these two values are plotted on the same graph, but against different axis. Which line is higher/lower on the graph relative to the other is of no real interest.
Looking at the site in question, I can currently see that the y-axis on the left lists the 'Market cap', ...
263.95 [USD/BTC] / 233.56 [USD/BTC] * 1 [BTC] = 1.13 [BTC], i.e. for each BTC you sold at the higher price, you can rebuy 1.13 BTC at the lower price.
The underlying concept is explained on Wikipedia: Cross-multiplication.
All of the exchanges have APIs http://pubapi.cryptsy.com/api.php?method=singlemarketdata&marketid=155
you can create a script to keep the numbers updated with wget and a cron job
Cryptsy has a pusher API for live updates.
I think you are viewing the metric incorrectly. The notion of Bitcoin Days Destroyed is not relative to any other standard of measure. Rather, it is the standard of measure.
To clarify, there is no "gold standard" for Bitcoin Days Destroyed saying "if all Bitcoins had been spent within X weeks the total would be Y". That just doesn't make any sense. Think ...