Bought from itradebtc.com

IIRC the test string doesn't trigger in the middle of another file, so that won't do anything.

See https://bitcointalk.org/index.php?topic=509858.0

Specifically, a redeemable code -- either purchased from their website or from a prepaid card available in retail stores in some locations. Payment can either be upon delivery and successful redemption, or using https://bitrated.com.

Suggestion: rename "Bitcoin-Qt core developer" to "Bitcoin Core developer". It's not just the GUI, it's also bitcoind, and as of 0.9, it's being rebranded Bitcoin Core.

You can't possibly have a CAPTCHA in a system like Bitcoin. A CAPTCHA requires, among other things, that there be a computer generating it and keeping the answer to compare to. The question of "is this right?" is asked of whatever generated it and has the answer stored. A decentralized system has, well, no central point that can issue the CAPTCHAs and validate them -- if nodes are generating their own CAPTCHA, you'd be relying on the honor system, and there's nothing to stop modified software from bypassing the CAPTCHA check.

For one, this is created and endorsed by Jeff Garzik, a well-known member of the community and a Bitcoin Core developer. However, that doesn't matter -- using the bootstrap.dat torrent doesn't require any trust whatsoever. The Bitcoin software imports the blocks from the file, but it validates them first, treating them the same way it would if they came over the Bitcoin network.

If you want people to test, it would help to have the site running on the testnet, so tests can be done without involving valuable bitcoins.

Well, what are those "Problem Details"?

The removal of the CENT rule is only for relaying, not creating, free transactions.

Or another way I've seen it phrased, "I can't stop you from raping me, but please be gentle."

To clarify, the only reason that OP_RETURN is in marginally better than other methods of inserting arbitrary data into transactions is that it doesn't bloat the UTXO set, because it can be pruned from there.

You won't immediately notice anything wrong, until the moment when the software tries to access a block from one of those files, which could happen for a variety of reasons, including a node requesting it over the network. When that happens, it'll crash.

Have you tried restarting your device? If not, try that.

Are you able to tap on the button in the bottom right, to see your account identifier? If so, you can login to blockchain.info in your browser with the identifier and your password.

Is the device jailbroken?

What version of iOS is it running?

Look at my message -- that command won't work, you want the following command:
This is because in OS X, applications are actually folders. Bitcoin-Qt.app isn't an executable, the executable itself is a few folders in, I don't remember the exact structure off the top of my head. The `open` command will look at it from OS X's perspective, and do what you want.

Yes, you are able to change the listening port, and yes, if you change the listening port you will advertise your address along with the new port. However, unless I'm misremembering, the default behavior of Bitcoin Core is to prefer connections on port 8333, so you're unlikely to get many (if any) incoming connections.

The following commands should back up your wallet and then start the salvage operation:
Note that the salvage operation may take time (a 2-digit number of minutes), because part of it it a rescan of the blockchain.

You could use jackjack's pywallet to dump the private keys from the wallet, and then I assume Multibit can import them. I don't have personal experience with either of those tools, so I unfortunately can't give you specific instructions, but hopefully this will point you in the right direction.

Download the latest version, v0.5.16, from https://multibit.org/releases/multibit-0.5.16/multibit-0.5.16.dmg.

Once you've installed that, see if it fixes the problem. If not, the next step would be to try backing up and deleting (or just moving/renaming) the settings and other files, but an update may fix the problem, and if it does, it's easier than going through the process of moving the files out of the way.

What system (hardware and software) is this? Are you using the latest version of Multibit? Have you tried backing up your wallet, uninstalling Multibit and reinstalling it? Also, is that the full text of the error? Is there any traceback information before or after that, saying anything about where in the code the error is? Which line it's at, which function, anything like that?

A nice feature would be if you could see on the status page, next to each coin, a list of its parameters.