I just tried the newest version (Mac OS X version 10.9.5). The good news is that building the first database was much faster than it used to be, and that starting up second time was lightning fast. The bad news is that paper backups do not work. When I click on the Print button, the OS X print menu comes up, but it is almost unresponsive. Sometimes it can be cancelled, and once I managed to open the sub-menu and choosing PDF preview (which never came up). I remember this being a problem once in the past too, but then the problem appeared to go away. EDIT: Then I tried to actually make a transaction. I got this strange error: There was an error constructing your transaction, due to a quirk in the way Bitcoin transactions work. If you see this error more than once, try sending your BTC in two or more separate transactions.
What can this possibly mean? I get this every time I try to make a transaction EDIT 2: I could not export the log file (menu item greyed out). In fact, Armory was completely stuck, had to Force Quit it to get away from the send bitcoin window. Now it rescans the database, good thing that it takes minutes instead of an hour or two as in the previous version I exported the log file while it did that, there is no hint of trouble there. EDIT 3: I cannot reproduce it. Once Armory had finished rescanning, I tried again, this time without problems. I really wonder what kind of "quirk in the way Bitcoin transactions work" this pop-up is supposed to be triggered by...
|
|
|
Why does OCO get's cancelled when the order is only partialy filled? IS that how it should work?
yes, anytime one order is "activated" it cancels the other orders. One cancels Others. So, it is a nice way to make sure you don't double down on buying or selling, if you want to have a stop loss AND a "take profit". But that does not work if a partial fill cancels the whole other order. It is only reliable if a partial fill cancels the same part of the other order (assuming the two had the same size to begin with, which I guess is not guaranteed).
|
|
|
What you have done is only a problem if your netbook does not have the muscles to run Armory. Otherwise, your coins are safe. Is your bitcoin core / bitcoind fully synchronized with the network? Is Armory online, and connected with bitcoin core? Check that the block number in the lower right corner matches the last block number as you can see it on blockchain.info. If not, that is the problem.
|
|
|
is this build supposed to let you send a transaction without the fee?
Up to now, it always forced me to put in 0.0001, but in this build, I can send zero fee transactions.
That has been possible for a while, but probably only if your coins are old enough that no fee is required by the network to propagate your transaction.
|
|
|
You should open a ticket on their support web page, that is the fastest way to get help - much faster than relying on somebody being able to guess what your problem is here.
And remember to attach the logs, that will usually tell them what is wrong. There is a menu point somewhere for finding the logs - sorry I cannot be more specific now, I do not have my Armory at hand.
|
|
|
No, he does not He talks about which state your Armory is. Not state as in country, but state as in "messed up", "working", "inconsistent" etc.
|
|
|
Is that bug back again? It is not a bug in Armory itself, but in the Qt toolkit that Armory is built upon - not that that helps you, of course. Last time it appeared was when Apple updated OS X, it took ages before the Qt toolkit (or OS X) was fixed. The bad news is that there is probably not anything the Armory developers can do about it - unless they have learned a few magic tricks since last time, which of course is entirely possible. The good news is that there is a slightly inconvenient workaround. You only need to backup your Armory wallet once, ever. So you can manually copy the codes from the sheet to be printed to a piece of paper. I have moved a wallet from one offline computer to another in this way once, it did not take long. Of course you need to test your backup extra carefully in that case, but you should always do that anyway, and Armory makes that easy. And you don't need to worry about your printer caching the private keys That being said, it is a weak point for Armory that OS X support is only given low priority by the developers of the QT toolkit. But there is next to nothing they can do about it. EDIT for the developers: I am still running OS X 10.9.5. And Armory 0.92.3-beta. That combination works flawlessly.
|
|
|
It's a bad idea to expose private keys from your chain.
Indeed, a very bad idea. Armory is designed so the use of a watch-only wallet is safe. It is **not** designed so that exposure of private keys is safe. If a hacker has access to your Armory cold storage wallet, he can watch your coins. If a hacker gains access to two of your private keys that you exported to another wallet, he *might* get access to all your funds. DO NOT TRANSFER MONEY TO ANY WALLET UNLESS YOU HAVE VERIFIED THAT YOU CAN GET THEM SAFELY OUT. Exporting private keys from a deterministic wallet is probably not safe.
|
|
|
Don't trust such a database too much. You will not be the first to lose the entire database of passwords. I once lost half a database of passwords due to some strange sync error between devices - fortunately it was only websites, no bitcoins were lost.
|
|
|
If anyone's interested, instead of printing the whole backup PDF I just cut the relevant information and pasted it in a regular text file. Then I encrypted it using aescrypt, and then parsed the result to base64 in order to produce "paper-friendly" text. Now this I'm confident enough to print and store it anywhere... And you just lost the most important function of a paper backup: When you forget the password, you can still get the funds. That is still the most common way of losing bitcoins. I am sure you remember the password in three months, but in three years? Have you tried typing it back in, and decrypting it?
|
|
|
Your paper backup can generate all addresses, also future ones.
You really need to make an official support request at their web page. We (the other Armory users) cannot guess what is wrong. The Armory guys may be able to help you, but only if you send them logs.
|
|
|
I assume that you have found said transactions on blockchain.info, that they are confirmed (Armory only discovers unconfirmed transactions if it is online when it arrives), and that you have checked that the receiving addresses are actually in the Armory wallet (Wallet properties).
If that is the case, then I am sorrry, I have no clue. Have you submitted an official bug report / request for help at their webpage?
|
|
|
Det er virkeligt et voldsomt antal valutaer I understøtter. Er der én fælles underliggende ordrebog, eller er jeres volumen spredt ud over et meget stort antal ordrebøger?
Det må være meget svært at "bootstrappe" en børs, men gør det det ikke unødigt svært at der er så vildt mange små kryptovalutaer, og et stort udvalg af alm. valutaer? Det volumen der trods alt må være bliver jo splittet mellem M*N forskellige ordrebøger.
I er vel næsten nød til selv at gøre noget for at generere lidt volumen. Enten at have nogle bots der fylder lidt i ordrebogen (sikkert dyrt i drift), eller slå diverse valutaer sammen så jeg kan sælge bitcoins for DKK og handlen bliver parret med en der køber bitcoins for USD. Det koster jer selvfølgeligt noget besvær og noget valutakonvertering i starten, når volumen er småt, men er der ellers en chance for at komme i luften?
|
|
|
With the same # of addresses, these transactions were visiable before in Armory. It's only since the crash and wallet restore that I don't see them.
Are you sure that bitcoind is up to date? Look at the block number in the lower right corner of Armory's window, and compare with the block number you see at blockchain.info.
|
|
|
"Cannot parse configuration file: the options configuration file contains an invalid line '{\rtf\ansi\ansicpg1252\cocoartf1343\cocoasubrtf160'.Only use key=value syntax"
...and then quits out of the launch process.
I'm running 10.10.1.
I really don't know, I am just guessing here. But the \rtf part makes me think of "rich text format". Are you 100% sure that you have saved the file as an ASCII text file, and not as a rich text file or something like that? Open a Terminal, go to the directory, and check the file type with "file": ~$ cd 'Library/Application Support/Bitcoin' Bitcoin$ file bitcoin.conf bitcoin.conf: ASCII text
(the bold marks what I typed)
|
|
|
I do not know about Tor, but the bitcoin.conf file would be in
Library/Application Support/Bitcoin
To open the hidden Library folder, click on Finder's Go menu while pressing Alt.
|
|
|
But do read the small print: It only works with addresses that have already been used to SEND bitcoins at least once, because they need the public key, and they get that from the blockchain. Of course if there is a market for it, they could easily make an interface reading it directly from the watch-only wallet, making their site equivalent to the online Armory computer (except for privacy issues, of course).
|
|
|
No, you should not need to do anything to "accept" a coin. The transactions (and thus the coins) are stored in the block chain, think of it as a database with thousands of backups all over the internet. Once the transaction is sent, it will be written into the block chain whether you are having your bitcoin wallet turned on or not. Armory and bitcoind download the database and show you the amount you have. Here is a picture of how armory should look (found somewhere on the net by google): http://spelunk.in/wp-content/uploads/2013/05/ArmoryMainScreen.pngIn the upper right panel, you should see you wallet. There should be an amount next to it. In the picture the (rich!) guy has four wallets, you most likely only have one. The numbers are the total amount, if it says (...) instead of an amount then Armory has somehow not finished scanning the block chain. The big window below shows the transactions. If the amount is in the wallet, but the transaction does not show, then it is most likely because it is a watch-only wallet and Armory think that the coins are not yours. Then you need to click on the wallet, click on wallet properties, and mark it as yours. I have no clue what could be wrong at your end, but perhaps this can help you find out what is different between your Armory and this picture.
|
|
|
OK, so in principle they do not leak any information. But if I somehow leaked a private key, then would this one would give away the rest? Or would it require the root key itself to gain any info? Not that I plan to leak any private keys - nor export them to wallets/services that I believe (for the time) to be safe
|
|
|
Hi, I can see in the armory directory a file called multipliers.txt. It contains lines of the type PrvChain (pkh, mult): ,<256-bit hex number> and occationally PubChain (pkh, mult): <160-bit hex number>,<256-bit hex number> What are these numbers? Do they expose information about my wallets? (I guess not, you guys seem to know what you are doing, but better safe than sorry)
|
|
|
|