BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

My rewards seem to be around 150K at present


12:10:24

exec getboincinfo

12:10:25

{
  "Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "NextSuperblockHeight": 5445,
  "8f273b30f8e0a298ed26e242762df701_RAC": 453.53,
  "LastSuperblockHeight": 5346,
  "Payments": 153915,
  "Budget": 1386000,
  "Magnitude": 111.0497835497836
}

Updated both my testnet wallets to 1.0.8.9

showblock 5228:

Code: [Select]

"blockmessage": "",
  "satisfiesbiblehash": "true",
  "biblehash": "0000000af3d9ac2d23b4eef3f5b0fd9303e6ca61b432fe2a15e5dbf50ce72bc7",
  "prayers": "",
  "nextblockhash": "449ff8cb60b4ce68691add717ebdd8980e3ea22716db8bd761bc523b1d1e9a87"
}

Thanks, Ill work on that botnet-busting feature a different way, so dont worry about the blockmessage for now, it needs a change.

My rewards seem to be around 150K at present


12:10:24

exec getboincinfo

12:10:25

{
  "Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "NextSuperblockHeight": 5445,
  "8f273b30f8e0a298ed26e242762df701_RAC": 453.53,
  "LastSuperblockHeight": 5346,
  "Payments": 153915,
  "Budget": 1386000,
  "Magnitude": 111.0497835497836
}

Glad to hear your being PAID!  Nice!
And heres a little more info on mag:
The magnitude is a value between 1-1000, with 1000 being the highest you can achieve in Biblepay (its impossible because 1000 means you are doing all the work).

Anyway if you divide the mag by 10, its equal to Your Share of the Last SUperblock.

So in Lukes case, he should receive 11% of the 1.386MM coins.  Looks like he did:  153K is 11% of the superblock.


So far so good all.... I like this, and I also like the plethora of tweaks a miner can make to their clock speeds and system boot options (mining as a service, running cross platform, mining multi machines against one CPID), sleep options, etc. 

Have 2 masternodes running on 1.0.8.9 now.

Have 2 masternodes running on 1.0.8.9 now.

I accidentally spent my hot masternode funds...recreating now.

Have 2 masternodes running on 1.0.8.9 now.

Ok, Im back and I see 2 of you did vote on the contract while I was down, which is great, in last superblock.
Why dont we try checking this next contract out without forcing it?

Mike are you online?

Ok, Im back and I see 2 of you did vote on the contract while I was down, which is great, in last superblock.
Why dont we try checking this next contract out without forcing it?

Mike are you online?

So I kind of answered my own question.  What I meant by force, was if users keep typing exec testvote, they are forcing a vote for their contract hash (which the code will do anyway, once per block).
So checking to see what kind of support we have for the  next superblock (without typing exec testvote),  you can type
cat debug.log | grep ExecuteDistributed -A5
And you will see what your node thinks its doing as blocks click by.  In my case it says "PENDING SUPERBLOCK", meaning two Sancs already voted on block #5643, telling me there will be a superblock.

Each Sancs vote only counts once per filehash.

Ok, Im back and I see 2 of you did vote on the contract while I was down, which is great, in last superblock.
Why dont we try checking this next contract out without forcing it?

Mike are you online?

Yeah, just finished settings up the 3rd one.

So I kind of answered my own question.  What I meant by force, was if users keep typing exec testvote, they are forcing a vote for their contract hash (which the code will do anyway, once per block).
So checking to see what kind of support we have for the  next superblock (without typing exec testvote),  you can type
cat debug.log | grep ExecuteDistributed -A5
And you will see what your node thinks its doing as blocks click by.  In my case it says "PENDING SUPERBLOCK", meaning two Sancs already voted on block #5643, telling me there will be a superblock.

Each Sancs vote only counts once per filehash.

Mine says:
AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK .
2018-02-10 02:05:00 UpdateTip: new best=6ee2dc9bc66a6310009d192ea9c6f67a4bd29e8efa17f92e2046374f8311281e  height=5571  log2_work=39.043051  tx=7504  date=2018-02-10 02:04:59 progress=0.031810  cache=0.1MiB(594tx)
2018-02-10 02:05:00 AddToWallet 5b3f2d75a103ead2d58a5ef32a41a41ff00e48d10b3f9726e0a92b915c3f21d9  new
2018-02-10 02:05:00 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 8b2affbe3d46b48ec87e6e6115f06e511a9673697f647b8ef1aa25172e14175b-1 -- found new 5571.000000
2018-02-10 02:05:00 ProcessNewBlock : ACCEPTED

Mine says:
AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK .
2018-02-10 02:05:00 UpdateTip: new best=6ee2dc9bc66a6310009d192ea9c6f67a4bd29e8efa17f92e2046374f8311281e  height=5571  log2_work=39.043051  tx=7504  date=2018-02-10 02:04:59 progress=0.031810  cache=0.1MiB(594tx)
2018-02-10 02:05:00 AddToWallet 5b3f2d75a103ead2d58a5ef32a41a41ff00e48d10b3f9726e0a92b915c3f21d9  new
2018-02-10 02:05:00 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 8b2affbe3d46b48ec87e6e6115f06e511a9673697f647b8ef1aa25172e14175b-1 -- found new 5571.000000
2018-02-10 02:05:00 ProcessNewBlock : ACCEPTED

Sweet,  so really things seem to be working properly.

Tomorrow I will move the distinct CPID rule to the blockcheck for testnet and have a release (Ill wait til something else can be merged with it before releasing another testnet release).

Does anyone have any security questions, or any questions about anything DC related?

Maybe I should add a feature to show total payments over 7 days, then we can do some math also.

Glad to hear your being PAID!  Nice!
And heres a little more info on mag:
The magnitude is a value between 1-1000, with 1000 being the highest you can achieve in Biblepay (its impossible because 1000 means you are doing all the work).

Anyway if you divide the mag by 10, its equal to Your Share of the Last SUperblock.

So in Lukes case, he should receive 11% of the 1.386MM coins.  Looks like he did:  153K is 11% of the superblock.


So far so good all.... I like this, and I also like the plethora of tweaks a miner can make to their clock speeds and system boot options (mining as a service, running cross platform, mining multi machines against one CPID), sleep options, etc.

Rob, when my mag actually had a number earlier today, I didn't see a payment for it.  How do I check?

Rob, when my mag actually had a number earlier today, I didn't see a payment for it.  How do I check?

If your mag had a number earlier it should still have a number, why no number now, did you move wallets?

The easiest way is to just scroll through your transaction history, look for anying over 20k in the last 24hours?

Since we have 7 superblocks a day, you'd really have to figure the spacing math (exec getboincinfo, see the difference between the 2) then showblock each prior block for 24 hours to check manually, but from what I remember, you didnt have a mag all day, this morning you were not in the list, what is your cpid?

If your mag had a number earlier it should still have a number, why no number now, did you move wallets?

The easiest way is to just scroll through your transaction history, look for anying over 20k in the last 24hours?

Since we have 7 superblocks a day, you'd really have to figure the spacing math (exec getboincinfo, see the difference between the 2) then showblock each prior block for 24 hours to check manually, but from what I remember, you didnt have a mag all day, this morning you were not in the list, what is your cpid?

CPID: e94c1704c75f731f8bfde303f08408ee

Before I took the node down about 3 hours ago I saw a number on the front page but now it's 0. I did not change wallets.

CPID: e94c1704c75f731f8bfde303f08408ee

Before I took the node down about 3 hours ago I saw a number on the front page but now it's 0.

*update

I looked through all the transactions today and didn't find the payment.

CPID: e94c1704c75f731f8bfde303f08408ee

Before I took the node down about 3 hours ago I saw a number on the front page but now it's 0.

I think you saw your CPID appear on the front page but not magnitude, since you are still not in the san\filtered file yet (that will always only get bigger).  Yeah your not in yet, so you should have 0 payments.

Also, 'exec getboincinfo' shows your up to date RAC and should show 0 mag.  Do u have RAC yet?


Maybe we should move to once per day superblocks in testnet so we dont have to check as many.  We need some type of report you can run that shows every cpid and payment in the last superblock.