Yea all mine have been good after getting them all caught up to the correct block (deleting the chain and blocks and resyncing). Hopefully in the morning they'll still be on track  |
|
|
|
|
If this actually starts some legal action against Cryptsy, good luck at ever seeing your coins again. Instead of having one issue to deal with, they'll have two, the second of which takes precedence over getting your coins back.
|
|
|
|
do -salvagewallet command Ok, I have one client fully updated and running fine, but when I try to re-install the other from the latest MSI using my old wallet.dat I am receiving: System Error: CDB() : Can't open database file wallet.dat, error -30974 That seems to have done the trick, thanks m8! Forgot about the "-salvagewallet" flag (never had to use it). So, now both clients are running, both clients are the latest version (version 30) both say they are synced, but they are on completely different blockchains. One block chain is currently 27,865 blocks long with a difficulty of 1.17921727 and the other is on a blockchain that is 27,881 blocks long with a difficulty of 1.44197764. I was about to post the same thing. I have one chain at 27,865 and two at 27,881 and neither have them have moved since updating. Is the chain playing catchup or something before it starts moving again? |
|
|
|
Oh, and for you guys on Cryptocoin talk, vote on which abbreviation you think we should use/keep while we aren't on an exchange yet XGR or GRC |
|
|
|
|
Yea that makes sense then as changing the security settings technically gave it admin rights to changes when ran.
|
|
|
|
|
First time using upgrade, but it says "Upgrade Failed. An exception occurred during a WebClient request."
Nevermind, I fixed it by changing the security settings on the \Program Files(x86)\Gridcoin folder
|
|
|
|
|
Yea I had it happen to all my machines the night before last (so I had to rescan yesterday morning) and it they're all good still except for one, which stalled 2 hours ago. So it's not happening as bad, but there are still instances it occurs.
|
|
|
|
|
Coins sent everyone, enjoy!
|
|
|
|
|
If anyone is having trouble with syncing or stalling after the latest update do this:
1. Close your Gridcoin client
2. Delete everything in your AppData\Roaming\Gridcoin folder EXCEPT the gridcoin.conf, wallet.dat, and if you use it, the guiminer folder
3. Make sure you have the latest client (if you open the Mining Console, you should see Version: 29, if not install the latest .MSI from the website
4. Start the client and it should completely resync
|
|
|
|
I just got a new crash. (There's a regular crash I get that doesn't give any useful errors, but this one seems to have some info of note)
Assertion Failed!
Program: C:\Program Files (x86)\Gridcoin\gridcoin-qt.exe
File: src/wallet.cpp
Line: 1847
Expression: vchPubKey.IsValid()
And the non-informative error usually just says "OSS GUI client for Gridcoin has stopped working".
You can also try doing this. Backup your wallet.dat, delete everything in your AppData\Roaming\Gridcoin folder, launch Gridcoin and let it sync completely with a new wallet. Then close out of it, replace the new wallet.dat with your old one, and relaunch and see if that helps. I got a few errors over the several updates where it said it couldn't open my wallet.dat, and just playing around with syncing, replacing the wallet, etc. it eventually booted up. I had a hell of a time yesterday since my two machines running Gridcoin both got them, spent like 45 min fixing it lol. |
|
|
|
Coins are sent! Glad to hear all the good words you guys are putting in for Gridcoin |
|
|
|
For those mining with an nvidia card, I'm doing about 106 kilo hashes, plus CPU and I've done 9.5 GRC in the last seven hours.
Does that match up to your stats?
I think I'm fully functional now except for my graphing.
I'm assuming that you're doing pool mining? If so, and you just started mining seven hours ago, the pooled mining works like PPLNS where it starts small, increments to your actual proportional share, then tapers off back to 0 after you stop mining. So that should increase throughout the next 24 hours to your proper average, and after you stop mining, it'll continue to pay you for about another 24 hours after you stop, slowly going to 0 each pool pay. |
|
|
|
|
I've Registered an account on Nextcoin.org using aysyr
|
|
|
|
|
Glad to see so much support! Coins sent!
|
|
|
|
|
I tried following the directions for retrieving my coins from page 33 of the original thread, but I got this error:
Already assigned to 6c81747257decbd565fb3b80bab1ab35521e04e1772bdc84238431fba122c0ea
The hash that it says it's assigned to above is the hash of my Sha256(Sha256(secret phrase)) that was used when sending the Bitcoin contribution. How do I retrieve my coins?
|
|
|
|
|
Show Posts
