Upgraded, deleted old databases, and am now running without issue!

That should work. As long as the wallet is in place before bitcoin core has a chance to prune anything it will work properly. The trouble comes when bitcoin core prunes something before the wallet had a chance to look at it.

I'm sorry to hear that Alan will no longer be working on Armory. Goatpig, I'm glad that you will be continuing the work. Armory has been my go-to wallet for many years. I appreciate all the hard work that you both put in.

0.12.0 introduces DB obfuscation to prevent false positives. It is my understanding that this work by xor-ing the block files with seeded random stream. If armory tries to read the block files it won't be able to. Is there any plan to work around this? If not, I'm guessing that there would be a way to disable the feature in bitcoin core, but I'm guessing it would at least take a reindex.

As always, thanks for the updated version!

Bitcoin.org still has the old downloads. https://bitcoin.org/en/release/v0.11.0. If you need to use 0.11.0, make sure to disable UPNP (https://bitcoin.org/en/alert/2015-10-12-upnp-vulnerability).

I believe that the reason why bitcoin stores its block per user instead of per computer is to make the system more trust free. Imagine that you are on a system where you trust the administrator, but not the other users. If another user messed with the blockchain files it could mess up your balance or transaction history. As long as proper filesystem permissions are in place, they won't be able to mess you up with the current default configuration.

Glanced at deponzit's code (diff) and didn't see any glaringly evil so I'm running that code now. Please don't consider this a full audit or anything. Overall it appears to be working, but it is a bit odd that you need multiple accounts to setup lending multiple currencies. Not a big deal, but a bit unintuitive.

I having trouble connecting using Firefox on Windows. I get https://imgur.com/L4Uhi9y. Also looks like there are lots of warnings from SSL Labs https://www.ssllabs.com/ssltest/analyze.html?d=bitcoinwisdom.com.

What is the plan for compatibility between Armory and a pruned version of Bitcoin Core? I assume that for now, if I run Bitcoin Core with pruning enabled, Armory won't be able to scan the blockchain files and therefore won't work. Two possible resolutions that I see are:
1. Make a rule that Bitcoin Core isn't allowed to prune any blocks that Armory hasn't indexed yet. This would probably involve a couple of new RPC calls that I don't believe exist yet.
2. Allow Bitcoin Core to run completely pruned, but then Armory might skip some transactions if Bitcoin Core prunes them before Armory indexes them. I believe that by just looking at the UTXO, Armory should be able to figure out all of the available/spendable bitcoin, but it wouldn't be able to find any intermediate transactions.

Its been a couple of weeks. Any progress?

Sounds good to me. Keep up the great work!

If that is the design, then I would have expected to see "XXXXXX" for the sender. Right now I am just left questioning what is/who controls 3J98t1Wp...

I just found this in 0.93.1. When I received a transaction, and brought up the advanced transaction info, it shows the wrong Transaction Inputs.


That same transaction on blockchain.info shows the correct inputs. https://blockchain.info/tx/20a62730bfa6d74baef15208e0a3456841eb9679c52b2b6b2ff4cc8eb35131c0?show_adv=true

This might be a dupe of https://bitcointalk.org/index.php?topic=919202.msg10372366#msg10372366, but that was a while ago.

Looks like its been a little over a year since the last Bitfinex Audit. Any word if/when another will be happening?

Late bug. The link to "lockbox documentation" on the lockboxes screen leads to https://bitcoinarmory.com/about/using-lockboxes/ which is a Page Not Found error.

Not exactly "a tool to monitor BIP 66 acceptance status", but closest thing that I have seen. bitcoin.sipa.be/ver-ever.png

Thats fine for monitoring nodes, but for the soft fork what matters is hash power. https://blockchain.info/pools shows that if the right 6 pools upgrade, then that will trigger the soft fork.

I'm probably too late for 0.93, but on the Announcemnts tab, I believe it should only show Notifications relevant to the running version. Right now I see 2 notifications that don't apply to 0.93 (One is all the way back from 0.90).

Is there a way to make MarginBot also lend out my BTC balance? All I see are options for USD. Right not I have my money stored in Bitfinex split between both USD and BTC because I'm not sure which direction the market is going to go.