Using the online computer, you can look up all of the unspent outputs of all of your addresses. You will need all of the transaction ids and all of the indices where the outputs you want are. Then using Bitcoin Core, use the createrawtransaction method in the console or through the command line and create a raw transaction. Make sure that all of your Bitcoin is accounted for and that you have included a fee. The fee is determined by the difference between the inputs and the outputs. Send all of the Bitcoin to an address in a new wallet you created on the offline pc. You must be very careful. when you create the transaction,. You will get the raw hex for it. Take the raw hex to your offline computer and sign it. Then broadcast that transaction through Bitcoin Core's sendrawtransaction method.

yes that is correct.

Yes, you can. There is nothing that can possibly disable the wallet once it has been used once.

Everything should be fine once the new watching-wallet imports to your online pc.

What Goatpig was saying was that once everything is synced, you should create a new wallet on your offline pc and transfer all of the coins from the old one to the new one since its moment of being online and unencrypted (since you didn't enter a password) exposed it to potential attack. Do this if you are paranoid.

You are misinformed. There are small outputs called dust which, if a dust output is detected, won't be relayed or accepted to mempools since transactions with dust outputs are considered non-standard. The dust threshold changes with the minimum transaction relay fee which is set by each node (meaning the dust threshold changes for each node). The current default is 2370 satoshis. It used to be 546 satoshis.

I don't think that output is considered dust. AFAIK the dust threshold is 2730 satoshis, and that output is a little more than double that.

I don't think so. There are many legitimate uses for reusing an address. For example, many people on this forum have tip jar addresses. A lot of people also use web wallets. If those services began blocking used addresses, then those with tip jars may not be able to get tips.

I would say that the length doesn't matter. If the post doesn't add anything of value to the discussion, then I consider it low quality. Short posts like your quoted one can be very helpful, and sometimes long posts don't add anything to the discussion. And I agree that many sig ad spammers will post long winded posts full of complete nonsense just so that it looks like they are posting something that contributes so that they get paid.

Yes, I do admit that I was wrong (I am not an egotistic bastard who thinks he's always right  ). But of course, things didn't happen the way that I though they would when I made that assumption. I figured that it would backfire if a large number of people began running NotXT, which didn't happen.

rpc.blockchain.info won't work unless you put in the details for their rpc server. What is probably happening is that your firewall is blocking the rpc requests. You need to open up the rpcport you specified (probably 8332) in both the firewalls on server with the bitcoind and on your router.

However, this is highly not recommended. You should have the bitcoind on the server that you are hosting the site on, or at least on the same local network. If you don't then that means that anyone may be able to access the rpc server and access the wallet. It would open it up to the internet and thus open it to attack.

What do you mean by wallet deatils?

It needs to connect to the server over the network, and to connect to the local computer, its hostname is localhost. What was it before you changed it?

While NotXT didn't backfire, you cannot say that just because XT died that that was due to NotXT. You cannot substantiate that claim. XT could have died for a number of other reasons, not  because if NotXT

How long have you waited after it freezes? Bitcoin core is known to sometimes take a very long time to start up.

The .1 will still be available. Blockchain.info will just show your balance as negative until they drop the unconfirmed transaction

Are you sure that it worked? Just because XT is pretty much dead doesn't mean that NotXT did its job. Can you provide proof that XT died due to this? And NotXT didn't necessarily do its job either.

The 0.1 you wanted to send was sent. And if your balance deducted 0.2 (which it probably did) then it is wrong.

Well if they had changed that without informing and giving developers enough time to update their software to where almost everyone uses compliant code, then the network would essentially be DoS'ing itself. In your scenario, both transactions would have been "bounced" if they used High S, making it an even bigger inconvenience to users. That would have been a bigger perceived failure of the bitcoin system, not just the fact that someone can malleate their transactions and thus make spending from an unconfirmed transaction an even worse idea (given that it already is a bad idea).

Do you have the tx-index enabled?

Will there be an android app for it as well as a web interface like Google play does?

Will it be open source?

When the release was announced in the bitcoin-dev mailing list, the email included the information about the change of the minrelaytxfee. However, this was never mentioned in the website for some reason.

Just wait a few days and the transaction should disappear. Blockchain.info will automatically remove the transaction from their database when it remains unconfirmed for too long and that it is also a double spend.

No, that is not true. You did not spend twice as much, your spent exactly the same amount. One of the transactions is useful, it is confirmed and can be didn't fun. The other is completely and absolutely useless. It is unconfirmed and will remain that way forever. Your balance does not change except for the amount you wanted to spend.