Armory - Discussion Thread - page 139.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Quote from: Parazyd on February 13, 2013, 08:58:43 AM

Let's say, 30 wallets and 2 addresses used in each one. I'll be OK?

That would actually be 102 used in each one, because Armory maintains a lookahead list of addresses 100 beyond the last used (for a variety of reasons). Either way, that's still only 3k addresses. I believe that the number of transactions combined among all addresses is the more important factor... having 1 address with 1,000,000 transactions (like an SD address) will be far more stressful than 10,000 addresses with 1 tx each.

On the other hand, I'm mostly speculating based on how I designed it. But speculations aren't always right. Try it out and let me know! Though, because of what I said before, you should consider whether you can get by with fewer wallets using more addresses each, solely due to the way the GUI is designed.

Parazyd

hero member

Activity: 812

Merit: 587

Space Lord

Let's say, 30 wallets and 2 addresses used in each one. I'll be OK?

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Quote from: Zedster on February 13, 2013, 07:00:53 AM

32GB RAM your just playing Call of Duty. But ok from now there is really no reason for me to be running constantly anyway. Glad to know you're on it.

I don't play many games anymore. The 32 GB of RAM is because I usually have 3+ virtual machines running at the same time, all running Bitcoin-Qt and Armory. It's for testing its performance on multiple OS. Plus, if I spend a lot of time digging into the C++ code, it's really nice to have a Windows VM with MSVS to do debugging of C++ ... nothing beats it...

Quote from: Parazyd on February 13, 2013, 08:32:04 AM

What's the maximum amount of wallets that can be loaded at the same time?

There's no arbitrary maximum. It ultimately comes down to how many addresses you have combined in all your wallets. I can tell you that I have run with tens of thousands of addresses, and there is no problem (but as we just noted, I also have 32 GB of RAM). But the number of addresses is not really the bottleneck -- the size of the blockchain is. So unless you are doing crazy stuff, like generating millions of addresses for research/experimental purposes, there should be no problem. Note that each wallet generates the next 100 addresses by default... so a new wallet will have the number of addresses actually used, plus 100.

One thing you might find annoying is that the interface isn't designed very well for lots of wallets -- for instance, you can't sort or resize the wallets table, and you can't do arbitrary filtering of the ledger (i.e. -- only show transactions from wallets A, E, F and Q). Other than that, it should work...

Parazyd

hero member

Activity: 812

Merit: 587

Space Lord

Updating my block index... This thing looks awesome. I'll finally be able to send from one addrrss to another.

One question.

What's the maximum amount of wallets that can be loaded at the same time?

Zedster

full member

Activity: 182

Merit: 100

32GB RAM your just playing Call of Duty. But ok from now there is really no reason for me to be running constantly anyway. Glad to know you're on it.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Quote from: Zedster on February 13, 2013, 05:16:21 AM

I apologize if this is discussed in this thread already, I could not find the search thread function here.

I have also just upgraded to Bitcoin 0.8 RC1. I can not say for sure this wasn't the case before that but should Armory.exe be using over 2GB memory and it crashes quite regularly on my system.

Unfortunately, this is real. A real consequence of SatoshiDice growing the blockchain much, much faster than I anticipated. The original Armory used to hold the entire blockchain in memory, requiring the user to have more than 2 GB. This was resolved by switching from storing the blockchain itself, to just storing file pointers to the tx/block data in RAM.

Unfortunately, with 10+ million transactions in the blockchain, even this tx index is too big for RAM. That's why one of my major upgrades in the near future (besides new wallets) consists of switching everything to LevelDB databases. Armory RAM usage should drop by an order of magnitude and run much more smoothly on less-powerful computers. It comes with a few other nice benefits, too. But at the expense of duplicating all the blockchain data (but it is needed anyway, if I'm going to ever have Armory connect to remote Bitcoin-Qt/bitcoind instances).

For now, you'll just have to hold on until I get the chance to replace the RAM usage with HDD usage. A lot of users are getting shut out... so this has become a very high priority... and one I tend to forget about because I have 32 GB of RAM on my development computer

Zedster

full member

Activity: 182

Merit: 100

I apologize if this is discussed in this thread already, I could not find the search thread function here.

I have also just upgraded to Bitcoin 0.8 RC1. I can not say for sure this wasn't the case before that but should Armory.exe be using over 2GB memory and it crashes quite regularly on my system.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

jl2012

legendary

Activity: 1792

Merit: 1111

I have just upgraded to Bitcoin 0.8 RC1 and I find that my Armory 0.87 beta would sometimes stop updating. The block count in the right bottom corner shows "Connected (220817 blocks)" but Bitcoin-qt is already showing 220903. Armory stills shows new tx, but the number of confirmation remains 0 despite it has been confirmed. Everything was back to normal for a while after Armory is restarted, but it would somehow stop updating again.

Code:

2013-02-12 20:34 (INFO) -- ArmoryQt.py:3205 - Dashboard switched to fully-online mode
2013-02-12 20:34 (INFO) -- ArmoryQt.py:3205 - Dashboard switched to fully-online mode
2013-02-12 20:37 (INFO) -- ArmoryQt.py:3410 - New Block! : 220809
2013-02-12 20:37 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 20:37 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000074a783b4427337c720ddc63727dea306f7fc5bb90c17d470bc
2013-02-12 21:18 (INFO) -- ArmoryQt.py:3410 - New Block! : 220810
2013-02-12 21:18 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:18 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003688e6effc415f0551dc8452da8ba8dec22d6035f1559618649
2013-02-12 21:25 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:25 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004829f8ec992570ad67a07c21d0ac188895446c6908a3ec77ce3
2013-02-12 21:25 (INFO) -- ArmoryQt.py:3410 - New Block! : 220811
2013-02-12 21:28 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:28 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000043751773e28d37e5b1628ef08bfde6bdbe13131cf4b1129a8b7
2013-02-12 21:28 (INFO) -- ArmoryQt.py:3410 - New Block! : 220812
2013-02-12 21:35 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:35 (INFO) -- ArmoryQt.py:3410 - New Block! : 220813
2013-02-12 21:36 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004a2e96fc0e15cba01f0570c1aece435c11e3ec11d24a8ee9804
2013-02-12 21:36 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:36 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002b4f3f0538deddecf04d7dad72402331977c76576283a8d1f4d
2013-02-12 21:36 (INFO) -- ArmoryQt.py:3410 - New Block! : 220814
2013-02-12 22:07 (INFO) -- ArmoryQt.py:3410 - New Block! : 220815
2013-02-12 22:07 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:07 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002bbfbe339f3dd48316c20b21be7ce1bdb5b5f131f0db296036a
2013-02-12 22:27 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:27 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:27 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004667e989a5ad255d6baa7f59db4db3906b02dc128634bf95a18
2013-02-12 22:27 (INFO) -- ArmoryQt.py:3410 - New Block! : 220817
2013-02-12 22:27 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003200a65a5146f8e894704976bd21d1cf209e2dc8c7f3d0d40ea
2013-02-12 22:34 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:34 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000015142450a030a8641e9a70290027eaaa8f8d52a6bd9d2afcac4
2013-02-12 22:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000038600b771887da5b3830947bb3ea129f8fc571cec43990410d3
2013-02-12 22:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000001a5964a6deca4a1b842889652e4c301f10a311de51d7a3d2e7
2013-02-12 23:04 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:04 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000c9de2b7ce3bd605cfed4dbbbcd3b3498c9e0946fe5dd0f2296
2013-02-12 23:08 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:08 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000412718fa5a1984a5a675746cf26199bf6cca60a501eaf842382
2013-02-12 23:18 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:18 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003e6afbd5a7215acedbc023c1749a2718145dae1a6c35feb4d71
2013-02-12 23:33 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:33 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000426c1c65d6b80deac16358d74c342724ef1ecfa9a1e0dc00e0e
2013-02-12 23:39 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:39 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000481f700e78826444fc7cc621dd31026b0e48fa2237289284414
2013-02-12 23:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000022ac4a92fe52d54369a983bd6a317761af0c81dbee919798271
2013-02-12 23:54 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:54 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000219272cdf8221744445a5dad573b31407b9a880d0118f714ba9
2013-02-13 00:25 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:25 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003cc8969bd449abd4e4e2dcf519a0110982748f00ca2db5753a4
2013-02-13 00:33 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:33 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002ce1618afdb84ebfd380049e1afa889ffe25f1b454e07a78039
2013-02-13 00:34 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:34 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001954c5d59d02efe184b1519afed0b00b12586fb5aff9e7c8310
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004f958de0219d509e8ba156d9893f4903f9fa6c23edfed5ef565
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000eb3c170ca260e1dffa2b1a91772dcae18a4df3446f377bd1b4
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000040681ba05ed54daa23667b2673d3ef6acbabd2dc36c95d66ab7
2013-02-13 00:48 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:48 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001f94f1644dfd3d056e5098d325b4b2bf4cb3c2690d7006c1a87
2013-02-13 01:03 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:03 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000379de774e67d9bdb305af68a956f891c548f0da19c538a79071
2013-02-13 01:10 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:10 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001cfaf40b52daf78d4cf9c0e93e427c242b90386ea6aae9d079b
2013-02-13 01:23 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:23 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000437a3ec102cf9050b7a26c0d986acf74cf9b3d6eff8ad7959de
2013-02-13 01:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004af3c30dac15e153941696c078a8e5c968bfe364de9a858e7c0
2013-02-13 01:57 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:57 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000576ea85bd5de07bdbc81a00549f6d20f8549b04a7597f5d64a
2013-02-13 02:00 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:00 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002bc74b17eb31d45dcac53ec1ba082c0bc7113e73ec32bae952f
2013-02-13 02:09 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:09 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000015bd9e602c027f1eb2367ec7a8c8d4d70baa44cb27e86c6af81
2013-02-13 02:18 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:18 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003ac4741d68090c24d6b7c3fd201a20f781c97759d472fec49a5
2013-02-13 02:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000029b96bec10dc57876c04c434af46751d6cc472c06cd1c92feec
2013-02-13 02:48 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:48 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000043808648eabbeda3022a41cb311bfb6d9af9fc1520b8061ec8
2013-02-13 02:53 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:53 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003b45a22c6e1959fd0e79061998e4c2ac5147fb9a99751fa5576
2013-02-13 03:00 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:01 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000c32ac05e662ee9bd4d222b549abe10178fb544d6e6f26e93c9
2013-02-13 03:21 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:21 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000334d1548d2423a37efd06ace379021b2b8385e483964fffa300
2013-02-13 03:44 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:44 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000013255a453dde9658c72a6e0f25d305554448361f35b529b2b73
2013-02-13 03:44 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:44 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000004cbe8d606dc4ba12dbd5cb1341aebac36d7865b5114c8eee0d
2013-02-13 03:51 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:51 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000020bcc1e59ce644505748582a62f4459b94a5f882fafbfbb3ba3
2013-02-13 03:52 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:52 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004b3cd2392613cfc92956e0e7a0031f61bc2f7df29734f5d5ea8
2013-02-13 04:02 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:02 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000024553030a164723359019d23ad199392f8a0a15a5e0099db2fd
2013-02-13 04:02 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:02 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000034daa0096eeded10790f95d5818abfb25c51f1fcbe7e2bb355d
2013-02-13 04:08 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:08 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003900a5672134b4cf28e6644aa8910f4ac6949cf7f4a261cc026
2013-02-13 04:25 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:25 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004af9c6b6a73d0070f174565ba88b5b0c08e752684f28ee6c716
2013-02-13 04:36 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:36 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:36 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000039ca2e3e0878ed6a01ab21dac204e542bc30a1a2f3dacbe254a
2013-02-13 04:36 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000046667582296b65fe3aa46b381ac1721529641a131a23f0b8cc5
2013-02-13 04:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000001d7ff7cd8e0b0dd99d98a240a3a46600542fa8d5971a88450c
2013-02-13 04:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004142fb1be064fbecac5aa5f2425e3e8ac81c2983774119f5df7
2013-02-13 05:01 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:01 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000028e922fc468545b37d57384bad8bf0e8865608a00db449c399e
2013-02-13 05:18 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:18 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002d58bea826565a1c18bab38cef66dbb574c3bc50720af4d3644
2013-02-13 05:37 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:37 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000042ad6a204886aab4a988a8a93a88c11db279cc2245b76d29742
2013-02-13 05:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000040bd33ab8464677122f1c549a7993c67b3fb5d22365c84d961
2013-02-13 05:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003eb48fbc7e7f17f49977b7938b5430459ce98821a3f81af360c
2013-02-13 05:48 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:48 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000031547d290a9f4b59cdfaebc82560c0da63ccf0ef435b547fcb6
2013-02-13 05:56 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:56 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:56 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000431d261f1612e14e5dd6f92f66fe27faabce1bd5e1a3ae53e1d
2013-02-13 05:56 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003371e40ad12f89d6f2f23a8b3e2df23f19ca75d4ac082e04d68
2013-02-13 06:24 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:24 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003df0f60971ba1a88de2fd3a89a203dbcf5862629bd0920d3a2c
2013-02-13 06:34 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:34 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002284bc9ab5c6fe33f7941a98a175f028c8643ce61fcbb4311d8
2013-02-13 06:40 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:40 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000006d7aaf3feeecda7e3f12bfabe4848ff866e391d2460a8dc35c
2013-02-13 06:46 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:46 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:46 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000492908d9d0271cc1655799c04bbfe1145c18683f67b8627c04b
2013-02-13 06:46 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000002a5c33e8eefbfc2912dcb1109f4ce4ed19abd708d3de921907
2013-02-13 06:49 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:49 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000028283a043aab59527db4e040e4cf551d6ef35811726e33e0733
2013-02-13 07:09 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 07:09 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000036770a969c85cea0f7fe3c2779032bc90aecfb0a71dd6cbc7fa
2013-02-13 07:35 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 07:35 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000001dcce624bb3d76337c1f7c4e8c1ed5b18a6f82f99b3ce8da7d
2013-02-13 07:49 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 07:49 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000abb59be4be356bf9bb9b9935c220aa6993c871985925416320
2013-02-13 08:05 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:05 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000038e39a10defe06fef9f21d07556b54ae13aa57156dab628417
2013-02-13 08:17 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:17 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000005c6d7b6836836cdd5b01b0a37363befff5eb715ea063615ef1
2013-02-13 08:24 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:24 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003759bee816c1839bb0d045e73c9565f121e51a66627be4291cc
2013-02-13 08:25 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:25 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000015a0d2846f580d3f02763480bddd88a3f5f28a6e67620f47809
2013-02-13 08:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000004673b271204959ac69f294ee6eeb179ff1568b3b072205e140
2013-02-13 08:49 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:49 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000004415cfdfdec7dd9ce8bbe57cc63bbdd565256b9dc2bd952ed2
2013-02-13 08:56 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:56 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002b2c2816eede3e5094bce80d28e410ebc994315862210ac00da
2013-02-13 09:06 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:06 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000022bf19f7191a0752402bf6ac5d078fdcc2c4ec19a461414bec
2013-02-13 09:24 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:24 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000321aa510c47e67cd9ec69a0c748b5fc619fe647e9bafbcd7cba
2013-02-13 09:30 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:30 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001494a50cdf8052692eb3b835ccb0e0ea74ff278da755fb418bf
2013-02-13 09:37 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:37 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000051a25052e0699c1f7295b9c7ebd4999ac99498c462d32d1f632
2013-02-13 09:48 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:48 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001dcca7d765f095078af64cb1553833335bef676fc74db85283c
2013-02-13 09:49 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:49 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001f5fd9e3877102f68641d95308b1088cd4367eb1958be6492c0
2013-02-13 09:56 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:56 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000017e1883d4266c0faf4789436b7eda06a8c77e7b9d624fa80b52
2013-02-13 09:58 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:58 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004ebb76cb1d8db0ea1eb9dd48919fb8dfe78a0dfdbc8730ebf60
2013-02-13 10:03 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:03 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001faa5f06c81b98ef9d008b5853243fa8449c1b4b1f2e6c76194
2013-02-13 10:07 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:07 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000023ba949750231780415d8f78d417a3f31f4582ca0cdc94c61f1
2013-02-13 10:40 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:40 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001cd76584294b036573375f69242add97919c617913bd11b0e13
2013-02-13 10:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000da7e927f6836ab33d59b2d178058287450aaeccb4294f6f628
2013-02-13 10:52 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:52 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000013b888d5d830863e5ecf719cd66b6042405186bed59c434d500
2013-02-13 10:58 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:58 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000443f105fb58797a444555e52626eb5dbc170ae026693a4c67c3

This is the log. It seems armoryengine.pyc keeps receiving new blocks, but ArmoryQt.py is stopped at 220817 (and somehow 220816 is missing)

My system is Windows Server 2008 R2 x64

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Quote from: Zedster on February 12, 2013, 07:38:31 PM

Bitcoinarmory.com down?

It's back up, now.

Having some issues with transferring the domain to another webhost, and also setting up some services on it. There will probably be one more downtime slot in the next week, and then it should be stable after that. Sorry for the trouble!

Zedster

full member

Activity: 182

Merit: 100

Bitcoinarmory.com down?

justusranvier

legendary

Activity: 1400

Merit: 1013

Quote from: picobit on February 11, 2013, 08:10:23 AM

Does anyone have any experience using Armory together with the 0.8rc1 version of the Satoshi client. I would like to try out the new client, mainly in the hope that the usual "wait for the Satoshi client to catch up" ritual can be shortened. But I don't really want all my funds to be inaccessible until I find a way to migrate backwards.

The newest Armory is working for me with a version of the Satoshi client that includes the new block format.

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

Does anyone have any experience using Armory together with the 0.8rc1 version of the Satoshi client. I would like to try out the new client, mainly in the hope that the usual "wait for the Satoshi client to catch up" ritual can be shortened. But I don't really want all my funds to be inaccessible until I find a way to migrate backwards.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Quote from: SgtSpike on February 06, 2013, 12:16:01 PM

Question about offline transactions... what are the system requirements for a computer that would ONLY hold private keys and sign transactions? And is there any special setup procedures for such an offline computer? Do I still have to install the Bitcoin-QT client?

@ SgtSpike:

Chrisrico hit it right on, but I'll add a link to the Quick Start Guide that I created recently. It shows a very short list of what you need for online and offline, and has some common questions like yours at the bottom.

@ Everyone else: I see I missed a lot of messages. FYI, I am on vacation right now, and have been fairly detached from... regular life. I will go back through these messages and respond soon. I promise!

chrisrico

hero member

Activity: 496

Merit: 500

Quote from: SgtSpike on February 06, 2013, 12:16:01 PM

Question about offline transactions... what are the system requirements for a computer that would ONLY hold private keys and sign transactions?

Nothing special. I run it on a Raspberry Pi.

Quote from: SgtSpike on February 06, 2013, 12:16:01 PM

And is there any special setup procedures for such an offline computer? Do I still have to install the Bitcoin-QT client?

Nope, no blockchain or network connection is necessary.

SgtSpike

legendary

Activity: 1400

Merit: 1005

Question about offline transactions... what are the system requirements for a computer that would ONLY hold private keys and sign transactions? And is there any special setup procedures for such an offline computer? Do I still have to install the Bitcoin-QT client?

ErebusBat

hero member

Activity: 560

Merit: 500

I am the one who knocks

Quote from: Red Emerald on February 02, 2013, 06:54:31 PM

Quote from: ErebusBat on February 02, 2013, 06:26:29 PM

I think you can also do listen=1 with a connect and it will work, that is how I got t working with TOR IIRC.

I hope you mean a Tor Hidden Service. If you are using Tor as a client, you don't want to listen.

I was connecting to nodes over tor; however armory did not work (obviously).

Adding the listen was a relatively small issue in my setup as the machine could only talk out via tor.

It was more messing around than anything. But the setup did allow to connect to the bitcoin net via tor and still use armory.

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: Red Emerald on February 02, 2013, 06:54:31 PM

Quote from: ErebusBat on February 02, 2013, 06:26:29 PM

I think you can also do listen=1 with a connect and it will work, that is how I got t working with TOR IIRC.

I hope you mean a Tor Hidden Service. If you are using Tor as a client, you don't want to listen.

if you want to use bitcoind and armory u have to specify listen=1, otherwise its impossible to work (unless u learn armory to interact with tor hidden services direcltly)

Red Emerald

hero member

Activity: 742

Merit: 500

Quote from: ErebusBat on February 02, 2013, 06:26:29 PM

I think you can also do listen=1 with a connect and it will work, that is how I got t working with TOR IIRC.

I hope you mean a Tor Hidden Service. If you are using Tor as a client, you don't want to listen.

ErebusBat

hero member

Activity: 560

Merit: 500

I am the one who knocks

I think you can also do listen=1 with a connect and it will work, that is how I got t working with TOR IIRC.

Topic: Armory - Discussion Thread - page 139. (Read 521829 times)