Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 71. (Read 243376 times)

Although capulinko, is probably in there already as far as a nickname being linked to an old address, try this:
exec cpk your-nickname your-emailaddress user true
The your-emailaddress and "user" must come before the "force=true"

Then try a sendgscc after 5 confirms after you are in the chain, then wait for the leaderboard.

Started one machine on WCG. shouldn't take long to get some decent RAC.

I can start some, but i need to recall how it works

It would be helpful if a few of you start up your WCG (world community grid) CPID again, and join it to team BiblePay, and start accumulating some RAC for testnet.

Im going to be inviting people into testnet on Friday.

It would be helpful if a few of you start up your WCG (world community grid) CPID again, and join it to team BiblePay, and start accumulating some RAC for testnet.

Im going to be inviting people into testnet on Friday.

i'm not able to rejoin pog...

}
capo@xeon4:~$ biblepay-cli exec cpk capulinko true
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}
capo@xeon4:~$ biblepay-cli exec join pog true
{
  "Command": "join",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"

how to fix this, seems force is not working for me

So although I don't expect PODC2.0 to solve all of our problems, as supporting Cancer Mining is going to be a lot of work, we are going to try to make big improvements over podc 1.0 (using the knowledge we've learned up til now) before releasing 2.0.

We need to make 2.0 more like the iPhone:  Easy to setup, easy to understand, easy to maintain.  The defaults should work.

Some of the pitfalls we had before:  Daily podcupdates required, meaning the core wallet had to be running, had to unlock wallets to send podc updates, had to have funds available for the CPID association, had to understand all the terminology, etc.

Last night I started working on something called an "external PODC purse".  This will allow a user to store a balance in an external purse.  Then PODC will be able to fund the association, and the daily updates (for both PODC & Cameroon one) through this purse, so you will no longer have to have the wallet unlocked.  Ive been waiting for this myself as I dont know how many times I booted biblepay and never unlocked the wallet, and lost the rewards for the day (probably 50% of the time) etc.  So this works in alpha now, so this will be coming.  You will basically type a command to join Cancer mining (or WCG, TBD), and we will make an external purse for you, IE an adddress called "PODC", and you will fund it with 1000 bbp.  Then we will associate your cpid to that address.  Later, we will ensure the updates are sent from the main thread (and no longer from the miner) and they will only cost about .25 bbp max (for tx fees) and they will send even when wallets are locked.  Then in a few years you can fund the purse using a special command.  This should cut down on support issues.

One volunteer helper I could use -- do we have a volunteer who wants to make a biblepay CPID stats website?  One that does something like pull the data from the core wallet via rpc commands, and cache it, and show RAC per CPID per day and a graph?  (Something that will cut down on support questions from new users).  I will gladly give you a subdomain of biblepay.org if you want to take this on.  This will allow me to focus on working on the Data, and the RPC commands, and someone else can focus on UI for ease of use?  (On a side note -- I can manage pulling in our prior core wallet cpid association page again from biblepay-classic -- asap).

Also, I will ensure we make the CPID data display in the rpc more user friendly this time.

Im also thinking since we will no longer require the 'bbp for rac' rule or escrow reqs anymore, therefore we can streamline things a little more, meaning boinc can keep crunching on phones or on cpus for days, and if you dont check in for 7 days you should still receive 7 rewards automatically in your locked (and non-running) wallet.

Basically we need a plug-n-play environment for PODC 2.0.