No, there are no Debit cards that are available for free. No business would do that, it isn't profitable. If you want to use a debit card, you should have enough money to pay the fee anyways. If you only have a few dollars worth of Bitcoin, getting a debit card is not worth it.

The government won't let that happen. Bitcoin's price is too volatile for them so they could lose money from accepting Bitcoin. They also think Bitcoin is that illegal magic internet money which, since it is "illegal", then they can't accept it.

You missed the most important Bitcoin website ever: Bitcoin.org

This is interesting. It is one of the few cards that will actually work in the US! Also, it is unlike other "debit cards" in that instead of funding the card with a prepaid amount, it actually deducts the Bitcoin from your account at the market rate, like Bit-x. And there are no fees for now. I wonder how long that will last.

I don't get it. What can this do that I can't already do with my own server. It is just a glorified server with apis to do stuff with bitcoin and the ability to generate a few satoshis for whatever. It might be good for beginners, but honestly, is there anything that this can do that I can't already do in my own server running bitcoin core (besides mining)?

Bit-x I have heard is the best debit card. I have used Wagecan before and it is ok. Setting up can be a little bit troublesome and the balance doesn't update with each transaction.

Part of the validation is to check the version number. If the version number is not a certain number or higher then the block is considered invalid and it is rejected. Miners will never mine on an invalid block.

If you have the seed, then you can restore your wallet and will have all of your bitcoin.

Oh, wait, I misread the thread.

Can you provide us a screenshot?

When you reinstalled Electrum, did you have to go through the setup a wallet wizard again or did it immediately load? What does Electrum report as its network status?

Did you export the keys from your Android and import them to Electrum? If you didn't there is no way that the desktop one would know about your address.

Technically version 4 blocks are being made (they have to be in order for the forking mechanism to know when to fork). According to the BIP, when 750 out of the last 1000 blocks are version 4 or greater, then the new rules will go into affect and OP_CLTV will work. After 950 out of the last 1000 blocks are version 4 or greater, then all new blocks that have a version number less than 4 are invalid.

Basically, contentious hard forks, and any sort of fork in general (hard or soft) requires consensus. The fork should only occur once a supermajority of the users switch to use the new rules. In most cases supermajority is defined as 95% of the last 1000 blocks, but its definition does vary. Without reaching supermajority, multiple competing blockchains can cause a loss of confidence, insecure network due to miners splitting to other chains, confirmation issues, and will in general be bad. This is why any code that involves any sort of fork, contentious or not, requires a supermajority before the node begins to enforce the new rules.

0.12 will have the wallet enabled with pruning. Pruning is already enabled in 0.11 with the -prune option when you run it.

I don't think there are any major compatibility breaking changes from 0.10 to 0.11. However, they still released 0.10.4 to backport the OP_CLTV code to 0.10 in case there is some difference between 0.10 and 0.11 which breaks some systems. They aren't actually updating 0.10 and writing more code for it on the side. They are updating the master branch and then backporting any significant code changes that should be released soon like the OP_CLTV soft fork stuff, stuff for fixing the upnp bug and enforcing LowS signatures.

The release has been tagged in the bitcoin repository and the release notes are available on the repository at https://github.com/bitcoin/bitcoin/blob/0.10/doc/release-notes.md. I think the problem is that not enough people have done the gitian builds (they require 3 or more people to continue with a release) so it cannot yet be released.

That is actually not correct. The address is a valid address, it just cannot spend the Bitcoin from the GENESIS TRANSACTION. This is because that transaction isn't actually in the unspent outputs database and never will be. All of the other transactions that go to it can be spent because those transactions are in the unspent output database. So actually of that 66 BTC, only 50 of it cannot be spend. The remaining 16 can be spent.

I think it should be something generic, not something ultra specific to one wallet.

It is not, where are you getting that information. The PIN is stored on the device itself. It would be stupid to store it on Trezor's servers. Again, why do you keep saying that it won't work? Trezor keeps the important data on the device itself, not someone else's servers.

The only problem I have with this is question 5. You are assuming that everyone is using Blockchain.info's wallet, which is not the case. In fact, it isn't even recommended to use blockchain.info's wallet. You should instead change that answer to something about how it is practically impossible to brute force a private key due to the massive number of possible addresses. You should also have something in the answer about good passwords and choosing a good and secure wallet.

Many wallets allow you to generate paper wallets locally. Also, most websites which let you generate paper wallets are open source. The idea is that you download the code for the website. Then you take that code and go to an offline computer and generate the address there. That way there is no way that the owners of the website could ever know the private keys and the private keys are never exposed to the internet.

The developers agreed and there was consensus to include OP_CHECKLOCKTIMEVERIFY in this version and on. The actual enforcement of BIP65 for this will only occur after 951 out of the last 1001 blocks have version 4 or higher. Read the info about it in the release notes in the OP.