GoldCoin Talk

Main Category => Technical Discussion => Topic started by: ipaint on June 07, 2013, 10:57:51 PM

Title: Encrypted Wallet wrong move
Post by: ipaint on June 07, 2013, 10:57:51 PM
I thought it would be a good idea to encrypt my wallet. Now that I did it I keep getting "GLDCoin Wallet (Not Responding)" If I close it and try to reopen it, it fails and I need to reboot to get it working again.
Title: Re: Encrypted Wallet wrong move
Post by: Sting17 on June 07, 2013, 11:03:22 PM
Thats odd, I havent had that issue before. You running the latest client?
Title: Re: Encrypted Wallet wrong move
Post by: ipaint on June 07, 2013, 11:38:28 PM
I just downloaded it a couple of days ago.

I did what gldcoin posted on a different forum a couple days ago. Updated everything and I encrypted the wallet lastnight, thats when I started getting the error.


All,

I had to go dark for a few days, to avoid the hard fork being leaked any more than it has, took down the repo temporarily etc.  I have instructed Cryptsy to install the update, so I am now making this public.

I have posted the links in the original thread, but made no mention of what it actually was until now.

The Binaries are here:

Windows: https://docs.google.com/file/d/0B5Jeb5kpOWshVVM1ZVFCV0RpSmM/edit?usp=sharing
Linux: https://docs.google.com/file/d/0B5Jeb5kpOWshekxOUnIzb2pXNkE/edit?usp=sharing
Source: https://github.com/gldcoin/gldcoin

INSTRUCTIONS:

1) Backup your wallet! File>Backup Wallet
2) Add this into your config file:

addnode=72.11.149.185
addnode=207.12.89.2
addnode=208.115.109.157
addnode=80.229.2.127
Title: Re: Encrypted Wallet wrong move
Post by: ipaint on June 09, 2013, 11:01:47 AM
I think I found the problem.

I was mining with my CPU's and I found when I mine the pool's coinminer.net:18321/static/ or next.afraid.org:8117/static/ my wallet will fail after a couple of hours or so. I get the error (Not Responding) so as a test, I tested the CPU mining on coinminer, next and VirCurPool and I found that I don't get the error when mining on VirCurPool.

No idea why it happens, maybe someone else can test mine with their CPU's on the three pool's to see if they get the same error.