 Show Posts
|
|
Pages: « 1 2 3 4 [5] 6 »
|
|
Are/have you been running MCM exclusively? And have you seen a slow down in the validation of work units? MCM require what is referred to as a wingman to validate the work units. Leading up to challenges, you will see numerous people deploying a tactic called bunkering where they load up their machines with a ton of work and then sit on the finished results waiting for the event to start so that they can dump all of the extra results during the challenge time frame. So, it is very possible a lot of your work was getting validated at a later time. Another possibility is that the points for work shifts slightly over time as part of the credit system used. You will find that for one person one type of work unit may pay better than for another person. The next day another work unit type may pay slightly better. In the end they kind of evens out.
|
|
|
|
|
I tend to come across the old thread when doing searches more often than this thread. That is probably why it has so many hits as well. Just a thought.
|
|
|
|
I agree with SVK Noko. It's obvious that the "wait time" needs to be improved. And yes of course the goal should be to have instant/immediate sync and payment if possible. Users/investors LOVE technology that is responsive and easy to use. Users/investors HATE technology that is difficult to use and requires a lot of patience to accomplish the goal.
Most of us aren't devs/programmers, so we can't provide specific instructions on how to fix it. However our job as users/investors is to give honest feedback so developers can develop the solutions.
What we need to work out is options. Currently we're tied to a few things syncing (CPID if using multiple projects, Nightly Superblock, and stake balance/PODC update). I believe WCG updates the web stats once a day? This is another limiting factor... unless someone can find a way to pull real-time stats. Thanks. I don't know which web stats would need to be updated or if WCG can provide the real-time info needed. Here's some info on their API that might help to find out what exact data they provide: https://www.worldcommunitygrid.org/help/viewTopic.do?shortName=apiWorld Community Grid statistics are updated twice a day. This occurs at 00:00 and 12:00 UTC. This includes all statistics on World Community Grid except for Team Statistics. For BOINC, statistics data is exported 4 times a day at 6 hour intervals. See https://secure.worldcommunitygrid.org/forums/wcg/printpost_post,377053 and stored at the address http://www.worldcommunitygrid.org/boinc/stats/The crontab entry for the export stats update: 16 0,12,18 * * * /usr/local/boinc/scripts/gen_stats.sh 16 6 * * 1,2,4,6 /usr/local/boinc/scripts/gen_stats.sh This means that the stats are updated every 6 hours EXCEPT on Wednesday and Sunday at 6:16 UTC. It is skipped at that time because that is when our database backup is run. Thus this morning, the job was skipped. I just verified and the 12:16 run of the stats was completed and the stats were updated 1 hour ago (completed at 12:32 UTC) Team Statistics are updated once a day at 00:00 UTC. The multiple updates a day will continue as long as the statistics update does not significantly interfere with members use of the site or overall system performance. Added: BOINC export frequency. - May 6, 2009 Added: Export crontab schedule info. - May 9, 2012 Added: Export store address statistics data - May 14, 2012 |
|
|
|
Just talking out loud, Does the "exec totalrac" command work if a cruncher hasnt linked/associated their BOINC account yet? I ran it on my wallet that isn't associated: exec totalrac
{
"Command": "totalrac",
"Total RAC": 0,
"UTXO Target": 10,
"StakeBalance": 767944,
"Threshhold to receive 10% rewards (below this UTXO Amount rewards are lost)": 10,
"Stake Level Required For 10% Level": 10,
"Stake Level Required For 20% Level": 10,
"Stake Level Required For 30% Level": 10,
"Stake Level Required For 40% Level": 10,
"Stake Level Required For 50% Level": 10,
"Stake Level Required For 60% Level": 10,
"Stake Level Required For 70% Level": 10,
"Stake Level Required For 80% Level": 10,
"Stake Level Required For 90% Level": 10,
"Stake Level Required For 100% Level": 10,
"Total Team RAC": 7914764
}
But in order to link a BOINC account to a BiblePay Wallet you need BiblePay coins? So they would have to buy a small amount to link/associate BOINC first, and then run exec totalrac and then figure out how much more they need to buy for staking and then buy more? Hmmm, so ideally then, we do want them to join Team BiblePay and get the Faucet reward, so they can start with funds for the BOINC Association, So they can run exec totalrac? The CPID Burn is about 1.001 BBP? Is there a way we can have a faucet that gives new users 2 BBP? I assume most all of these crunchers will want to stick to their teams and cant do the faucet? Would we want some sort of Web Calculator for Staking? Where user enters in RAC manually? Could even pull in real time BBP price to give a fiat value If all they need is ~2BBP, then this should suffice - http://biblepayfaucet.com/ |
|
|
|
I have joined Team Biblepay on wcg (Team ID 35006) before 4 Days.
On Rosetta the same weeks before.
On both i had set my Userdata from "hide" to "display"
I DONT have the same CPID on Rosetta and wcg.
Is that my fault? Can I Change that?
Thanks.
Morka
The easiest way to get CPID to sync is to have at least one of your hosts attached to both projects. Typically within a day or two the CPID will become the same. If you do not want to run work at both projects, just set one to "No New Tasks". However stay attached. |
|
|
|
for mining BBP you getting 3 others coins = Byteball and DCC and NEUMANNIUM (ANN)
can you please explain how to get DCC rewards on boinc ? is it using grcpool ? I think he is referring to what used to be called "Sparc" https://alpha.sparc.network/index.html their coin is now DCC but i don't know of any place that trades the tokens yet And keep in mind that WCG rewards haven't worked since the privacy laws went into effect. So, the system is what it is as they have no intention in fixing the Alpha portion. There is also no guarantee how much longer the Alpha will continue. Here is my how to though if you need it. https://hardforum.com/threads/how-to-get-sparc-during-the-alpha-phase-using-boinc.1953164/Also, keep in mind that there are a hand full of projects that were on the list that are now closed. |
|
|
|
I gave up on this coin when the lead dev (Rob) threatened to label me a satanist because I had a difference in opinion. He also thinks he ran a "successful" BOINC project in the past. In his eyes it may have been "successful". In the eyes of the BOINC community it was poorly ran and never addressed some major issues it had. An example is hard coding the BOINC data directory into your app. This is unnecessary as the BOINC client handles this. Many BOINC users deliberately move the data directory elsewhere to avoid things like apps taking too much storage or too much IO usage on the primary disk. His app was buggy and would balloon on multiple hosts with different OS's. I saw it multiple times taking up several GB's of space which it would not release without manually deleting. He refused to fix the issues the project had. And he tried to punish those that spoke out. One of the worst projects I ever contributed to and I've supported well over 100 of them.
I personally do not trust him.
I'm sorry that happened to you. His attitude towards some of us has caused a lot of anger, sadness, and some division. I hope you know that God loves you whether you are a Christian or not and that we are sticking around to see more people in need be helped. -Mike Oh I'm aware God still loves me. I just want others to know what kind of person he is. I don't see a "Godly" man going around threatening to label others as "satanists" simply because they disagree with him or dislike some of the behavior he may have been a part of... If the team membership requirement was removed, I would return. However, I have a strong sense of dedication to my team and will not switch simply because HE is mimicing Gridcoins marketing success. However, what he should be watching it Byteballs success without NEEDING to require the team membership. |
|
|
|
|
I gave up on this coin when the lead dev (Rob) threatened to label me a satanist because I had a difference in opinion. He also thinks he ran a "successful" BOINC project in the past. In his eyes it may have been "successful". In the eyes of the BOINC community it was poorly ran and never addressed some major issues it had. An example is hard coding the BOINC data directory into your app. This is unnecessary as the BOINC client handles this. Many BOINC users deliberately move the data directory elsewhere to avoid things like apps taking too much storage or too much IO usage on the primary disk. His app was buggy and would balloon on multiple hosts with different OS's. I saw it multiple times taking up several GB's of space which it would not release without manually deleting. He refused to fix the issues the project had. And he tried to punish those that spoke out. One of the worst projects I ever contributed to and I've supported well over 100 of them.
I personally do not trust him.
|
|
|
|
Apple announced changes to its policies to disallow mining on their mobile devices inside an app.
While this is largely targeted against scammy devs that build background mining into their apps, this clause concerned me:
3.1.5 (b) (ii) Mining: Apps may not mine for cryptocurrencies unless the processing is performed off device (e.g. cloud-based mining).
Google might take a very similar stance; if this is the direction things are moving, how do we see this affecting our goal of allowing unbanked mining on phones for people in remote areas without computers? It would be a real shame to lose that feature.
In our case from the apple standpoint, I think we would be OK, because BOINC does the research (and that activity should be construed as research not mining) but either way, the mother process BOINC, starts the threads for the research, while MIP's mobile wallet acts as a block acceptor and wallet. But the main show stopper with running boinc on the iphone is no project supports the proprietary apple processor so boinc only works on the mac currently. However this scenario could come up on the samsung galaxy, and we have a couple beta testers running biblepay-android and boinc currently on that device although I realize google doesnt have the clause yet. Actually, what is preventing BOINC on iOS is that they (Apple) do not allow the software do download executables from outside sources and run them. Otherwise there would have been an iOS version years ago. Basically, BOINC is in a similar boat as mining software.... I cannot really tell you how to do it as I'm not that fluent in the workings of crypto when looking under the hood. However, I would strongly encourage the devs to really try to lock down ways to mitigate cheaters better than Gridcoin has done. Collatz had to completely rebuild their site/servers/etc... because at least one Gridcoin user was cheating on a large scale under one of their pools. https://boinc.thesonntags.com/collatz/forum_thread.php?id=15#190The responses from the Gridcoin team did not sit well with the community as it basically came down to telling the community to fix their projects and to not tell Gridcoin how to run theirs. Science was indeed affected and has to be re-ran. This event was the straw that broke the camels back and essentially caused Gridcoin to be banned from the Annual Pentathlon which is the largest competition in the BOINC world amongst teams. Gridcoin users basically had coin stolen from them because of the cheater getting rewarded. I do not know if they ever resolved any of it as I don't follow their threads. Collatz lost the old forums that had a lot of the details in them. And it appears that a possible cheater has appeared yet again at another BOINC project - http://gene.disi.unitn.it/test/forum_thread.php?id=216#1325On a positive note, have you guys considered possibly adding GPUGrid to your list of projects? http://www.gpugrid.net/Thanks for the post and the links. So from what I can see, in both instances of the cheating that went on in those projects in that community, the user took advantage of an attack vector in which a vulnerability existed on the specific boinc project's server side, in the validation process, which made it possible to cheat on the actual result submission (IE it fooled the server into accepting the result of the workunit). Another words they studied the traffic that is posted by boinc that allows the work unit to be solved and falsified it. Note that there is no example of cheating outside of those few projects. (Thats partially why we picked Rosetta originally, it was partially discussed in the swongle discussions when we were in testnet with cancer mining- Part of the due diligence was to find a project that would be extremely hard if not impossible to cheat. This is because if you look at the manual from Rosetta commons, the work you are doing is so complicated (it requires a 3mb database on the client side to refer to), with 300 scientists on the back end, I don't think its possible to falsify a low energy 'result' without doing more effort than the client does to compute the low energy result. Also in both cases of the cheating note that the gridcoin user diluted their own project compensation - another words a report could have been written that showed a discrepency in task-turnaround/cobblestone-work, picking up the bad user. In that case if that happened here we would have to disable the project and regroup. As far as adding other projects, I feel we should stay focused with what we have now - these projects are related to our healing aspect (we picked Rosetta because it was based on potentially curing cancer), and WCG with their AIDS research. Although I'm interested in using clock cycles for the benefit of humanity, I'm not interested in expanding our mining side into a volunteer computing platform, primarily because I would rather support a high quality project and maintain the healing aspect or facet of biblepay. We have a lot of things to do on the roadmap, and one behind the scenes is investigating partners in the financial sector that also have some options for us in replacing proof of work with other cool cutting edge ideas (like analyzing financial markets etc). I don't know if you looked up GPUGrid or not, but they seem to be in line with what you are asking. http://www.gpugrid.net/science.phpCancer, HIV/AIDS, Neural Disorders, and Methods (pushing boundaries within their fields). They happen to also utilize GPU's (given their name) though they are doing some tests with CPU's too. They do have times where they don't have enough work for everyone, but it would be a good compliment for those wishing to utilize GPU's for something other than mining. Currently only nVidia cards are used. I understand not wanting to delve too quickly, but perhaps keep it on your radar. |
|
|
|
I cannot really tell you how to do it as I'm not that fluent in the workings of crypto when looking under the hood. However, I would strongly encourage the devs to really try to lock down ways to mitigate cheaters better than Gridcoin has done. Collatz had to completely rebuild their site/servers/etc... because at least one Gridcoin user was cheating on a large scale under one of their pools. https://boinc.thesonntags.com/collatz/forum_thread.php?id=15#190The responses from the Gridcoin team did not sit well with the community as it basically came down to telling the community to fix their projects and to not tell Gridcoin how to run theirs. Science was indeed affected and has to be re-ran. This event was the straw that broke the camels back and essentially caused Gridcoin to be banned from the Annual Pentathlon which is the largest competition in the BOINC world amongst teams. Gridcoin users basically had coin stolen from them because of the cheater getting rewarded. I do not know if they ever resolved any of it as I don't follow their threads. Collatz lost the old forums that had a lot of the details in them. And it appears that a possible cheater has appeared yet again at another BOINC project - http://gene.disi.unitn.it/test/forum_thread.php?id=216#1325On a positive note, have you guys considered possibly adding GPUGrid to your list of projects? http://www.gpugrid.net/ |
|
|
|
Oh...and it is ALWAYS a great time to start with WCG...lol. I've been following the GDPR issues with WCG. I'm glad they are taking initiative so quick to iron it out. It hurts the wallet with some of these new projects, but nobody is getting rich doing DC anyways. Now if Gridcoin would stop requiring you to join their team, that would be great. Until then, they don't get any of my support.
While you may have figured it out, we also require you to join our team to get credit. Not trying to discourage you but in all fairness thought that point should be made clear. Hmm...I was not aware of that. When I originally read up on it, the site I was reading said it wasn't necessary. Perhaps that has changed. That is a shame as many DC'ers are truly loyal to their teams. I do see on the BiblePay site it has that step. I will have to edit my how-to. Guess I won't be contributing much... |
|
|
|
I didn't want to have to read through 400+ pages. However, I'm not seeing anything clarifying how to add WCG. I see adding Rosetta. If someone has the CPID from Rosetta already associated with their account and their CPID with WCG is the same, does that automatically opt them in to PODC with WCG as well or is there another step needed? I could see it beneficial and hindering both at the same time depending on situation. I'm always supporting WCG but only support Rosetta during challenges normally.
Also, are you basing the RAC off of what the project site is reporting? I ask because that can take a few weeks to actually become accurate while running the project but becomes very inaccurate if you stop. For instance, I can stop running the project now and several weeks/months/possibly years I will continue to have a RAC at the project. You will find most projects never return you back to 0 RAC because of how RAC is calculated. I was just curious to which "report" I should watch for this...
Welcome aboard! To associate WCG with Biblepay, once you have Rosetta@Home crunching, just check the WCG web portal to ensure your CPID is the same as your RAH CPID. If it is different, just attach WCG to an existing machine that is crunching RAH, and also ensure your web portal WCG e-mail address matches your RAH e-mail address. Then within 24 hours of the next WCG work update, your CPIDs should match. Biblepay will automatically pick up your WCG credits. However, due to the GDPR issue, we are currently in the process of freezing WCG temporarily until the DPA issue is sorted out, so it is not a good time to start with WCG. Regarding diminishing RAC, yes it is true that BOINC'ers who had > 100 RAC and then stopped boincing now exist years later with a RAC of .01 (due to the fact that the RAC never really decays to 0). We filter these out by : requiring a payment of over 1 bbp, requiring recent RAC timestamps, and requiring tasks to be solved. So yes, if you stop boincing you will be paid for weeks as long as you are solving at least 1 task per day, but eventually this will stop when your daily payment decreases below 1 bbp. Thanks for the reply. This is very helpful. I'm aware of how CPID works so that is great as well.  Oh...and it is ALWAYS a great time to start with WCG...lol. I've been following the GDPR issues with WCG. I'm glad they are taking initiative so quick to iron it out. It hurts the wallet with some of these new projects, but nobody is getting rich doing DC anyways. Now if Gridcoin would stop requiring you to join their team, that would be great. Until then, they don't get any of my support. dave_bbp - Thanks for the kind words. Keep in mind SPARC hasn't finished ICO yet and may not be of value for a while. However, it is nice to be getting in early if it does ever go anywhere. Just keep in mind there are a hand full of DC projects that either ended this year, ending this year, or have had a lot of stability problems and thus you earn 0 SPARC when that happens. they pay out every Wednesday. They will only keep doing the DC payouts as they have until the end of the Alpha phase. After that, they may continue or they may require an alternative approach. |
|
|
|
|
