Is it possible to have bitcoin Armory use an external blockchain rather than downloading the whole blockchain on my computer?
It would be nice to have that option. At some point, it won't make sense to download terabytes of the blockchain and should be left to specialized miners/servers offering that service.
We plan on implementing that eventually. |
|
|
|
I always feel uneasy about the fact that so much money has to depend on MIT's server working properly and uninfilitrated, wonder if there is a way we can employ blockchain itself for further authetication  Sounds like a job for Namecoin! |
|
|
|
|
Are you building the DB without a wallet loaded?
I've received a log file with no body text. The email is titled "logfile" with just the one 84.2kb log attached. Is this yours?
|
|
|
|
Is 6gig or ram going to be a good middle ground? I have a 2gb lying around and bought a 4gb not to long ago. Just running the 4gb stick now (32bit) and even with windows only seeing 3gig worth, still rarely go over the 50% mark. Really don't want to spend the money to go for 8gig just for amory only. I always have a taskbar full of icons and constantly switching between. So it's not like I'm just checking email, close down and open internet explorer, close down and open kingsoft office... Kind of annoying that it always takes 20mins or more to 'build databases". Not only that but can hear my hd grinding away for the entire time. Or maybe the solution is to run it while taking a shower, or making dinner  Are you scanning the chain on every start with 0.90? This is a bug, we have fixes ready for the next version. |
|
|
|
|
There are actually 3 places where Armory gets its data in that regard:
1) The block height is fetched straight from the raw blockchain files
2) Assuming you let Armory manage bitcoind, it will query bitcoind's status through the RPC, mainly for the progress bar. Armory won't use the RPC at all if you manage BitcoinQt yourself.
3) Armory connects as a network node on localhost to your (local, obviously) bitcoin instance to monitor the network and push its transactions.
|
|
|
|
|
add a connect=127.0.0.1
scratch that, its bind=127.0.0.1 that you need
|
|
|
|
gpg: key 98832223: "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" 6 new signatures gpg: no ultimately trusted keys found gpg: no ultimately trusted keys found This is the line you care about. You have to up the trust leve of Alan's offline key yourself |
|
|
|
|
Check your system clock, make sure it matches your local time.
|
|
|
|
|
Armory won't care about a deleted wallet. Go ahead and shred them yourself instead of deleting them through Armory.
My advice to you would be to run Armory with its data dir pointed at an encrypted folder. You can use the --datadir="mypath" command line argument to achieve that. Make sure to move the DB dir to another location with the --dbdir="mydbpath" arg.
It side steps the shredding issue by keeping the wallets and their left overs encrypted.
|
|
|
|
|
We actually are changing to this behavior in the next release, turns out it is preferable.
|
|
|
|
|
At this point you have to manually delete the DB and rebuild.
|
|
|
|
WO: watch only Make sure the WO and the offline wallet have the same address chain length and see if that fixes your issue. If not, with coin selection (in expert mode), pick the addresses you want to spend from and make sure they are present in the Offline wallet. Then let me know how it all went. Also, I'd like to see both the offline and online Armory log files. Do a File -> Export Log Files in both and send them to support@bitcoinarmory.com |
|
|
|
|
How far have you extended the chain on both the offline and WO wallets? Did you have imported addresses in the offline wallet, prior to restoring from paper?
|
|
|
|
|
The WO displays the same ID as the offline wallet?
|
|
|
|
|
You need to push you address chain up to its previous length. Start Armory in Expert mode, go to your wallet properties and click the number next to "Addresses Used", and extend your total address count by 100, see if that does it.
|
|
|
|
|
Assuming you don't hold your .wallet files on a SSD, you'll have to shred them yourself. You only need to concern yourself with .wallet files.
|
|
|
|
Send us your log file at support@bitcoinarmory.comI think we already encountered this bug and have a fix scheduled for the next release. |
|
|
|
|
In expert mode, there is an export key list option in the backup center, maybe that's what you are looking for.
|
|
|
|
|
Show Posts
