Bible Pay

Read 100362 times

  • Rob Andrews
  • Administrator

    • 2134


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

Great!  So it looks like you guys have debugged a lot of things in prod and I have not gotten around to feeling prod out yet - or associating a CPID.
Yes, I see you made it in the prod chain with exec datalist dcc, so that is very revealing for others, who have reported today they received that Unable to Sign CPID error.  So guys, if you just associated a CPID, and reboot before the 6th confirm, this is yet another way you could receive the "unable to sign cpid" other than not having enough to stake, or a locked wallet.

As far as upgrading no rush, as long as nothing goes wrong tomorrow, whenever you feel like it.  Im hoping we can form a sanctuary supermajority sometime Wednesday, (thats when the cutover block hits), and then lets not give word for the exchanges to upgrade until *after* we solve our first DC superblock in prod.  (Hopefully that will be Thursday evening).  (We can wait a couple extra days for good measure also).



  • Rob Andrews
  • Administrator

    • 2134


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
** Rosetta Leaderboard Fixed in pool.biblepay.org **

It was an unrelated SQL issue, you should now all see yourselves and your machines, as long as you have not Hidden your machines.

I also made the pool refresh the leaderboard every hour.



  • Rob Andrews
  • Administrator

    • 2134


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
The staking percentage command is suppose to be in the controller wallet config file right?

Yea, and just to clarify the UTXO staking wallet is always the one with the DC association.
You could have a controller for sanctuaries with 10 million in it, and a separate controller with 100K in it with your CPID associations and the unlocked wallet.  The important thing is to put the funds in the one with the association, because that wallet will then know how to loop through your CPIDs Tasks and send the PODCUpdate properly.

On a side note, if you associated 1 cpid on a laptop and then tried to use your home PC as your staking controller it wouldnt send PODC updates because it would not know your CPID list....




  • T-Mike
  • Administrator

    • 398


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

I used the GUI to send some to myself:
Transaction ID: edd8348af06de7463e3f95bf7381736581d4c03a932c3efee6f75b931bc3f974-000

So far haven't got a confirmation. But I did double check that my wallet is unlocked when I ran podcupdate.

UPDATE:
Looks like no confirmations after 13 min.
« Last Edit: March 04, 2018, 10:02:27 pm by T-Mike »


  • Rob Andrews
  • Administrator

    • 2134


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I used the GUI to send some to myself:
Transaction ID: edd8348af06de7463e3f95bf7381736581d4c03a932c3efee6f75b931bc3f974-000

So far haven't got a confirmation. But I did double check that my wallet is unlocked when I ran podcupdate.

UPDATE:
Looks like no confirmations after 13 min.

Looks like exec podcupdate has about 5 possible reasons to return false.   It should log the reason then return false.
So please try 'exec podcupdate' again, then immediately look at the log for the error.

Here is the most likely one:
   LogPrintf("\n PODCUpdate::Failed to Sign CPID Signature.  %s ",sError.c_str());
            

I believe that is happening when you dont have a CPID in the chain as of yet...


NOTE to all users:  You will never need to manually run exec podcupdate under normal circumstances; this is just to force it if your machine was off for long periods of time.


As far as the waiting for confirm:  Check the last block timestamp, its probably a lagging block.

** We just solved 33049; it probably confirmed



  • znffal
  • Full Member

    • 135


    • 7
    • October 02, 2017, 04:01:47 pm
    more
Hi,

One of the Slovakian guys messaged me with an issue. i wonder if we can help. So I think this is the issue he is having:

Linux, commandline

1. He associated CPID to Wallet #1 (W1), he had receiving address RA1.
2. He wanted to change to wallet 2 (W2) with receiving address RA2. He typed
"exec associate mail pass true"
He received the message about welcome to cancer mining
3. The URL on this website https://boinc.bakerlab.org/rosetta/home.php
should be the wallet receiving address.
The URL matched RA2. Perfect!
4. He wasn't sure it had worked so he associated his CPID with wallet 2 again. This time there was a new address created and shown in the  https://boinc.bakerlab.org/rosetta/home.php site.
But he does not recognize the address. It is not RA1 or RA2. I checked, it is also not a mining address.
The question is, should this address on the boinc site be your receiving address of the wallet? Is there an error here?

5. He tried associating it again on another machine in QT mode. It worked fine and the address changed to his receiving address.


Seems that people may have issues if they associate CPID to the same wallet twice (by accident)



  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Looks like exec podcupdate has about 5 possible reasons to return false.   It should log the reason then return false.
So please try 'exec podcupdate' again, then immediately look at the log for the error.

Here is the most likely one:
   LogPrintf("\n PODCUpdate::Failed to Sign CPID Signature.  %s ",sError.c_str());
            

I believe that is happening when you dont have a CPID in the chain as of yet...


NOTE to all users:  You will never need to manually run exec podcupdate under normal circumstances; this is just to force it if your machine was off for long periods of time.


As far as the waiting for confirm:  Check the last block timestamp, its probably a lagging block.

** We just solved 33049; it probably confirmed

The transaction I sent myself is getting confrimations now. The error I'm getting is:

2018-03-05 04:06:47
 PODCUpdate::Error: Insufficient funds.

But there is plenty of BBP in my wallet. Does it have to be under a certain wallet address? This is in production by the way.

UPDATE:
I think the issue might be the receiving address that is associated with my CPID doesn't have enough BBP in it. Trying again now.

UPDATE 2:
podcupdate returned true. I didn't know it was only using a certain receiving address. Thanks guys!
« Last Edit: March 04, 2018, 10:24:51 pm by T-Mike »


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Hi,

One of the Slovakian guys messaged me with an issue. i wonder if we can help. So I think this is the issue he is having:

Linux, commandline

1. He associated CPID to Wallet #1 (W1), he had receiving address RA1.
2. He wanted to change to wallet 2 (W2) with receiving address RA2. He typed
"exec associate mail pass true"
He received the message about welcome to cancer mining
3. The URL on this website https://boinc.bakerlab.org/rosetta/home.php
should be the wallet receiving address.
The URL matched RA2. Perfect!
4. He wasn't sure it had worked so he associated his CPID with wallet 2 again. This time there was a new address created and shown in the  https://boinc.bakerlab.org/rosetta/home.php site.
But he does not recognize the address. It is not RA1 or RA2. I checked, it is also not a mining address.
The question is, should this address on the boinc site be your receiving address of the wallet? Is there an error here?

5. He tried associating it again on another machine in QT mode. It worked fine and the address changed to his receiving address.


Seems that people may have issues if they associate CPID to the same wallet twice (by accident)

I also associated my account to the same wallet twice because I forgot it takes a while before the CPID shows up in the GUI. Oh, I see waht address your talking about now. I wonder if that's why I'm having issues, I don't have enough BBP in that address.
« Last Edit: March 04, 2018, 10:17:55 pm by T-Mike »


  • Rob Andrews
  • Administrator

    • 2134


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I also associated my account to the same wallet twice because I forgot it takes a while before the CPID shows up in the GUI. Oh, I see waht address your talking about now. I wonder if that's why I'm having issues, I don't have enough BBP in that address.

Hmm, I dont think it requires a specific sending address to send funds though - can you instead go into coin control and see how much is available that is not locked?  It could be that all is allocated to sanctuary locked funds?


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Hmm, I dont think it requires a specific sending address to send funds though - can you instead go into coin control and see how much is available that is not locked?  It could be that all is allocated to sanctuary locked funds?

The receiving address that was on the Rosetta website did not have enough BBP in it. Once I put enough in, podcupdate shows true now. I actually had other receiving addresses on my account with BBP in them and none of them were locked except for the sanctuary wallet address.


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
One comment, when I installed the windows wallet, the sanctuaries tab was hidden because of the PODC tab I think. I couldn't find it until I dragged the window larger. Someone new might have some trouble figuring that out. Now it just may be just me on my computer with the desktop configuration I have but I'm not sure.


  • znffal
  • Full Member

    • 135


    • 7
    • October 02, 2017, 04:01:47 pm
    more
Ok I'm about to upgrade my wallet (in prod) to newest version.
Do I need to backup wallet.dat every time I upgrade wallet?

After I upgrade successfully I will transfer the stake to my wallet. Then is it true that my UXTO should be greater than 0?
Is it true that my taskweight will stay 0 until  the first superblock payout?

Thanks :)


  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Ok I'm about to upgrade my wallet (in prod) to newest version.
Do I need to backup wallet.dat every time I upgrade wallet?


I would always backup your wallet.dat, just in case :)
Don't know about your other questions...
« Last Edit: March 05, 2018, 03:23:00 am by jaapgvk »


  • znffal
  • Full Member

    • 135


    • 7
    • October 02, 2017, 04:01:47 pm
    more
I would always backup your wallet.dat, just in case :)
Don't know about your other questions...

thanks :)


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
thanks :)

You only need to backup your wallet once I believe, even if you added new addresses or had transactions after you backed it up.