Bible Pay

Read 17188 times

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. 


  • jaapgvk
  • Sr. Member

    • 409


    • 15
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
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?


  • jaapgvk
  • Sr. Member

    • 409


    • 15
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
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 (%)



  • MIP
  • Jr. Member

    • 82


    • 7
    • February 13, 2018, 11:55:52 am
    more
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


  • Rob A.
  • Administrator

    • 1022


    • 15
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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.



  • Rob A.
  • Administrator

    • 1022


    • 15
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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.



  • MIP
  • Jr. Member

    • 82


    • 7
    • February 13, 2018, 11:55:52 am
    more
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.
« Last Edit: March 20, 2018, 09:46:45 am by MIP »


  • Rob A.
  • Administrator

    • 1022


    • 15
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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.


Hmmm, it looks like these transactions were signed by a wallet not associated to the CPID - another words, to the foreign nodes these transactions look forged.

The first few on the list were signed by BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H, yet when I look in the chain, exec search dcc 96892, I see your CPID is associated with a different public wallet key.

The controller doing the podcupdate should be the one associated with the CPID.

(Otherwise nodes will disregard your podcupdates as if the signature is forged).

EDIT: Whats the TXID of the one you just did successfully, I can check it?

« Last Edit: March 20, 2018, 09:53:42 am by Rob A. »


  • MIP
  • Jr. Member

    • 82


    • 7
    • February 13, 2018, 11:55:52 am
    more

Hmmm, it looks like these transactions were signed by a wallet not associated to the CPID - another words, to the foreign nodes these transactions look forged.

The first few on the list were signed by BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H, yet when I look in the chain, exec search dcc 96892, I see your CPID is associated with a different public wallet key.

The controller doing the podcupdate should be the one associated with the CPID.

(Otherwise nodes will disregard your podcupdates as if the signature is forged).

EDIT: Whats the TXID of the one you just did successfully, I can check it?

I don't really know which is the last one that worked, How can I know? to me all seem exactly the same.

And I have been using the same address for a week without a problem. In fact I got payments until yesterday ...

Edit: ok I will start again with a "new" wallet file and re-associate from scratch to avoid interferences with other addresses.

« Last Edit: March 20, 2018, 10:05:06 am by MIP »


  • Rob A.
  • Administrator

    • 1022


    • 15
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I don't really know which is the last one that worked, How can I know? to me all seem exactly the same.

And I have been using the same address for a week without a problem. In fact I got payments until yesterday ...

Edit: ok I will start again with a "new" wallet file and re-associate from scratch to avoid interferences with other addresses.

I meant last one sent by timestamp, not last one that worked (last one that worked for you is probably the one that is invalid for me).

Anyway, if you reassociate your CPID with force, and try to sign with a different wallet.dat, this type of forge will happen.

Nothing changes in the chain, so it must have changed on your end - otherwise I would have over 1,250 messages telling me the system is broken completely.  Unless we have a bug that is only transmitting half of the public key or half of the cpid in the chain, but these messages you pasted earlier are complete (as they end in an XML suffix with an end character + a suffix).  The data all comes from your wallet, so there is no way other peoples data is intermingled into your data either.

You should never have to start over, unless you accidentally reassociated with a second wallet.dat.



  • MIP
  • Jr. Member

    • 82


    • 7
    • February 13, 2018, 11:55:52 am
    more
I just created a clean wallet, imported the address to stake with, re-associated and made podcupdate true, waited for confirmations,

Code: [Select]

exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "96892ec0fc8a2710fa84f26c9c84cd3e",
  "Address": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "CPIDS": "96892ec0fc8a2710fa84f26c9c84cd3e;",
  "CPID-Age (hours)": 422657,
  "NextSuperblockHeight": 35670,
  "NextSuperblockBudget": 1197260,
  "96892ec0fc8a2710fa84f26c9c84cd3e_ADDRESS": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "96892ec0fc8a2710fa84f26c9c84cd3e_RAC": 19534.21,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TEAM": 15044,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TaskWeight": 100,
  "96892ec0fc8a2710fa84f26c9c84cd3e_UTXOWeight": 0,
  "Total_RAC": 19534.21,
  "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
}


 :(

The PoDC transactions:
172bd33f5ee7757d82464b071bc312cf4f570fa1d6d473c94bb42c84ab50ee5d
8a4df3cdc03ad31be3a4acf7d20edc2229cd0c96c1bed6756ec20c7add5c7bce

How can you check that it's valid or it is rejected?


  • Rob A.
  • Administrator

    • 1022


    • 15
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I just created a clean wallet, imported the address to stake with, re-associated and made podcupdate true, waited for confirmations,

Code: [Select]

exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "96892ec0fc8a2710fa84f26c9c84cd3e",
  "Address": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "CPIDS": "96892ec0fc8a2710fa84f26c9c84cd3e;",
  "CPID-Age (hours)": 422657,
  "NextSuperblockHeight": 35670,
  "NextSuperblockBudget": 1197260,
  "96892ec0fc8a2710fa84f26c9c84cd3e_ADDRESS": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "96892ec0fc8a2710fa84f26c9c84cd3e_RAC": 19534.21,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TEAM": 15044,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TaskWeight": 100,
  "96892ec0fc8a2710fa84f26c9c84cd3e_UTXOWeight": 0,
  "Total_RAC": 19534.21,
  "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
}


 :(

The PoDC transactions:
172bd33f5ee7757d82464b071bc312cf4f570fa1d6d473c94bb42c84ab50ee5d
8a4df3cdc03ad31be3a4acf7d20edc2229cd0c96c1bed6756ec20c7add5c7bce

How can you check that it's valid or it is rejected?

Yeah, there is something funny going on here.  I see your taskweight in the chain, I see your Tx, and I see your updated CPID, but its almost as if it is ignoring your UTXO weight only.  This time it does look valid (probably what caused you to change it to begin with was the fact that you had no utxo weight), I see the CPID matches the sig and the key, so now its an interesting problem.

Im going to have to add a command to the RPC to diagnose this one.

Hang on please, I have an appointment in an hour but Ill try to work on this now.



  • MIP
  • Jr. Member

    • 82


    • 7
    • February 13, 2018, 11:55:52 am
    more
Sure, thank you


  • Rob A.
  • Administrator

    • 1022


    • 15
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Sure, thank you

Getting closer; what OS and BBP compile version are you currently running that is emitting this particular sig?



  • MIP
  • Jr. Member

    • 82


    • 7
    • February 13, 2018, 11:55:52 am
    more
Getting closer; what OS and BBP compile version are you currently running that is emitting this particular sig?

OS: Windows Server 2012 R2 Standard
BBP compile version: 1.1.1.1