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

Yes, there is no 0.8 support yet.  The Bitcoin-Qt devs left out some important details about the way 0.8+ works, because they didn't think it mattered.  It does matter, and I haven't had the time to revamp the low-level blockchain utilities to accommodate it.  Figuring that out is near the top of my list, though.

On the upside, I think I figured out what has been causing Armory to crash after being open for a long time.  And the code needed to fix that, is closely related to the updates I need to work with 0.8.  I might be able to do both at the same time.

Ever since I upgraded bitcoin-qt to a pre-0.8 test version. Armory will not leave offline mode.

Unfortunately, the log shows nothing is wrong.  Can you do it again with the "--debug" flag?  It sounds like the watching-only wallet is corrupted.  Can you try re-forking it from the offline computer?  What offline version was it created from?  I know it won't have all the comments, but I can make you a very quick script to move all your comments/labels over, if it works.

---

Bug Bounty Test Drive!

Recommendations welcome.  Bug reports welcome.  Let's find out if this works...

If you find bugs, please report them in that thread.  If you don't, I'll post a link to this thread from there... I want to make sure there's a clear timeline of bug reports so that duplicate reports are avoided (and multiple payouts for the same bug).

That sounds like a lot of fun, will let you know when I'm done.

I can confirm this bug is fixed.

Please Sanity Check v0.86.3-beta!

I just posted a v0.86.3-beta to the new AmazonS3 "bucket."  The Get Armory! page now references the new download location, and I need to make sure everyone has access, and that there's no other stupid bugs that will require further fixes before I trigger version notifications.

I haven't merged it into master yet, because I don't want to trigger any notifications until I get this sanity check.  But I did create a signed tag and pushed it to github:  "v0.86.3-beta".  You can check that out right now and play with it.  ("git tag -v v0.86.3-beta" to verify the signature)

---

I want to start bug-bounties.  Something like 0.1 BTC per new bug you discover.  If you report a significant bug, and there's no one else has mentioned it since the last release, I'll send you 0.1 BTC.  Of course, this won't be so clean, because what is a "significant" bug?  What qualifies as a bug vs. a missing feature?  I don't want to be stingy about it, but I also don't want people to start expecting payment for pointing out missing punctuation in a warning box.... or maybe I should be paying for such tiny things...?

Please feel free to discuss how I might do execute this idea with the best efficiency.  I'm thinking I'll start by doing it for 2 weeks only, and with a maximum of 3 BTC paid out (30 bugs) in that two weeks.  That will limit my risk of unexpected abuses.  Also, I probably won't send out the 0.1 right away, unless someone requests it.  If the bug reports are coming in quickly, I will aggregate multiple payouts into one transaction.  I am considering posting it in the main discussion forum, but I might get too much attention.

That is not a subtle bug at all!  I just tested creating a new wallet and it really fails!  I probably didn't notice it because it doesn't trigger if you create the wallet after the blockchain is loaded.  It only triggers if the wallet has never been used at the time the initial blockchain scan finishes.


Well, thanks!  And I'm always happy to have people help out.  Dig into the code, maybe even develop new features.  If you want to get involved, please email me and I'll give you little homework assignments that will get you acquainted with the code and might be useful, too! 

---

I just fixed the bug in my local copy of the github repo, but github is down for maintenance, so I can't sync any of my other virtual machines in order to compile the new version.  Gah!  As soon as it's back up, I'll be releasing it officially as 0.86.3-beta.

As someone who used to have this same problem I totally get it. It helped me to purposely slow down my programming.

I always make a new wallet to check new functionality with, so you have this approach covered

Not a problem, that's why we are here.

I'm currently very busy (writing my master thesis), but have been looking for a way to contribute to the bitcoin comunity (with a degree in computer science and mathematics I think I might have something to give), and after that I'd be happy to help you with anything you might need (I guess code reviews never hurt). I don't think I've ever been as impressed with any piece of software as I am with armory.

Crap!  As usual, what seemed like an arbitrarily small update to fix something small, resulted in breaking something subtle.  I can see how it is possible to have negative values for a number that is encoded as a positive number and would throw that error.  Fixed a bug, made another one.

I really need to start bug bounties or something.  This bug is really only triggered on new wallets, which would be a disaster for new users, but very few users on this thread are creating new wallets.  I think I'll start a 0.1 BTC/bug bounty, for a month.  If someone has ideas for how to run this in a sane way that won't result in lots of disputes, I'm all for it.  I think it could also be a good marketing ploy -- some users would probably start using Armory just to try to get bounties! 

Looks like I have to fix that bug, and recompile and re-sign everything.  Ugh!   But thanks, prezbo, you actually saved me a lot of heartache from new users having bad experiences!

I ran the new version, it said that armory is online but none of the transactions appeared.

Might be because I created a new wallet while it was synching, and got a bunch of these errors:

all these errors are only linked to the newly created wallet.

edit: tried it again, this time didn't do anything at all, the result is still the same, no transactions show up.
edit 2: permanently deleted the wallet in question and all transactions suddenly showed up.

great work.

Well, what a pain in the @$$.  Github has decided they no longer support uploading files.  I was paying an exorbitant amount to them for a premium acct just to have that feature.  Oh well.  Onto Amazon S3...

I'm fairly comfortable with the 0.86.2 as-is, so I basically just moved the existing installers over to my offline system for signing, and then brought them back for an official release.  I just uploaded them to my new Amazon S3 account.  Let's find out if it works:

https://s3.amazonaws.com/BitcoinArmoryReleases/0.86.2-beta/armory_0.86.2-beta_win64.msi
https://s3.amazonaws.com/BitcoinArmoryReleases/0.86.2-beta/armory_0.86.2-beta_windows_all.msi
https://s3.amazonaws.com/BitcoinArmoryReleases/0.86.2-beta/armory_0.86.2_amd64.deb
https://s3.amazonaws.com/BitcoinArmoryReleases/0.86.2-beta/armory_0.86.2_i386.deb

And, I saw no reason not to switch to using SHA256 for hashing the installers into a signed release file, so that's what I did.  If you were previously downloading the .asc file and checking the hashes with "md5sum *.deb *.msi", just change that to "sha256sum *.deb *.msi". 

Once I hear back from people that the downloads work, I will update the website and the merge it into master (and tag and sign the repo).

That's what I figured, but I thought it was worth checking. I'll just re-purpose another machine until you finish the upgrade.

Thanks again.

there is a workaround (still a bit slow armory but a working one).
install linux with a big swap (atleast 4GB, best 8GB)
set swapiness (google) to 100
run armory and enjoy

If you have 2GB or less, I'm guessing Armory won't work very well (perhaps like what you said).  Before SatoshiDice came along, it was fine, but even just indexing pointers to data on disk is over 1 GB now.  I started upgrading Armory to switch to disk-based indexing (which really needed to be done eventually, but I didn't realize it was going to be so soon!), but it's turning out to be a pretty substantial upgrade for Armory.  It will happen in the next month or two, though ...

The bitcoin-qt disconnect-reconnect cycle is a side effect of your system thrashing.  It can happen when bitcoin-qt isn't fully sync'ed with the network yet and Armory is struggling to keep up with the blocks, or when you don't have enough RAM to build the blockchain index. 

I wish I had better news for you...

I've been trying to use Armory on netbook (EeePC 1005HAB), and I've run into a couple problems:
 1. When I start Armory in online-mode, it hangs at scanning the blockchain. The program says "Connected (0 blocks)" and endlessly scans. I've let it run overnight to no avail.
 2. Armory randomly drops the connection to bitcoin-qt and reconnects a second later. This tends to happen a number of times consecutively.

You mentioned that Armory is fairly RAM intensive - could this be the cause? It's running Windows 7 32-bit and Armory 0.86.2-beta.

Thanks,
--winter

Indeed!  It's on the webpage:  http://bitcoinarmory.com/index.php/armory-wallet-files

However, I'm working on a new wallet format now, so that will be changing pretty substantially in the near future, but there's also a lot of work left to be done (so maybe not near-near future...)

Is there anywhere I can read about the wallet specification without delving into armory source?

There doesn't seem to be anything interesting in Armory's log (even with --debug), but when I first start it up I get these notifications in Bitcoin's debug.log...

Whoops!
Thank you, you two! Running on dev now! :-)

Ente