But cloudflare could still not access the private keys if one is using the plugin, right? Or could they still inject malicious javascript?
With the browser extension it would be impossible for them to alter the javascript. In a couple of days the site will be moving off cloudflare instead using several nginx proxies (
http://blog.unixy.net/2010/08/the-penultimate-guide-to-stopping-a-ddos-attack-a-new-approach/).
Ben can this be sorted ASAP please? I pmed all my details to you...
Looking at the addresses in your wallet there are many double spends which has caused the blockchain interface to get confused somewhat. I assume you are are using another client also?
The balance of 138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr is 1.309424 BTC, the other addresses are zero.
There are several transactions that were confirmed in the major fork a few days ago but have not confirmed in the new chain for some reason. Normally these transactions would be pruned however since they are already included in an orphaned block they cannot be removed, this is unusual and I'm not sure why they are not confirming. I have rebroadcasted them several times but it doesn't seem to have helped, the best course of action would be to double spend them with another client.
The following page shows which double spends in your wallet are unspendable:
http://blockchain.info/unspent?active=12U63dueaNH1ANWLe2XWF6uUqNnstyNi6c%7C138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr%7C149PQjaoTXLBkcX5wczcs947zcUbgTUdxp&format=htmlinsufficient funds. Value Needed 0.491646 BTC. Available amount 0.2915 BTC
i have .491646
There is 0.20027549 BTC available in address 17Wt5vmidhegUGXFiyiuQYc21QPb8rMYnC. Is there another address?
So ... I take it that there's a bug also with creating a shared address? I keep clicking on the green button to create one and nothing happens until it suddenly stops even letting me access that "Shared" tab.
Please try clearing your cache and reloading the page.
But I've set up my wallet to send notifications for received transactions only. What's that -50001 value? Why is it negative? It looks like it notified me about an outgoing transaction.
The address has received an output but the result of the transaction was < 0. This will happen when change is returned to the same address. I would just ignore any values < 0.
Apologies this was a bug I introduced last night, and should have been fixed this morning.
I think Puik must have scrapped the forum signatures for bitcoin addresses and added the text to the tags. I've seen other addresses like that on blockchain.info.
Yes this is correct.
-----------
The default display filter for address pages has been changed to "filter unspendable" which means double spends and transactions not confirmed in the main chain (apart from recent unconfirmed transactions) will be hidden. This means balances displayed on /address will be much more accurate of representation of the of the balance of an address even if it has received double spends or has received payments from an orphaned block.
If we use btctrada's address as an example:
"Filter Unspendable" shows a balance of 1.309424 BTC -
http://blockchain.info/address/138bqSSnWz23fNHe6qUHRz8LfieqVmvkYrViewing all transactions (Old default) shows a balance of 194.73778528 BTC -
http://blockchain.info/address/138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr?filter=0Filtering by confirmed only shows a balance 0 BTC -
http://blockchain.info/address/138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr?filter=5Wallet balances have always defaulted to "Filter Unspendable" however a bug has been fixed preventing the children of unspendable transaction being properly filtered (occurred when there was a chain of double spends).
Database improvementsPreviously when a wallet reached about 10k transactions fetching the balance and creating transaction would become a little slow. This has now been fixed and the speed of all the major API calls has been improved. This transactions should be very quick to construct regardless of the size of the wallet.
