Whoa, what? What 400k? Did anyone steal 400K? Is Zhou connected to someone stealing 400k? Where did you get that figure from?

The last time I checked this thread, Aurumxchange was holding $40k of Zhou's money or something to that nature, and Chen was caught stealing something as well, which Zhou is trying to get back from him. Refresh my memory.

There's no particular reason Bitcoin is incompatible with VAT-style tax systems. Think about inverting the situation.

Right now discounts for paying in cash is obviously a tempting deal for both parties because the buyer has no particular incentive to help the tax man.

The government could provide a rebate for reporting transactions to it. This is too much hassle for people to do today, so they rely on tapping the banking network to view transactions. But if you have open source clients and an automated, open payments system like Bitcoin nothing stops you having software that automatically reports things you purchased to the tax authorities who then effectively "cut you in" on the resultant tax take.

Alternatively, businesses are required to register the root public deterministic key, so the tax collectors can generate all the public keys that the business will be using. Random audits and/or micro-payments to consumers for reporting transactions mean the collectors can cross-check against the public addresses. If a business requests payment to an address that isn't derived from the right root key, it's obvious they are not reporting all their income.

It's not clear to me that our current tax system (in the UK) is the best way to do things, carousel fraud is a fairly obvious problem, but I feel that with further research a country could come up with a remarkably efficient and fair tax collection system that leverages Bitcoins strengths.

Version 0.82.1

This version doesn't look a whole lot different, but it now creates an $(ARMORY_HOME_DIR)/armorylog.txt file which contains a ton of python logging information.  I couldn't redirect C++ output to file very easily, but most problems to date have been resolved through the python messages/errors.  I touched a ton of different pieces of code, and this needs some serious testing.  Help me out!   And if there's mysterious problems, use "File->Export Log File..." to create a copy of the log file to send me!  Feel free to check the log and tell me if what you think of the information it contains (and remove any info before sending).

Also added a version check.  There's a fake updated version so that you can see the pop-up it shows you and how it displays info.  I'll be removing the fake version before I actually release this version.  You can see a full changelog by going to "Help-->Armory Versions..."


Windows 64-bit installer
Windows 32-bit installer
Linux 64-bit Debian package
Linux 32-bit Debian package

For those of you compiling from source:  version 0.82.1 is the "logger" branch.