 Show Posts
|
|
Pages: [1] 2 »
|
|
Do you have a contingency plan should Bitcoin Classic gain majority? I've not seen Armory weigh in one way or the other in the block size debate.
|
|
|
|
|
I'm running Linux but not Ubuntu. I've been converting .deb packages to .txz for Slackware but I'd prefer to compile from source and I don't see source downloads listed anywhere on the website.
|
|
|
|
I got it working finally. Thanks for your help bitpop. FYI 0.92 is the necessary version required. Since Armory version 0.92 the formats for offline transaction operations has changed to accommodate multi-signature transactions. This format is not compatible with versions of Armory before 0.92. If anybody else running Ubuntu 12.04 is in the same boat, here's where I found all of my dependencies. https://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.1-0ubuntu4.8/+build/5933354 |
|
|
|
I recently updated my online machine to 0.92.3 and was wondering if there is any need, or there will ever be a need to update the software on my offline computer. I believe I'm running 0.90 on that one.
In the same vein, is there any reason for me to worry that my hard copies wouldn't work in the future? Say I put them in a safe deposit box and then died. Would my kids be able to use the same codes to recover my bitcoins in Armory 16.8.0 in 15 years?
It should always be backwards compatible but you should keep the old installers saved. But it's open source, anyone can make a tool to parse. Now your offline must be updated I think after .90.1 Thanks for the quick response. So my paper backups should be good forever but keep old versions of the software just in case. Cool. I just checked and I'm running 0.90-beta on my offline computer. You're saying I should be at version 0.90.1 or higher for compatibility? Is this something that will need to be continually updated or it's due to a one time change? Well the offline transfer protocol changed that's why it's needed. It was changed to add support for mutli sig. It shouldn't happen too often. You'll get a notification when you try to do an offline transaction. Try it without actually broadcasting. OK thanks. I'm now stuck in dependency hell as my offline computer doesn't have the necessary versions of the libraries necessary and isn't connected to the internet. I seem to remember going through this last time. Crap yeah you need to update to do transactions. But no rush unless you need to send. Yeah no need to send anything from here. I'll just go through the motions and not have to worry about it again for awhile. |
|
|
|
I recently updated my online machine to 0.92.3 and was wondering if there is any need, or there will ever be a need to update the software on my offline computer. I believe I'm running 0.90 on that one.
In the same vein, is there any reason for me to worry that my hard copies wouldn't work in the future? Say I put them in a safe deposit box and then died. Would my kids be able to use the same codes to recover my bitcoins in Armory 16.8.0 in 15 years?
It should always be backwards compatible but you should keep the old installers saved. But it's open source, anyone can make a tool to parse. Now your offline must be updated I think after .90.1 Thanks for the quick response. So my paper backups should be good forever but keep old versions of the software just in case. Cool. I just checked and I'm running 0.90-beta on my offline computer. You're saying I should be at version 0.90.1 or higher for compatibility? Is this something that will need to be continually updated or it's due to a one time change? Well the offline transfer protocol changed that's why it's needed. It was changed to add support for mutli sig. It shouldn't happen too often. You'll get a notification when you try to do an offline transaction. Try it without actually broadcasting. Cool thanks. I'm now stuck in dependency hell as my offline computer doesn't have the necessary versions of the libraries necessary and isn't connected to the internet. I seem to remember going through this last time. |
|
|
|
I recently updated my online machine to 0.92.3 and was wondering if there is any need, or there will ever be a need to update the software on my offline computer. I believe I'm running 0.90 on that one.
In the same vein, is there any reason for me to worry that my hard copies wouldn't work in the future? Say I put them in a safe deposit box and then died. Would my kids be able to use the same codes to recover my bitcoins in Armory 16.8.0 in 15 years?
It should always be backwards compatible but you should keep the old installers saved. But it's open source, anyone can make a tool to parse. Now your offline must be updated I think after .90.1 Thanks for the quick response. So my paper backups should be good forever but keep old versions of the software just in case. Cool. I just checked and I'm running 0.90-beta on my offline computer. You're saying I should be at version 0.90.1 or higher for compatibility? Is this something that will need to be continually updated or it's due to a one time change? |
|
|
|
|
I recently updated my online machine to 0.92.3 and was wondering if there is any need, or there will ever be a need to update the software on my offline computer. I believe I'm running 0.90 on that one.
In the same vein, is there any reason for me to worry that my hard copies wouldn't work in the future? Say I put them in a safe deposit box and then died. Would my kids be able to use the same codes to recover my bitcoins in Armory 16.8.0 in 15 years?
|
|
|
|
|
I don't see a Linux version for 0.91 yet. Also is there any compelling reason to update Armory on my offline computer (currently running 0.90).
|
|
|
|
|
I want the ability to setup watching only wallets for public keys. Specifically for Casascius Coins and paper wallets for which I don't control the private keys (short of breaking the seal).
I've searched this forum and apparently this functionality has been deliberately avoided as there's a fear that watching only addresses could somehow find their way it into our ordinary wallets and give us a false sense of control. I don't understand how this is possible as I control which addresses I import into my wallets.
Anyway if I'm missing something perhaps we could introduce a new wallet designation where it's clear that these balances can't be spent without importing the private keys first.
|
|
|
|
|
Ok I backed up and deleted my armory_*********_.wallet file, restarted and was able to restore. Phew.
|
|
|
|
|
Ok I did something stupid. Not sure if I closed my password vault without saving or what but I already lost my wallet password.
Anyway the first thing I did upon creation was to print a paper wallet so I'm not too worried yet.
Problem is when I attempt to restore my wallet I get the following message:
You already own this wallet!
Nothing to do...
To me the obvious next step would be to delete it and then attempt to restore it. But you can understand why I'm apprehensive to go this route.
|
|
|
|
For now, try to run BitcoinQt on your own and turn off the 'manage bitcoind' option in settings, see if that fixes it. Also get rid of bitoin.conf in your bitcoin folder if there is one
Further testing proved that transactions weren't showing up until the the first confirmation went through. I did what you suggested goatpig and it did indeed fixed my problem. Thank you. This works but I'm wondering if Bitcoin-QT is more resource intensive than bitcoind or is the difference negligable? Edit: LOL I just realized you were probably talking to sdczen rather than me. It fixed my issue just the same though  |
|
|
|
Armory shows zero-confirmation transactions. Have you seen this persistently, or once? Because occasionally the transactions do not propagate to every node, though I haven't seen that happen in a long time. But I would not be surprised if that happened once. If it happens more than once, please send a log file to our support email (at bitcoinarmory.com).
I just installed Armory for the first time and was running some tests. I noticed this was the case when I sent my first bitcoin transaction to Armory. I'm not sure if it was a one time deal or a consistent issue with my install. I appreciate your response, I'll run further tests and let you know. |
|
|
|
|
I want to see pending transaction even when there are zero confirmations. I get nervous waiting to see $1000's of dollars of fiat in limbo for ~10+ minutes. The QT client shows pending transactions within seconds.
|
|
|
|
|
Thanks but it still doesn't work.
|
|
|
|
|
Can somebody please explain this to me like I'm 12?
I want to automate various online transactions but I always get:
$ ./bitcoind getbalance
error: couldn't connect to server
$ cat bitcoin.conf
rpcpassword=********** # Is this my wallet password?
rpcallowip=192.168.1.2
rpcssl=1
rpcsslciphers=DEFAULT:@STRENGTH
|
|
|
|
|
Can somebody please explain this to me like I'm 12?
I want to automate various online transactions but I always get:
$ ./bitcoind getbalance
error: couldn't connect to server
$ cat bitcoin.conf
rpcpassword=********** # Is this my wallet password?
rpcallowip=192.168.1.2
rpcssl=1
rpcsslciphers=DEFAULT:@STRENGTH
|
|
|
|
|
Good to know, thank you. Why is there a hard limit at 100 and what happens if I go over 100?
Several forums that I've read recommend that I use a new address for each transaction. That would add up real quick.
|
|
|
|
|
The balance in my wallet fluctuates up and down quite a bit. I backup my wallet maybe once every couple of weeks.
What would happen if my computer crashed and I restored a wallet that has more bitcoins in it than the wallet that I lost?
Would the system know which coins I no longer hold or would my transactions fail a lot?
|
|
|
|
|
