Its an average of bids/asks at given amount of BTC.
My question is: why there is sometimes shown depth of up to 200 BTC, sometimes up to 500 BTC? What about to zoom there using mouse wheel, please, please?
|
|
|
Always look at the bright side of life. Imagine the volume of fees all exchanges (BTCChina included) are earning! Maybe MtGox will end this year in black! ;-)
|
|
|
I really start feeling stupid for not selling a single coin since I bought some in late summer... It seems that all bulls sold at least some of their coins during the runup? But on the other side, I do not have many coins and I believe a much greater value will be achieved during the next years, so I don't want to "lose" some due to bad trading (even I'd profit $-wise). It just feels strange to lose more dollars than I ever owned...
I thought the same on April this year. Calm down, everybody.
|
|
|
If I remember correctly, Creditanstalt was fused into Unicredit few years ago. Maybe that's the cause of this collision.
|
|
|
Alert. Incoming BIG RED CANDLE ...
|
|
|
Possible bug of Android client:
When I use Custom Send and specify exact address (with enough funds) to use for input and set "Create new" for change, the transaction will not be created and sent. It shows "Sending" and then returns to the same window.
|
|
|
bitaddress.org can decode it, works offline.
|
|
|
You can always roll enough times to generate at least 256-bit entropy, form it as e.g. string (1536123 ... ) and hash it.
|
|
|
CoinJoin is like collecting 20 of 100 USD bills into a hat and then passing the hat to another group of 20 people, each one takes its 100 USD bill. Noone knows who gives you which bill.
|
|
|
Changes made on blockchain.info modify only the cloud-stored password-protected blockchain wallet (wallet.aes.json). Of course, it can't modify your backups etc.
So, you can safely delete private keys from blockchain.info *IF YOU HAVE THEM ELSEWHERE BACKED UP*.
Of course, if somehow your private keys got leaked, deleting them from some wallet does not improve security. Who knows the private keys, he can use the funds on those addresses.
If in doubt, convert larger amounts to new addresses in cold storage.
|
|
|
1000 EUR withdrawal. Ordered on 2013/10/19, came through 2013/11/11 (noticed it today). 43 days to Sweden. I should NOT have sold those coins 11/11 - 19/10 is 23 days, not 43.
|
|
|
What happens when we hit 266? Expect large drop (correction) before we hit 266.
|
|
|
Do not trust anyone using COMIC SANS ..
|
|
|
I think it's more beautiful if you put € sign before the number, like $ world does it. Also amount of decimals used for € is more than 2, which is unnecessary, and amount of decimals for btc is only 2 which is too few. (top page) I'm really excited with your exchange. Hope it succeeds Since mtgox is basically down and btc-e seems untrustworthy there really is an alternative needed to bitstamp. Thanks for the support and thanks for your suggestion. I'm not sure if we'll do it, but I like the idea of putting '€' before the number. As for 2 decimals being too few, do you mean for 24 hour volume at the top of the page? What the hell with putting '€' before the number? I own TWO EUROS, not EURO TWO. No need to mimick all US idiosyncrasies. I guess Foot-Ball is enough at all.
|
|
|
I would prefer mixing arbitrary values of BTC. Ideally, the adversary should not be able to distinguish on-purpose mixing transaction from normal multiple input/multiple output transactions.
That's why I would like to do the mixing kind of automatically, from the queue of transactions to be mined.
If there are signed transactions A1+A2->X1+X2 from one user, B1->Y1+Y2 from other, etc., there should be a mechanism how to "RESIGN" mixing large transaction A1+B1+A2 -> X2+Y1+X1+Y2. If both A and B sign this and add a slighly better fee, it will be mined. It may look like double spend, but this could be solved using special "propose transaction" message instead of "broadcast transaction".
Thus, the Bitcoin transfers of users, who do not know each other, will be, kinda automatically (think of "offer for mixing" checkbox in Bitcoin-QT) mixed together by the network prior to be mined. Could save some blockchain space, too.
|
|
|
Bitfury. 240 Gh/s. 500 W.
Passive cooling of 500W? Are you serious?
|
|
|
Note: Please, I encourage someone to check the research I did and post "yes it's true". I still have the felling that this is too awkward to be true, and I may have made a mistake somewhere.
I hacked short script pulling out nonces from blockchain.info and the statistics (even on first 2k blocks) are similar to yours. Please, could you upload somewhere the block number, nonce and extranonce list for first 20k blocks? The theory of 59 machines can be proven/discarded on independent statistical analysis on the expected hashrate of each such machine, they should be kinda consistent in time and independent on each other.
|
|
|
We should know whether Satoshi was generating blocks at difficulty 1 too slow (and needed multiple machines) or too fast (and needed to discard already found blocks). Does anyone know what kH/sec one could expect from 2009 CPU and C-style SHA256 implementation?
|
|
|
|