Please stop spreading misinformation. We know that you didn't get your question answered and are now butthurt. Your posts aren't doing you any favors as you are spreading misinformation and acting like an immature troll.

Armory is not a one-man operation. There are still multiple people who are actively contributing to armory, myself included.

And neither would I. I follow the advised security practice of verifying the source code myself and building from source. You should do this too.

Maybe you missed the first part of his statement when he addresses the security:


If you can't follow that advice where he EXPLICITLY says "Don't trust me" and you don't do anything else to verify that nothing is malicious, then that is your own fault. If he were to release a malicious Armory version, then the other people who work on armory such as myself, droark, josephbisch, fanquake, etc, would notice that he inserted malicious code into the software. If he did it in the binary and not the git source, then simply following the advice of "review the code and build it yourself ... [or] find someone you trust that did it for you" would protect you from such actions.

We are also working on a system similar to Bitcoin Core's gitian builds which will ensure that the binaries are built from the source code that it is supposed to be built from.

You should update the software. The latest software doesn't have this issue anymore.

You will have to rescan the blockchain. The software does not rescan the blockchain when it reindexs or resyncs, it simply isn't something that should normally happen. Start Bitcoin Core with the -rescan option and it should fix your problems.

You use a USB drive and download the file to it. Then verify the installer and take it to your offline computer and install. At not point is the offline computer then connected to the internet. This security isn't a meme, it is just security for the paranoid.

You can earn bitcoin in the exact same way that you earn any other money. You can sell some sort of good or service for bitcoin

You can't. As was said by Belcher in the thread you mentioned, there are two forks, the Bitcoin Core fork and Bitcoin Classic. I'm not sure if sure if any of them have faster confirmations. You should only use the Button Core fork because that is more representative of the mainnet state.

It is working for me. What error do you see?

Fixed

No, that is not an example of a merkle tree. In fact they are talking about two completely opposite things. A merkle tree is a cryptographic structure, the node stuff is networking.

A merkle tree is a tree of hashes. At the base are individual hashes, in the case of bitcoin, those hashes are the hashes of all of the transactions in a block. Each hash is hashed with another hash. The resulting hashes are the next level. This process repeats until only one hash remains. That is the merkle root, and that is included in the block header.

For the nodes, Satoshi was talking about node policy for accepting transactions to the mempool. His statement is currently used. If a transaction contains a fee that is too low, the node will reject it. That threshold for Bitcoin Core (the most common node software) is 0.00005 BTC/Kb. This can also be configured by the node owner.

Testnet mining power tends to vary a lot. Considering that testnet has forked, it is likely that there is not a lot of mining power on testnet to have fast blocks

It is a full node wallet which makes it very secure. I would say that armory is more secure, but a lot of its security come from its utilization of bitcoin core.

Multibit if an SPV wallet, which is subsystem less secure than a full node.

Goatpig was one of the developers when ATI was still working on Armory. There isn't any "extra risk". You can check that it is trustworthy the same way that you would check any other open source software: examine the source code and build the software yourself.

It has to rescan the blockchain, which can take a while. Honestly, I have no estimates as I haven't had to do a rescan in a while. It shouldn't take more than a few hours to complete. Once it is done, the bitcoind will be used normally. There is no need to restart the program and it shouldn't stop itself.

It isn't Bitcoin Core that is eating up all of the space, but rather the blockchain. You can enable blockchain pruning and it will save you a lot of space. Just start bitcoin core with the -prune option and it will prune the blockchain so that it only uses a few Gb instead of 60+ Gb.

Make sure that bitcoind is shut down when you run this. It will start bitcoind.

No as embedding data in any form into the blockchain is generally frowned upon.

Generally any application which uses OP_RETURN or other methods of storing data in the blockhain us frowned upon by a larger portion of the community, especially those who run full nodes. Your data, even though a few thousand transactions annually, have to be stored and maintained by full nodes for eternity. Those transactions are generally considered spam.

Then you will have to contact the sender and have him resend the bitcoin. I

Alternatively, if you have a copy of the transaction (as in the raw hex code for the transaction) then you can keep rebroadcasting it so that the network remembers the transaction so that it may eventually confirm.

Just restart bitcoind with the -zapwallettxes argument. This removes all of the transactions from the wallet and rescans from the beginning so that it will remove the unconfirmed transactions. You should then be able to respend those Bitcoin.

This is normal behavior. After a few days, the network "forgets" unconfirmed transactions due to the natural node restart cycle which clears the node's mempool which contains the unconfirmed transactions. If it is "forgotten", then you should see the Bitcoin back in your wallet and be able to resend it, but this time with a fee.

No. Full nodes provide the entire blockhain and all transactions that they receive and accept. That is the information they provide, not the information if the nodes that connect to them.