Quote from: sunk818 on September 21, 2018, 04:24:14 PM

Quote from: capulo on September 21, 2018, 01:46:40 PM

as i can see, there are still same questions like 'how to setup mining', 'how to set wcg', 'how to add byteball', 'howto something', 'why it is not working', 'what i need to do..' ...
we will need better guidelines, with even better troubleshooting steps.
not just 'you need to stake', but how to stake, how to check stakebalance, how much time i need to wait until coins are available to stake, how much i need to stake, how to check if i'm staking something, when stake will take effect in payments etc etc...
or maybe some helpdesk or just contacts to some experienced users which can help online

If you have any edits you want to suggest, please make them and send them to me in a PM.
I'll need the URLs you are fixing and I'll forward them to the correct person.

ByteBall and DCC are not really part of BiblePay, so that is really a side benefit of crunching Rosetta@Home (DCC) and WCG (ByteBall, Neumannium - WAVES platform). So, I could host those on a wiki if you want to write up the instructions. I can get a free wiki hosted on herokuapp.

Quote from: nsummy on September 21, 2018, 04:23:29 AM

4. Eventually the CPIDs will match and credit from WCG will be applied?

That's right. Only Rob knows the intention of why only Rosetta@Home is available to register, but I suspect that's partly why. If you register with Rosetta@Home and do those tasks first, that will be your CPID. When you register for WCG, your CPID is different, but having the same e-mail address, your WCG CPID will merge with Rosetta@Home.

If BiblePay allowed registration with WCG in the wallet, can you see there being issues with CPID matching? If you registered your WCG CPID and it changed because you registered Rosetta@Home first, the CPID you registered with BBP would stop working. That's why it is better to have only one project to register on BiblePay (Rosetta@Home).

Its a complicated answer. In wallet versions before 1.1.5.0, sancs needed the RAH CPID first to find the WCG RAC. (Because the Sancs looked up WCG RAC by the primary key of the RAH user in the contract). Starting in the next mandatory release (which is not out yet so please dont try this yet, should be out in 14 days we believe) we actually do allow you to have WCG RAC only - and be missing in RAH.

Thats only half of it. The other half is for new users who have a CPID first in RAH, WCG adapts better to learn your existing CPID (it pulls in and respects the externalcpid field). Otoh, if you start with WCG only- I can't say if Rosetta will pull your cpid from WCG, this is because IBM's implementation of boinc is the only custom implementation out of the 70 projects, since they rewrote the Web RPC. It might work, someone should test that situation.