Author

Topic: Gridcoin (GRC) - first coin utilizing BOINC - Official Thread - page 214. (Read 597505 times)

hero member
Activity: 1666
Merit: 565
is it normal that i pay this 3 beacon in cpumining?






I get this as well (3 beacons same amount).  I assumed it was 3 CPUs running?
It's sending one beacon per project; we can't change it, it's required to prove the cpuminer is participating per project.

Thanks,
Grid


thx!
full member
Activity: 144
Merit: 100
Hi everyone!

Thanks to everyone who helped me get setup with gpu mining..everything is running smoothly so far.
I'm now running 2x r9 280x and waiting for risers so I can install a third one...I've never been mining before so I'm quite surprised how much heat and noise these things make. Good thing it's winter Smiley

It's sending one beacon per project; we can't change it, it's required to prove the cpuminer is participating per project.

Thanks,
Grid

Hi Rob!
Regarding CPU Mining, I have several machines running and each one mines fine without a problem.
It takes time for the payouts to start, but I guess it is normal because the machine first needs to generate some BOINC credits.

The multiple beacon thing:
I have encountered it on several on my machines, they are all running only one project(so the beacons were sent to one address) and the maximum was 5 beacons sent in a row..separated by 26 minutes.
Also in Projects Console I have seen several times a "-3" error, which is the problem connecting to Berkley API.
So my guess would be that if there is -3 error when the client tries to send the beacon it fails and tries again in 26 minutes intervals until it succeeds.

Hope this helps.

Seems like things are really picking up and we're very close to start hitting exchanges! Looking forward to that! Smiley
Regards,
Andrew.
sr. member
Activity: 364
Merit: 252
i am trying to be an early adopter.  i have a few questions. first of all, i am mining 2 gpus solo with a 12 thread processor.  my average daily credits is 2700 and i have 11 threads devoted to boinc.  my boinc processing power won't go above 65 points.  this has been 100 fairly consistently until i decided to take a few days off with my rig.  i have not had syncing issues so long as i kept up with all the updates and addnodes.  my questions are these:

1. what can cause this to stay at only 65?

2. can someone please explain the scrypt sleep?  does this mean when my sleep is on that my hashing is doing nothing? 

3. does closing the mining console have to hide command prompts? i have other things running in command prompt sometimes and these get hidden as well.  it would be helpful if the mining console only hid process that it started. 

thanks, and good work so far. 


Scrypt sleep allows our network as a whole to be more efficient.  Sleep causes your GPUs to sleep when your leaderboard sleep level is below the network sleep level.

Team, answer the rest.
sr. member
Activity: 364
Merit: 252
is it normal that i pay this 3 beacon in cpumining?






I get this as well (3 beacons same amount).  I assumed it was 3 CPUs running?
It's sending one beacon per project; we can't change it, it's required to prove the cpuminer is participating per project.

Thanks,
Grid
sr. member
Activity: 364
Merit: 252
I think what fxmulder is saying is that the client does not compile, if I am understanding him correctly?

grid says the linux client works find but you just can't mine with linux is. (You will be able to within a week)

Yeah, i thought there was a linux client already released, turns out its just the source code atm.

traderman this is correct

hamiltino I always build from source, going down the rabbit hole it seems there's some core dependencies on qt components, not sure why they exist but they prevent compilation
Is this for an exchange?  We have a coin-only client for Linux that builds; it just wont mine.  It runs natively.
The one Im talking about for this weekend is a mining version that works on Linux & Mac and requires wine to run.

Rob H.


This was the post I meant to quote, I need to be able to build the wallet on 64 bit ubuntu without gui/qt support



Hi FxMulder,

I'm coming off the road from a trip and almost back at the office.  I do have the GitHub modified Linux code to make the headless native daemon for Grid and it builds, but Im going to need some time to sync it to the repo.  I'll do it asap and keep you informed when it is in.  Latest should be Sat afternoon if not sooner.

Thanks,
Grid
newbie
Activity: 52
Merit: 0
New Version Available:
7.7.7/70/1.1.5.7: Upgrade from RPC: Yes

* In this version we correct the cpumining next payment amount and outstanding amount owed and resolve most of the bloated wallet issue.

Please upgrade ASAP as this version will only work correctly after 51% upgrade.

Maybe, resolving bloated wallets doesn't cope with every wallet in the same way..
Still looking for possible reasons.
Rob, may I ask you to comment on this, please?

i have ver. 1.1.5.5 GRC client, i was mining the whole day and found a block then when i woke up my miner say " not responding" and found out the client close by it self so i re open the client and its not synchronizing properly so what i did is uninstall the client, delete the gridcoin folder, delete the blocks and chainstate folder as well as the peers.dat files and reistall the grc client but still unlucky to synchronize it, so i have no choice but to restart my computer and when i re-run the client again it says "Warning Displayed transaction may not be correct! you may need to upgrade or node need to be upgrade" i don't know what to do now? any solution? Thanks Huh  
How did it work out for you, airtreb? Could you recover?

The recent upgrades required an additional security check for cpumined blocks and could have broken older versions; after upgrading to 7.7 did you all recover? 
All 5 of my machines recovered and went through that block.

Grid



couldn't recover, sadly. but thank you for the explanation.
I started with new wallets on each machine and will try to recover one by one.
hero member
Activity: 1666
Merit: 565
is it normal that i pay this 3 beacon in cpumining?






I get this as well (3 beacons same amount).  I assumed it was 3 CPUs running?

1 cpu, 4 core.
full member
Activity: 217
Merit: 100
New Version Available:
7.7.7/70/1.1.5.7: Upgrade from RPC: Yes

* In this version we correct the cpumining next payment amount and outstanding amount owed and resolve most of the bloated wallet issue.

Please upgrade ASAP as this version will only work correctly after 51% upgrade.

Maybe, resolving bloated wallets doesn't cope with every wallet in the same way..
Still looking for possible reasons.
Rob, may I ask you to comment on this, please?

i have ver. 1.1.5.5 GRC client, i was mining the whole day and found a block then when i woke up my miner say " not responding" and found out the client close by it self so i re open the client and its not synchronizing properly so what i did is uninstall the client, delete the gridcoin folder, delete the blocks and chainstate folder as well as the peers.dat files and reistall the grc client but still unlucky to synchronize it, so i have no choice but to restart my computer and when i re-run the client again it says "Warning Displayed transaction may not be correct! you may need to upgrade or node need to be upgrade" i don't know what to do now? any solution? Thanks Huh  
How did it work out for you, airtreb? Could you recover?

its my fault i never thought that there is latest version 1.1.5.7, i just downloaded it in the gridcoin home page and its seems to be fine now ")
hero member
Activity: 644
Merit: 500
P2P The Planet!
go into Boinc manager > tools > computing preferences > change the cpu time and thread % to 100%  (both those settings are at the bottom)

Give that a shot.
newbie
Activity: 25
Merit: 0
i am trying to be an early adopter.  i have a few questions. first of all, i am mining 2 gpus solo with a 12 thread processor.  my average daily credits is 2700 and i have 11 threads devoted to boinc.  my boinc processing power won't go above 65 points.  this has been 100 fairly consistently until i decided to take a few days off with my rig.  i have not had syncing issues so long as i kept up with all the updates and addnodes.  my questions are these:

1. what can cause this to stay at only 65?

2. can someone please explain the scrypt sleep?  does this mean when my sleep is on that my hashing is doing nothing? 

3. does closing the mining console have to hide command prompts? i have other things running in command prompt sometimes and these get hidden as well.  it would be helpful if the mining console only hid process that it started. 

thanks, and good work so far. 

full member
Activity: 124
Merit: 100
Difficulty:    6.963243
Blocks:    51984
NetworkHashPs:    122471752.00000
Updated:    1/21/2014 3:49:54 PM

that is a new record!

GRC is now trading in China at QQ group: 258951963. Please add.
Price now is 0.08 USD per GRC.

中国GRC qq交易群:258951963
full member
Activity: 124
Merit: 100
Difficulty:    6.963243
Blocks:    51984
NetworkHashPs:    122471752.00000
Updated:    1/21/2014 3:49:54 PM

that is a new record!

GRC is now trading in China at QQ group: 258951963. Please add.
Price now is 0.08 USD per GRC.

中国GRC qq交易群:258951963
full member
Activity: 150
Merit: 100
is it normal that i pay this 3 beacon in cpumining?






I get this as well (3 beacons same amount).  I assumed it was 3 CPUs running?
hero member
Activity: 1666
Merit: 565
is it normal that i pay this 3 beacon in cpumining?




newbie
Activity: 13
Merit: 0
Thx, fixed the problem

if you have a wallet backup it's easy to get them back again.
Just delete the current wallet with the lost coins, and put the intact backup in place.
Then run gridcoin and it will rescan the wallet and adjust for all transactions that did and did not complete.
I've been having a bunch of transactions not complete and get them back this way.

Also, I had some that remained uncompleted for the better part of a day suddenly go through. I believe it had something to do with the timing of finding a new block. They sent right around then. So it might have taken them that long to notice they had a node to travel to and confirm on.

edit: typo fix. them/then


I transferred the last days some coins to my back-up wallet cos my wallet size is exploding (6Mb), all transactions succeeded, except the last one from yesterday.

Money is not in my wallet anymore and in the transactions historie I can see following,

19-1-2014 12:00 To FyxhBbEjhfWQznDHjrJWpCgcz8WuiXuq8E, debit -500, transaction fee -1,74, transaction ID 7b55bba6ad2c75a4c1211c7fc33ad891012579effe421093dfdd2d9152561d6b

However Status 0/unconfirmed.

After that transaction I got three mined received transactions, they are all confirmed en show up in my balance.

Upgraded just to 1.1.5.7-g71-prod/70

What can be wrong, are these coins lost??

hero member
Activity: 1666
Merit: 565
Reinstall wallet and delete the blocks and sql folders in appdata, then resync from start. I had same issue, that is a way to fix it.

my wallet doesn't sync anymore!!!

gridcoin-qt client says (i try to traslate from italy): the transaction showed might be wrong. You may need to update or or node need to be upgrade

But i have the lastest version (7.77) and this is my .conf

pcuser=RPCUser
rpcpassword=RPCPassword
rpcallowip=127.0.0.1
rpcport=####
server=1
poolmining=false
restartwallet=0
addnode=98.114.181.178
addnode=76.187.184.27
addnode=66.187.94.194
addnode=76.74.177.224
addnode=84.125.196.167
addnode=71.233.139.62
addnode=72.92.48.105
addnode=72.208.65.226
addnode=77.64.220.124
addnode=50.152.78.46
addnode=207.229.136.136

Any help?

thx! i did it just 2 min ago Smiley
legendary
Activity: 1260
Merit: 1001
Reinstall wallet and delete the blocks and sql folders in appdata, then resync from start. I had same issue, that is a way to fix it.

my wallet doesn't sync anymore!!!

gridcoin-qt client says (i try to traslate from italy): the transaction showed might be wrong. You may need to update or or node need to be upgrade

But i have the lastest version (7.77) and this is my .conf

pcuser=RPCUser
rpcpassword=RPCPassword
rpcallowip=127.0.0.1
rpcport=####
server=1
poolmining=false
restartwallet=0
addnode=98.114.181.178
addnode=76.187.184.27
addnode=66.187.94.194
addnode=76.74.177.224
addnode=84.125.196.167
addnode=71.233.139.62
addnode=72.92.48.105
addnode=72.208.65.226
addnode=77.64.220.124
addnode=50.152.78.46
addnode=207.229.136.136

Any help?
hero member
Activity: 1666
Merit: 565
my wallet doesn't sync anymore!!!

gridcoin-qt client says (i try to traslate from italy): the transaction showed might be wrong. You may need to update or or node need to be upgrade

But i have the lastest version (7.77) and this is my .conf

pcuser=RPCUser
rpcpassword=RPCPassword
rpcallowip=127.0.0.1
rpcport=####
server=1
poolmining=false
restartwallet=0
addnode=98.114.181.178
addnode=76.187.184.27
addnode=66.187.94.194
addnode=76.74.177.224
addnode=84.125.196.167
addnode=71.233.139.62
addnode=72.92.48.105
addnode=72.208.65.226
addnode=77.64.220.124
addnode=50.152.78.46
addnode=207.229.136.136

Any help?


edit: problem solved!
full member
Activity: 124
Merit: 100
good news. we start trading internally as well in china. The price is similar to here. around 0.5 RMB (ca. 0.08 USD)/ 1 GRC.
sr. member
Activity: 325
Merit: 250
I think what fxmulder is saying is that the client does not compile, if I am understanding him correctly?

grid says the linux client works find but you just can't mine with linux is. (You will be able to within a week)

Yeah, i thought there was a linux client already released, turns out its just the source code atm.

traderman this is correct

hamiltino I always build from source, going down the rabbit hole it seems there's some core dependencies on qt components, not sure why they exist but they prevent compilation
Is this for an exchange?  We have a coin-only client for Linux that builds; it just wont mine.  It runs natively.
The one Im talking about for this weekend is a mining version that works on Linux & Mac and requires wine to run.

Rob H.


This was the post I meant to quote, I need to be able to build the wallet on 64 bit ubuntu without gui/qt support
Jump to: