Bible Pay

Read 166640 times

  • znffal
  • Full Member

    • 129


    • 7
    • October 02, 2017, 04:01:47 PM
    more
Ok I set up a wallet running in qt mode in prod.
I have associated my cpid and it seemed happy.

getinfo gives me

Code: [Select]
"version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 9.05762053,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33038,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 3207.285566212733,
  "testnet": false,
  "keypoololdest": 1507790364,
  "keypoolsize": 1007,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

getmininginfo gives me
Code: [Select]
"blocks": 33038,
  "currentblocksize": 2034,
  "currentblocktx": 2,
  "difficulty_podc": 0,
  "difficulty_pow": 32072.85566212733,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 206993854304.6948,
  "hashps": 86.77371370534651,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 96544,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 169,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false


Are there other commands I should be checking to see weights etc?

EDIT: By the way, my wallet does not yet have a password on it. Is this OK? I assumed this means it is always unlocked for staking...



  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
My TaskWeight and UTXOWeight are 100
but I think its saying my Magnitude is 0?

Code: [Select]
[email protected]:~/biblepay/src$ ./biblepay-cli getinfo
{
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 41951758.00458577,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15493,
  "timeoffset": 0,
  "connections": 16,
  "proxy": "",
  "difficulty": 0.1304545155954208,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422278,
  "NextSuperblockHeight": 15543,
  "NextSuperblockBudget": 1339285,
  "93138f032bdd027fa3246b48bb715a77_RAC": 42468.79,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 42468.79,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 4299843,
  "Total Budget (One Day)": 13392850,
  "Total Budget (One Week)": 79670455,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 60,
  "Superblock List": "15444,15345,15246,15147,15048,14949,14850,14751,14652,14553,14454,14355,14256,14157,14058,13860,13761,13365,13167,13068,12969,12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514,8415",
  "Last Superblock Height": 15444,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 53.97035827145709
}

./biblepay-cli getblockhash 15508
ae40c3edf8874e7a6c78d1a9720d3460a7c9d98d88e28b92cdb02777a136aaca

After Superblock at 15543:

[email protected]:~/biblepay/src$ ./biblepay-cli getinfo
{
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 41963981.79231373,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15551,
  "timeoffset": 0,
  "connections": 17,
  "proxy": "",
  "difficulty": 0.1200567171124102,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422279,
  "NextSuperblockHeight": 15642,
  "NextSuperblockBudget": 1339285,
  "93138f032bdd027fa3246b48bb715a77_RAC": 43224.22,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 43224.22,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 4016960,
  "Total Budget (One Day)": 14732135,
  "Total Budget (One Week)": 79650060,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 60,
  "Superblock List": "15543,15444,15345,15246,15147,15048,14949,14850,14751,14652,14553,14454,14355,14256,14157,14058,13860,13761,13365,13167,13068,12969,12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514",
  "Last Superblock Height": 15543,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 50.43260482164106
}


Wait, I spoke too soon, Ive been analyzing your data ever since I replied, to see if any superblocks have actually been created in testnet over the last few hours while Ive been gone, and actually they have been being created without your 9313* CPID in them... So, yes something is awry with your account.

Let me debug this and get to the bottom of it.  If we need a code change, then thanks for discovering this for us, this is the beauty of having full coverage in testnet.

Don't worry, we will not go live without you, if this is flaw, lets hold the network back until you are in the contract.



  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more

Wait, I spoke too soon, Ive been analyzing your data ever since I replied, to see if any superblocks have actually been created in testnet over the last few hours while Ive been gone, and actually they have been being created without your 9313* CPID in them... So, yes something is awry with your account.

Let me debug this and get to the bottom of it.  If we need a code change, then thanks for discovering this for us, this is the beauty of having full coverage in testnet.

Don't worry, we will not go live without you, if this is flaw, lets hold the network back until you are in the contract.

So Togo, the reason you are missing is your CPID exploited a circumstance not caught in testing:  A circumstance where a researcher is part of team biblepay, then one who is not, then one immediately who follows - a particular flag was not being handled properly causing certain accounts to be skipped. 

Fixed.

We will need everyone + Sancs to upgrade to 1.0.9.8.

Windows is compiling.


« Last Edit: March 04, 2018, 08:39:52 PM by Rob A. »


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more

Biblepay 1.0.9.8
Mandatory Upgrade for Testnet


- Handle Rosetta Teams properly - to avoid CPIDs from being skipped in the superblock

** Windows is compiling **


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Ok I set up a wallet running in qt mode in prod.
I have associated my cpid and it seemed happy.

getinfo gives me

Code: [Select]
"version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 9.05762053,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33038,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 3207.285566212733,
  "testnet": false,
  "keypoololdest": 1507790364,
  "keypoolsize": 1007,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

getmininginfo gives me
Code: [Select]
"blocks": 33038,
  "currentblocksize": 2034,
  "currentblocktx": 2,
  "difficulty_podc": 0,
  "difficulty_pow": 32072.85566212733,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 206993854304.6948,
  "hashps": 86.77371370534651,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 96544,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 169,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false


Are there other commands I should be checking to see weights etc?

EDIT: By the way, my wallet does not yet have a password on it. Is this OK? I assumed this means it is always unlocked for staking...


So this is a very, very good guinea pig test.  After 6 blocks could you please do an 'exec datalist dcc', this is a secret command, see if your CPID is in the list.  I believe the "FAILED TO SIGN CPID Error" is occuring, because you just associated yourself.  Once its in the list try a reboot then check getmininginfo again just to see that the error cleared?

Yes if you are not encrypted, your not locked (lock on the front bottom right GUI overview should be Open), so no it should not be a lock issue....


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Im going to analyze the pool.biblepay.org next for missing users, please, post here if we have any other critical issues that need fixed before the end of the night?




  • znffal
  • Full Member

    • 129


    • 7
    • October 02, 2017, 04:01:47 PM
    more

So this is a very, very good guinea pig test.  After 6 blocks could you please do an 'exec datalist dcc', this is a secret command, see if your CPID is in the list.  I believe the "FAILED TO SIGN CPID Error" is occuring, because you just associated yourself.  Once its in the list try a reboot then check getmininginfo again just to see that the error cleared?

Yes if you are not encrypted, your not locked (lock on the front bottom right GUI overview should be Open), so no it should not be a lock issue....

Awesome, I will do once 6 blocks are gone.
I will not upgrade to new version just yet then


  • togoshigekata
  • Sr. Member

    • 493


    • 25
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Glad I could help a little Rob! Wouldnt be possible without you though 8)

Updating to v1.0.9.8 now


  • znffal
  • Full Member

    • 129


    • 7
    • October 02, 2017, 04:01:47 PM
    more

So this is a very, very good guinea pig test.  After 6 blocks could you please do an 'exec datalist dcc', this is a secret command, see if your CPID is in the list.  I believe the "FAILED TO SIGN CPID Error" is occuring, because you just associated yourself.  Once its in the list try a reboot then check getmininginfo again just to see that the error cleared?

Yes if you are not encrypted, your not locked (lock on the front bottom right GUI overview should be Open), so no it should not be a lock issue....

OK here we go "exec datalist dcc"

Code: [Select]
"DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 00:24:09)": "04fba56d89a5eb38b1b82f8a6240132c;BHUyNiVgRcW4ZudFmyyzJydL9t2QW8fdWD;BHUyNiVgRcW4ZudFmyyzJydL9t2QW8fdWD;1981529;H1MouWGO6yWBk/fQBKp0OTEGApw9FZY5Tnbf8BQz1LujYjQnY/PyPhpd+tjce2vpUhIYaQ/4cxrMF0lfYwg9wSU=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}

I'm sorry, to me it is gibberish.


"getmininginfo"

Code: [Select]
{
  "blocks": 33045,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 0,
  "difficulty_pow": 33728.72968180398,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 228922584200.2176,
  "hashps": 88.14359163965726,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 354736,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 614,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false
}

That error has gone...


"exec getboincinfo"

Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422283,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_RAC": 24261.07,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 24261.07,
  "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

So it looks to be working fine!

Should I upgrade my prod wallet to 1098?

My UXTO weight is zero, but I have only a few BBP (I need to backup wallet first)


  • T-Mike
  • Sr. Member

    • 375


    • 2
    • February 06, 2018, 06:12:58 PM
    more
The staking percentage command is suppose to be in the controller wallet config file right?


  • znffal
  • Full Member

    • 129


    • 7
    • October 02, 2017, 04:01:47 PM
    more
The staking percentage command is suppose to be in the controller wallet config file right?
I have this as my config file for my PoDC wallet (not Sanctuary)

addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network
gen=1
genproclimit=1
polpercentage=50


  • T-Mike
  • Sr. Member

    • 375


    • 2
    • February 06, 2018, 06:12:58 PM
    more
"hashps": 74.40307451385468,
  "minerstarttime": "03-05-2018 02:19:07",
  "hashcounter": 296188,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": false,

I think you said the wallet automatically starts with gen=1 right? So why is biblepay-generate: false


  • T-Mike
  • Sr. Member

    • 375


    • 2
    • February 06, 2018, 06:12:58 PM
    more
How do I debug "PODCUpdate": false? I updated my windows wallet about an hour ago. getboincinfo and getmininginfo both show no errors and the CPID is associated. OR does it say false because my CPID is already in the system?


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
How do I debug "PODCUpdate": false? I updated my windows wallet about an hour ago. getboincinfo and getmininginfo both show no errors and the CPID is associated. OR does it say false because my CPID is already in the system?
It really should only say false if your wallet does not have enough funds to send 1 bbp out, or if its locked.
Could you please try a 'sendtoaddress YYYY 1" to yourself to see if that succeeds?



  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
"hashps": 74.40307451385468,
  "minerstarttime": "03-05-2018 02:19:07",
  "hashcounter": 296188,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": false,

I think you said the wallet automatically starts with gen=1 right? So why is biblepay-generate: false

Right, it starts with 1 thread and generate=true now.  The "generate": = false, thats a bug!  I just fixed it , but it is low priority so it will be in next build.  But yes, it should be running with some HPS, usually about 50 HPS.