Ah, I was just in advanced, not expert mode -- I restarted in expert mode and the copy hex button is visible.
Thanks!
Topic: Armory - Discussion Thread - page 111. (Read 521829 times)
Can you make it so that you can broadcast signed transactions immediately when loading armory, instead of waiting for it to scan the transaction history?
Or is it possible to broadcast it from bitcoin-qt? I tried sendrawtransaction and pasting in my signed transaction, but it complains about it not being a serialized hex string.
Or is it possible to broadcast it from bitcoin-qt? I tried sendrawtransaction and pasting in my signed transaction, but it complains about it not being a serialized hex string.
I should find a way to make that easier for sure. But hopefully it won't matter so much after the need upgrade. For now :
-switch to expert user mode
-click on offline transactions
-broadcast signed transaction
-load the transaction from file or clipboard
-click "Copy Raw TX (hex)"
Now the clipboard should contain the properly-formatted tx to be copied into bitcoin-qt or blockchain.info pushtx (I forget the exact URL, and I'm on my phone right now making it hard to look up)
Can you make it so that you can broadcast signed transactions immediately when loading armory, instead of waiting for it to scan the transaction history?
Or is it possible to broadcast it from bitcoin-qt? I tried sendrawtransaction and pasting in my signed transaction, but it complains about it not being a serialized hex string.
Or is it possible to broadcast it from bitcoin-qt? I tried sendrawtransaction and pasting in my signed transaction, but it complains about it not being a serialized hex string.
Here's the script I wrote to extract the private keys from your Armory wallet, so you can import it into a different wallet. Keep in mind that you lose the deterministic function and you should immediately sweep these keys to a new, secure address. If you go back to using Armory, start a new wallet.
I'm not sure how to run this on Windows (maybe someone more familiar with Python on Windows could help), but here's how you'd use it on Linux...
It will write a file with all of the private keys that have been generated and stored in the wallet structure.
I'm not sure how to run this on Windows (maybe someone more familiar with Python on Windows could help), but here's how you'd use it on Linux...
Code:
cd /path/to/extras
python extractArmoryKeys.py /path/to/wallet
python extractArmoryKeys.py /path/to/wallet
It will write a file with all of the private keys that have been generated and stored in the wallet structure.
I just had a random scary thought.
Is there anyway that editing the makefile like I've done in order to get it to compile could possibly jeopardize the coins in my wallets? Like, for example, being able to send bitcoins to my armory wallets but not being being able to spend them, because the wallets are invalid because of some tweaking made to the makefile?
Is there anyway that editing the makefile like I've done in order to get it to compile could possibly jeopardize the coins in my wallets? Like, for example, being able to send bitcoins to my armory wallets but not being being able to spend them, because the wallets are invalid because of some tweaking made to the makefile?
Only if you tweaked the makefile to point to a library that identical code/functions/interfaces, but produced different (incorrect) answers. This is basically impossible without something malicious going on, or if the version of your library has a bug so extraordinary that it produces incorrect public keys for a given private key -- which would be caught immediately with any respectable crypto library before an official release.
Okay. Thanks for the explanation!
I just had a random scary thought.
Is there anyway that editing the makefile like I've done in order to get it to compile could possibly jeopardize the coins in my wallets? Like, for example, being able to send bitcoins to my armory wallets but not being being able to spend them, because the wallets are invalid because of some tweaking made to the makefile?
Is there anyway that editing the makefile like I've done in order to get it to compile could possibly jeopardize the coins in my wallets? Like, for example, being able to send bitcoins to my armory wallets but not being being able to spend them, because the wallets are invalid because of some tweaking made to the makefile?
Only if you tweaked the makefile to point to a library that identical code/functions/interfaces, but produced different (incorrect) answers. This is basically impossible without something malicious going on, or if the version of your library has a bug so extraordinary that it produces incorrect public keys for a given private key -- which would be caught immediately with any respectable crypto library before an official release.
SUCCESS!!!! 
Okay, normally, this is the time I move on with my life, but I really think it would be a good idea to share all of the steps I had to take, so that etothepi can put these instructions on the BitcoinArmory website for the NEXT person who runs Fedora and wants to install Bitcoin Armory. There are a lot of Fedora users out there and it would be a shame for them to turn away from using Bitcoin Armory because they couldn't figure out how to get it installed, or perhaps they saw there weren't installation instructions and didn't even try. So, here's everything I did in order to get Bitcoin Armory installed. I hope you'll put this up.
In addition to all of the packages you list to install, also include:
gcc-c++
python-devel
PyQt4-devel
Then have them edit cppForSwig/Makefile and
replace line 26 with:
26 STATICPYTHON += "/usr/lib64/libpython2.7.so.1.0"
and line 29 with:
29 STATICPYTHON += "$(DEPSDIR)/lib64/libpython2.7.so.1.0"
making sure to put either 64 or 32 depending on the architecture.
Then it should work great! And you've just increased the number of users that can and will use Bitcoin Armory.
Thanks for all the help guys!
Okay, normally, this is the time I move on with my life, but I really think it would be a good idea to share all of the steps I had to take, so that etothepi can put these instructions on the BitcoinArmory website for the NEXT person who runs Fedora and wants to install Bitcoin Armory. There are a lot of Fedora users out there and it would be a shame for them to turn away from using Bitcoin Armory because they couldn't figure out how to get it installed, or perhaps they saw there weren't installation instructions and didn't even try. So, here's everything I did in order to get Bitcoin Armory installed. I hope you'll put this up.
In addition to all of the packages you list to install, also include:
gcc-c++
python-devel
PyQt4-devel
Then have them edit cppForSwig/Makefile and
replace line 26 with:
26 STATICPYTHON += "/usr/lib64/libpython2.7.so.1.0"
and line 29 with:
29 STATICPYTHON += "$(DEPSDIR)/lib64/libpython2.7.so.1.0"
making sure to put either 64 or 32 depending on the architecture.
Then it should work great! And you've just increased the number of users that can and will use Bitcoin Armory.
Thanks for all the help guys!
I just had a random scary thought.
Is there anyway that editing the makefile like I've done in order to get it to compile could possibly jeopardize the coins in my wallets? Like, for example, being able to send bitcoins to my armory wallets but not being being able to spend them, because the wallets are invalid because of some tweaking made to the makefile?
SUCCESS!!!!
Okay, normally, this is the time I move on with my life, but I really think it would be a good idea to share all of the steps I had to take, so that etothepi can put these instructions on the BitcoinArmory website for the NEXT person who runs Fedora and wants to install Bitcoin Armory. There are a lot of Fedora users out there and it would be a shame for them to turn away from using Bitcoin Armory because they couldn't figure out how to get it installed, or perhaps they saw there weren't installation instructions and didn't even try. So, here's everything I did in order to get Bitcoin Armory installed. I hope you'll put this up.
In addition to all of the packages you list to install, also include:
gcc-c++
python-devel
PyQt4-devel
Then have them edit cppForSwig/Makefile and
replace line 26 with:
26 STATICPYTHON += "/usr/lib64/libpython2.7.so.1.0"
and line 29 with:
29 STATICPYTHON += "$(DEPSDIR)/lib64/libpython2.7.so.1.0"
making sure to put either 64 or 32 depending on the architecture.
Then it should work great! And you've just increased the number of users that can and will use Bitcoin Armory.
Thanks for all the help guys!
Okay, normally, this is the time I move on with my life, but I really think it would be a good idea to share all of the steps I had to take, so that etothepi can put these instructions on the BitcoinArmory website for the NEXT person who runs Fedora and wants to install Bitcoin Armory. There are a lot of Fedora users out there and it would be a shame for them to turn away from using Bitcoin Armory because they couldn't figure out how to get it installed, or perhaps they saw there weren't installation instructions and didn't even try. So, here's everything I did in order to get Bitcoin Armory installed. I hope you'll put this up.
In addition to all of the packages you list to install, also include:
gcc-c++
python-devel
PyQt4-devel
Then have them edit cppForSwig/Makefile and
replace line 26 with:
26 STATICPYTHON += "/usr/lib64/libpython2.7.so.1.0"
and line 29 with:
29 STATICPYTHON += "$(DEPSDIR)/lib64/libpython2.7.so.1.0"
making sure to put either 64 or 32 depending on the architecture.
Then it should work great! And you've just increased the number of users that can and will use Bitcoin Armory.
Thanks for all the help guys!
I just had a random scary thought.
Is there anyway that editing the makefile like I've done in order to get it to compile could possibly jeopardize the coins in my wallets? Like, for example, being able to send bitcoins to my armory wallets but not being being able to spend them, because the wallets are invalid because of some tweaking made to the makefile?
FYI, it turns out that my code.google.com project was banned because I was offering downloads of installers without associated source code. They thought that I was using their service to assist with distribution of closed-source software.
I offered to move the repo to google servers, but they said it was actually fine, as long as it's actually open source and the code is available somewhere. So they re-enabled the downloads and I added a comment to the project description with the link to the github repo. All is well, now.
I offered to move the repo to google servers, but they said it was actually fine, as long as it's actually open source and the code is available somewhere. So they re-enabled the downloads and I added a comment to the project description with the link to the github repo. All is well, now.
Glad to hear that you got it resolved.
FYI, it turns out that my code.google.com project was banned because I was offering downloads of installers without associated source code. They thought that I was using their service to assist with distribution of closed-source software.
I offered to move the repo to google servers, but they said it was actually fine, as long as it's actually open source and the code is available somewhere. So they re-enabled the downloads and I added a comment to the project description with the link to the github repo. All is well, now.
I offered to move the repo to google servers, but they said it was actually fine, as long as it's actually open source and the code is available somewhere. So they re-enabled the downloads and I added a comment to the project description with the link to the github repo. All is well, now.
Ram is insane expensive right now. I got the 32 for $100 last black Friday.
You must mean inexpensive, right? 32 GB for $100 is crazy cheap. This is what happens when it's scanning the blockchain, never completes. This is using the 32-bit version, 64 bit version would crash before even showing the splash screen.
Is there any way to use another client until these bugs get fixed? I really need to use my coins, but can't as they are all stored in the Armory... and the Armory is locking me out :-/
Is there any way to use another client until these bugs get fixed? I really need to use my coins, but can't as they are all stored in the Armory... and the Armory is locking me out :-/
Armory stores the private keys in a pretty simple format. You could extract them and import them into another client. Give me a minute and I'll write a quick script to do that...
I tried to sign a message but it comes back with the following:
"Runtime Error!
Program: C:\...
This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information."
"Runtime Error!
Program: C:\...
This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information."
This is what happens when it's scanning the blockchain, never completes. This is using the 32-bit version, 64 bit version would crash before even showing the splash screen.
Is there any way to use another client until these bugs get fixed? I really need to use my coins, but can't as they are all stored in the Armory... and the Armory is locking me out :-/
I tried to sign a message but it comes back with the following:
"Runtime Error!
Program: C:\...
This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information."
"Runtime Error!
Program: C:\...
This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information."
Have you got any reply from Google code? Did they just lose everything?
I have 5 GB of RAM and for me the only real slow part is the startup - that takes several minutes. After that, it works pretty well.
Scratch that. This used to be the case, but it doesn't really work any more.
etotheipi, if you're still looking for the installer - Google Code is back up now, so you should be able to download it off there.
Are you logged in as a google user? It still get "access denied" for all googlecode pages when logged in. And when logged out, I still can't find it or access it directly.
Oh, you're right. I went to code.google.com, which is working fine, but the one remaining googlecode page linked to from bitcoinarmory.com is returning a 403 error. Apparently I didn't look far enough.
Armory is awesome on my new 16GB RAM PC with Linux OS!
The whole blockchain downloaded in 12 hours and Armory's scan took about 2 minutes.
The whole blockchain downloaded in 12 hours and Armory's scan took about 2 minutes.
Real men have 32 GB of RAM
I am feeling very inadequate around all you with my 4gb mac
Armory is awesome on my new 16GB RAM PC with Linux OS!
The whole blockchain downloaded in 12 hours and Armory's scan took about 2 minutes.
The whole blockchain downloaded in 12 hours and Armory's scan took about 2 minutes.
Real men have 32 GB of RAM
Armory is awesome on my new 16GB RAM PC with Linux OS!
The whole blockchain downloaded in 12 hours and Armory's scan took about 2 minutes.
The whole blockchain downloaded in 12 hours and Armory's scan took about 2 minutes.
I have 5 GB of RAM and for me the only real slow part is the startup - that takes several minutes. After that, it works pretty well.
Scratch that. This used to be the case, but it doesn't really work any more.
etotheipi, if you're still looking for the installer - Google Code is back up now, so you should be able to download it off there.
Are you logged in as a google user? It still get "access denied" for all googlecode pages when logged in. And when logged out, I still can't find it or access it directly.
Jump to: