Kerogore, Is Armory crashing every time you type in your password? We have a known wallet corruption problem, but it's easy to fix if you have a backup. If not we, can also perform a recovery of the wallet file, which is usually successful. See the following page for more info ("Armory crashes every time I type in my password"): https://bitcoinarmory.com/download/troubleshooting/ |
|
|
|
I know there are some people following this thread who speak German. I got a guy who has a lot of money stuck in Armory, and his written English is very poor. I do not understand his situation. Anyone knowledgeable about Armory willing to help him, or at least help translate? I'll split any donations received with you (which may be 0 BTC, but sometimes people like this tip generously).
Let me know if you can help. Even if you just speak german but don't know much about Armory, you can just act as a middle-man translator for our emails.
I am a native german and using armory quite a while now. Please don't hesitate to contact me, maybe I can help you with this. I am also happy to help transalte any strings into German. I love Armory and I have recently introduced it to many others who are not very confident in English but wanted to invest in Bitcoin. How will that work. Do we get a list of strings and just send you back the list of German strings? Goatpig is currently working on proper unicode support, which is the first step to internationalization. After we can handle arbitrary locales and character encodings, I'm going to prepare the app for localization ... basically just wrapping all the user-facing text with a translate function and making sure that everything can handle unicode characters (I wasn't really familiar with unicode or internationalization in general when I started Armory, so I didn't design it from the start with proper support). Once that's done, then we can start soliciting help creating translation files. We won't be able to actually execute it until the new wallet files are done, which will natively support unicode (the current wallet file assumes all strings are single-byte characters... using any other encoding is going to cause widespread wallet-corruption issues, and I'm not excited about modifying the current wallets...). But I think the new wallets will be done around the time that we actually get all the translation files in place for a few different apps. |
|
|
|
|
I forgot to make the RAM usage for that first build configurable (or at least dynamically adjustable based on available RAM). But right now it should only use 1 GB to build the DB. However it is likely to slow things down because it's doing very heavy disk accessing. But after that process is done, it should only use 200-300 MB, and start up very quickly. And not station the system much at all.
Please let us know if your experience differs significantly.
|
|
|
|
|
The vast majority of lost coins in the world are not stolen or on broken harddrives, but instead due to forgotten passwords. I am very aggressive about getting people to make paper backups, because it protects you for all these situations. An encrypted digital backup doesn't protect you from forgotten passwords, which are vastly more common than any other problem. eople are not used to the idea of irrecoverable data.
If you are concerned about physical security, I recommend using the new fragmented backup feature in the latest version of Armory.
|
|
|
|
|
I know there are some people following this thread who speak German. I got a guy who has a lot of money stuck in Armory, and his written English is very poor. I do not understand his situation. Anyone knowledgeable about Armory willing to help him, or at least help translate? I'll split any donations received with you (which may be 0 BTC, but sometimes people like this tip generously).
Let me know if you can help. Even if you just speak german but don't know much about Armory, you can just act as a middle-man translator for our emails.
|
|
|
|
|
Paper backups are not encumbered with a password. The number one reason to use a paper backup is when you forget your password. You could prove it to yourself by looking at the paper backup data before and after you change the password. It'll be the same.
|
|
|
|
How about any derived private key, which is not the root key? How serious a leak would that make? Does it compromise all the other private keys as well, if the attacker knows the chain code? (which I assumed is the same for both, private and public chains).
You should always assume that revealing a private key from a deterministic wallet will reveal all siblings. In Armory wallets, if private key x is revealed with the chaincode, all private keys >= X+1 are revealed. But I don't spend much time worrying about this. We do not support or claim to support any use cases where private keys are intentionally revealed. And if your wallet is unintentionally compromised, they will all be revealed anyway. |
|
|
|
Grab the latest from the bitcoinarmory.com website. It hasn't been perfect for everyone, but if you are nice to it, it is dramatically better than the previous versions (uses dramatically less RAM, starts up faster, has cool new backup features, etc).
Any known problems with running the latest version online and 0.87 offline? Nope. Until we get the new wallet format done, you can use something as ancient as 0.60 on the offline computer and it will still work with the latest version online (though those ancient versions will no longer work online) |
|
|
|
|
A full Armory wallet is just
1x Root Private Key
1x Root Public Key
1x Chaincode
A watching-only Armory wallet is just
1x Root Public Key
1x Chaincode
So basically watching-only wallets don't have any private key data at all, and the chain code is just a constant that is carried through all the calculations. With the priv key + chaincode, you can compute all private keys. With public key + chain, you can compute all public keys that match the private keys produced on the full/offline wallet.
The chaincode and public key are not security-sensitive. Someone getting them is a breach of privacy, not security. All internet security is based on the fact that the public key is widely distributed (i.e. "public") and that the scheme maintains full security as long as no one else has the private key.
|
|
|
|
I tried searching for the answers but I couldn't find any. Just in case in the future if for any reason Armory is not working, I wanted to see the alternatives of importing a wallet. The only reason I find interest in importing the wallet is just for convenience. By importing every private key separate, it would take a while if one had small amounts of btc in each.
You can't do this, because right now Armory uses a deterministic wallet that no one else uses. When Armory started, there werent' any other apps that had deterministic wallet, so there was no one to be compatible with. We'll all upgrade to BIP 32 eventually, but until then the only way to do it is to export the first X keys and import them into the target application/service. Or mod one of the other wallets to do the same deterministic algorithm  |
|
|
|
|
Grab the latest from the bitcoinarmory.com website. It hasn't been perfect for everyone, but if you are nice to it, it is dramatically better than the previous versions (uses dramatically less RAM, starts up faster, has cool new backup features, etc).
|
|
|
|
Hi there:
Running Armory 0.87, and sometimes, when I haven't maximized it for a while, it starts again from scratch as if it had shut down on its own.
Is this a time-out function within Armory? Why would it shut down?
That behavior doesn't sound familiar. However, 0.87.2 and 0.88.1 both had bugs that would cause them to crash once every few days (every time the blockchain grows 128 MB). This has been fixed in the latest version. Don't know if it's related. |
|
|
|
|
(1) Yes, it's all UI. But we risk alienating users by making Bitcoin even more complicated and confusing than it already is. If everyone (and every wallet app) uses different units, and they can't convert in their head easily, and it's even the slightest bit feasible to enter incorrect values... it's becomes a serious usability problem.
(2) Making a concerted effort to have everyone changing units will cause confusion even if we "do it right". And there will be resistence. And disagreement. Let's decide it's a good idea, then do it once and push it hard.
(3) Now that I'm a business owner, I can tell you that there are a plethora of tools out there for helping manage and track financials. And there's no guarantee they handle anything more than 2 decimal places, because they don't need to. I don't know if there's any currencies that use more than two.
And I recently talked to a guy about using NetSuite for our company which is used by multi-billion dollar companies, and it doesn't handle more than two decimal places. He had to implement everything he did in microbitcoins because of that.
|
|
|
|
|
There was some discussion recently on the mailing list about this. The general consensus was that:
(1) This needs to be done carefully to avoid people sending 1000x what they intended
(2) It is difficult to change an established system. So we want to do it once.
(3) It'd be nice to only have two digits after the decimal since most accounting software can't handle more
Therefore, we go straight to micro-BTC. It solves all of this in one fell swoop. At the current Bitcoin price (~$1,000) that would be 1,000 uBTC per $1 USD. That's a totally reasonable, human-usable system. And accommodates all future non-hardforking growth (i.e. if we never need more than 8 decimal places, this will be last forever).
|
|
|
|
Did you say the transaction last is correct? If the balance is correct then there should be a transaction in you history with coins going to the hidden address. It would also show you the wallet id next to that address. Can you confirm? Yea I can confirm that, and that is my wallet address (ID) and my first key A (what is missing). I have sent you some PM's with more specific details - pictures of my wallet. BUT can we restore my money? Should I make a backup restore? It is even possible to get my money back? Did I really lost them? And if yes, HOW? How it is possible that my first address with my balance impute is missing/disappear? They're not lost. The only thing that's missing is the address from your wallet display. If you wanted to spend them you could--armory wouldn't show you the balance unless it was spendable. Go to the wallet "Backup this wallet" then "See other backup options", the "Export Key Lists". The check "Include Unused (address pool)". Only show the address strings and none of the public or private keys. That will leave you with a list of about 120 addresses. Your address must be on that list. If it's not, there's no way Armory could label that address as being part of your wallet. |
|
|
|
|
Okay, it is in the GUI, but a warning first:
There's a bug in address generation, that causes generation time to be O(N2) of the number of addresses you want to generate only if the wallet is encrypted. Therefore, you should only generate up to 500 addresses at a time ,if it's encrypted. If you make the wallet unencrypted first, you can do any number in O(N). Of course, most people don't want to write an unencrypted copy of their wallet, but it may be the only real way to work around this.
There is a work around if you modify the code directly, and make the walletLockTimeout > 10s. Make it like 10 min. Then unlock your wallet anywhere in the app, and it will remain unlocked for 10m. Then go generate your 1,000,000 addresses. (btw, 237 bytes on disk for every address you calculate)
The new wallet format should resolve this issue. Until then, you'll have to work around this constraint.
Btw, the operation is in the GUI, in Expert usermode, within the wallet properties. Click on "# Addressses used"
|
|
|
|
Need some help compiling Armory on Ubuntu 13.10. It exits with: g++: error: /usr/lib64/libpython2.7.so.1.0: No such file or directory
make[1]: *** [swig] Error 1
make[1]: Leaving directory `/home/itod/BitcoinArmory/cppForSwig'
make: *** [all] Error 2 Sorry if this was answered somewhere, but having browsed through this thread haven't found an answer. Changing two lines in Make suggested in this post https://bitcointalk.org/index.php?topic=56424.msg1463846#msg1463846didn't help. Please suggest a fix. Thanks. Agreed this is the wrong thread, but I'll respond quickly. Did you follow the instructions on the Building Armory from Source webpage? I just tried it on a stock 13.10 install and it worked. |
|
|
|
IF you drop your wallet, don't drop it completely. Just move the file somewhere else, then if everything else fails you move it back, and everything should be OK. Like I said before I have paper backup (first thing I did), digital backup and keys backup. I did digital backup with those new keys after @etotheipi response (I have 15 keys but still not the first one with my funds). But first: Look at your wallet with Wallet Properties. Are you sure that none of the three check-boxes are selected. They are called "Hide empty", "hide change" and "hide unused". If any of them is selected, try unselecting it. I did check it several times. When I peep (F3) my keys backup I can see my keys (A,B,C,D - first four I did backup) where A is my first key (with PrivBase58: xxx and PrivHexBE : xxx). I did run bitcoin-qt without armory and there is no address, no funds. @picobit anyway thanks for your interest and reply. I would like that armory maintainer give me some advice step by step what to do now, so I wont accidentally break something up or make things worse. If no support is given, then I will definitely use your advice. Remember that till now nobody clarified that ->paper backup = safety<- as is wrote everywhere and 95% ppl think. Like here - http://www.reddit.com/r/Bitcoin/comments/1bhky4/i_recovered_my_lost_bitcoins/ it's not my case but some interesting thoughts and advice is given there, definitely worth to read. I honestly don't know how the address wouldn't show up if it registers so having a balance in your wallet. Given that it has you correct balance, then the coins have got to be in either the addresses already shown or the first 100 after that. Did you say the transaction last is correct? If the balance is correct then there should be a transaction in you history with coins going to the hidden address. It would also show you the wallet id next to that address. Can you confirm? |
|
|
|
|
Right-click on the transaction and "View on Blockchain.info". If the transaction was broadcast properly, you'll see it on blockchain.info. If not, go to "Help" -> "Clear all unconfirmed" and then send/broadcast your transaction again.
|
|
|
|
|
Show Posts
