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

Is the reduction in the superblock because of the tithe block?

Block 35055 hit, shows next superblock budget as 1197260 at 35260, those look about where I was anticipating the breakdown should be initially.

What is the official word on staking for the UTXO reward component, and will that require a MN update to implement ?

Yes I agree, me too, but too bad we didn't catch it in TEST.

Hopefully this answers your question:
https://bitcointalk.org/index.php?topic=2388064.msg32447969#msg32447969

Is the reduction in the superblock because of the tithe block?

No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

Got it. Thanks Rob!

Yes I agree, me too, but too bad we didn't catch it in TEST.

Hopefully this answers your question:
https://bitcointalk.org/index.php?topic=2388064.msg32447969#msg32447969

I guess my better question is when, if ever, is it going to change from 500BBP/Mag and what will be the final determining factor in deciding how much.

I guess my better question is when, if ever, is it going to change from 500BBP/Mag and what will be the final determining factor in deciding how much.

In 1111, we have the SPM or SPR (stake per mag or stake per rac) indicator Spork doubles (double is like a floating point number) compiled in. 

So when this poll outcome :
http://forum.biblepay.org/index.php?topic=127.0

is known, then I sign a spork and induce it in the chain that night, and right away the sancs start honoring the new business logic rule for the next superblock.

So as an example if this poll ends of April Fools Day, and it dictates 20 bbp per rac, as of that evening, the sancs will start being influenced to create and vote on the contract using that new business logic.

No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

Will the time between blocks be about what it is right now. 32.5 hours?

Will the time between blocks be about what it is right now. 32.5 hours?

Starting at block 35110, it should technically speed up to 205 blocks per day.  Lets hope we got it right this time.

In 1111, we have the SPM or SPR (stake per mag or stake per rac) indicator Spork doubles (double is like a floating point number) compiled in. 

So when this poll outcome :
http://forum.biblepay.org/index.php?topic=127.0

is known, then I sign a spork and induce it in the chain that night, and right away the sancs start honoring the new business logic rule for the next superblock.

So as an example if this poll ends of April Fools Day, and it dictates 20 bbp per rac, as of that evening, the sancs will start being influenced to create and vote on the contract using that new business logic.

Is there a reason this poll is running so long?  20 BBP/RAC has nearly 40% of the vote in a 19 selection race.  Could we reduce it to the top three options and run a shorter vote?  Or since 20 BBP/RAC has more than the 2nd and 3rd option combined, I would think it is the winner even though it's not my choice. 

It seems like I missed the last two payments from my pool unbanked account.

CPID: 8791a036b545f35e9ebd9333922738ac
BBP adress: 8791A036B545F35E9EBD9333922738AC

Code: [Select]

21:42:51

exec search dcc 8791a036b545f35e9ebd9333922738ac


21:42:51

{
  "DataList": "DCC",
  "8791A036B545F35E9EBD9333922738AC (03-11-2018 16:50:26)": "8791a036b545f35e9ebd9333922738ac;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;1986929;;1"
}

This phone is only calculating for Rosetta when it's on the charger (about 10-12 hours every day). But that shouldn't need to be a problem, right?

It seems like I missed the last two payments from my pool unbanked account.

CPID: 8791a036b545f35e9ebd9333922738ac
BBP adress: 8791A036B545F35E9EBD9333922738AC

Code: [Select]

21:42:51

exec search dcc 8791a036b545f35e9ebd9333922738ac


21:42:51

{
  "DataList": "DCC",
  "8791A036B545F35E9EBD9333922738AC (03-11-2018 16:50:26)": "8791a036b545f35e9ebd9333922738ac;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;1986929;;1"
}

This phone is only calculating for Rosetta when it's on the charger (about 10-12 hours every day). But that shouldn't need to be a problem, right?

Rob, could you shine some light on this?

Code: [Select]

UTXO amount  0.0000 bbp
UTXO weight 0 (%)

I don't know what happened but I got dropped down from the next payment list. I see utxoamount=0 even if PoDC payments have been happening for the latest hours without apparent trouble. I even changed utxoamount=100001 in conf file just in case...

Code: [Select]

exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "96892ec0fc8a2710fa84f26c9c84cd3e",
  "Address": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "CPIDS": "96892ec0fc8a2710fa84f26c9c84cd3e;",
  "CPID-Age (hours)": 422649,
  "NextSuperblockHeight": 35670,
  "NextSuperblockBudget": 1197260,
  "96892ec0fc8a2710fa84f26c9c84cd3e_ADDRESS": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "96892ec0fc8a2710fa84f26c9c84cd3e_RAC": 19239.3,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TEAM": 15044,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TaskWeight": 100,
  "96892ec0fc8a2710fa84f26c9c84cd3e_UTXOWeight": 0,
  "Total_RAC": 19239.3,
  "Total Payments (One Day)": 5543,
  "Total Payments (One Week)": 70287,
  "Total Budget (One Day)": 1197260,
  "Total Budget (One Week)": 13036836,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "35465,35260,35055,34850,34645,34440,34235",
  "Last Superblock Height": 35465,
  "Last Superblock Budget": 1197260,
  "Last Superblock Payment": 5543,
  "Magnitude (One-Day)": 4.629737901541854,
  "Magnitude (One-Week)": 5.391415524441666
}

Any ideas? Thank you

It seems like I missed the last two payments from my pool unbanked account.

CPID: 8791a036b545f35e9ebd9333922738ac
BBP adress: 8791A036B545F35E9EBD9333922738AC

Code: [Select]

21:42:51

exec search dcc 8791a036b545f35e9ebd9333922738ac


21:42:51

{
  "DataList": "DCC",
  "8791A036B545F35E9EBD9333922738AC (03-11-2018 16:50:26)": "8791a036b545f35e9ebd9333922738ac;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;1986929;;1"
}

This phone is only calculating for Rosetta when it's on the charger (about 10-12 hours every day). But that shouldn't need to be a problem, right?

Hi Jaap,

I finally got a chance to look at this- and the great news is it was just a network setting set improperly and it has been corrected, so now looking at the

cat filtered | grep 8791a -B7 -A11
I see that you do have the <unbanked> indicator showing as 1 on sancs now.  This will go into effect during the next contract, so please lets see if you start receiving payments now.  It might take 24 more hours for it to cascade. 

Note that in the pool, you can look for the unbanked flag on your superblock row, to see if it shows as "1".  At that point you can expect a payment.

I don't know what happened but I got dropped down from the next payment list. I see utxoamount=0 even if PoDC payments have been happening for the latest hours without apparent trouble. I even changed utxoamount=100001 in conf file just in case...

Code: [Select]

exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "96892ec0fc8a2710fa84f26c9c84cd3e",
  "Address": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "CPIDS": "96892ec0fc8a2710fa84f26c9c84cd3e;",
  "CPID-Age (hours)": 422649,
  "NextSuperblockHeight": 35670,
  "NextSuperblockBudget": 1197260,
  "96892ec0fc8a2710fa84f26c9c84cd3e_ADDRESS": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "96892ec0fc8a2710fa84f26c9c84cd3e_RAC": 19239.3,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TEAM": 15044,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TaskWeight": 100,
  "96892ec0fc8a2710fa84f26c9c84cd3e_UTXOWeight": 0,
  "Total_RAC": 19239.3,
  "Total Payments (One Day)": 5543,
  "Total Payments (One Week)": 70287,
  "Total Budget (One Day)": 1197260,
  "Total Budget (One Week)": 13036836,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "35465,35260,35055,34850,34645,34440,34235",
  "Last Superblock Height": 35465,
  "Last Superblock Budget": 1197260,
  "Last Superblock Payment": 5543,
  "Magnitude (One-Day)": 4.629737901541854,
  "Magnitude (One-Week)": 5.391415524441666
}

Any ideas? Thank you

I dont see you sending any UTXO weight out on the network:
exec search utxoweight 9689

Although I do see your cpid is present... 
I would try 'exec podcupdate true'
Lets see what kind of error you receive. 

With no UTXO stake, the utxoweight will remain 0, resulting in no superblock payments and no daily magnitude.

I dont see you sending any UTXO weight out on the network:
exec search utxoweight 9689

Although I do see your cpid is present... 
I would try 'exec podcupdate true'
Lets see what kind of error you receive. 

With no UTXO stake, the utxoweight will remain 0, resulting in no superblock payments and no daily magnitude.

I understand, but that's the issue because I've been sending Podc updates regularly... I post the PoDC update txids since yesterday

1b21f2b352383ca00cd3c51e494cd99d032c540ba3af3f8963bd36c9b49c9ac0
2c43abb2fb1ae9e9e2db25005fb784dd045ce5fe304632f653aa0d91d2c2adbf
19ffe0b8cff60ae1939a9bf90dbff7794c99fb057090ccd6c3e73b0ea0d2f608
ed77dc115de82127c2e939594ee64993b151e80ed007172b72e7bcf70fe6e4d0
bcc9ce63827c6c29d7afea01d8068511fc7d7ebb7db2740d7f14d7aa707a0a3d
6d351f1e193535d6aa8622390374e9bc3fd1108bdfdb239d661a7ef0adfdb253
2f55f35dbabcd0fed7175e039f677533342a0442adc1b789d0a88de4735b2236
99b7bada905b0fb2c81f97e49b2468e52df341a39f91b0d351b74dc5491a6a87
9b3e2af19849bbaf2fa9a9250004f7ab69eeb4e82bfb5173dbfad5f3d747030c
05ae2f2d9776175ab37758b2bee3c73c12d7fbf7cf5847beb0b27f07bd9fb2fc
af897c9d4eb63eb8e538392c63b556a8f654eae2b397d6b83058fa9a2042c4bf
c9938257ee11646f6eb0984aaaadd08e08c71048c5aff802db7c6a8617a5d066
ea695770ba3708dbaec396777c2b8940a693574b52444191c832a640557981ab

Some of them were forced

I tried to re-associate but nothing. I'll try podcupdate true and see..

Edit:

Code: [Select]

exec podcupdate true

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (128) over 1 CPID(s) successfully."
}


I will wait and see.

By the way I remember the only change is that yesterday afternoon I password locked the wallet. But when I reloaded I unlocked it for PoDC. I don't know if it may be the cause.