Topic: Armory - Discussion Thread - page 71. (Read 521829 times)

Here's a first shot at cross-compiling for RPi.  I didn't get all the packages bundled yet, but maybe if you've already had it working before (and thus already have the dependencies), you could try this out for me.

I have a few other things to do before I head out tomorrow, so I don't have time to setup my RPi.  Otherwise I'll do it when I get back:

https://s3.amazonaws.com/bitcoinarmory-releases/raspberrypi_armory_0.90.99-testing.tar.gz

EDIT: Here's the package list:


EDIT²: I just realized that the above tar.gz is the make-install'd version.  I just tried to merge it into the way it would be right after you compiled it (no make install):

https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.90.99-testing_rpibuild.tar.gz

(obviously, I need to improve this proces...)

You're doing a great job, guys. All the usability improvements I was expecting are included, plus a few extra.

Nice indeed!
Great to see the armory team grow!

Ente

Awesome! Nice work Armory team!

I like that you've allowed the user to block spending zero confirmation change (and protect themselves from the transaction mutating bot)! Thanks for that!

It's that time again... Testing time!

Brought to you by the Armory team, this time.  Yes, we have a team!  A few guys came on recently and are still getting up to speed, but they're contributing, nonetheless.  And even though they're not at full efficiency yet, I think we're finally moving faster than when it was just me by myself  

Version 0.91-beta (currently 0.90.99.0-testing, the testing branch) will not contain any groundbreaking features.  However, it has dramatic stability improvements for all OS, and a whole ton of small-but-important things that improve the user experience.

Here's the list, in arbitrary order (well, kind of reverse-chronological order):

• Use --nospendzeroconfchange to not allow spending of any unconfirmed TxOuts (Armory already deprioritizes ZC change, but it's off-limits with this flag)
• Full P2SH support in send-BTC dialog, address book, tx info, etc
• WinXP support
• Proper unicode path handling (wallets will support unicode in 0.92-beta)
• No more choking on bad blocks written by Bitcoin-Qt/bitcoind
• Major improvements to OSX compatibility!  (hopefully)
• Fixed fonts in OSX
• Bug reporting window
• Progress bars for long-running operations
• Better version notification system (will be implemented before release)
• Factory reset window -- including "Delete Bitcoin-Qt databases and re-download"
• Raspberry Pi offline bundle (process ironed out, will create test bundles soon!)
• Minimize-on-open (in settings)
• Wallets->"Recover Damaged Wallet"
• Wallet creation wizard
• Faster rescanning and rebuilding
• Better logic to prevent unnecessary rescans
• Better zero-conf tx handling
• Fee calculation fixes
• armoryd.py fixes and upgrades
• Multithreading improvements
• Code refactoring

A few points to emphasize:

• Slowness and UI freezes should be mostly gone.  It turns out that large wallets were choking on the number of zero-confirmation transactions on the network, combined with an inefficiency in Armory's handling of them.  It should be dramatically improved.
• We now handle broken blk*.dat files more intelligently (produced by Bitcoin-Qt/bitcoind):  It will pop up a warning if you are affected (instead of seg faulting). We believe that most of the problems people have experienced while syncing and scanning are due to this condition.  .  You can now do a "Factory Reset" which will delete the blk*.dat files and force Bitcoin-Qt to redownload it.
• Arbitrary rescans should be mostly gone.  Unclean shutdowns or not.  It will only rebuild or rescan if it detects problems with the database, or new addresses show up that have not been scanned
• Wallet consistency checks are now performed in the background on every load.  You will see the progress bar at the bottom-left.  If a problem is detected with your wallets, some information should pop up and you can use "Wallets"->"Recover Damaged Wallet" to try to fix it.
• armoryd.py has been upgraded (but still needs a bit more testing).  We have a Python Scripting page to help people get into it, and devchanges.txt describes how developers can update their code to work with the changes between 0.90 and 0.91.
• OSX updates:  No promises that this totally works yet, but we do finally have a [paid!] developer working exclusively in OSX, which means that it will no longer be neglected!  He already found some issues with the prior build process, and thinks the next release will be dramatically improved.  At the very least, the font issues on paper backups should be fixed

I am going to try to do a little more testing, probably followed by some tweaks.  Then I'm going to attempt to do some testing builds for Windows, OSX, and Raspberry Pi!  The RPi builds can easily be integrated into the release process, because goatpig helped figure out how to cross-compile it on my non-ARM build systems.  Sweet!

---

I will start a new thread for this round of testing, as soon as I flesh out the last few details and get some of the non-Linux testing builds together.  Unfortunatley, I'm leaving for a trip tomorrow -- I hope to get some of it out there before I leave, otherwise it will have to wait until late next week.  If you are adventurous, you can help speed up the process by checking out the "testing" branch and banging on it a bit.

Gotcha.  Thanks for the answer.

This kind of feature is a lot more complicated than it sounds. Possibly as an add-on on top of plug-in modularization, but nothing in the near future if that's what you're looking for.

Request:  Would it be possible to set up a recurring transaction in Armory?  I am not sure this functionality has been implemented yet in any wallet.  (I think coinbase has it though, but its a web wallet).  This would be fairly useful to me and perhaps many others. 

Makes sense.

So I did all of the above and it has not locked up, but it is behaving oddly.  I have a tough time opening the transactions pane and it will only show one wallet at a time.
I also got an error message saying that:

Bitcoin-QT is not synched to the network.  Don't start Armory until it's synced.

So I shut Armory and pulled up the Qt.  It was already synced so I'm not sure what Armory's issue is.

I often had lockups with the 0.88 in the initialization phase, but only if I had brought another application to the foreground. Must have something to do with the process prioritiy level when spawning bitcoin-qt, I assume. When I keep it on top and wait during syncing and scanning, it never happened.

Having Armory issues for the first time.  Started it up today and came back to the computer and it had locked up.
Would not restart until I restarted my computer.  I am using .88.
Tried it three times and each time the upper progress bar (can't remember what it's called) would complete to 100% and the bottom (transactions?) bar would lock up at 1%.
So I thought I would go the website.  Noticed that .90 was out so I downloaded that.  But it does the same thing.
I am now going to uninstall all the armory software, restart and re-install just .90 and see if that works.
I checked bitcoin-qt and that one is fine.

Thanks both replies.

Yes, I am scanning just the appdata/armory folder with avast too.
What's exactly inside those sst files ? Is it text ?

I'm running avast as well and I do not have that issue.  I even manually scanned appdata/armory to check.

ProbablY just random text in the Blockchain triggering

Uninstalled Armory, deleted the Armory files, including databases. Reinstalled, synchronized OK. I Ran the antivirus program (Avast) again and AGAIN I got a TROJAN warning as the above, mwith a different SST file this time. The Antivirus program deleted that one too but then Armory crashed with an error warning when trying to Sync again.

Can anyone give me some feedback as to if there are any precedents to this sort of thing ? Should I worry ? Is there anyplace else where this sort of issue has been addressed ?

THANKS

After re-export, still crashing. 

Hi, I saw gmaxwell mentioning that the bitcoin-qt's algorithm for finding unspent outputs have a time complexity of O(N^2!), wonder what's the situation with Armory? Just curious, thanks.

It wasn't me who sent you the WO wallet.  I will try with a freshly exported WO wallet from the backup and update you.  I will keep a backup of the WO wallet that's crashing.

It's not an old wallet.  The first tx I have in there is early Dec. 2013 so I imagine I made it with whatever Armory version was current then.

As an aside, using 0.88.1 is working well right now.

bitcoin.conf?

Do you mean this WO is ages old? I thought you had it exported from your recently restored wallets. If it is very old, now I really want to take a look at it.

Someome just recently sent us a WO that crashes Armory. I don't know if its yours but I'll be getting on it soon. I'm not gonna insist to see your WO until I'm done with the current one, however it may be very interesting. If anything don't delete it.

As for your test, you should try with a freshly derivated WO.