Interesting project. Not fit for Armory's use case sadly. We're looking to send the data over wires, with speed in mind.

You are losing track of the conversation. I was presenting the concept of address renewal as recommended by Satoshi's white paper and implemented in Armory in the context of change addresses, in order to explain the tagged change addresses. I don't really know at which point you had it all slip into "address re-use is bad, we are trying to to put an end to it"

You fail to see the benefit here apparently. You receive coins in address A and B. You spend some with A and get change back in C. You spend some with B and get change back with C. Now A and B are linked.

The issue at hand isn't to force people into a certain behavior. That stance is actually untrue as far as Armory is concerned. With expert mode and coin control, you can reuse addresses as much as you like.

The issue at hand is to make sure people do not compromise their privacy by default. Change is an automated concept, for reasons I doubt anyone would oppose. As such, this automation shouldn't reveal informations that it doesn't have to by default. Then there is expert mode, for those who wish to consciously alter that automation.

People complaining about fees is recurrent. However, the Armory team has no power on that front. This discussion doesn't belong here.

If you want to allow for no minimum fees, you can modify the code. It is actually quite a simple modification.

That's my responsibility. However it isn't at the top of my priority list just yet. Busy with a wallet recovery tool and Trezor integration for now.

Armory follows the Bitcoin network rules. Keep in mind that Armory uses BitcoinQt as its interface to access the Bitcoin network, so all transactions it creates are broadcasted through the core client, and thus cannot break the transaction rules as implemented by the core team.

Fees are calculated by the size of the transaction, its value and the age of the coin, so it is possible to send 0 fee transactions indeed.

There is indeed a difference between Armory crashing and Armory hanging. We plan on adding some UI notifications to make the distinction easier.

Armory is brought to you at no charge. Our resources are limited, which means you need to be patient and help us diagnose these issues. So, for the 3rd time, send us your log files at support@bitcoinarmory.com

On a side note, I think I found the fix for this particular bug, which will be pushed to the next release. But again, if you don't let me see a log file, I cannot know if this bug I fixed is the one you are experiencing. Thanks for your patience.

You can specify any address in your wallet to receive change with the coin control feature in expert mode.

[[change received]] labels an address as having being used for change. The address is of course still valid, as it holds your change. the Bitcoin protocol strongly recommends to not reuse addresses, mainly to protect your privacy. So, as default, Armory picks a new address in your wallet every time it needs to send you back change. The corollary is that Armory will not pick that address again for change, and it will mark it as such, so that you may abide to that recommendation.

Of course this remains a recommendation. Addresses marked as change do not have their mechanics altered in any way, and you can use them to receive other payments at your leisure. It simply is considered bad practice, and Armory makes a point of offering you the opportunity to use the recommended way as described in Satoshi's white paper.

The offline bundles support Ubuntu 10.04, 12.04 and 13.10. The offline bundles come with the necessary packages to run Armory on a pristine Ubuntu install for these version. There are quite a lot of Linux distributions on the market, so just saying "comes with Linux installed" isn't enough to identify the specifics of the operating system your hardware is running.

As for the installation steps: Grab the version of Ubuntu you want (I'd suggest 13.10, the link you posted is for 10.04, which is fine), burn the ISO to a DVD and install away. Then grab Armory's offline package, extract it, browse to that folder and run: sudo dpkg -i ./*

This will get Armory and all its required packages installed. As for moving the offline bundle to your offline computer, either use a usb key or burn it on the DVD into another session, you should have enough room left.


LvM: The fees enforced in 0.88.1 were hardcoded based on the calculation mechanics used by the Bitcoin network at the time it was released. Those mechanics were updated since then, and newer versions of Armory comply to those. You can either update your version, or modify the code in your older version.

As for how the fees are decided, this discussion does not belong to the Armory sub forum, nor does the Armory team have power over such matters. If you have complaints, take them up to the core team.

Depends how hard Namecoin has forked from the core Bitcoin source. Armory grabs its data from the raw binary block files created by the core client. As such it trusts the core client with block verification. This makes porting Armory rather easy.

Assuming Namecoin uses the same transaction signing scheme and EC as Bitcoin, you're left with node port, magic words, fee calculation and dust sweeping/ignoring rules to change. And everything else I possibly overlooked =P

Then the DB was corrupted early on. Currently calling --rebuild doesn't actually destroy the DB files before creating new ones. It writes over it instead. We intent to fix that for 0.91

At this time, deleting the DB folder manually is the right way to fix the crash.

It means none of the keys you trust have signed the Armory offline key. If you pull the offline key locally and set its trust level higher, the warning will go off.

In the context that you download Armory through a  VPN or a proxy, or anything remotely critical for that matter, you should verify you got what you expected with PGP.

I think his comment was that regardless of how you acquired Armory, you should check it against the provided signature, which is good practice.

There are cross platform webcam solutions, although the multi platform part may narrow the usable hardware list. We definitely intent to support webcam interfaces for QR code scanning in the future, so don't despair just yet.

Ubuntu is close enough to Debian that an offline bundle targeted at Ubuntu has a high chance of working. With Tails it's another story. First of all, Tails is a live CD. It doesn't come with as many packages as a local installation of Debian or Ubuntu.

The second point is that it is possible the Tails team got rid of certain packages that usually come with a Debian live CD. So my guess is that none of our offline bundles would run as is on Tails.

The best approach here is to compare what is needed specifically for Tails and tailor a 'ready to go' bundle for it, since the offline part makes little sense for Tails.

The file is signed with Armory's offline key.

The .asc file carries the signature. As long as you verify this signature was made by Armory's offline key, it doesn't matter where you are pulling it from.

The backup is an extra file used to perform drive IO operations twice. It's main purpose is to confirm data was properly written to the wallet. The backup and its designated wallet carry the exact same information.

You can save either the wallet file or its backup, or both. Paper backups allow you to recreate deterministic wallets. It guarantees you can reproduce all the possible key pairs your wallet can yield. Keep in kind that a paper backup does not carry information about imported private keys, as those were not produced in a deterministic fashion, using the wallet's rootkey and chaincode.

The chaincode is now extracted out of the root key, obviously in a fashion that can't reveal the root key. It increases recovery security in the sense that the chaincode isn't generated in an isolate fashion regarding the root key, so a damaged chaincode can be recovered.

It increases determinism in the wallets while maintaining the same level of security.

You should send us your logs files at support@bitcoinarmory.com

Keep in mind Armory is an open source software, brought to you at no charges, which means we have limited ressources. While most users have good a good experience with setting up Armory, some edge cases have a hard time. In that case, get in touch with us, give as much informations as possible and arm yourself with patience.