Bible Pay

Read 1855 times

  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
September 2020 Release


Welcome to the Biblepay September 2020 Testnet Testing thread for POOS!


In this thread we will be testing:

- POOS (Proof of Orphan Sponsorship):
     Verify the Sanctuary Owner may Sponsor a Cameroon-One Orphan (by associating this Orphan with the Sanctuary public key)
     Verify the legacy POSE ban system still POSE bans a node for lack of service
     Verify the POOS ban system will increase the ban for non-paid orphan accounts
     Verify the POOS ban system will decrease the ban once the orphan is paid for
     Verify the sanctuary cannot revive itself unless they pay the amount owed first

- Coin-Age voting:
     Verify you can vote from the Proposals UI by right clicking a proposal and voting with coin-age
     Verify you can increase the default (configurable) coin-age percentage using the biblepaytest.conf key value
     Verify the voted tally shows the correct coin-age and distinct sum of users who voted
     Verify we can vote with coin age from the RPC

- ChainLocks and DIP0008:
     Verify that testnet LLMQ quorums are forming, and advancing
     Verify testnet LLMQ locked IX transactions occur automatically, and quickly (IE test autolocks)
     Verify chainlocks locks the block (getblock hash, verify when entire block is IX locked, then it is also chainlocked)

- APM (Automatic Price Mooning)
     Verify the subsidy is 7 if an APM decrease event occurs day-over-day
     Verify the subsidy is normal if the price is unchanged, or if the APM increase event occurs day-over-day

- DWS (Dynamic Whale Staking)
     Verify the 'dws' and 'dwsquote' commands work as dedicated commands.


Additional Testing for BiblePay Unchained - added on August 6th:
First, read this guide:
https://wiki.biblepay.org/Using_Unchained


- BIPFS (Biblepay IPFS)
     Test exec bipfs_file (Upload a file into unchained).  Once the file is uploaded, verify the price, the duration, the density, and that you can navigate to the URL.
          (Verify both large and small files).
     Test exec bipfs_folder (Upload a folder into unchained).  Verify the price, duration, density, and a few URLs from the upload.
     Test uploading an encrypted file, retrieving the encrypted file (with exec bipfs_get), and re-opening the encrypted file.  Test it with a bad password also.
     Test exec bipfs_get (Download a file).
     Verify the sidechain sync height (Info Sidechain Sync Blocks).
     Verify bipfs_list (the uploaded file is now in the sidechain).

- BIPFS C# Client
     Test file upload and folder upload in the c# client.  Verify the file density, duration, and URL result, and download the asset from the URL.
     Verify the charge amount and the TXID was charged to the payment source (via API-KEY method).
   
- DWS UI
     Verify you can make a DWS burn from Send Coins Entry (these burns are always 90 days).  Verify the Quote works.


- Verify Monthly Budget changes:
     Verify as of block 55720, the sanctuary payout is 8.75% higher and the monthly governance budget is 8.75% lower












NOTE:
Most likely you will need to recreate your sanctuary, unless you see your sanctuary is POSE banned.  In that case you can revive the sanctuary with 'exec revivesanc'.


Starting Version:    1.5.1.7+


(Please ensure your version is greater than this, otherwise your testnet branch will not sync. 

We are at block  ____52500_____ as of July 21st, 2020).

BlockHash:
getblock 52500   "hash": "12287aa66bb3e29c354b276aa1738efcf93ea031c8b57d9e17ea6242252604f1"



Testnet Download Links:


Ready:
     Windows 64-bit:      https://biblepay.org/biblepayevo64develop.exe
     MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg
     Linux 64 bits II (QT/biblepayd/biblepay-cli) zip:  https://biblepay.org/bbp-lin-develop-64.zip


To self compile:
https://github.com/biblepay/biblepay/blob/develop/BuildBiblePay.txt





CONFIGURING FOR TESTNET:


Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepay



Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepay/testnet3 folder.


NOTE: This version will also work side-by-side our production nodes,
so, you also have the option if you are short on machines, to run TestNet side by side a prod node!

To run a TestNet Sanctuary:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

__________________________________________________________________________________________________________________________________________________________________________________________



« Last Edit: August 06, 2020, 09:53:07 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Ok, this version is ready for testnet.



  • oncoapop
  • Full Member

    • 142


    • 14
    • October 23, 2018, 12:31:17 PM
    more
Ok, this version is ready for testnet.

Hi Rob. Sorry for the absence. I have synced my sancs but unable to revive them
error code: -2
error message:
Safe mode: Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade.

Even though they are all on the correct blockhash
cli getblockhash 52500
12287aa66bb3e29c354b276aa1738efcf93ea031c8b57d9e17ea6242252604f1



  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Hi Rob. Sorry for the absence. I have synced my sancs but unable to revive them
error code: -2
error message:
Safe mode: Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade.

Even though they are all on the correct blockhash
cli getblockhash 52500
12287aa66bb3e29c354b276aa1738efcf93ea031c8b57d9e17ea6242252604f1

Hi bro-
Good to have a helper here in testnet make this release a success.
To make this easier on us, I have 4 sancs going also.

Also, in testnet, we have a quorum of 5 with 2 or more signers required (for llmq) so we should be able to test everything positively, including chainlocks.

So first you appear to be close to set up properly since you have the right hash.

Lets get rid of the safemode warning first.  Please restart the wallet, then look at any peers in the peers list that have a height of less than 52500 and ban them, then your safe mode should go away.

Let me know why you cant revive a sanc - you should get an error message.

If its code -25, that means 'unpaid POOS'.  If its 25, let me know what the sanctuary public key is for the sanc you try to revive - you can find it by double clicking on the sanc.

In testnet Im temporarily acting as cameroon-one.  Of course in prod, they will completely take over because in prod we will use their domain name.  In testnet we use foundation.biblepay.org for POOS.




  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Hi bro-
Good to have a helper here in testnet make this release a success.
To make this easier on us, I have 4 sancs going also.

Also, in testnet, we have a quorum of 5 with 2 or more signers required (for llmq) so we should be able to test everything positively, including chainlocks.

So first you appear to be close to set up properly since you have the right hash.

Lets get rid of the safemode warning first.  Please restart the wallet, then look at any peers in the peers list that have a height of less than 52500 and ban them, then your safe mode should go away.

Let me know why you cant revive a sanc - you should get an error message.

If its code -25, that means 'unpaid POOS'.  If its 25, let me know what the sanctuary public key is for the sanc you try to revive - you can find it by double clicking on the sanc.

In testnet Im temporarily acting as cameroon-one.  Of course in prod, they will completely take over because in prod we will use their domain name.  In testnet we use foundation.biblepay.org for POOS.


I made biographies for the 6 sancs that are POOS banned in testnet.

So please try to revive now.



  • Rob Andrews
  • Administrator

    • 2854


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

I made biographies for the 6 sancs that are POOS banned in testnet.

So please try to revive now.


Also guys if you could please test at least one wallet per distinct test user from the biblepay-QT wallet, so we can test the main GUI features, thanks.



  • oncoapop
  • Full Member

    • 142


    • 14
    • October 23, 2018, 12:31:17 PM
    more

I made biographies for the 6 sancs that are POOS banned in testnet.

So please try to revive now.

Sancs are synced and revived. There are 7 enabled sancs on testnet now.


  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Sancs are synced and revived. There are 7 enabled sancs on testnet now.

Ok great, lets start by pretending you paid for the first month and just fell behind on payments to cameroon-one.

Please give me a couple sanctuary public keys so I can put your bios in non-payment mode.



  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Sancs are synced and revived. There are 7 enabled sancs on testnet now.

Another test we can start doing - coin-age voting.
In coin-age voting, we let the average user, not the sanctuary, place a vote on a proposal.  This lets us see the total-coin-age voted, and the total distinct user votes.

For example, lets say 5 regular users voted FOR a proposal, and each had 1 mil in coin age.  The total would be +5 FOR, 0 Against, and +5 MM coin-age in the "FOR" bracket.

To vote, please right click the proposal from your regular wallet (NOT from the sanctuary).


I entered a proposal called Bikers For Jesus.  Please go ahead and vote as a regular user and then check it after 3 blocks to see if the two totals incremented?




  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
In testnet we have LLMQ autolocks turned on (this allows 10 second confirmations) and we have LLMQ Chainlocks on.

Lets test autolocks - please send a tithe to the foundation (just click Donate to Foundation), but ensure Instant Send is off.
See if the little Key appears within 10 seconds after you send it in the tx list.

Then after its in a block you can type 'getrawtransaction txid 1' and just see if both the chainlock and the Instant Send autolock is true?

This is going to allow us to then test chainlocks (as we do NOT have this feature turned on in prod, due to a probblem with dip008 in prod).  This will be great once we confirm this works 100%, as then we can turn on faster tx and more secure Chainlocks in prod.  Our prod environment has an LLMQ issue because of dip008 which we need to iron out here in testnet for September.



  • oncoapop
  • Full Member

    • 142


    • 14
    • October 23, 2018, 12:31:17 PM
    more
Ok great, lets start by pretending you paid for the first month and just fell behind on payments to cameroon-one.

Please give me a couple sanctuary public keys so I can put your bios in non-payment mode.

My 3 that are enabled
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.108.63:40002
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.116.179:19998
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 45.62.240.90:19998


  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
My 3 that are enabled
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.108.63:40002
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.116.179:19998
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 45.62.240.90:19998

Ok, I made your 89c* sanc and your 07ba* sanc as if you didnt pay, so now you should see the POOS level increase.
Btw, you can see your sanctuary POOS level in the QT wallet - in the Sanctuaries UI.

You should then start receiving only 1 bbp for those two sancs.

EDIT:  I just made the biblepayd (non-qt non-gui wallet) also show the POOS level in 'masternodelist full' - this will be in the next release, but its not a high priority to get it out yet (until we find a bug, etc).

« Last Edit: July 22, 2020, 04:59:35 PM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
1.5.1.8-Mandatory Upgrade for TestNet

- Add POOS ban level to masternodelist full
- Fix bug in APM calculation
- Add APM narrative banner to the overview page


  • oncoapop
  • Full Member

    • 142


    • 14
    • October 23, 2018, 12:31:17 PM
    more
Ok, I made your 89c* sanc and your 07ba* sanc as if you didnt pay, so now you should see the POOS level increase.
Btw, you can see your sanctuary POOS level in the QT wallet - in the Sanctuaries UI.

You should then start receiving only 1 bbp for those two sancs.

EDIT:  I just made the biblepayd (non-qt non-gui wallet) also show the POOS level in 'masternodelist full' - this will be in the next release, but its not a high priority to get it out yet (until we find a bug, etc).

1. "613535d6ea651c5b5c3c224ab782409da6a873b8c10dda3216c6da9a6098f7de-1": "       POSE_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595486691  52832 45.62.240.90:19998",
Result of update: (initially updated, tried again and this is the second result. Sanc
  "service": "45.62.240.90:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned")
error code: -26
error message:
18: protx-dup


2.   "7392277be75eac0b90f2faea5a023565d1b408ecc045a17074d49bc227532a60-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595467363  52785 104.167.116.179:19998",
Result of update:
error code: -25
error message:

3.  "900c710e527cd634ca2c0e3d30d8f0a9983f0b8a5b93964adb1b8a7f5902b034-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595468292  52786 104.167.108.63:40002",
Result of update:
error code: -25
error message:

Note the error messages on the sanc themselves
BiblePay Core RPC client version 1.5.1.8
> sanc status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "104.167.116.179:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned"
}

Don't know reason for ban - mandatory upgrade (POSE) or POOS when queried from sanc itself.


  • Rob Andrews
  • Administrator

    • 2854


    • 44
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
1. "613535d6ea651c5b5c3c224ab782409da6a873b8c10dda3216c6da9a6098f7de-1": "       POSE_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595486691  52832 45.62.240.90:19998",
Result of update: (initially updated, tried again and this is the second result. Sanc
  "service": "45.62.240.90:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned")
error code: -26
error message:
18: protx-dup


2.   "7392277be75eac0b90f2faea5a023565d1b408ecc045a17074d49bc227532a60-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595467363  52785 104.167.116.179:19998",
Result of update:
error code: -25
error message:

3.  "900c710e527cd634ca2c0e3d30d8f0a9983f0b8a5b93964adb1b8a7f5902b034-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595468292  52786 104.167.108.63:40002",
Result of update:
error code: -25
error message:

Note the error messages on the sanc themselves
BiblePay Core RPC client version 1.5.1.8
> sanc status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "104.167.116.179:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned"
}

Don't know reason for ban - mandatory upgrade (POSE) or POOS when queried from sanc itself.

Note that any time we have a mandatory upgrade, all sancs that are part of the current quorum will end up getting POSE banned.  This also happens if all of us have our miners shut off.  Yesterday for example I had a power outage here and no one was mining for about 4 hours, so we had a lot of members of the quorum get pose banned. 

Today, I have a single thread miner running on one of the sancs - so theroetically none of us that are at the 0 ban level should increase.  Im going to be watching that.

I see your sancs:  104.167.116.179, and 108.63 are both POOS banned.  The way you can tell if you are POOS, or POSE, or both is:  700=POOS, 100=POSE, 800 = BOTH.
I see your two POOS banned sancs are both POOS+POSE banned (thats good) because they didnt pay their theoretical orphanage bill.

Ill set 104.167.108.63 as PAID now: OK 63 is paid.  Please revive it now.

Thats good you got the code -25 earlier, when trying to revive the POOS banned sancs.  Thats correct, people cant revive them unless the bill is paid first (this keeps people from slipping in and out and getting half paid by sending 15 revivals per month and tricking us).

Yes, I see you revived 45.62.240.90 earlier.  Good.  The "protx-dup' just means you sent a duplicate revival tx before the network fully processed the other one.  That doesnt hurt anything.  I think it takes about 2-3 confirms for us to all see the revival occur.

So far this test case (for cameroon one orphan-banning vs revival) has passed for me and for you.

Let me know if you have problems testing the test cases I posted in the OP post.

I dont know if you run the QT wallet or not.

On a side note, do you like the idea of POOS?  Didnt see any comments about it in the POOS thread.  How do you feel about sanc owners paying for an orphan?



« Last Edit: July 25, 2020, 01:52:04 PM by Rob Andrews »