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

You receive 1.5 * the boinc processing power # on the mining console.

Thanks!

Grid

Anyone having trouble with the boinc processing power number:


50% weight goes to the"Boinc Avg Daily Credits":  if you are lower than 1000,that is the culprit and is dragging down your total.  To get to 100, you need to increase those.

Other technical solutions:

-Ensure you are running gridcoin as admin
-for a very rare issue when performance counters are corrupted:
lodctr /r
from the command prompt
-Try adding projects such as milkyway, world community grid, rosetta

The system is working for 100 users, so rest assured the problem can be solved.

Thanks,
Grid

uhm, so i'm not the only one with this problem. How many coins do you get for one block?

Sorry ment Boinc in the Gridcoin client.

and gridcoin what does it say?

My taskmanager says I'm using 100% CPU, but Boinc says 53.
Is this correct?

Regards,
Guido

@TribalBob: thx man for the suggestion, but nothing change



so do you have my problem too?? and if i find a block, i'll get 150 coins or not?

Hi Rob,

Chrome still marks the download as malicious because of the packaged miners, any miners will likely cause the download to be flagged...

I will test with the packaged cgminer today when I get the chance and will let you know how it goes!

Wow, quite a few improvements there! That's the sort of development I like to see for altcoins.

New version available at http://www.gridcoin.us/download/gridcoin.msi
Release notes (1.1.4.9/6.4/49):

1. This version will need to be installed from the MSI; you will need to delete your program files (x86)\gridcoin directory before installing
   otherwise the installation will succeed and fail later.
2. We will be expanding the installer; however this release includes cgminer3.4 in cgminer.zip,
   a new query analyzer, and a new SQL server database.
3. An optional feature has been added for users who do not want any command line interfaces closed by gridcoin:
   Add the following key to your gridcoin.conf file: closeconhost=false
3b. More optional features: Set key closeguiminer=false to prevent guiminer from being closed (or closecgminer=false or closreaper=false).
    Note: Only add keys in step 3 or step 3b if your system requires it. 
4. We have removed the cgminer files since they show as a virus, now we zip up cgminer 3.4 - the master version is installed in the AppDir.
4b. OPTIONAL: If you would like to replace Gridcoin's cgminer version with your own version
   (Please see Con Colivas's downloads at :
       http://ck.kolivas.org/apps/cgminer/
   )
   download the appropriate version and test it thoroughly (verify it supports scrypt also),
   then zip your version of cgminer
   as "cgminer.zip" and place it in your DataDir, and gridcoin will prefer that version when creating new instances in Mining | Configuration | GPU Miner Settings.
   Note: You should only include the EXE, kernel files (.cl files) and DLLs as we do in example file "cgminer.zip" (located in your gridcoin appdir).

5.  We Added scantime=7 to the cgminer create instance function,
   for quicker detection of new blocks when using cgminer.
6.  When adding a cgminer instance, gridcoin will unzip the cgminer.zip into the "cgminerX"
   instance directory and create the cgmX file.
7.  For our upcoming features related to 3rd party API checks, transaction confirms, CPU-only mining for boinc users,
   and scrypt_sleep, We decided to use SqlLite instead of MySql,
   due to packaging size considerations (MySQL is a 300 meg download
   and it requires the MySQL connector for each OS; we didnt want to add 306megs to the
   core program, and replicate that size to our future userbase of 25,000 machines . 

   So far, SQL Lite has been solid; we tested the standard insert update delete and order by;
    devs- please test an inner join.
8.  Added the Gridcoin sql query analyzer (it's still in its infancy). 
   You may access it by clicking "SQL Query Analyzer" from the main page.
8a.  So far, we have only added a few test tables: System, Blocks, and Peers. To keep from using system resources
   we insert one gridcoin block into the database every 10 seconds.  The peers are loaded once every half an hour.
   To do a sample query from query analyzer:
   Select * from Blocks
   Etc.  Or other ansi-92 standard queries.
   Inserts/updates do work, but will not be stored in the database after you click close.
   Note: Gridcoin has a master lock on the database, so you only receive a snapshot of the
   database when inside query analyzer, (this is to protect from errors during inserts by gridcoin),
   you will have to close the query analyzer window and re-open it to see new blocks.
8b.  The Results pane contains a data grid of the data; eventually we will make it copy and paste into excel, etc.
8c.  Note: For speed, you can type a query and press F5 instead of execute
9.  TribalBob: Please let us know if 4.3 fixes the cgminer version problem that you experienced;
    and also let us know if this fixes the virus scanner test.

Good luck!

Rob Halford

It looks like we have a microdust flooding vulnerability, i can't see any fees hardcoded in gridcoin client.

Solution: https://github.com/bitcoin/bitcoin/pull/2577

With the new scheme I think it has to be showing around 50-60 under full load and the other half comes from the averages over time. That is my understanding of it.

We are discussing some security enhancements based on a post Sunny King made (it wasn't really a bash) it was more of an observation he made that if a client finds a way to lie about their utilization (in our case, the avg daily credits), they are potentially receiving a higher subsidy than deserved; and obviously we want a coin that is 100% solid without any possible loophole.

Here is my proposed solution to closing the security gap the rest of the way:
 
1) Let us assume that bitcoins proof of work actually proves that a node generated a lot of heat and secured the block chain.
2) Let us assume that our GPU PoW (scrypt) + boinc credits prove that a user completed boinc tasks and secured the block chain: more useful.
3) A GPU user will look back over the last 30 days of history in the blockchain and pick a random public wallet; and attempt to verify the credits through the official project API (for that project).  A    "-1"     means that nodes credits were lower than the purported credits.  A +1 means it did match (or the nodes credits were even Higher than purported).  Other numbers are failures and dont count.  All project APIs are compiled into the code.
4) Any gridcoin gpu node that solves a block will "vouch" for the verified node, and add that vouching result to the boinchash in the chain.
5) The scrypt sleep algo will look back 30 days, compiling a list of total "confirmations" or voucher points for each wallet, and multiply that vouching sum * the (factored) avg_daily_credits per project.  The results will be sorted descending, and each node on the list will have between a 100% chance of working the next block and 40% chance depending on their position.
6) Users who ever find a way to defraud the system will be much lower, since 3rd party verifications include negatives.
7) Users who have the most positive confirmations will have the most avg_credits in the total, therefore have a higher chance of working the next block.
All this will be automated and compiled into every client so there is no central authority.
9) Out of this, we gain 100% provable integrity, AND we will be the first efficient coin with SCRYPT_SLEEP implemented!
 
Thoughts?
 
Grid

Ok, gridcoin won't display hashrate info for external instances of cgminer, only if it's started from inside gridcoin.

As far as the utilization being wrong I'm not sure what is wrong there as it seems like you have things setup correctly. Double check your BOINC settings to make sure they are set to allow 100% usage, then while still in BOINC go to View> Advanced View> Advanced> Read local prefs file

After that go to "Activity" (still in BOINC) and select "Run based on preferences".

ok, i understand. I run gridcoin-qt.exe as admin, but boinc utilizzation 66% instead of 100%, and i don't see cgminer hashrate info.

I use an external instance of cgminer..

You don't need to run cgminer as admin but you do need to run gridcoin-qt.exe as admin.

All your BOINC info is displaying correctly then, yes...?

You are just missing cgminer hashrate info...? Are you running cgminer from inside the gridcoin client or are you starting an external instance of cgminer...?

do you mean gridcoin-qt.exe? no.., but now i try running it as admin but nothing change
same exactly values i had before

do i need to run as admin also cgminer?

Are you running Gridcoin as admin?

LOL, no worries m8! Just remember me when you get rich on GRC!!!   

thanks! a little step forward.

Now, cgminer works fine, but i have boinc utilizzation 66% when it would be 100% and, also, i see no hashrate on cgminer API in Grindcoin mining module.

I red the posts before, and i've already tried to write lodctr /r from an elevated prompt, and restart gridcoin-qt, but nothing changed.

I'm missing something...but what?

edit: my boinc thread counter is 4, and that's correct, and my boinc avg daily credits is 339...