Bible Pay

Read 74108 times

  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Alright good news, even though it requires an upgrade for the users, good news, I debugged the exec podcupdate feature this morning and I did find a bug!  This explains why T-Mike cant send the exact right stake amount and Simons UTXO is 0 and Rastiks is probably the same issue.

So I now confirm you dont need to worry about the source address of the funds, we will still sign the UTXO packet with your CPID no matter which "bucket" it originates from in the wallet, so that will alleviate a huge portion of the hassle with sending a PODC Update (in the next version).  The other biggie I found was the math the wallet was using was slightly off due to rounding, its kind of hard to explain, but the lions share of the problem was, if you were trying to send say 49K of your 50,000 balance, and your tasks consumed say 3.5K bytes, the internal math (in decimal) rounded down to an amount that was not properly split among the vouts ending with too small of a UTXO expenditure, so I had to fix that so the PODC update leg count (internally) would always round up the specific UTXO for that amount per leg, its a little technical but that is now fixed (in the next version). 

This should be checked in ASAP, doing a little unit testing with this.

Rob, for some reason my UTXOweight is 100 this morning, I checked the last PODC update transaction that happened at around 4am and it was only 15k, not sure why it make my weight 100.

Code: [Select]
Status: 25 confirmations, broadcast through 7 nodes
Date: 3/8/2018 04:35
Source: PODC-Update
Total debit: -15 762.10882064 Biblepay
Total credit: 15 762.10882064 Biblepay
Transaction fee: -0.00500860 Biblepay
Net amount: -0.00500860 Biblepay

Height: 33524
Difficulty: 0.000000
Time: 03-08-2018 09:49:06
Subsidy: 555.4128

PODC_UPDATE:
Transaction ID: 272c95b9f40a5d3a7d18c2b925301f79dc334845abb80272d04c9258c8a94b8a-000

Updating now. Does this build use utxoamount=x instead?
« Last Edit: March 08, 2018, 07:13:41 am by T-Mike »


  • Rob Andrews
  • Administrator

    • 1908


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
No, they aren't there - they newer were as I only had 1 address: B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m
I think that if I do re-associate agan I will end up with another strange address.

When someone reassociates a CPID, we do ask the wallet to create a new dedicated receiving address, this is so the chain contains distinct addresses per CPID during magnitude reverse engineering.

The address should be in your receiving address.  I confirm that we do pull one from your own wallet.

Note, in the next version we dont require any funds to actually be in the CPIDs address, so dont worry about sending funds to it anymore.



  • Rob Andrews
  • Administrator

    • 1908


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Rob, for some reason my UTXOweight is 100 this morning, I checked the last PODC update transaction that happened at around 4am and it was only 15k, not sure why it make my weight 100.

Code: [Select]
Status: 25 confirmations, broadcast through 7 nodes
Date: 3/8/2018 04:35
Source: PODC-Update
Total debit: -15 762.10882064 Biblepay
Total credit: 15 762.10882064 Biblepay
Transaction fee: -0.00500860 Biblepay
Net amount: -0.00500860 Biblepay

Height: 33524
Difficulty: 0.000000
Time: 03-08-2018 09:49:06
Subsidy: 555.4128

PODC_UPDATE:
Transaction ID: 272c95b9f40a5d3a7d18c2b925301f79dc334845abb80272d04c9258c8a94b8a-000

Updating now. Does this build use utxoamount=x instead?

Yeah, I need to inform everyone on the main thread of the big change, we now use "utxoamount=X" across the board.  Ill do that when windows is done building and explain it in that message.

So on your tx, I do see your CPID e94* in my utxoweight list being 100, so that is great.

The reason its 100 is you sent : 106.3K in leg 1 of your UTXO transaction.

Dont worry about debugging it, the last versions squirrely math might have sent an unpredictable amount, the new version should be dead on every time and send change back to you.



  • SimonSays
  • Newbie

    • 25


    • 1
    • January 04, 2018, 01:27:39 pm
    more
When someone reassociates a CPID, we do ask the wallet to create a new dedicated receiving address, this is so the chain contains distinct addresses per CPID during magnitude reverse engineering.

The address should be in your receiving address.  I confirm that we do pull one from your own wallet.

Note, in the next version we dont require any funds to actually be in the CPIDs address, so dont worry about sending funds to it anymore.


Hi Rob,

Thanks for hard work.
Would it be possible to reassign the address manually?

This is list of my addresses (printscreen):
https://drive.google.com/open?id=1YQinWqsheQWfCE_Z2RvRv_5fedGR8gif

Best regards,
Simon


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Yeah, I need to inform everyone on the main thread of the big change, we now use "utxoamount=X" across the board.  Ill do that when windows is done building and explain it in that message.

So on your tx, I do see your CPID e94* in my utxoweight list being 100, so that is great.

The reason its 100 is you sent : 106.3K in leg 1 of your UTXO transaction.

Dont worry about debugging it, the last versions squirrely math might have sent an unpredictable amount, the new version should be dead on every time and send change back to you.

Oh, I see it in the details, it was not showing in the debited amount at the top.

You remember I told you I tried to associate it to my Sanctuary wallet yesterday? Well the address on Rosetta has changed to that account even though it failed.

https://boinc.bakerlab.org/rosetta/show_user.php?userid=1981209

Code: [Select]
exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422364,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "e94c1704c75f731f8bfde303f08408ee_RAC": 58863.33,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
  "Total_RAC": 58863.33,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Update:
I just tried adding my Android Rosetta account to the linux Sanctuary wallet and I get the same error: "Results": "Unable to sign CPID 4b7d2d64c88b32927a21ad20a57868e4"

I see no errors in debug.log.
« Last Edit: March 08, 2018, 07:48:08 am by T-Mike »


  • Rob Andrews
  • Administrator

    • 1908


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Oh, I see it in the details, it was not showing in the debited amount at the top.

You remember I told you I tried to associate it to my Sanctuary wallet yesterday? Well the address on Rosetta has changed to that account even though it failed.

https://boinc.bakerlab.org/rosetta/show_user.php?userid=1981209

Code: [Select]
exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422364,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "e94c1704c75f731f8bfde303f08408ee_RAC": 58863.33,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
  "Total_RAC": 58863.33,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Update:
I just tried adding my Android Rosetta account to the linux Sanctuary wallet and I get the same error: "Results": "Unable to sign CPID 4b7d2d64c88b32927a21ad20a57868e4"

I see no errors in debug.log.

Its really OK if the wallet makes it through phase 1 of association and fails (IE changes your boinc URL) as that is just part of the process, but as far as it failing due to cannot sign cpid:

That means the wallet is locked.  Try sending some bbp to yourself with 'sendtoaddress address 1' first, then run the exec associate command.  Then it should pass.



  • Rob Andrews
  • Administrator

    • 1908


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Hi Rob,

Thanks for hard work.
Would it be possible to reassign the address manually?

This is list of my addresses (printscreen):
https://drive.google.com/open?id=1YQinWqsheQWfCE_Z2RvRv_5fedGR8gif

Best regards,
Simon

Hi Simon, no its not possible.

Best thing to do is send some BBP to the exec getboincinfo address, and ensure you receive it.  Then youre all set.



  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Its really OK if the wallet makes it through phase 1 of association and fails (IE changes your boinc URL) as that is just part of the process, but as far as it failing due to cannot sign cpid:

That means the wallet is locked.  Try sending some bbp to yourself with 'sendtoaddress address 1' first, then run the exec associate command.  Then it should pass.

I apologize, I forgot to delete my old encrypted wallet, I was going to use an un-encrypted one for PODC. Thanks.


  • Rob Andrews
  • Administrator

    • 1908


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Hi Simon, no its not possible.

Best thing to do is send some BBP to the exec getboincinfo address, and ensure you receive it.  Then youre all set.

But,  I will  figure out why its not adding bbp addresses to the address book and naming them rosetta... Let me check....



  • Rob Andrews
  • Administrator

    • 1908


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal :), hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?


  • jaapgvk
  • Hero Member

    • 613


    • 30
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal :), hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?

Is there a minimum version that is required? My sancs are on 1.1.0.5. now.


  • Rob Andrews
  • Administrator

    • 1908


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal :), hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?
If anyone wants to help us verify their sanc so we ensure Togos will get processed please run this on the sanc:

"If you want to test your Sancs health with Togos cpid his cpid is 9313, you can type 'exec dcc', and when its done go to bash, cd /SAN, then 
cat filtered | grep 9313 -A10 -B10 and take a look at Togo's <taskweight> and it should be up to 100."




  • Rob Andrews
  • Administrator

    • 1908


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Is there a minimum version that is required? My sancs are on 1.1.0.5. now.
Yes exactly, it was put in 1105,  Thanks.



  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal :), hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?

Not sure what's going on:
./biblepay-cli exec dcc
error code: -1
error message:
bad lexical cast: source type value could not be interpreted as target

But actually I ran that a few pages back and posted it.

From yesterday:
Code: [Select]
cat filtered | grep 9313 -A10 -B10
 <name>strayapple</name>
 <id>1981219</id>
<utxoweight>75</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

</user>
<user>

 <teamid>15044</teamid>
 <url>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs</url>
 <cpid>93138f032bdd027fa3246b48bb715a77</cpid>
 <expavg_time>1520462480.639447</expavg_time>
 <expavg_credit>80933.641932</expavg_credit>
 <total_credit>1254458.742816</total_credit>
 <create_time>1517967718</create_time>
 <country>United States</country>
 <name>togoshigekata</name>
 <id>1981221</id>
<utxoweight>100</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

Update:
Now it's saying:
./biblepay-cli exec dcc
{
  "Command": "dcc",
  "Success": false,
  "Error": ""
}

Nothing in debug.log
« Last Edit: March 08, 2018, 08:43:20 am by T-Mike »


  • jaapgvk
  • Hero Member

    • 613


    • 30
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
If anyone wants to help us verify their sanc so we ensure Togos will get processed please run this on the sanc:

"If you want to test your Sancs health with Togos cpid his cpid is 9313, you can type 'exec dcc', and when its done go to bash, cd /SAN, then 
cat filtered | grep 9313 -A10 -B10 and take a look at Togo's <taskweight> and it should be up to 100."

Yeah, I wanted to do this earlier, but I don't understand this step:
'go to bash, cd /SAN'