Little question, but how do we know that these services are legit. My fear would be that these generated addresses could be logged?

I’ve edited my post to notify me of any replies, so I know when your back up…

Cool, cheers Tuck…

I think you’ve got to treat it like cash, emailing your wallet is like sending a safe box with the money in. They could keep hammering that box, unless you spent it before they get in.

Yes, it’s every 126. The rate of change is radically different, which is what the rest of that talk about. But every 126, the difficulty can (and does) change.

Have you synced the wallet yet? PM me and I will addnode you.

‘‘Doesn’t exactly instill me with confidence’’ well hey, it was not sent by purpose, they don’t want new members and they dislike good working systems. /sarcasm-off

Hi Newb.

I monitored the connection to your wallet, when I gave you the addnode. It would appear that it is your network that is the problem.

In both cases your mathematical calculation will only be a rough approximation (does that make sense? *lol).

IMHO there would be no other way than comparing the target block generation speed (time) vs actual block generation speed since e.g. last retarget or last [i]n[/i] blocks etc. The closer you get to the next retarget, the more accurate your approximation - at least for next difficulty.

Personally I would go with api calls. Beeing a php/py guy I did like the jsonRPCClient class and the json-rpc lib. Both are really super easy to use/integrate and there are several available for other languages too.

I’ve tried both before I moved to my own little curl/curlmulti based class. But that was just personal preference b/c I was used to grabbing data from lots of urls in parallel for forum signature generators, google kwt data etc. and I’m grabbing data from different qt clients as well.

Yes wrapper go ahead and close it. Cheers :)

Minor aberration: couldn’t have said it better myself.

This problem has been investigated by admin. The Daemon has been restarted and is being monitored closely.

Hi Richard, can I assume the new client sorted out the glitch? and mark this Solved.

If not let me know.

[url=http://www.coindesk.com/hrmc-decides-rethink-tax-stance-bitcoin/]http://www.coindesk.com/hrmc-decides-rethink-tax-stance-bitcoin/[/url]

Interesting article.

Can I assume this is solved? as the thread is dead?

Thanks for your help that’s worked. :)

Nice work…

[quote name=“bobtaco” post=“48106” timestamp=“1388265263”]
On last quick question regarding wallets.

If my wallet has been encrypted, do I have any reason to fear writing down the dumpprivkey information, or putting back up copies of my wallet.dat file on a service such as DropBox?

Obviously nothing is 100%, but shouldn’t the encryption make it extremely difficult for any malicious activity?

Thanks again all!
[/quote]

I believe dumpprivkey requires you to decrypt your wallet first, and it outputs it unencrypted.

But I may be wrong. It should be obvious when you test your restore procedures with your key (WHICH YOU SHOULD DO ANYWAY). If it asks for your password when you import it, then it’s not encrypted.

Also there is this page too: [url=http://preshing.com/20110811/xkcd-password-generator/]http://preshing.com/20110811/xkcd-password-generator/[/url]

I do use them for non tech people when I help them set accounts up and stuff because I know two things:

[list type=decimal]
[*]It will be memorable for them and they won’t default to something like “Manchester United”!
[*]It will be way better than anything they could come up with given a set of rules
[/list]

Feathercoind is the command line wallet. You can find it in the same package and the QT client, usually.

I use it instead of the QT client on VPS servers because they don’t have a GUI, just SSH. But on my local windows box, the QT clients works just as well. YMMV.