You communicate with it like on any other system or like any other JSON-RPC interface. You use HTTP POST to send JSON encoded commands to the rpcport and you will get JSON encoded replies.

If you just want to interact with the RPC server from the command line, you can use the provided bitcoin-cli.exe binary.

In order to enable the RPC server with bitcoin-qt, you need to start Bitcoin Core with the -server option or add server=1 to your bitcoin.conf file.

Yes. There is a segwit developer's guide: https://bitcoincore.org/en/segwit_wallet_dev/ which explains everything that needs to be done to implement all parts of segwit. The BIPs also explain most of this.

I assume the "extra space" you are talking about is the witness data "extra space". That space is for witness data only (and it really isn't actually a separate "reserved for witness data" space in blocks either). Since only the signatures go in the witness data, you still have the rest of the transaction that must compete for the "normal" block space too. There is no guarantee that your transaction will get included in the next block.

There currently is no address for the native P2WSH and P2WPKH outputs yet. Bech32 has been written and proposed but not yet finalized.

Segwit addresses for now will the be the nested P2SH type. There is no difference between these nested types and any other p2sh address for sending to them and receiving payments with them. You send to them as you normally would any other address.

For spending from these addresses, the nested output is the redeemScript of the p2sh address and then the rest of spending it is as normal spending from a P2WSH or P2WPKH output. This is all detailed in BIP 143: https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki

Yes

The move command is something for Bitcoin Core's internal accounts system. It does not actually create a transaction, it just changes the balances of 2 of the accounts that are internal to Bitcoin Core. Since the accounts system is going to be removed, there is no need for the move command anymore and it too will be removed (along with many other RPCs that are for accounts only).

To actually send Bitcoin with RPCs, you should be using sendtoaddress or sendmany.

It would likely be the other way around as every loses confidence in Bitcoin (i.e. which Bitcoin is the real "Bitcoin"). Anyways, this discussion is speculation and off topic.

No, that is incorrect. Armory still uses Bitcoin Core. ArmoryDB is just another layer of Armory (the part that interacts with Core) abstracted into its own binary. This is to allow for litenode functionality in the future.

That output is the change output. Inputs are spent in full, so the amount that isn't in the output for the intended recipient must be sent to a different output that the sender controls. That other output is the change output. It is like paying for a 10$ item with a 20$ bill; you receive back to yourself 10$ in change.

Yes. The current blockchain history is kept on both forks so your pre-fork balance will carry over to both forks.

This should be fixed in the testing builds. Try installing the third testing build: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.3-testing and see if you still see it (I don't see it).

This topic has been moved to Trashcan.

Duplicate

You are trying to spend an input that has already been spent. The first input of your transaction is the output at index 30 (aka 31st output) of 9a3a928c596b662812559eff97c63d6a559c03bc6463684237a8f31427d78562 which was spent in 27a7c6023e00080c4627bc0afaf0a200412491f1f44d0fac03fae8bde507acce. Since this output is already spent, your transaction is a double spend and is invalid.

Is the datadir correct? If you go to Help > Debug Window, it will tell you what your datadir is. If it is not correct, go to the folder where Bitcoin Core is installed and find the bitcoin-qt.exe file. Then open a command prompt window. Then type
and hit enter. This will start Bitcoin Core with the prompt to choose your datadir and choose wherever you want Bitcoin Core's data to be stored. You can then stop Bitcoin Core and start it normally, it will use the datadir you selected.

Also, you will need to reindex the blockchain. This is because you only copied the blocks folder and not the chainstate. The chainstate folder contains all of the databases, and without it, the databases will need to be rebuilt. The reindexing process looks like it is resyncing, but it really is not. It only looks like it is resyncing because it has to read through all of the blocks and validate all of them.

Anything that can sign a Bitcoin transaction is, by definition, a Bitcoin client. This is because bitcoin transactions have a certain format and algorithm for signing and require data that can only come from something that is designed for Bitcoin specifically.

It certainly is possible to have such a setup, and in fact, it is fairly easy to do. Armory is designed to make such a setup very easy to do. So you can install Armory on both machines, and on the online one, you also install Core and download the entire blockchain. On the offline machine, you install Armory and make a new wallet. Then make a watch-only version of that wallet and move it to the online machine via a USB drive. When you want to spend, you use the online machine to make the unsigned transaction (and all of the other necessary data for signing) and put that on the USB drive and take it to the offline machine to sign. Once it is signed, you take it back to the online machine to broadcast.

What isn't "starting"? What exactly are you trying to do and what exactly have you already tried? Are you using the -datadir option? The filesystem doesn't matter if the OS can read from it and it shows as a drive that you can read and write to.

If you have to ask, you probably shouldn't be doing this. Would you feel comfortable knowing that people are trusting you to keep their Bitcoin safe and that if you screw up, you will lose all of their money?

What wallet software are you using?

You can move the install of the wallet software to an external drive as you would with any other software. However the data will not necessarily move with it, but moving the data depends on your wallet software as each one does it differently.

---

Side note: Can you please skip the preamble in your new threads? It makes it difficult for people to actually find your question to be able to answer it.

You can make a paper backup of your wallet by getting all of the private keys in that wallet and printing them out on a piece of paper. However, I do not recommend that you do this as anyone who finds that paper can get access to your Bitcoin and the private keys containing your Bitcoin will change over time so your backup will become outdated. If you use an HD wallet and put the seed or master private key on the paper, that is slightly better, but means that anyone who finds the paper can steal all of your Bitcoin.

If you want to have your Bitcoin on paper instead of on a computer, I recommend that you create a paper wallet. A paper wallet is a private key (which can and should be encrypted) and address printed on a piece of paper. This can be done offline and the private key is not stored on your computer at any point in time. Once you create the paper wallet, you send all of your Bitcoin to it. This is more secure, but also much more difficult for you to spend your Bitcoin in the future. You can make a paper wallet through bitaddress.org. You will need to download the website (they have a github repo you can download from) and run it on an offline machine.

What exactly are you asking about?

If you want to have the blockchain stored on your HDD instead of the main SSD, then you can start Bitcoin Core with the -datadir=<path> option where <path> is the path to the folder where you want the blockchain to be stored.

Download what through torrent? The blockchain? If so, do not use any torrent to download the blockchain. It will be slower than allowing Bitcoin Core to sync normally.

BIP 148 is set to activate on August 1st. If it doesn't have a majority of the hashrate (which, right now, seems basically guaranteed), then there will be a fork. Even if it does have a majority, there still will likely be a fork, but not for long. Bitmain is also going to hard fork shortly after BIP 148 activates so there will be another fork. I think that on August 1st and for a few days after, there will be at least 1 blockchain fork event.