|
Up for grabs is 1,000 Gridcoins. Please place bids here or via PM. Thanks!
|
|
|
|
Just an update, my 2 latest fresh installs have been running flawlessly for about 24 hours now  |
|
|
|
|
Selling 1,000 Gridcoins, post offers here or via pm.
|
|
|
|
I might still be off slightly, but if you use the listcpuminers you get to see other people in the internal pool. Usually there's just a few of them. From what I understand that's as close as we have to a third party pool so far  When you use poolmining=true you become part of the internal pool.
Oh wow, I totally misunderstood the use of "poolmining=" I thought that "poolmining=true" enabled other users to mine on your client using their own wallet addresses with a pooled payout similar to p2pool. Thanks for clearing that up for me! Sweet, when the difficulty gets a little higher I will have to check it out. |
|
|
|
When you use poolmining=true you become part of the internal pool.
Oh wow, I totally misunderstood the use of "poolmining=" I thought that "poolmining=true" enabled other users to mine on your client using their own wallet addresses with a pooled payout similar to p2pool. Thanks for clearing that up for me! |
|
|
|
What's the syntax for commenting out lines in the .conf file?
#This is a comment in the conf file |
|
|
|
|
Please post the following:
1) What program are you mining with?
2) What launch flags are you using (if any) when you launch your miner?
3) What does your config file look like for your mining program?
|
|
|
|
All mine have been working great the whole day thankfully. Is there a compiled list of working nodes? I can start one up if there isn't. As of 10:49 PM Bitcointalk time, I'm at block 28271 addnode=71.162.218.111 I am using: addnode=98.114.181.178
addnode=76.187.184.27:9778
addnode=66.187.94.194:9778
addnode=76.74.177.224:9778
addnode=84.125.196.167:9778
addnode=71.233.139.62:9778
addnode=72.92.48.105:9778 |
|
|
|
Nope. It's my only machine. I have a habit of giving my computers away when I upgrade. I'm stalled at block 28146. Anyone else?
The machine that is stalled, are you mining on that computer and also mining on it from another computer at the same time? Yeah, it seems my theory has been completely blown out of the water because my other machine just stalled out now for apparently no reason, lol |
|
|
|
Can any of you help me in understanding this?
I used to fold@home for cancer research until crypto-currencies came along, and I guess I saw an opportunity to make a bit of money for once. In a way I do feel a little guilty for giving up a good cause and i've always felt if the two could ever be combined it would be revolutionary. Does this coin offer that? If so, then surely is it not decentralised?
Hello, This coin rewards you based on the amount of processing you apply towards a program called BOINC. BOINC is a platform for volunteer grid computing which uses your spare processing cycles to advance scientific studies. It is very much like what you have been doing, except that when you use BOINC with Gridcoin you are eligible for increased GRC block rewards based on the amount of processing power being applied to the BOINC application. It is very much decentralized as no person/entity directly regulates/controls the funds flowing through the GRC network. |
|
|
|
I'm stalled at block 28146. Anyone else?
The machine that is stalled, are you mining on that computer and also mining on it from another computer at the same time? |
|
|
|
|
Alright, I believe I have tracked the source of the problem (at least for me anyway).
As mentioned earlier I am running two clients on two different machines.
Machine "A" is my desktop and has been running fine all night.
Machine "B" is my laptop and it is continuously having problems.
Machine "A" runs the client and also runs cgminer set to "-loadbalance" bewteen Machine "A" and Machine "B".
Machine "B" runs the client and Pooler's CPUMiner.
It seems that every time cgminer on Machine "B" finds a block on Machine "A", Machine "A" is credited with a full reward as if it had come through the loopback address (which it did not). The transaction then usually gains one or two confirmations and then the client stops updating which is when I am forced to re-launch the app (usually having to launch with "-rescan" or "-salvagewallet" to get things running.
Once I am up and have had some coffee I will start looking through the source and see if I can find the problem in the loopback address check.
|
|
|
|
|
Alright, the new wallet has stalled out too, but the problem seems to only be with the wallet on my laptop now. My other machine seems to be running fine, I'm just going to leave that one running for now and I'll mess with the client on my laptop later as it is late and I am getting tired...
|
|
|
|
|
My client running the wallet with the coins from the old blockchain has stalled out again. It seems that particular set of coins is somehow corrupted. I'm just going to go back to the fresh wallet. I'll hold onto the glitchy wallet for now in case a future update fixes the problem, but for now I'm just going to see how the fresh wallets go.
|
|
|
|
Заебала эта кристина уже в хлам! WDC не вводятся, битки исчезли, всё на хуй исчезло! Тех поддержка тупо морозится! Пидары ебучие  Funniest fucking thing I've ever read. I'm sure Google translator didn't translate it correctly, but I think I got the idea. |
|
|
|
|
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...
|
|
|
|
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",
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. |
|
|
|
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. Correct, that is the version I am using. Version 30 in the mining console, Gridcoin 5.4 in Programs list. |
|
|
|
|
Show Posts
