Bible Pay

Read 96300 times

  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
It look, that it is just bad "label". It is still not corrected, but after download it is the newest version.

Yes, waiting for Tom (zthomasz) to implement a dynamic label on the website, needs done as a high priority. 



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Okay, interesting. Maybe they changed something on their end, and that's  we we didn't get new tasks for a while.

My phone is on the charger now, so soon I can see if I also get new tasks.
About that: I want to test the 'Associate Unbanked CPID' function on the pool. But of course we are on testnet now. I if switch the pool to testnet (Network>test), will I be able to associate a testnet BBP adres via the Unbanked funtion in the pool?

And my wallets no longer crash at the password prompt  ;D Running smoothly now.

Sweet, so far so good.  On that unbanked feature, I need to release one RPC command in the win version to the wallet the pool uses (it has one more field in the associate result command), but, with the ninja release coming up, I need to merge all the latest changes required for prod into this next version.  Im working on that now.... so heres my game plan:

- Ensure the unbanked feature for the pool is in this next version
- Ready the wallet with a Prod block cutover
- Release this some time today for testing

If all goes well, we can possibly stay on this same version in prod, and sail through the block number.

Ill notify as soon as its ready...  But yes the pool unbanked feature cant be tested until this next windows version is ready.



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
While Im readying this next version will someone please test this:
 Slovakia said on the main thread he cant force a reassociation to a new wallet, he was typing the wrong command:
exec associate email pass force

The command should be:
exec associate email pass true

Anyway will someone please retry association wait 6 blocks then reassociate back using the latest version?

Thanks!


  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
While Im readying this next version will someone please test this:
 Slovakia said on the main thread he cant force a reassociation to a new wallet, he was typing the wrong command:
exec associate email pass force

The command should be:
exec associate email pass true

Anyway will someone please retry association wait 6 blocks then reassociate back using the latest version?

Thanks!

Fired up a testwallet (1.0.9.6.) and tried it:

Code: [Select]
16:34:45

exec associate [email protected] password true


16:34:51

{
  "Command": "associate",
  "E-Mail": "[email protected]",
  "Results": "Successfully advertised DC-Key.  Type exec getboincinfo to find more researcher information.  Welcome Aboard!  Thank you for donating your clock-cycles to help cure cancer!"
}

I will wait a few blocks and reassociate with the old wallet again. Or I can wait to see if I now receive payments with this wallet.


  • capulo
  • Newbie

    • 6


    • 0
    • March 04, 2018, 07:42:39 am
    more
Rob  weve tried with SLOVAKIA and true helped.... we´re trying to understand how it working.... you wrote about command force few days ago for change adminwallet btw....

we was think that this command is for change wallet    exec associate email pass force

Quote
"Results": "Successfully advertised DC-Key.  Type exec getboincinfo to find more researcher information.  Welcome Aboard!  Thank you for donating your clock-cycles to help cure cancer!"
}

thanks for your time  ;)

can i to ask about utxoweight and taskweight... this parameters will be visible after 24hours,right? when adminwallet was close more like 24 hours, podcupdate will be inapplicable?  me and slovakia tried exec podcupdate on mainwallet and we see FALSE

PODC looks amazing




« Last Edit: March 04, 2018, 09:49:59 am by capulo »


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Fired up a testwallet (1.0.9.6.) and tried it:

Code: [Select]
16:34:45

exec associate [email protected] password true


16:34:51

{
  "Command": "associate",
  "E-Mail": "[email protected]",
  "Results": "Successfully advertised DC-Key.  Type exec getboincinfo to find more researcher information.  Welcome Aboard!  Thank you for donating your clock-cycles to help cure cancer!"
}

I will wait a few blocks and reassociate with the old wallet again. Or I can wait to see if I now receive payments with this wallet.


Thanks for helping out!  Its best to double check first, then associate back later.  After you waited 6 blocks after you ran the associate command, here is how we can tell if it worked.  This is a secret command not meant for normal users use, although thinking more about it, it would be nice to add a filter to this command so we can sometimes use this under normal circumstances.  But for now:

exec datalist dcc

Please take a look at the first column, ensure your CPID is only in the list once.  Then look at the 2nd column of the "value" side (thats the semicolon delimited string side), and ensure its associated with the new address.

Once you know that is true, thats what all the nodes know about that CPID.

Then you can reassociate back and wait another 6 blocks and retry the datalist command and ensure its only in there once and its back to your original address.



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Rob  weve tried with SLOVAKIA and true helped.... we´re trying to understand how it working.... you wrote about command force few days ago for change adminwallet btw....

we was think that this command is for change wallet    exec associate email pass force

thanks for your time  ;)

can i to ask about utxoweight and taskweight... this parameters will be visible after 24hours,right? when adminwallet was close more like 24 hours, podcupdate will be inapplicable?  me and slovakia tried exec podcupdate on mainwallet and we see FALSE

PODC looks amazing

Thanks, well he basically said the commands didnt work in the main thread.  Im running out of patience with him, not only is he blaming the software and cant test properly but he cant explain the issue properly. 

Yes, most users never need the force part of the command.  The idea is to associate the rosetta email and password once to a biblepay address, until someday you receive the error "ALREADY_IN_CHAIN" - that happens when you try to reassociate to a new wallet but yet the CPID is already in use.  Thats when you need the force command, so it can forcefully overwrite the old CPID association in the chain (this protects the integrity of the original cpid in most cases from accidents).

So PODC has some dynamic natured programming in it, in that if we receive over 16,384 researchers it can actually adjust to the influx, and the timing of UTXO weight and Task weight can adjust dynamically, but for all intents and purposes for now, we are looking for a PODC update once every 24 hours - that will refresh one researchers given UTXO weight and Task weight for up to 24 more hours.  The Sanctuaries check the tasks integrity and determine the Task weight.  The UTXO weight is determined by the amount staked by the controller wallet.  Btw, also see the charts for task weight and utxo in the wiki page.  Im sure I have not answered your question yet, give me a minute.



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Just wanted to give everyone a heads up, Im going to be forced to upgrade the mandatory sanctuary protocol version up to 70716.

Primarily because when we go live with the mandatory, we are going to need to force every Sanctuary to upgrade to 70716, otherwise they are not acting properly in the quorum.

This means I am also forced to increment the required Payment Protocol version to 70716, meaning Sancs wont be paid if they do not upgrade.

This will most likely break compatibility for all testnet sancs also, (as the code cannot discern between testnet & prod sanc versions, its just not possible at this time), meaning that for the short period of testing, we will need to upgrade some of our hot sancs to 70716 also.

So keep that in mind, and don't jump to the conclusion that we broke everything, we will need to verify we have a supermajority on 70716, verify everything works, then release the mandatory (sometime Wednesday).

It should be ready for testing within 1 hour...



  • capulo
  • Newbie

    • 6


    • 0
    • March 04, 2018, 07:42:39 am
    more
we askin you cos this:

our adminwallet running w/mistakes,bugs = we have 1testnet machine with SLOVAKIA....

and we checked today our adminwallet and from 1.3.2018 didnt receive PODC PAYMENT, we dont know whats wrong ... utxo+task was 0 on both

weve tried EXEC PODCUPDATE and received FALSE still ...


now,we change adminwallet to windows from linux.....


edit:// we can go to update our linux+windows masternode now
« Last Edit: March 04, 2018, 10:08:49 am by capulo »


  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more

Thanks for helping out!  Its best to double check first, then associate back later.  After you waited 6 blocks after you ran the associate command, here is how we can tell if it worked.  This is a secret command not meant for normal users use, although thinking more about it, it would be nice to add a filter to this command so we can sometimes use this under normal circumstances.  But for now:

exec datalist dcc

Please take a look at the first column, ensure your CPID is only in the list once.  Then look at the 2nd column of the "value" side (thats the semicolon delimited string side), and ensure its associated with the new address.

Once you know that is true, thats what all the nodes know about that CPID.

Then you can reassociate back and wait another 6 blocks and retry the datalist command and ensure its only in there once and its back to your original address.

Glad to be of assistance!

My CPID is listed only once and is associated with the new address :)

Code: [Select]
17:02:19

exec datalist dcc


17:02:19

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (02-28-2018 18:57:43)": "04fba56d89a5eb38b1b82f8a6240132c;yfvTaGZakXWsLqyTCSZRG3kqabY6WYhFym;yfvTaGZakXWsLqyTCSZRG3kqabY6WYhFym;1981529;H3TE1ocsh4C0LjTdPyiGi2REXCFYBDyMogAJAO4IBD2eLeT1xmxwdjyfJ8s+Fl3Tn7KqEffHcJLS/G9l4BEP/Q0=",
  "4B7D2D64C88B32927A21AD20A57868E4 (02-27-2018 04:53:55)": "4b7d2d64c88b32927a21ad20a57868e4;yhwRCipWmkGncgFMp9hK2v92pSEKnqHWj2;yhwRCipWmkGncgFMp9hK2v92pSEKnqHWj2;1985935;INgDBUp1XVgjxa5vkADf9cXP20NOQ7MNyMJRCqYlgr7KYcHwu0vdjsZjVWqpgYmgUn44Lq1jJaZnJA3p1TXfwMw=",
  "4FD1BF6C6900D92B226E16C6A6935661 (02-19-2018 22:01:42)": "4fd1bf6c6900d92b226e16c6a6935661;yWQfYmBCAQrcn9RkjM9DJwWGfgjHdvpZwn;yWQfYmBCAQrcn9RkjM9DJwWGfgjHdvpZwn;1981544;H2x6mg4cutmIdtLMbt0tA3QDJt2sFoAzJi50YzkGHd5mfJlDmgMNj7dQCGVJR3lKw6808qr8aMyOJdA69+Aqacg=",
  "6785DED1F65063EF8F01F42DEB31CF1D (02-20-2018 00:22:34)": "6785ded1f65063ef8f01f42deb31cf1d;yQj1rFpeMbaWJ9dNBGrYLoZ1YZdV5zQ9Qr;yQj1rFpeMbaWJ9dNBGrYLoZ1YZdV5zQ9Qr;1981965;IIKcfM2lOlykKDslRzCfZ94QR6R82VAC1rtvV8anwBW0exp3SxWD6x5NejDKuSwfekjv+J0sd7L75Hv+dlYy1AU=",
  "71F1F1F46DEB2F25961C7D9AF06F2B31 (02-19-2018 21:39:32)": "71f1f1f46deb2f25961c7d9af06f2b31;yWR4LS4qTQJnE9FiYGJPdfFDSWfv62gNNd;yWR4LS4qTQJnE9FiYGJPdfFDSWfv62gNNd;1981959;H7PHD0KXvbJpnnr8k/38jDJpRHMlOpFafuXuwMQuQNc2cwMqZdkSdhdNMfjB9ULE8fwJYoiZfAvAyk+HVwEg8H8=",
  "8735CFE64D964416DBA6015EB414CF7E (02-20-2018 02:48:50)": "8735cfe64d964416dba6015eb414cf7e;yXnQ21gKRh1t5vMr4jKbGHSSJkMeXc8R5o;yXnQ21gKRh1t5vMr4jKbGHSSJkMeXc8R5o;1981648;H3Hxm+K0Gx6KuKpXV5RuIUTf7BGNd/2EBdFGOIF6qt//CFwBvti8069t8GtIhvCX+kZA84QDEsenhJzgo53dz40=",
  "93138F032BDD027FA3246B48BB715A77 (02-19-2018 18:11:22)": "93138f032bdd027fa3246b48bb715a77;yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc;yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc;1981221;H9fC303lsYACiELVZejQeZA2m1RK+N9WVeH+mLDMIRI9AbgRVtF1pRz18fY8J6bxDgSf9cIx4Ub39sVwZX43dqY=",
  "95A79CD5829E8315B0B946709930DF18 (02-19-2018 21:45:46)": "95a79cd5829e8315b0b946709930df18;yggudABrHvV5vuKZnnsdWPfjcJ7vApijdF;yggudABrHvV5vuKZnnsdWPfjcJ7vApijdF;1981963;ICuPmhSRKXo5Uftd+KG+V8HfY8IktQCAfD2SaSizkjoZJzdn5B6pnAma6ie/BtwhShMgWs5I2bgWa1dST4MVF+E=",
  "C852DA1A620AD630B70C8EC1CCDEE366 (02-27-2018 08:46:06)": "c852da1a620ad630b70c8ec1ccdee366;ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv;ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv;1985966;IMfOvAS2bWCb6RqYQwbh6Jkur8zBres4HVkFMgZXPVCuBSgtwD7YrfQH2zbWBspnbrTzuQLxsf+5TqZ9H/dkE+s=",
  "C9085154B7CC0CA2B5189672559DD6D8 (03-01-2018 16:58:03)": "c9085154b7cc0ca2b5189672559dd6d8;yNeXHaws4KRpEfuaDT6sjQWvomFTfALZWU;yNeXHaws4KRpEfuaDT6sjQWvomFTfALZWU;1084150;IE1yZ8x8MM6QYOU9n76qEkdBfRWWzkvbvrBi1s+2d9GAcdk4JOOhSV3RHViVRanTrQhViavub6L9ycbAZlfCQQI=;1",
  "CA895B47AACFFBDBF906201821AF2F9F (02-19-2018 15:43:50)": "ca895b47aacffbdbf906201821af2f9f;yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb;yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb;475629;H1C+xdEuI73ipUtnvqIcJz7V1ohM2e9KrhEl0TtcZvQjT+WI5lZ0IeiZvzKvv+6P7QUfKiAmx99rArTgrOyS8jA=",
  "CC37D0EF74A621379974484F43D3B1C5 (02-19-2018 21:47:10)": "cc37d0ef74a621379974484f43d3b1c5;ya4AtNH78Q2px2iQyewG6fvpctFzLZMnVR;ya4AtNH78Q2px2iQyewG6fvpctFzLZMnVR;1981964;H88UWU+ZPMh5aQr6k4d3QmJ+Cmr9Cr8HLRm6TPiGi1gDSvyHdFaulR/gAoktaPT6BCoHH3l75b0pXbH3nRz5Tmk=",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-04-2018 15:35:56)": "d9b22fccfae5582d4ee7838883aaa3cf;yhW1cbeQeNvVZaGJuqNkKCMzPkQGs4J6fg;yhW1cbeQeNvVZaGJuqNkKCMzPkQGs4J6fg;1981615;IOc9ei8QtgBjRXpc6UMyHc4Y2W7EFIvc3oghnSNkM8KxMdHJilis79qS0PliV9Pyhr9lcSdENaZaUzazs+3C4wU=;0",
  "DDE30F3EF57ED2DF69ECBC687DB75E46 (03-04-2018 15:24:18)": "dde30f3ef57ed2df69ecbc687db75e46;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;1982089;IG5f8Wv8SuXsay+7CNqRXrI0fyVbgBMKtA5fDOb3zS6iaXAkNLQhVDqNKgdv2238AV0AWHUYJFTPQQ6rCJ1X0IE=;0",
  "E6CE50042187D4B285568D86EF458F32 (02-24-2018 19:20:38)": "e6ce50042187d4b285568d86ef458f32;yjSv5YRA1tmBAYtkqpoZJELnKLhKpC1vGY;yjSv5YRA1tmBAYtkqpoZJELnKLhKpC1vGY;1985116;IIQRXbG0I6lryqqKHh/d6DQYCC5LechhP+yadz8OeNNYF1o44mIUQhWAQZ4WVB2o4VpKu3hxh7W/UBseeIyALPA=",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7 (02-20-2018 16:56:53)": "e7ae6abd6284b05f3fd5f7c780e60bc7;yanQXohgWcygJznMn8NGs3yrA77MFXTLAy;yanQXohgWcygJznMn8NGs3yrA77MFXTLAy;1981355;IAdgY+TLxFKwsnOWPEhp/gdLa+FiPQiug6lH56AYxxu/Ec7zkH4aFkO5ynsNbOSBVJHJNLZCTThvGNz36aT84oY=",
  "E94C1704C75F731F8BFDE303F08408EE (02-19-2018 20:01:17)": "e94c1704c75f731f8bfde303f08408ee;yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84;yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84;1981209;H1tzerdJv8Ot1f2dQG23Jl30pG7LLhktLbOBCls64h91XqmmQq3lFex3jR7+E98KOa/wibJ/FCrOSkZhPEWr6bw=",
  "F80AB050AB53459EC937879A046D603E (02-19-2018 21:43:10)": "f80ab050ab53459ec937879a046d603e;yV6DCWkg9pmbLhCYwZM8jiEd9dNgvQGEZx;yV6DCWkg9pmbLhCYwZM8jiEd9dNgvQGEZx;1981962;H4qaxt5D8Mo2qb/NPbRXouMT+5hQBCdnuz0rzq56XBLmAUI1dZr/Ck70rgI5LIv8vK1u2EMiuzSUo7tLQjYc2PY="
}


(my CPID is d9b22fccfae5582d4ee7838883aaa3cf btw)


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Rob  weve tried with SLOVAKIA and true helped.... we´re trying to understand how it working.... you wrote about command force few days ago for change adminwallet btw....

we was think that this command is for change wallet    exec associate email pass force

thanks for your time  ;)

can i to ask about utxoweight and taskweight... this parameters will be visible after 24hours,right? when adminwallet was close more like 24 hours, podcupdate will be inapplicable?  me and slovakia tried exec podcupdate on mainwallet and we see FALSE

PODC looks amazing

Yes, if the controller wallet was closed > 24 hours, podc updates have lagged and fell out of the visibility window, so the researchers utxo weight = 0 and task weight = 0, when you type 'exec getboincinfo' you should see that problem.

As far as 'exec podcupdate' that will force a PODC update forcefully, then you can see the results in 6 blocks.

If you receive 'false', that usually means the wallet is encrypted & locked, or has no funds in it.  PODC updates cost about .01 BBP (for miner tx fees).




  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
we askin you cos this:

our adminwallet running w/mistakes,bugs = we have 1testnet machine with SLOVAKIA....

and we checked today our adminwallet and from 1.3.2018 didnt receive PODC PAYMENT, we dont know whats wrong ... utxo+task was 0 on both

weve tried EXEC PODCUPDATE and received FALSE still ...


now,we change adminwallet to windows from linux.....


edit:// we can go to update our linux+windows masternode now


Please initialize PODC, set this up yourself, check it personally then post back.  These lines above are incomprehensible to me. 


  • capulo
  • Newbie

    • 6


    • 0
    • March 04, 2018, 07:42:39 am
    more
and here is problem what SLOVAKIA tried asking you

we have 8M tBBP in wallet and testnet wallet is unlock
on running adminwallet utxo+task droped to 0 and PODCUPDATE doesnt unresponsive : response : FALSE

exec podcupdate helps when is admin wallet close 24+ hours?


this is us
"DDE30F3EF57ED2DF69ECBC687DB75E46 (03-04-2018 15:24:18)": "dde30f3ef57ed2df69ecbc687db75e46;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;1982089;IG5f8Wv8SuXsay+7CNqRXrI0fyVbgBMKtA5fDOb3zS6iaXAkNLQhVDqNKgdv2238AV0AWHUYJFTPQQ6rCJ1X0IE=;0",


« Last Edit: March 04, 2018, 10:14:49 am by capulo »


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
and here is problem what SLOVAKIA tried asking you

we have 8M tBBP in wallet and testnet wallet is unlock
on running adminwallet utxo+task droped to 0 and PODCUPDATE doesnt unresponsive : response : FALSE

exec podcupdate helps when is admin wallet close 24+ hours?


this is us
"DDE30F3EF57ED2DF69ECBC687DB75E46 (03-04-2018 15:24:18)": "dde30f3ef57ed2df69ecbc687db75e46;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;1982089;IG5f8Wv8SuXsay+7CNqRXrI0fyVbgBMKtA5fDOb3zS6iaXAkNLQhVDqNKgdv2238AV0AWHUYJFTPQQ6rCJ1X0IE=;0",


Can anyone help Capulo?

Capulo, Im going to delete the messages if they are not comprehensible.



  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more

Can anyone help Capulo?

Capulo, Im going to delete the messages if they are not comprehensible.

Sure... I'll give it a shot via private messages.