Yes, but for a full node that is segwit capable, it WILL receive the witness data. Once segwit updates, running a full node without segwit should not be optional and is less secure since that node cannot verify the signatures of segwit transactions.

The problem is XP. There are known problems with 0.12 with XP. See https://github.com/bitcoin/bitcoin/issues/7674 and https://github.com/bitcoin/bitcoin/issues/7639. However i don't think it will be fixed since XP support from Microsoft has ended and thus fixing an XP only problem is not worth it to the core devs. See https://github.com/bitcoin/bitcoin/issues/7681 for the discussion about that.

No. You are incorrect. The signatures are required to validate a block. Full nodes need that data in order to verify the block. If the node announces that it supports segwit, then it will receive the witnesses to validate them. It is not optional for any full node. For reference, a full node is any node which fully verifies all transactions and blocks it receives. This includes pruned nodes and "archiving" nodes.

What coin?

BTW this belongs on the altcoin section.

Yes, they are.

Yes, you are mostly correct. The witness data is sent to nodes that have the proper service bit set. When segwit activates, nearly all of the miners will have this bit set so they will be receiving all of the witness data. The data will be omitted if the node doesn't have that service bit.

That's up to you to decide. You figure out what you want done and then implement your idea and test it. There is no simulation here, it is just do and test and see if it works. The Testing occurs on your private blockchain so as to not spam one that people actually use.

You can make your own blockchain. Either create an altcoin or use Bitcoin's regression test mode. This mode creates a private bitcoin network and blockchain which you can use to test and experiment with.

The buyer or seller contacts the escrow to arrange an escrow of a good or service.

The escrow creates an escrow address. This address can be either a normal address or a multisig address. The multisig address requires that 2 of the 3 parties involved (seller, buyer, escrow) allows the transaction from that address to happen. It is extra protection.

Then the seller sends the funds for the payment to the escrow address. The product is then exchanged. If it is a digital good and the escrow can verify it, then it is sent to the escrow. The escrow will verify the good and if it meets what the buyer stated that he wanted, it is forwarded to the buyer. If the buyer likes the product, then he tells the escrow to release the funds from the escrow address to the seller. If the buyer doesn't, he can dispute.

For physical goods, usually it is just the seller ships the item to the buyer and the buyer will verify that the item he received was what he wanted. He then informs the escrow to release the funds. If what he got wasn't what he wanted, he can dispute.

If a dispute happens, the escrow mediates. He takes information and evidence from both parties and decides who gets how much of the money.

That is how escrow typically works.

It's pretty close to being finished

Probably. I think it will be merged in ready for a release by the end of April.

The actual transaction hash is ff96ced7178cb83d6c17cfa677bef877ec67e37061ad71fc2e4cca13c2b84ac4 without the -000 on the end.

However, when you look that up the transaction doesn't exist. This means that your Bitcoin did not go anywhere. Because you were not synced, it is possible that your transaction was spending from inputs that were already spent from and this caused a double spend which is rejected by the network.

Once your wallet is synced, you need to remove that transaction from your wallet. This will then allow you to spend your Bitcoin as it is not actually gone. To do this, you must start Bitcoin Core (I assume it is Bitcoin Core because that is the only wallet that has -000 in the txid) with the -zapwallettxes option which will remove your transaction. Then you can spend the Bitcoin again and it should go through.

Nope. Not possible.

You would need to decrypt the keys. The encrypted keys can probably only be decrypted at blockchain.info but, because their software is open source, it should be fairly trivial for someone to modify the code to decrypt your private keys.

Yes. It depends on the software and service whether to show the confirmations. Blockchain.info stops showing them after 120 confirmations I think.

Most likely. People have figured out how to encode the data for a virus in the blockchain but that cannot do anything since the virus is not executed. However, you need to make sure that your antivirus doesn't delete any files in that folder (and the bitcoin data directory in general) otherwise that will cause you to need to resync.

The updated Windows version is already out and posted on https://github.com/goatpig/BitcoinArmory/releases/tag/v0.94.0

Confirmations are the number of blocks built on top of the block your transaction is included in with 1 confirmation meaning that the block your transaction is in is the most recent block. As the blockchain grows, the number of confirmations will increase indefinitely. After about 2 confirmations, your transaction is fairly safe as it is unlikely that the block it is in will be orphaned and thus potentially reversed. After 6, your transaction is pretty much guaranteed to not be able to be reversed (although this guarantee really happens around 2 or 3 confirmations.)

Unless the payment to another person can be routed through you (by being a hop), I think that Alice would need to close the channel in order to pay someone else.

Nope. Transactions between two people that happen in a channel (meaning it doesn't go through hops) won't have any extra fees. The fees only come in if you have to have the payment hop through other nodes.

Yes. That's the point. It removes the recurring micro transactions like faucet payouts from the blockchain.


Not necessarily. There will be plenty of transactions happening on chain because they are not recurring payments. Opening and closing channels also has to pay fees.

Yup. It should be fixed now. The transaction had already gone through a while ago, whenever it got its first confirmation. It is just that your wallet was not fully synced so it didn't know about the transaction. Now that it is, it does not about the transaction and you can spend from it. You should now be able to spend that Bitcoin and receive more without any issue.

Yeah, you are way behind. The current blockchain length is 404765. You should uncheck auto connect and tap the button next to Server. Then choose another server from the list and then tap OK. You may need to restart the app by double tapping back and then opening the app again.