Armory - Discussion Thread

[etotheipi]

Wallet Migration Borked for 0.6.0!

Cypherdoc got around to helping me test the wallet migration... and it doesn't work if your wallet has ever touched the 0.6.0 Satoshi client.  It's because 0.6.0 adds compressed public keys to the wallet, and Armory does not yet support them.  And I set it to fail if it cannot handle 100% of the keys:  I don't want to risk someone thinking they're importing their whole wallet, when in fact they might be leaving money behind (if there happens to be any in those compressed addresses).

Given that I desperately need to complete RAM reduction, this feature is going to have to be restricted to only wallets pre-0.6.0 until I get a chance to implement the compressed public keys.  Gah!  If I had realized this was going to happen, I would've done RAM reduction first instead of putting in a feature that will only be 50% useful until after RAM reduction

But at least I'm making progress on the RAM reduction!

[runeks]

Yay! Just made my first offline transaction. It works perfectly, though Armory popped up with a message on my online computer saying the transaction didn't get broadcast and that I can find information about the transaction in failedtx.bin. But the Satoshi client received the transaction fine and it's been picked up in a block: http://blockexplorer.com/tx/a090caf70a778ee7393e33c1283311b332ec92271fbe719a3a2030d82dbbc1fe#o0

It sounds like you're using version 0.55.  I had accidentally switched the endianness of a variable somewhere that prevented Armory from detecting that the tx was accepted, even though it already hit the network.  Please upgrade to 0.60...and try the wallet migration   (though 0.56 fixes that error, too).  Glad to finally get some more feedback about offline transactions working!  Please let me know if there's anything I can do to improve it!

I just pulled from git and made another transaction, same thing, the message pops up saying it didn't broadcast, even though it did. This time there's no error on the console though:

Code:

Coin Selection:  (Total =         0.50000000 BTC)
    Owner Address                                  TxOutValue      NumConf       PriorityFactor
    1CcBVdAtFzbXSjjWsyeGyjXmip3Jjot3s5             0.50000000 BTC            1                 0.00
50000000
49950000
   Distribution Proposal :  EbeuUAwy
   Transaction Version   :  1
   Transaction Lock Time :  0
   Num Inputs            :  1
      Value: 50000000
      SrcScript:   76a9147f50b3aadc7c7df11e7afb4cbb4cbabbe4d8bac688ac
      Sig0 = ""
   Num Outputs           :  1
   Recipient:         0.49950000 BTC 1runeksijzfVxyrpiyCY2LCBvYsSiFsCm
Signature 0 is valid!
Signature 0 is valid!
Signature 0 is valid!
Pretty tx:  Transaction:
   TxHash:    50f149523e490ab84c17cf9b93aa32bd135e6f771b79d724c0f65322113a6ef6 (BE)
   Version:   1
   nInputs:   1
   nOutputs:  1
   LockTime:  0
   Inputs: 
      PyTxIn:
         PrevTxHash: 198ed799129b33c3276e21caecd212e3c15be59d83ffa9e1582fa5f9172e6380 (BE)
         TxOutIndex: 1
         Script:     (493046022100c286a5e264eb8d4caeeb22a76a9f461f6aae7cb1530e6ee0609d)
         Sender:     1CcBVdAtFzbXSjjWsyeGyjXmip3Jjot3s5
         Seq:        4294967295
   Outputs: 
      TxOut:
         Value:    49950000 ( 0.4995 )
         Script:   OP_DUP OP_HASH (1runeksijzfVxyrpiyCY2LCBvYsSiFsCm) OP_EQUAL OP_CHECKSIG
None
Raw serialize tx:  010000000180632e17f9a52f58e1a9ff839de55bc1e312d2ecca216e27c3339b1299d78e19010000008c493046022100c286a5e264eb8d4caeeb22a76a9f461f6aae7cb1530e6ee0609d151d5e2a46be022100267e5bc96b654d6e4a494f955b12e8e9902e2a25d97af1e717e99dbe19e494a3014104d283456638942d43ad27c5049a3bfa7cee66f2d16f06d53ffc64a40d3f1eff10fd72370f78935b8cf455bdcf07b20d1b38ae3db403b0d0e1e19efd1cb73b6486ffffffff01302dfa02000000001976a914097072524438d003d23a2f23edb65aae1bb3e46988ac00000000
Sending Tx, 50f149523e490ab84c17cf9b93aa32bd135e6f771b79d724c0f65322113a6ef6
Done!

[etotheipi]

I just pulled from git and made another transaction, same thing, the message pops up saying it didn't broadcast, even though it did. This time there's no error on the console though:

That's an error that only happened in version 0.55.  Are you sure you are in the master branch of the git repo?

Open ArmoryQt.py and go to line 1215:  you should see this:

Code:

else:
   newTxHash = pytx.getHash()   # CHECK THIS LINE
   print 'Sending Tx,', binary_to_hex(newTxHash)

Here's the commit that fixed it:  https://github.com/etotheipi/BitcoinArmory/commit/98bdfc29699be671fcfb959590fc733aeba9eb0c
If instead you see binary_switchEndian(pytx.getHash()), then you must be on the wrong branch...

I had originally switched the endianness for display purposes not realizing it was used to verify the transaction was sent, too.  It's looking for the wrong tx.  If you are running the correct code, then I'm kinda concerned...  (what OS, btw?)

[runeks]

Ah, yes, of course. That was it. I was not on master. I think I switched to another branch at some point to check out the EC calculation stuff. All is well .

[etotheipi]

Ah, yes, of course. That was it. I was not on master. I think I switched to another branch at some point to check out the EC calculation stuff. All is well .

I bet that's why message verification failed, too! (from a previous message you posted in the thread)

Now that you have the updated version, try it again:  http://cloud.github.com/downloads/etotheipi/BitcoinArmory/Armory_0.56_sig_block.txt

[etotheipi]

Okay, I got enough feedback and done my own testing to have confidence in releasing

Armory Version 0.60:  with migrate Satoshi-wallet feature

This is the last version increment before RAM-reduction!  In the near future, I have to sort out rewards for crowdfunding donors, and finally implement a once-and-for-all memory overhaul that will let Armory run on just about any system.   This is becoming critical, since it seems the size of the blockchain is accelerating, and soon 4GB of RAM might not even be enough for 0.60-alpha!

As for 0.60, I'll repeat the previous warning:  if your Satoshi wallet was ever touched by the 0.6.0+ Satoshi client, do not use the wallet-import feature.  The only difference between this version and the release copy is that I added a message-box warning before the migrate window opens, giving you a chance to bail before being tempted to try.  I don't know the true consequences of trying to import compressed public keys into an Armory wallet, but I guarantee you won't get what you wanted!

This means that if you have any wallets you want to convert, please convert them now.  Of course, you can always start a new wallet and send the funds to it from the Satoshi client (which I recommend anyway), but the migration feature will need an upgrade after the community moves onto 0.6.0.

[runeks]

Ah, yes, of course. That was it. I was not on master. I think I switched to another branch at some point to check out the EC calculation stuff. All is well .

I bet that's why message verification failed, too! (from a previous message you posted in the thread)

Now that you have the updated version, try it again:  http://cloud.github.com/downloads/etotheipi/BitcoinArmory/Armory_0.56_sig_block.txt

I already tried it previous to upgrading, and it worked then. So I expect it to work now as well.

I'm all out of bugs to report .

[etotheipi]

I'm all out of bugs to report .

What a shame...

[cypherdoc]

I'm all out of bugs to report .

What a shame...

clairvoyance...

[splatster]

If I only I could manage to build it on OS X...

[Red Emerald]

If I only I could manage to build it on OS X...

Yeah. I had no luck either.

brew failed me for the first time

[etotheipi]

I wish I could find the email, but Thunderbird search is failing me...

Someone emailed me a month ago to tell me that the directions on the Building Armory from Source page worked flawlessly on his OSX installation except for one line:

Code:

/usr/local/share/python/easy_install-2.7 twisted

  (just needed to add the abs path to the easy_install)

I updated it in the build instructions, but never followed up with anyone else about it.  I guess that's not the case for everyone (anyone?).  I would track down the email but I remember that's all he said.  And I still don't have any Mac/OSX system on which to try it (and even if I did, I'm not sure I would know how).  I guess I'm going to need to get a Mac system, do it myself, and then compile binaries... but Macs are expensive...

[Red Emerald]

I wish I could find the email, but Thunderbird search is failing me...

Someone emailed me a month ago to tell me that the directions on the Building Armory from Source page worked flawlessly on his OSX installation except for one line:

Code:

/usr/local/share/python/easy_install-2.7 twisted

 (just needed to add the abs path to the easy_install)

I updated it in the build instructions, but never followed up with anyone else about it.  I guess that's not the case for everyone (anyone?).  I would track down the email but I remember that's all he said.  And I still don't have any Mac/OSX system on which to try it (and even if I did, I'm not sure I would know how).  I guess I'm going to need to get a Mac system, do it myself, and then compile binaries... but Macs are expensive...

I think that person was using snow leopard.  I used the linked directions on my Lion system and had no luck.

With lots of fuxing around, I got it to this:

$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.55
   PyBtcAddress Version: 1.00
   PyBtcWallet  Version: 1.35
Detected Operating system: Mac/OSX
   User home-directory   : /Users/bwstitt/Library/Application Support
   Satoshi BTC directory : /Users/bwstitt/Library/Application Support/Bitcoin/
   Satoshi blk0001.dat   : /Users/bwstitt/Library/Application Support/Bitcoin/blk0001.dat
   Armory home dir       : /Users/bwstitt/Library/Application Support/Armory/
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort trap: 6

[etotheipi]

I wish I could find the email, but Thunderbird search is failing me...

Someone emailed me a month ago to tell me that the directions on the Building Armory from Source page worked flawlessly on his OSX installation except for one line:

Code:

/usr/local/share/python/easy_install-2.7 twisted

 (just needed to add the abs path to the easy_install)

I updated it in the build instructions, but never followed up with anyone else about it.  I guess that's not the case for everyone (anyone?).  I would track down the email but I remember that's all he said.  And I still don't have any Mac/OSX system on which to try it (and even if I did, I'm not sure I would know how).  I guess I'm going to need to get a Mac system, do it myself, and then compile binaries... but Macs are expensive...

I think that person was using snow leopard.  I used the linked directions on my Lion system and had no luck.

With lots of fuxing around, I got it to this:

$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.55
   PyBtcAddress Version: 1.00
   PyBtcWallet  Version: 1.35
Detected Operating system: Mac/OSX
   User home-directory   : /Users/bwstitt/Library/Application Support
   Satoshi BTC directory : /Users/bwstitt/Library/Application Support/Bitcoin/
   Satoshi blk0001.dat   : /Users/bwstitt/Library/Application Support/Bitcoin/blk0001.dat
   Armory home dir       : /Users/bwstitt/Library/Application Support/Armory/
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort trap: 6

Perhaps it's worth starting a separate Armory+OSX thread in the Alt Clients subforum.  Mainly because I have absolutely no experience with OSX at all.  I've never even touched an OSX machine.  And at the moment, I couldn't dig into it even if I wanted to (no access to such a machine).

On the other hand, if others dig in and have a place to discuss it, I will happily offer as much assistance as I can, and then I'll have some place to go when I finally do get my hands on such a machine, and maybe it'll soften the blow for me to get into it...

On that note, if I were to start searching craigslist or ebay for a Mac, what should I get?  Presumably, something "relevant" but not anywhere near top-of-the-line, either.  I would probably start on it, myself, when I am finished with RAM-reduction, so I especially don't need anything too powerful.

[Red Emerald]

I wish I could find the email, but Thunderbird search is failing me...

Someone emailed me a month ago to tell me that the directions on the Building Armory from Source page worked flawlessly on his OSX installation except for one line:

Code:

/usr/local/share/python/easy_install-2.7 twisted

 (just needed to add the abs path to the easy_install)

I updated it in the build instructions, but never followed up with anyone else about it.  I guess that's not the case for everyone (anyone?).  I would track down the email but I remember that's all he said.  And I still don't have any Mac/OSX system on which to try it (and even if I did, I'm not sure I would know how).  I guess I'm going to need to get a Mac system, do it myself, and then compile binaries... but Macs are expensive...

I think that person was using snow leopard.  I used the linked directions on my Lion system and had no luck.

With lots of fuxing around, I got it to this:

$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.55
   PyBtcAddress Version: 1.00
   PyBtcWallet  Version: 1.35
Detected Operating system: Mac/OSX
   User home-directory   : /Users/bwstitt/Library/Application Support
   Satoshi BTC directory : /Users/bwstitt/Library/Application Support/Bitcoin/
   Satoshi blk0001.dat   : /Users/bwstitt/Library/Application Support/Bitcoin/blk0001.dat
   Armory home dir       : /Users/bwstitt/Library/Application Support/Armory/
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort trap: 6

Perhaps it's worth starting a separate Armory+OSX thread in the Alt Clients subforum.  Mainly because I have absolutely no experience with OSX at all.  I've never even touched an OSX machine.  And at the moment, I couldn't dig into it even if I wanted to (no access to such a machine).

On the other hand, if others dig in and have a place to discuss it, I will happily offer as much assistance as I can, and then I'll have some place to go when I finally do get my hands on such a machine, and maybe it'll soften the blow for me to get into it...

On that note, if I were to start searching craigslist or ebay for a Mac, what should I get?  Presumably, something "relevant" but not anywhere near top-of-the-line, either.  I would probably start on it, myself, when I am finished with RAM-reduction, so I especially don't need anything too powerful.

Well this is kinda OT, but if you buy a mac, I HIGHLY recommend you buy it from apple.  Apple has the best customer service for computers by far and if you buy from craigslist or some 3rd party, you don't get that.

Mac minis start at $599.  All you'll need after that is a monitor that supports HDMI or DVI.

[etotheipi]

Well this is kinda OT, but if you buy a mac, I HIGHLY recommend you buy it from apple.  Apple has the best customer service for computers by far and if you buy from craigslist or some 3rd party, you don't get that.

Mac minis start at $599.  All you'll need after that is a monitor that supports HDMI or DVI.

That's pretty heavy for a computer I'm not ever going to really use.  I basically anticipate only compiling binaries on it... and if I have to do multiple versions (like 32-bit and 64-bit), I might need a second one.  I really want the cheapest I can get, I'm not too concerned about warranty service.  Even if one dies and i have to get another, it was still cheaper to get each for $200 each than pay $600 for one.

[RoloTonyBrownTown]

Well this is kinda OT, but if you buy a mac, I HIGHLY recommend you buy it from apple.  Apple has the best customer service for computers by far and if you buy from craigslist or some 3rd party, you don't get that.

Mac minis start at $599.  All you'll need after that is a monitor that supports HDMI or DVI.

That's pretty heavy for a computer I'm not ever going to really use.  I basically anticipate only compiling binaries on it... and if I have to do multiple versions (like 32-bit and 64-bit), I might need a second one.  I really want the cheapest I can get, I'm not too concerned about warranty service.  Even if one dies and i have to get another, it was still cheaper to get each for $200 each than pay $600 for one.

Rather than buy a Mac just for compiling sake, could you not just set up a couple of virtual machines running OSX (or whatever it's called nowadays) on your Windows box?    I know it's possible as I did it myself a while ago, although I'm not sure if that messes anything up with regards to compiling to be honest.

[etotheipi]

Well this is kinda OT, but if you buy a mac, I HIGHLY recommend you buy it from apple.  Apple has the best customer service for computers by far and if you buy from craigslist or some 3rd party, you don't get that.

Mac minis start at $599.  All you'll need after that is a monitor that supports HDMI or DVI.

That's pretty heavy for a computer I'm not ever going to really use.  I basically anticipate only compiling binaries on it... and if I have to do multiple versions (like 32-bit and 64-bit), I might need a second one.  I really want the cheapest I can get, I'm not too concerned about warranty service.  Even if one dies and i have to get another, it was still cheaper to get each for $200 each than pay $600 for one.

Rather than buy a Mac just for compiling sake, could you not just set up a couple of virtual machines running OSX (or whatever it's called nowadays) on your Windows box?    I know it's possible as I did it myself a while ago, although I'm not sure if that messes anything up with regards to compiling to be honest.

I've tried to set up an OSX VM no less than 3 times, but it's never worked.  I just don't have the touch (they're very finnicky, because of strict hardware specs).  Though if it does work, there's no reason the compiled binaries wouldn't work.  That's how I compile the Windows binaries...

Maybe I should just convince my girlfriend her laptop is crappy and she would looove a new mac mini!  "It's so cute!  And you totally make enough money to afford it...."

If anyone can help me out with this, please email me.  Either used hardware you could send me, help setting up a VM, or other ideas...
(etotheipi a t g mail com)

[RoloTonyBrownTown]

I've tried to set up an OSX VM no less than 3 times, but it's never worked.  I just don't have the touch (they're very finnicky, because of strict hardware specs).  Though if it does work, there's no reason the compiled binaries wouldn't work.  That's how I compile the Windows binaries...

Maybe I should just convince my girlfriend her laptop is crappy and she would looove a new mac mini!  "It's so cute!  And you totally make enough money to afford it...."

If anyone can help me out with this, please email me.  Either used hardware you could send me, help setting up a VM, or other ideas...
(etotheipi a t g mail com)

I'm pretty sure I used this (http://www.redmondpie.com/how-to-install-os-x-snow-leopard-in-vmware-windows-7-9140301/) when I did it.  That's obviously an older version of OSX, but if that doesn't matter then give it a crack

[malevolent]

Try either OS X on a VM or Hackintosh, Macs are waaay overpriced but it is because so many people are willing to buy it (convincing marketing?) Cpt. Obvious i know