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

[rastiks]

I have the same issue. Plenty of BBP to stake, but zero UTXOWeight. Sent the BBP to the address from exec getboincinfo, now waiting for 6 confirms to see what happens.

aargh. Still not working for me. I have > 50 000 BBP in the wallet address from exec getboincinfo. Stakabalance confirms that. But my UTXOWeight is still 0, and exec podcupdate says Insufficient funds.

This is the second node I'm trying to make this runing (started from scratch today, since it did not work for me yestarday).

Code Select Expand


# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422363,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "fe553a955f0e21d46724858870014cbe_RAC": 6007.06,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 6007.06,
  "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
}


# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 50099
}

# biblepay-cli listaddressgroupings
[
  [
    [
      "BCAPPX5PosAcqc5Z4codkaTMLnmQJSwhMX",
      0.00076300
    ],
    [
      "BMskLQZcPd8EUA8c5iHCmCiAruPjVXtUe1",
      0.00000000,
      ""
    ],
    [
      "BSF8FbMtBKVJ3XiP7fAtrMSU7NfQGQDtmw",
      0.00000000
    ]
  ],
  [
    [
      "BMdWb8WHRbgo6x6AEErNi4cvUVuiKqXn1u",
      0.00000000
    ]
  ],
  [
    [
      "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
      50099.99900000,
      ""
    ]
  ]
]

Code Select Expand


# biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}



[znffal]

aargh. Still not working for me. I have > 50 000 BBP in the wallet address from exec getboincinfo. Stakabalance confirms that. But my UTXOWeight is still 0, and exec podcupdate says Insufficient funds.

This is the second node I'm trying to make this runing (started from scratch today, since it did not work for me yestarday).

Code Select Expand


# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422363,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "fe553a955f0e21d46724858870014cbe_RAC": 6007.06,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 6007.06,
  "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
}


Code Select Expand


# biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}



You could try reassociating your CPID again

[rastiks]

You could try reassociating your CPID again

Have just tried that. So far still zero UTXOWeight, but let's wait 6 blocks. But frankly, I do not believe in success.

[Rob Andrews]

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.

[rastiks]

You could try reassociating your CPID again

Well, I tried. Waited 6 blocks, and still the same. Stakebalance shows 50093, but exec podcupdate syas Insufficient funds. UTXOWeight & TaskWeight are zero. May there be something wrong with my CPID ? Maybe, because I have some ARM (tablet + phone) connected to it? I have run out of ideas.

Code Select Expand


# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422364,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
  "fe553a955f0e21d46724858870014cbe_RAC": 6331.92,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 6331.92,
  "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
}


Code Select Expand


# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 50093
}


Code Select Expand


# biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}


The wallet is quite fragmented after i did several attempts and moved the coins back and forth

Code Select Expand


# biblepay-cli listaddressgroupings
[
  [
    [
      "B7Wtksz1hbBWXRY6U9QhdxMn78h9oEcV5B",
      0.00000000
    ],
    [
      "B7vWrPFoLLawsrpC6hewcxJ6ZbjtPXupV8",
      0.00000000
    ],
    [
      "B8RLs7oTsXvM4QXLQrVVHYwipKqaJXmH4W",
      0.00000000
    ],
    [
      "BB3WzCSGdH6ZYAn5o1a7N4XXKTNcYZ8K6C",
      93.99990840
    ],
    [
      "BCAPPX5PosAcqc5Z4codkaTMLnmQJSwhMX",
      0.00076300
    ],
    [
      "BHRvGs45us9mGimkWimv8kwgYgfmDn2iqm",
      994.99995420
    ],
    [
      "BMskLQZcPd8EUA8c5iHCmCiAruPjVXtUe1",
      0.00000000,
      ""
    ],
    [
      "BQNfVQxb75ssRZ5aqas4Wt2rj6AcPxaZkX",
      48993.99879240
    ],
    [
      "BSF8FbMtBKVJ3XiP7fAtrMSU7NfQGQDtmw",
      0.00000000
    ],
    [
      "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
      0.00000000,
      ""
    ]
  ],
  [
    [
      "BMdWb8WHRbgo6x6AEErNi4cvUVuiKqXn1u",
      0.00000000
    ]
  ],
  [
    [
      "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
      11.00000000,
      ""
    ]
  ]
]


[rastiks]

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.

Great! thanks

[Rob Andrews]

I have around 3 mining rewards so far (~555 each).
Has anyone received Sanctuary rewards yet?

I havent, but the pool is killing it now!  It received about 13 blocks this morning.

[Rob Andrews]

Biblepay
1.1.0.6 - Leisure Upgrade


- Make exec podcupdate much more robust (error messages, utxo leg rounding)

** Windows is compiling **

[T-Mike]

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 Expand


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?

[Rob Andrews]

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]

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 Expand


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.

[T-Mike]

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 Expand


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.

[Rob Andrews]

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 Expand


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]

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]

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.