Topic: Gridcoin (GRC) - first coin utilizing BOINC - Official Thread - page 269. (Read 597476 times)
December 08, 2013, 02:56:28 AM
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
December 08, 2013, 02:24:12 AM
Ok, I appear to be properly synced for the moment. That may have done the trick. I hope it does because I'd really like to be able to keep my coins, lol...
December 08, 2013, 02:15:57 AM
Just a note, the fresh install of a brand new wallet just stalled out again on my laptop. I re-launched with re-scan and it's back on track, hopefully it sticks.
Try to delete the peers.dat, blockchain and add this node to gridcoin.conf
addnode=98.114.181.178
You can also add working peers:
"addr" : "76.187.184.27:9778",
"addr" : "66.187.94.194:9778",
"addr" : "76.74.177.224:9778",
"addr" : "84.125.196.167:9778",
"addr" : "71.233.139.62:9778",
"addr" : "72.92.48.105:9778",
"addr" : "76.187.184.27:9778",
"addr" : "66.187.94.194:9778",
"addr" : "76.74.177.224:9778",
"addr" : "84.125.196.167:9778",
"addr" : "71.233.139.62:9778",
"addr" : "72.92.48.105:9778",
Alright, I have deleted everything except for my wallet and conf files and have added these nodes, I launched with my old wallet, I will let you know how it turns out.
December 08, 2013, 02:08:26 AM
You can also add working peers:
"addr" : "76.187.184.27:9778",
"addr" : "66.187.94.194:9778",
"addr" : "76.74.177.224:9778",
"addr" : "84.125.196.167:9778",
"addr" : "71.233.139.62:9778",
"addr" : "72.92.48.105:9778",
"addr" : "76.187.184.27:9778",
"addr" : "66.187.94.194:9778",
"addr" : "76.74.177.224:9778",
"addr" : "84.125.196.167:9778",
"addr" : "71.233.139.62:9778",
"addr" : "72.92.48.105:9778",
December 08, 2013, 02:06:54 AM
I deleted everything, except wallet.dat and gridcoin.conf in the appdata, everything is ok.
Are you running v1.1.3.9-g71-prod ? I was already using this version in wrong chain.
Are you running v1.1.3.9-g71-prod ? I was already using this version in wrong chain.
Correct, that is the version I am using. Version 30 in the mining console, Gridcoin 5.4 in Programs list.
December 08, 2013, 02:03:33 AM
Just a note, the fresh install of a brand new wallet just stalled out again on my laptop. I re-launched with re-scan and it's back on track, hopefully it sticks.
Try to delete the peers.dat, blockchain and add this node to gridcoin.conf
addnode=98.114.181.178
December 08, 2013, 02:00:23 AM
I deleted everything, except wallet.dat and gridcoin.conf in the appdata, everything is ok.
Are you running v1.1.3.9-g71-prod ? I was already using this version in wrong chain.
Are you running v1.1.3.9-g71-prod ? I was already using this version in wrong chain.
December 08, 2013, 01:57:12 AM
Just a note, the fresh install of a brand new wallet just stalled out again on my laptop. I re-launched with re-scan and it's back on track, hopefully it sticks.
December 08, 2013, 01:49:17 AM
Alright, my wallet with all of my coins in it has now stalled out...
The other wallet which has not been tainted with coins from any of the old chains seems to be running fine so I guess I will just wipe the corrupted wallet with my earnings from the past few days and start anew back at a completely zero balance, lol...
Oh well, for SCIENCE!
The other wallet which has not been tainted with coins from any of the old chains seems to be running fine so I guess I will just wipe the corrupted wallet with my earnings from the past few days and start anew back at a completely zero balance, lol...
Oh well, for SCIENCE!
I also have a wallet in old chain, have not tried to fix it yet
I wish you luck!
December 08, 2013, 01:40:47 AM
Alright, my wallet with all of my coins in it has now stalled out...
The other wallet which has not been tainted with coins from any of the old chains seems to be running fine so I guess I will just wipe the corrupted wallet with my earnings from the past few days and start anew back at a completely zero balance, lol...
Oh well, for SCIENCE!
The other wallet which has not been tainted with coins from any of the old chains seems to be running fine so I guess I will just wipe the corrupted wallet with my earnings from the past few days and start anew back at a completely zero balance, lol...
Oh well, for SCIENCE!
I also have a wallet in old chain, have not tried to fix it yet
December 08, 2013, 01:15:28 AM
Alright, my wallet with all of my coins in it has now stalled out...
The other wallet which has not been tainted with coins from any of the old chains seems to be running fine so I guess I will just wipe the corrupted wallet with my earnings from the past few days and start anew back at a completely zero balance, lol...
Oh well, for SCIENCE!
The other wallet which has not been tainted with coins from any of the old chains seems to be running fine so I guess I will just wipe the corrupted wallet with my earnings from the past few days and start anew back at a completely zero balance, lol...
Oh well, for SCIENCE!
December 08, 2013, 12:27:48 AM
Ok,
So I just renamed both of my data directories for both of my clients to "Gridcoin OLD". I re-launched the application and let it build new directories on both machines.
Both wallets started up and synced to the same block chain.
I re-started Gridcoin and used "-datadir=Gridcoin OLD" to get back into my old wallets and sent the coins from those wallets to my new primary address.
I have received the coins from both wallets and both machines are currently on the same blockchain. Now just need to see if my machines stay on the same blockchain this time, lol...
So I just renamed both of my data directories for both of my clients to "Gridcoin OLD". I re-launched the application and let it build new directories on both machines.
Both wallets started up and synced to the same block chain.
I re-started Gridcoin and used "-datadir=Gridcoin OLD" to get back into my old wallets and sent the coins from those wallets to my new primary address.
I have received the coins from both wallets and both machines are currently on the same blockchain. Now just need to see if my machines stay on the same blockchain this time, lol...
December 07, 2013, 11:50:19 PM
I feel better about this upgrade; I think we have to wait for the supermajority rule to kick in. Now that we are almost over 51% upgraded, Im pretty sure its about to kick in, because my bad node is now counting backwards and blocks are being taken off the chain; that didnt happen yesterday..... I think the wallet corruption was due to constant closing while the client had a lock on the file.
Rob H.
Rob H.
December 07, 2013, 11:21:05 PM
In main.cpp I see where nBestChain is set, but I don't see any definition really as to HOW nBestChain is set. I looked through main.cpp, alert.h, alert.cpp, protocol.cpp and protocol.h, didn't see anything in those places, maybe there was some where I missed...?
Is there anywhere in the code that tells it to look for the longest blockchain (blockchain with the most confirmations for all included transactions) or how exactly does the client determine how nBestChain is defined...?
It has not been changed from litecoin's code.Is there anywhere in the code that tells it to look for the longest blockchain (blockchain with the most confirmations for all included transactions) or how exactly does the client determine how nBestChain is defined...?
The longest chain ends up being chosen.
Main.cpp 1887 (Disconnect shorter branch)
Ah ok, I see it now. Thanks!
December 07, 2013, 11:05:10 PM
In main.cpp I see where nBestChain is set, but I don't see any definition really as to HOW nBestChain is set. I looked through main.cpp, alert.h, alert.cpp, protocol.cpp and protocol.h, didn't see anything in those places, maybe there was some where I missed...?
Is there anywhere in the code that tells it to look for the longest blockchain (blockchain with the most confirmations for all included transactions) or how exactly does the client determine how nBestChain is defined...?
It has not been changed from litecoin's code.Is there anywhere in the code that tells it to look for the longest blockchain (blockchain with the most confirmations for all included transactions) or how exactly does the client determine how nBestChain is defined...?
The longest chain ends up being chosen.
Main.cpp 1887 (Disconnect shorter branch)
December 07, 2013, 10:24:29 PM
In main.cpp I see where nBestChain is set, but I don't see any definition really as to HOW nBestChain is set. I looked through main.cpp, alert.h, alert.cpp, protocol.cpp and protocol.h, didn't see anything in those places, maybe there was some where I missed...?
Is there anywhere in the code that tells it to look for the longest blockchain (blockchain with the most confirmations for all included transactions) or how exactly does the client determine how nBestChain is defined...?
Is there anywhere in the code that tells it to look for the longest blockchain (blockchain with the most confirmations for all included transactions) or how exactly does the client determine how nBestChain is defined...?
December 07, 2013, 09:46:12 PM
Question for the dev:
Could the fact that I have multiple projects running in BOINC that aren't in the project list be somehow placing me on a separate blockchain...?
I have been using BOINC for a while now and I am signed up to almost every project...
Could the fact that I have multiple projects running in BOINC that aren't in the project list be somehow placing me on a separate blockchain...?
I have been using BOINC for a while now and I am signed up to almost every project...
December 07, 2013, 09:42:30 PM
The stall right now is because the new client requires people to be upgraded to the latest version so anyone who has not yet seen this thread is pretty much still mining on an out of date blockchain, there are probably only a handful of us at the moment who are on the latest version and the difficulty is still set from the old chain so the chain thinks there is a whole network f miners when there is actually only a handful of us.
It will start moving again either when we reach the next re-target or when the other miners catch up with their upgrades.
It will start moving again either when we reach the next re-target or when the other miners catch up with their upgrades.
December 07, 2013, 09:36:28 PM
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:
Code:
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?
December 07, 2013, 09:29:11 PM
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:
Code:
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.
Jump to: