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

[Rob Andrews]

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]

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]

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]

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]

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]

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 Expand


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

[jaapgvk]

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'

[T-Mike]

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

go into the biblepaycore dir and run cd SAN.

[jaapgvk]

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 Expand


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

I get the same error:

Code Select Expand

error code: -1
error message:
bad lexical cast: source type value could not be interpreted as target

Later tried it again, also the same error Mike got (I think):

Code Select Expand

{
  "Command": "dcc",
  "Success": false,
  "Error": ""
}

[jaapgvk]

go into the biblepaycore dir and run cd SAN.

Thx!

[Rob Andrews]

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 Expand


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

Confirmed, I was able to reproduce this exact same issue on my sanc.

The problem turned out to be during my morning PODC test, my particular task weight had a bad scale, to fix this, let me attempt to retransmit my podcupdate now, and see if it fixes you.  I will Fix this particular issue from happening permanently also, but in a way where we will not need to upgrade now as we are running out of time. 

[Ichthus220]

Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code Select Expand


09:03:44

exec getboincinfo


09:03:45

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422367,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2917.45,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2917.45,
  "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
}


[T-Mike]

Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code Select Expand


09:03:44

exec getboincinfo


09:03:45

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422367,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2917.45,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2917.45,
  "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
}


Did you run exec podcupdate true and wait 6 blocks?

[Rob Andrews]

go into the biblepaycore dir and run cd SAN.

Ok, anyone who had the bad lexical cast error, I have added code to the sanc side to prevent any number longer than the Max c++ length from happening again, and thankfully I was able to re-send my bad podcupdate, and the network accepted it.

So please, try the test over - if you type exec dcc - if it returns with false, just reboot your node.  This is a one time thing to clear the sanc out of its bad memories.

I just reran the test, and I see Togo is up and running with a magnitude of 268, looks like I have 56, etc.. you can see the mag this way from a sanc:
cd SAN
cat magnitude | grep 9313

Etc.

[Rob Andrews]

Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code Select Expand


09:03:44

exec getboincinfo


09:03:45

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422367,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2917.45,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2917.45,
  "Total Payments (One Day)": 0,
  "Total Pa
  "Magnitude (One-Week)": 0
}


Could you please double click , copy, and paste the outgoing UTXO txid here?

Edit: I dont show a PODCUpdate coming from E6CE recently - last one was yesterday.