Topic: Armory - Discussion Thread - page 195. (Read 521829 times)
Any chance I can order a shirt for BTC? I know you had some trouble with the first batch of shirts, but if thats all sorted out, I would like one.
Uses just under 2GB of memory here, initial load <20seconds. This is however on a dedicated server with 128GB of memory 
I cant really complain about that.
You got me beat for sure. My macbook air loads it in anywhere from 60 - 90 seconds depending on how much other stuff I am doing. It still locks up at 100% CPU for a few seconds when new blocks are found in both Mac and in a linux VM on mac. Windows and native linux don't seem to have the problemI cant really complain about that.
FYI: the next release of Armory will be 0.80-BETA, and will have no more RAM requirements at all. The initial startup will still be scanning the blockchain, but the program will only store references to file data, and retrieve it on demand. Technically, that's what MMAP is supposed to do, but the mmap-equivalent in Windows is pretty terrible. I would complain that I am being forced to change the architecture based on Windows alone, but I suspect Linux 32-bit might stop working once blockchain is 4 GB, anyway...
And the semi-regular freezes in 0.76 will be fixed as well. I'm 98% confident that it's due to table sorting, even when you didn't explicitly sort any tables. Performance like this has never been an issue, and it doesn't need to be. I just got have to a little work to get the "correct" solution in there.
Hoping to have all this for 0.80-beta, but it might be a while before I get it done, so don't hold your breath
Uses just under 2GB of memory here, initial load <20seconds. This is however on a dedicated server with 128GB of memory
I cant really complain about that.
You got me beat for sure. My macbook air loads it in anywhere from 60 - 90 seconds depending on how much other stuff I am doing. It still locks up at 100% CPU for a few seconds when new blocks are found in both Mac and in a linux VM on mac. Windows and native linux don't seem to have the problem I cant really complain about that.
Uses just under 2GB of memory here, initial load <20seconds. This is however on a dedicated server with 128GB of memory
I cant really complain about that.
I cant really complain about that.
I guess the only thing I can say is: Thank god I have 6 GBs of RAM and happened not to be running much (relatively speaking), otherwise this program would have brought my computer to its knees... not that I can get it to get beyond "Loading Blockchain. Please Wait...", but it's the thought that counts, I guess.
ABSURD memory suckage: http://picpaste.com/pics/iiBPAcLr.1337767611.png
ABSURD memory suckage: http://picpaste.com/pics/iiBPAcLr.1337767611.png
On my linux with only 4GB of RAM it takes a little more than 1GB of it and less than 1min to open the window.
Also, it seems you are forgeting that Armory it's still in Alpha stage, not even Beta.
It's not to use as your everyday wallet, not a chance.
I found -- after a long search -- the reason why it's using so much memory. If I had known when I wrote my previous post that it loaded the entire block chain into memory, it wouldn't have been such a shock.
It doesn't load the whole blockchain into memory anymore. But the more memory you have available in your comouter, the more it will use.
I guess the only thing I can say is: Thank god I have 6 GBs of RAM and happened not to be running much (relatively speaking), otherwise this program would have brought my computer to its knees... not that I can get it to get beyond "Loading Blockchain. Please Wait...", but it's the thought that counts, I guess.
ABSURD memory suckage: http://picpaste.com/pics/iiBPAcLr.1337767611.png
ABSURD memory suckage: http://picpaste.com/pics/iiBPAcLr.1337767611.png
On my linux with only 4GB of RAM it takes a little more than 1GB of it and less than 1min to open the window.
Also, it seems you are forgeting that Armory it's still in Alpha stage, not even Beta.
It's not to use as your everyday wallet, not a chance.
I found -- after a long search -- the reason why it's using so much memory. If I had known when I wrote my previous post that it loaded the entire block chain into memory, it wouldn't have been such a shock.
I guess the only thing I can say is: Thank god I have 6 GBs of RAM and happened not to be running much (relatively speaking), otherwise this program would have brought my computer to its knees... not that I can get it to get beyond "Loading Blockchain. Please Wait...", but it's the thought that counts, I guess.
ABSURD memory suckage: http://picpaste.com/pics/iiBPAcLr.1337767611.png
ABSURD memory suckage: http://picpaste.com/pics/iiBPAcLr.1337767611.png
On my linux with only 4GB of RAM it takes a little more than 1GB of it and less than 1min to open the window.
Also, it seems you are forgeting that Armory it's still in Alpha stage, not even Beta.
It's not to use as your everyday wallet, not a chance.
I guess the only thing I can say is: Thank god I have 6 GBs of RAM and happened not to be running much (relatively speaking), otherwise this program would have brought my computer to its knees... not that I can get it to get beyond "Loading Blockchain. Please Wait...", but it's the thought that counts, I guess.
ABSURD memory suckage: http://picpaste.com/pics/iiBPAcLr.1337767611.png
ABSURD memory suckage: http://picpaste.com/pics/iiBPAcLr.1337767611.png
Brilliant client, just switched to it.
I'm questioning this because you obviously can't paper copy the imported keys in the wallet.
yes you can. "Backup Individual Keys".
You are right, I was unclear. What I meant was that the imported keys are not included in the paper copy of the wallet.
If I make a paper copy of only the imported keys, is it possible to not have it send some to a newly generated address when sending transactions? I've noticed when I send an amount, some end up in a new address in the wallet - but this is maybe only for very small transactions (<1 btc?)?
All Armory wallets you create are deterministic, regardless of your intentions. And all wallets are designed to use the next address in the deterministic wallet for transaction change, which means you will end up using addresses that were not imported every time you send coins. This is because I don't want to default to sending change back to any existing addresses, for a variety of reasons. In the future I will add a way to specify change outputs, but it's not there yet.
Luckily, every deterministic address is captured in the single "Paper backup" printout (which you can copy by hand, if you want). So, you really only need to back up one more piece of information in addition to the imported keys...
I'm questioning this because you obviously can't paper copy the imported keys in the wallet.
yes you can. "Backup Individual Keys".
You are right, I was unclear. What I meant was that the imported keys are not included in the paper copy of the wallet.
If I make a paper copy of only the imported keys, is it possible to not have it send some to a newly generated address when sending transactions? I've noticed when I send an amount, some end up in a new address in the wallet - but this is maybe only for very small transactions (<1 btc?)?
I'm questioning this because you obviously can't paper copy the imported keys in the wallet.
yes you can. "Backup Individual Keys".
Great work on Armory, etotheipi!
I've been playing around with some vanitygen-adresses and I see that you only can import them into an existing wallet. Is it possible with the nature of how a wallet is created, to create a wallet based on a private key/address generated by vanitygen? I'm questioning this because you obviously can't paper copy the imported keys in the wallet.
I've been playing around with some vanitygen-adresses and I see that you only can import them into an existing wallet. Is it possible with the nature of how a wallet is created, to create a wallet based on a private key/address generated by vanitygen? I'm questioning this because you obviously can't paper copy the imported keys in the wallet.
My Armory branded USB key showed up in the mail today! Very cool!
just got mine too! very cool.
thanks eto! Armory is performing great!
oh, i forgot that the T shirts are awesome!!!
My Armory branded USB key showed up in the mail today! Very cool!
Yeah, I finally got all the rewards together and organized. Plus it gave me some time to put together a solid offline bundle for Ubuntu 10.04-32bit and put them on the keys.
The keys are only 128 MB, which is just enough for distributing all the different installers for Armory, and using it for offline transactions. The keys have also been "vaccinated" to help reduce the risk of auto-run viruses. I don't know what the true risk, and risk-mitigated is, but it doesn't hurt!
Btw, do not order from ooshirts.com! They messed up the shirts, then didn't respond to inquiries for 3 weeks! The final shirts were fine, but definitely not very good customer service (well it was good, starting 3 weeks later).
My Armory branded USB key showed up in the mail today! Very cool!
Quote
do u mean u can't import keys to a watching only wallet?
Right, the option isn't there for an offline wallet.
You have to create a wallet first, and then select the wallet into which you want to import the keys. From the wallet properties, there's an option on the bottom right for importing private keys.
Unfortunately, there is no way to import public keys into a watch-only wallet. There's a couple reasons for this, and not all of them are laziness
I just realized that you can't import private keys in to an offline wallet.
I created a new wallet and now the option shows up.
Thanks!
do u mean u can't import keys to a watching only wallet?
You have to create a wallet first, and then select the wallet into which you want to import the keys. From the wallet properties, there's an option on the bottom right for importing private keys.
Unfortunately, there is no way to import public keys into a watch-only wallet. There's a couple reasons for this, and not all of them are laziness
I just realized that you can't import private keys in to an offline wallet.
I created a new wallet and now the option shows up.
Thanks!
Where is the option to import private keys? I saw various pages mentioning that it is located in the wallet properties page but I can't seem to find it.
Also, is there a way to import a public key as a "Watch only" type of address?
Also, is there a way to import a public key as a "Watch only" type of address?
You have to create a wallet first, and then select the wallet into which you want to import the keys. From the wallet properties, there's an option on the bottom right for importing private keys.
Unfortunately, there is no way to import public keys into a watch-only wallet. There's a couple reasons for this, and not all of them are laziness
Jump to: