Delete

delete

Delete

It works. Excellent, thank you goatpig.

Thank you for that goatpig.

I came across a different problem; how to start the program. I usually start programs from the "start" menu, but this time when I search for armory nothing comes up.

Is there a way to start the program from command line / terminal?

I have great difficulty getting Armory running. I've downloaded the blockchain two times, I've deleted the .armory folder and started over many times, but still no success.

I see from dbLog that there's perhaps a connection problem, but I'm not an expert. I would love some tips on how to proceed.

armorylog.txt:
https://pastebin.com/hu17yHkF

ArmorySettings:
https://pastebin.com/DXS8vmWD

dbLog.txt
https://pastebin.com/KB6BST4D

Thank you very much goatpig.
I realize in hindsight that I didn't ask very politely. Sorry about that.

So I got Armory working, but then I imported several wallets.
Now Armory is not starting up, I'm not sure why, but I guess it's too many wallets.

So just as a quick fix I want to try to reduce the number of wallets.

I'm using Armory 0.96.

Where are the wallets stored on Ubuntu?
I'm not an Ubuntu expert, so I need the exact folder.

OK.

Do you know how the block data get corrupted? I'd think there's some kind of verification process after the block has been downloaded, for example a hash of the block that can be verified, and if it's not adding up, then it should be downloaded over again?

And there is not some kind of repair tool that can fix only the blocks that are wrong? Would save a lot of bandwidth for the bitcoin network.

I was a bit soon to sing praise.

So I'm still not able to run Armory.

I've downloaded the blockchain from the start using Bitcoin Core as suggested.
When that was done I cleared out the Armory folder, so Armory started from scratch.
I tried first running Bitcoin Core in background myself and starting Armory afterwards.
When that didn't work, I cleared out Armory folder again and let Armory run bitcoind itself.
I ran with the block files in default directory, as well as in a different directory

The program seems to stop multiple times at around block file 377. I've noticed because I've restarted it many times, and it seems to start there every time except when I start from scratch.

I'm also using wallet from an older version of Armory, but hopefully that shouldn't have an effect.

Any suggestions are appreciated.

updated logs
armorylog:  http://pastebin.com/Cf6iMHg5
dbLog.txt:  http://pastebin.com/dLhE1uGw

Thanks for helping me out.

Tip on its way.

OK.

Well I did have to make some changes to location of the blockchain, I moved it to a new disk and fiddled around with it. I might have slipped up at some point.

Thanks for your help.

Ah, one more thing. Is it accurate that the size of the Armory database is reduced to around 1 gig?
If it should be 70+ gigs, I should probably move it to another disk as well. If it's been resized I won't bother.

Yeah it looks like you might be right, I see that 31 of the last 100 blocks have unexpected version.

So just delete the chain and wait for a week for it to download again?

OK.

debug.log
http://pastebin.com/0QgPW4Xy

First thanks to the devs of Armory for supporting it.

I'm having some issues with getting Armory started.
I upgraded from 0.93X to 0.95.1. Then I deleted all the armory database and all other files to rebuild from scratch.
It builds the blocks in %appdata%/Armory, though it's much smaller than it used to be (used to be over 70 gigs, now it's just about 1 gig).

Armory then stops every time when it's about to organizing chain (as you can see from the log, wich stops at that point), after it's done parsing, and it uses one core to it's full capacity. I've had it run for a max of perhaps 8 hours without any further progress. I have tried running Bitcoin Core in background myself, and I've tried letting Armory run bitcoind in background. It ends up with the same result.

dbLog.txt
http://pastebin.com/atwYGKZJ


armorycpplog.txt
http://pastebin.com/m0v6JfHc


armorylog.txt (just first 1000 lines)
http://pastebin.com/sP6pKkV1

I would very much appreciate any clue to what actions I could take to make it work, as I've tried all the options I've come up with already.

You're right. Going through the debug.log, I see I was probably on version 10.2.
The log only goes back so far. According to log I was on version 0.12.1 much later.

Using Windows for the moment, I keep the wallet file in C:\Users\[USERNAME]\AppData\Roaming\Bitcoin.
That's the default directory.

I've been switching between different wallet files and restarting bitcoin when I do that.
I have not kept a repository on the wallet files, something I realize in hindsight I should have done.

OK, that's good to hear. As long as it's my mistake I might figure it out.

[later]

All right!

I got it back!

Most helpful was achow101. Please PM me a bitcoin address for your reward. It's too much for so little work, but I stand by my word.

The mistake I made was to assume that it was one wallet, while it really was another.
What I did was restore an old version of the wallet, which had a known password, and just as you said it had the 100 addresses buffered.

I tested to sign a message, and it works smoothly. I also sent a transaction for testing, and it works as well.

The person that helps the most in getting me my bitcoins back will get 1 bitcoin reward.

I have a wallet in Bitcoin core.
I think I upgraded to core 12.1 maybe 9 months ago, and my wallet is older than that. I haven't used core very much, but decided to receive bitcoins to core wallet some time ago, which of course I expected to work.

I know I know, I shouldn't have used a wallet that didn't have the 12 words that will keep my private keys forever, but I knew that I had multiple backups of the wallet so I thought it couldn't be that risky to use Bitcoin Core.

However, now my core wallet doesn't work. I's saying that the password is wrong. I don't remember changing the password, and why would I do that anyway, because I had a nice system on it. But I cannot sign messages or send the bitcoins. It's as if the wallet file is corrupted or something, and now I cannot unlock the private keys. I've tried all kinds of password, but they don't work. The original password I set on the wallet is not working.
If I didn't know any better, I'd suggest that Core has changed the way it stores or retrieves the private keys in a way that's not working properly with the old way the keys were stored. So after upgrading maybe the new keys are not compatible with the wallet? I don't know.

I have backup of the core wallet with a known password that can sign messages, but when I use those wallets, they don't generate the same bitcoin addresses.

I thought even core stored at least 100 addresses in the wallet file, but it seems these addresses are all generated on the spot, with no memory of what's happened before and no seed for the random generator.

Any help in any direction is appreciated, because we're talking quite a few bitcoins.


If nobody can help, maybe we could hard fork bitcoin if I made a mistake, it's just a few months ago that this happened.

Joke aside, I know there's a guy in the bitcoin community that helps people with these kinds of things, and he has a reputation for doing a good job and being an honest person. I don't remember his name. Anyone know who I'm talking about?

Thanks for the tip, it's a good idea.


Yeah, you have to be reasonably close, because my Spanish is not solid at all and I might need help while moving around.


Thanks for the suggestion, I do however expect the person I end up working with to be good in both languages, and communications will be in English.

I am looking for someone to help me in Asunción, Paraguay.

Why should you care?
* I will pay you for your time, 7000 PYG per hour, payment in Bitcoin.
* Minimum billing time is 15 minutes, so if we talk for only a 3 minutes one day, you can charge for 15 minutes that day.
* You get to practice English with a person fluent in English
* You will probably get to learn about the process of purchasing real estate
* For the most part you can work from home, a cafe, your current work or anywhere you want.

What's the job?
* Help me find a lot of properties for sale. I’m not going to buy many, but I am going to look at many.
* Translate between English and Spanish
* Most work might be done with a smart-phone or your computer over the Internet.
* You will need to translate between Spanish speakers and a English speaker at times.
* I might need you to come with me in case I want to travel to a property to look at it/buy it, since there will probably not be Internet everywhere.
* You need to be available for some time, perhaps a few years. The job will not take much time, but I need to know that you're willing to translate and stay in touch at rare intervals for some years until I learn Spanish.

In practice, you'll download an app on your phone, then I'll call you when I need something translated, and you'll translate the conversation. At other times you’ll be looking for real estate for me, and when you come across something that fits my checklist, you’ll report the finding to me. I'll pay you for your time as we go. Easy as air, but you need to know both languages.


Requirements

* You must speak good English and Spanish, and fluency in both languages is preferred.
* You must have access to Internet, as I might need you to translate over the phone.
* You must have a smart-phone, so that you can download an app and talk over the Internet if required; something like Whatsapp.
* You must have access to a computer, so that you can search for property. This is too slow to do on a smart-phone.
* You must live in Asunción, Paraguay, as I might need you to help me translate if I go to a site where there's no Internet.
* Your regular job must have such a flexibility that you can talk for a few minutes here and there. (So if you're a fireman or a brain surgeon who's on call, this job is not a good idea for you)


I will be looking for real estate, so if you are familiar with the expressions of real estate in both Spanish and English, that is an advantage. It’s not required though, as I'm sure you can pick it up quite quickly if you're familiar with both languages.

If you're interested, please PM me.
Thanks for your time

Advantage of having checksum on each ask and bid
Each bid and ask should be signed by the client software of node B. So when node B is sending a bid or an ask to node A, node B will have to refer to a previously established contract, and the software will also have to sign the bid or ask. If a bid or ask is cancelled, a cancel message is created and signed by private key.
Node A specifies in the contract with B the maximum number of messages or RPC that B is allowed to send per second.
If node A receives a flood of messages, but these have the wrong checksums, they are simply thrown away. Perhaps it would be possible to have the GPU do the checking, since this work seems to be of the type that GPUs are good at. This would allow even a modest computer with a GPU to do significant amount of checksum or message-checking.