Bible Pay

Read 92970 times

  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
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
  • Hero Member

    • 617


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

I get the same error:

Code: [Select]
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]
{
  "Command": "dcc",
  "Success": false,
  "Error": ""
}
« Last Edit: March 08, 2018, 08:48:14 am by jaapgvk »


  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
go into the biblepaycore dir and run cd SAN.

Thx!


  • Rob Andrews
  • Administrator

    • 2029


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

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
  • Newbie

    • 29


    • 0
    • December 11, 2017, 10:09:35 pm
    more
Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code: [Select]
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
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code: [Select]
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
  • Administrator

    • 2029


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

    • 2029


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code: [Select]
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.




  • Ichthus220
  • Newbie

    • 29


    • 0
    • December 11, 2017, 10:09:35 pm
    more
Could you please double click , copy, and paste the outgoing UTXO txid here?

Code: [Select]
Status: 122 confirmations
Date: 3/5/2018 23:26
To: BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM
Debit: -1.00000000 Biblepay
Transaction fee: -0.00019140 Biblepay
Net amount: -1.00019140 Biblepay


DCC: e6ce50042187d4b285568d86ef458f32;BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk;BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk;1985116;H4P4qzNTeEqMQtyNKSalu01omMRfGXBhHe+8Y/IaVoKfEUwY3ZoA9PlMkAkyT9DbQsabpPvUOF0635hdXBrvkR8=;0
Transaction ID: 21d81563d6e3ecccaab0215df0a1fd7a3fc6ef4826e9f867e7fdf8abc5f6e8f4-000



Debug information

Debit: -1.00000000 Biblepay
Debit: -1.00000000 Biblepay
Credit: 0.99980860 Biblepay

Transaction:
CTransaction(hash=21d81563d6, ver=1, vin.size=2, vout.size=2, nLockTime=33204)
    CTxIn(COutPoint(d05dc9749756f29cee88e2267dff2ac4725cc346911518b6d6b902bde2a8ee41, 1), scriptSig=473044022024c6a78088fb37, nSequence=4294967294)
    CTxIn(COutPoint(14f89fcf60f39d461d7924326fc2f8b1189b9153566c77cbc1a66f9b0bbeb3f2, 0), scriptSig=47304402205db2565a1609bd, nSequence=4294967294)
    CTxOut(nValue=0.99980860, scriptPubKey=76a914aeea512bcbc96c148376c04d)
    CTxOut(nValue=1.00000000, scriptPubKey=76a9144813c26f2846cfcde5d1cc62)

Inputs:


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
./biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance (1.00) less than target UTXO (50000.00)."
}

Looks like it is working, going to have to wait for a few confirmations then I will try again. It is still looking for the right address on "version": 1010006 even though I have enough in my wallet.


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
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.

exec dcc works now, thanks.


  • Rob Andrews
  • Administrator

    • 2029


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Biblepay
1.1.0.6 - Leisure Upgrade



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


** Note to All: please modify the Distributed Computing process in this way:
Retire the use of -polpercentage in your config files.
Use "utxoamount=50000" instead, where 50000 is the amount of UTXO you choose to stake in each podcupdate (this occurs approx. once per day).
Note - the default is now 50,000, so you do not need to set it if you desire 50,000 **

Anyone with 'exec getboincinfo' with less than 100 utxoweight, please 'exec podcupdate' to send a new UTXO using this new version.

** Windows is ready for download **




  • Rob Andrews
  • Administrator

    • 2029


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
exec dcc works now, thanks.

Do you show the same mag for Togo Mike?



  • Rob Andrews
  • Administrator

    • 2029


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
./biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance (1.00) less than target UTXO (50000.00)."
}

Looks like it is working, going to have to wait for a few confirmations then I will try again. It is still looking for the right address on "version": 1010006 even though I have enough in my wallet.

As long as 'exec stakebalance' shows 1 then no bug found yet.

It should now spend from any bucket, not just the CPID address, so I think the problem is not enough confirms in your wallet tx as of yet.


See Coin Control to ensure.

EDIT: I sent myself an instantsend this morning, waited 1 confirm and it had 6, and I was able to do a podcupdate.


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Do you show the same mag for Togo Mike?

cat magnitude | grep 9313
<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,291.640,1981221,15044,100,100,277512

Not sure if there was an update but it's not the same.