I bet I botched the build process and compiled for i386 instead of armhf.  We verified the build process worked, and then I made a script to make it easier, but I bet I did the script wrong.

I'm about to put out 0.91.1 with some tweaks to the wallet-fixing logic and the new Bitcoin Core download.  I'll see if I can fix the RPi cross-compile script.

It's actually on the first page:

https://bitcointalk.org/index.php?topic=29416.msg384034#msg384034

Though please doublec-check that's up to date.  It's been updated a couple times and it's possible I updated a copy of that svg.

Just to check it's not a problem with the wallet fix button... can you cancel fixing the wallet, and then simply double-click on the wallet and create a paper backup?  It will ask you for your password and then pop up the print window.  You don't have to print it, just see if it takes your passphrase, there.

This is a problem with Bitcoin-Qt/bitcoind/Bitcoin Core (whatever the heck it is called these days).  Armory is stuck until that is resolved.

I suspect this can be resolved by manually starting Bitcoin Core and reindexing the blockchain.  That should rebuild the databases that Bitcoin Core uses.  As much as we hate redownloading the blockchain, that may be required if you get the exact same error after you reindex.  Or if you don't know how to reindex, just redownload.  Armory includes a new BitTorrent downloader on Windows and Linux that downloads the blockchain as fast as your bandwidth will allow (sorry Mac, you get decent compatibility in 0.91, but not any of the torrent features).  It still takes a while for Bitcoin Core to verify it, but the whole process is like 5-10 hours, instead of 24+ 

We have a new feature in 0.91-beta:  "Help"->"Factory Reset".  It will wipe all settings, unconfirmed tx, and all databases for both Bitcoin Core and Armory.  I meant to have an option that allows you to wipe the databases without deleting your settings, but not much I can do about that right now.  Your wallets will still be untouched, and automatically loaded when you restart.

If you go that route, make sure your wallets are backed up (as an extra precaution), use the factory reset and wait.

Nope!  Armory actually uses Crypto++, not OpenSSL.  Though even if we did, offline computers would be unaffected (as far I can tell from the little I've read about -- I've been at a conference all day and haven't had time to dig into the specifics of the heartbleed stuff).

Speaking of the conference, check this out -- I was on Bloomberg TV!

http://www.businessweek.com/videos/2014-04-07/why-are-people-so-excited-about-bitcoin

Got the joy of being invited to speak on Bloomberg TV after giving my talk on best security practices.


http://www.businessweek.com/videos/2014-04-07/why-are-people-so-excited-about-bitcoin

FYI:  The host (Trish) was obviously quite skeptical about Bitcoin.  That clip was preceeded by an description of recent Bitcoin woes, that included the "plummeting value" and that Bitcoin had been "banned in China and Russia."  Glad we got to offer a little counterbalance.

Yup.  That's where we're going next.  But we need a new wallet format to do that, and I wanted to get some usable multisig tools released before we go down that path.  Most of this will remain useful or at least can be recycled to support the full linked wallet solution.

Introducing Multi-key Lockboxes by Armory Technologies, Inc.

Armory Technologies, Inc. has come a long way since we incorporated 9 months ago.  We now have 5 full-time developers, and for the first time since I started Armory I was able to take my hands off the steering wheel, and focus on innovating, instead of just bug fixes and testing.  This gave me the opportunity to do something I've been wanting to do for a very long time... Multi-signature transactions!.  

I've been busy getting a form of multi-sig implemented before the conference this week (Apr 7-8), but without the new wallet format, yet.  This isn't a waste of time, because this kind of interface should be available for one-time escrow situations where you won't need a full wallet, anyway.  And in the short-term, it can used for low-volume, secure savings (when it's ready in a few weeks).

In the end, it turned out to be more than just a demo: it's actually quite usable!   See screenshots below.  If you can compile from github, you can play with it on the "multihacker" "devel" branch.  More details below.

Keep in mind the multi-key lockbox interface is an advanced tool.  All manual data exchange, multiple steps, multiple wallets, etc.  But just like offline transactions, I think we've taken something that is inherently quite complex, and made it about as simple as it can be without centralization.  We will be providing a server-assisted mode in the future which will make this far easier, but it will always be usable without a 3rd party service.

UPDATE: lockboxes are now being updated on the "devel" branch

---

Multi-key lockboxes:

WARNING: This is not ready for real money!  I have powered through the design process to get it demo-ready for the conference under time constraints.  Over the next couple weeks, we will be fixing all of it's limitations, reduce bugs, add simulfunding, and test it!  Until then, only use this with testnet!

A "lockbox" is created from a list of public keys (and some meta-data), and then anyone can put money into the lockbox.  To spend from the lockbox, one party initiates a transaction, and then circulates it to collect signatures.  Whoever adds the last signature can then broadcast it.





All data exchanged looks like the following example lockbox (go ahead and import it, see what happens):



Some great things about the current state of "Multi-key lockboxes":

• No central points of failure.  Private keys never exposed to any other device, and only used at time of signing much like offline transactions.  Armory lets you collect all public keys from all devices/parties, and creates a multi-signature address to deposit money in the lockbox.  
• Totally online/offline agnostic!  All circulated transaction data is treated as "offline" transactions, and thus includes data needed for secure offline review and signing!  You can mix any kinds of wallets you want, even do a 5-of-5 spread out between cold laptops kept in bank vaults in 5 different countries! (please don't do this yet, but it technically will be possible soon)
• Uses ASCII (base64) text blocks for easy exchange inline via email.   Armory used to use BIP 10, but that had some serious limitations.  A new format was created that accommodates all the quirks and security issues of exchanging data and offline signing (especially lots of complexities if P2SH is involved).
• Change is handled automatically:  It's handled by sending the change back to the exact same lockbox, which all remains transparent to the user, as always.  This is certainly "address reuse", but until we have multi-sig/linked wallets, we have no other choice unless you require the user to spend all or nothing.
• Completely decentralized:  We will add a server-assisted mode in the future, but we wanted to guarantee that it's theoretically usable if no servers exist.

Some current limitations of what's there:

• Plain multi-sig only -- limited to 3-of-3 on mainnet:  P2SH is theoretically supported, and I have designed all the data formats, and blockchain code to be able to accomodate P2SH.  But none of it has been tested, and requires a bit more complexity under the hood to make it work.  However, supporting P2SH will be required to go above 3-of-3 on mainnet, so it will be done. Eventually
• No simulfunding yet:  Certain types of contracts require both/all parties to send coins to the lockbox simultaneously (in the same transaction).  Again, I have designed the data formats to accommodate simulfunding, and even created a "Promissory Note" structure that can be exchanged like LOCKBOX and TXSIGCOLLECT blocks, but it's not complete yet.  Until then, these lockboxes are best suited when either (1) All devices are your own [you can't scam yourself], (2) All other parties are trusted, such as family members, (3)  Only one person is funding the lockbox.
• Expert tool!  All manual exchange of data: These are building blocks of multi-signature transactions.  Once we have all the mechanics in place, Armory will start hosting servers that will facilitate the exchange of this data (privately, of course!).  Until then, all data must be exchanged via email or shared folders.
• No signature merging yet:  Right now you must literally circulate the transaction to all parties, in any order.  Each party must sign it before passing it to the next party.  In the future, you will be able to send all parties the proposed transaction, they can each sign it and send it back, and the organizer can merge and broadcast
• All devices must be upgraded:  None of the data exchange formats are compatible with older versions

Using Lockboxes
You must be in Expert usermode on Testnet to use lockboxes!

• (1) One party/device is elected to make and organize the lockbox.  All other parties send them their public keys and contact info, etc (there's a new right-click menu in the wallet address table, to copy the hex public key).  If you are setting up a lockbox between multiple devices, you can simply use the addressbook buttons to pull the keys from watching-only wallets.
• (2) When the organizer is done creating the lockbox, and decorating it with contact info, lockbox description, etc, he will be given a "=====LOCKBOX" block of data to send to all the other parties.
• (3) Each other party will go into the lockbox manager and import the lockbox.  They will then be able to see its balance and transaction history only within the lockbox manage (from the the multisig menu)  There are no notifications.
• (4) Any party may send money to the lockbox by selecting it in the manager and clicking "Deposit Funds".  Or you can copy the ID into the regular "Send Bitcoins" window (from a regular wallet) in the following format "Lockbox[ID:z87Qnm42]".
• (5) To spend funds, one party is elected to create the spending transaction.  They click "Spend Funds" from the lockbox manager, which will open a regular dialog, but will only show UTXOs and balance of the selected lockbox.
• (6) Armory will open a "Signature Collector" window.   At any time, you can export the tx with all available signatures, to an ASCII block and email it inline to other participants, or put it on USB key or shared folder to get it to the other devices that need to sign
• (7) Once a sufficient number of signatures are present, the "Broadcast" button will appear.  Simply broadcast it and wait!

Final note:  No compiled versions will be available for a while.  If you can compile from the github repo, you are welcome to play with it and provide feedback, but we don't even want to give any hint that it might be usable for real money.  Check back in a couple weeks for updates!

---

Simulfunding is Implemented!

The simulfunding options menu.  Create notes, merge into a single tx, then sign and broadcast:


Each user selects a source wallet and destination lockbox to create a promissory note.  Then the organizer merges them into a funding transaction to be signed by all funders (right now no labels are passed through, so you only see how many participants there are and how much they are contributing, but not who is who...)


Once the promissory notes are collected, the parties have to sign.  This works identically to spend-from-lockbox (it's the same dialog).  Note that it only shows you the net value difference for each wallet, even though each "funder" is providing both inputs and change.  Armory figures it out.


As you can see, the final transaction has three different input wallets, and change back to those wallets as well.  

Sorry, my new release script forgot to pull it from the offline computer.  It will be posted to the website shortly.  Until then:

https://s3.amazonaws.com/bitcoinarmory-media/armory_0.91-beta_sha256.txt.asc

Sorry guys, running around like a chicken with my head cut off.  I did post 0.91 yesterday.  We have a conference tomorrow, and I'll be out for a few days.  Of course changing from X.XX-testing to X.XX-beta broke the notifications... gonna have to tweak some things.  But it is posted on our website.  We'll send out something to the email list too   (sign up on the webpage).

@forever3x:  I am going to guess you have lots of transactions.  Like thousands?  We are aware that we have a problems with that, and we're not exactly sure of a good short-term solution.  But any information about the wallet would be useful so we can try to run with a wallet like it to fix it in the future.

Haven't seen this one in a while, but we think it's caused by building your DB with the old version and corrupt blk*.dat files from Bitcoin Core.  Since your DB is already built, you need to rebuild it with the new version.  We'd love to know if this fixes your problem -- because we actually haven't run into the "don't-have-full-tx" problem on any of our own systems before, so we can't test whether we fixed it!

So please use "Help"->Rebuild & Rescan Databases.  With some luck that fixes it.  If not, I recommend you do a factory reset and redownload the blockchain (because this is ultimately caused by bad blk*.dat files which will only be fixed with a redownload).  With the new bittorrent stuff, it's a heck of a lot faster than it used to be!

Alright, lots of the issues with 0.90.99.5 have been resolved, and pushed to 0.90.99.7.  I just pushed the new version along with notifications.  Hopefully the notifications will actually work properly this time (no more "You are using version X+1 please upgrade to X+1!").

The website has "offline bundles" you can use.  It has a link to Ubuntu 10.04-32bit and a bundle that you can unpack and install on the first boot of a never-touched-the-internet boot of 10.04.  you should try it out... I made it for exactly the same reasons your complaining about here

Is this with 0.90.99.5?  We had a bug-fix snafu to make 0.90.99.5 and actually broke some ledger code that was leading to some missing, and some duplicated ledger entries.  That might be what you're seeing.  This should be fixed in .6+

Indeed, we haven't been keeping up with our changes to armoryd.py as much as we should.   We're in the process of piecing together some testnet-in-a-box tests which will automate the process of testing on-blockchain functionality in both the GUI and armoryd.py.   If you are an armoryd.py user, I recommend you hold out for 0.91.1, in which armoryd.py will get some more rigorous testing (though it doesn't mean we won't entertain bug reports and fix small things before the 0.91 release

no, 0x03 says "the next three bytes will be pushed onto the stack as a single object", then it reads and pushes those three bytes... the 3 itself is not pushed.

I'm pretty sure that goatpig already fixed this.   You probably don't see it because you've already pulled the fix that he pushed.

Hey japandrew73,

If Armory is bouncing on the dock, that's a good sign -- at least it's trying to open, and probably left us some useful messages in the log file.  If you simply double-clicked it without any command-line args, etc, then it created a log file in

~/Library/Application Support/Armory/armorylog.txt

Could you either post the contents, or just the end of it?

Yes, testing branch should be at 0.90.99.5, the same as the links in this thread.   Though, I was just thinking of merging some fixes that goatpig pushed which will be part of .6 or .7

New wallets are top priority after 0.91-beta which is in testing right now.  The following version, 0.92-beta, will include the new wallet format, which includes native BIP32 support along with a ton of other things (including compressed public keys and some multisig capability).