Bible Pay

TestNet => TestNet Discussion Archive => Topic started by: Rob Andrews on April 30, 2020, 05:16:11 PM

Title: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on April 30, 2020, 05:16:11 PM
June 2020 Release


Welcome to the Biblepay June 2020 Testnet Testing thread.


In this thread we will be testing:


- 'exec price' : XMR price has been added
- Sanctuary Voting :
     (This is the ability for a sanctuary to vote on a spork, and if the Vote outcome is a PASS, the spork will go into effect.  If it is a FAIL we need to see this spork fail to enter into the chain).

- Anti-Censorship-Feature (ACF)  - Although I went through the pain of coding this, releasing it and testing it, I have decided that (as I believe we as a community) will be better off with BiblePay unchained for this use case (as it is safer and does not risk bloating the governance system and the nodes).  So for safetey reasons, I have removed this and now am planning on releasing the design for Unchained.  (This is a sidechain that holds documents off-chain).

- Removing "BiblePay-Evolution" from the windows wallet and fixing the default program directory name (it is still Evolution).  This should go back to BiblePay.  Check to see if the windows installer wizard is correct.

- Test a VendorList change (Charity monero addresses in a semicolon delimited list) and a PoolList change (allowable RX pools).

- Remove POOM from the wallet (remove poom listchildren, poom pay).  Move POOM payment budget from GSC to Heat mined blocks.  Ensure these heat payments go to the heat side and not to the sanctuary.  I believe POOM causes the GSC budget to drop by 240K per day, and the mined block subsidy to rise by 1200~, and the sanc payment should stay the same.

- Any Dash changes that occurred between Jan 1,2020 and March 30th?  Ask MIP?  MIP has made me aware we need a little more time to move up to .15, because Dash has changed 1800 files!  So lets shoot for releasing .15 in September.

- The ability for a RandomX hash to be mined in a more RX compatible way (check to see if foundation.biblepay can receive a blakehash as Solution #1) (This is just a reminder note that may result in a code change in the core wallet if this streamlines the xmrig code to be 100% compatible with the xmrig branch), Checking this.  (This basically frees us from maintaining a special version of xmrig).

->  Great news, I tested pure merge-mining using the plain vanilla xmrig, and it worked.  The changes are in this version already.

- Test Marcus Antonios Russian and Ukrainian Bible viewer(s)


Starting Version:    1.5.1.0+


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

We are at block  ____37650_____ as of May 1st, 2020).

BlockHash 37650:
573935383afc18055f0207355e49262a4243db5705d019506aac153eba5c503e


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


Retiring (do not use these downloads):
     Linux PC 64bits Daemon:     https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz
     Linux 64 bits QT:       https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz






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

__________________________________________________________________________________________________________________________________________________________________________________________





Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: sunk818 on May 01, 2020, 09:35:11 AM
re: xmrig - That is brilliant move if you can pull it off!
Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 01, 2020, 09:52:53 AM
re: xmrig - That is brilliant move if you can pull it off!

I think it can be done at a 95% level - which would still be worth it from our code-merging and maintenance levels for the future (for xmrig).
We will still need to maintain the custom branch though for the final blakehash.  (As that prevents preimage attacks, and keeps biblepays blocks more valuable).

But I still need to test it, working on that today hopefully.

Everyone else:
This thread isn't ready yet because we need to merge in Antonios changes too.

Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 01, 2020, 08:27:04 PM
Welcome back everyone!

I believe we will need at least 6 sancs to test this version as we need to do a few tests on sanctuary spork voting outcomes.

Unfortunately our sancs are totally down in testnet.

Im going to fire up 3 myself, so we only need 3-4 more minimum.

Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: MIP on May 22, 2020, 02:06:39 PM
I have 2 nodes now in block

getblockhash 41364
c99c76f6c56e12f0798ceba43216f2a85ce807e852204496af8616f0e4e008e4

I will promote the one in the vps to sanc in a while


Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 22, 2020, 05:01:20 PM
I have 2 nodes now in block

getblockhash 41364
c99c76f6c56e12f0798ceba43216f2a85ce807e852204496af8616f0e4e008e4

I will promote the one in the vps to sanc in a while

Welcome aboard, my only friend and lone tester (rural chum!)

Yes, hash matches.

I just sent the tBBP u needed and revived my three sancs.  My 3 sancs show as revived.

Time to review all the testnet changes now.


Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 22, 2020, 05:26:40 PM
Welcome aboard, my only friend and lone tester (rural chum!)

Yes, hash matches.

I just sent the tBBP u needed and revived my three sancs.  My 3 sancs show as revived.

Time to review all the testnet changes now.

So first testnet test, and probably the most mission critical is to ensure we can execute Sanctuary Spork voting.

The way this works is, if you for example type 'datalist spork' you will see the current spork values.  Lets take a real live spork:
GETBMSCRYPTOPRICEXMR : Server?action=XMR_PRICE_QUOTE
The spork name is "GETBMSCRYPTOPRICEXMR" and the page it gets its price from is "Server?action=XMR_PRICE_QUOTE" (which provides the midpoint of the price for XMR).
So if I die, the idea is the Sancs should be able to update a current spork (or, vote on a pool change, or vote on a vendor list change).

So if you wanted to execute a change for that spork - we use the pipe delimiter between name and value - to change the spork value to "sx_api_xmr_price" for example you would enter a new proposal with this name:

GETBMSCRYPTOPRICEXMR|sx_api_xmr_price
(Very critical note!  You must change the TYPE to SPORK in the proposal!).


Then if the vote passes, the value of the spork will be updated.

I just added a couple new proposals for new sporks (testspork8 and testspork4).

Give it a few more blocks then once you see them in the proposals please vote on them.

Then we have to wait 48 hours, and then we will see the Spork value change.  Spork votes go for 7 days and we don't honor the outcome for 24 hours (this is to prevent false positives). 


Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 22, 2020, 05:32:36 PM
I have updated the OP post with the rest of the test cases.

Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: earlzmoade on May 23, 2020, 02:31:49 AM
I have been real busy with work, im working at cemetery.

Anyhow i cant help out with the masternodes  but tomorrow i will test out some of the other stuff that you posted Rob and will give some feedback.
Hope all is fine in these times// earlz
Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: earlzmoade on May 23, 2020, 03:26:29 AM
I have been real busy with work, im working at cemetery.

Anyhow i cant help out with the masternodes  but tomorrow i will test out some of the other stuff that you posted Rob and will give some feedback.
Hope all is fine in these times// earlz

PS : It looks like the Testnet download link for windows downloads the older 1.5.0.5 version
Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: MIP on May 23, 2020, 05:30:51 AM
I finally have the sanc online.

Code: [Select]
datalist spork
{
  "DataList": "SPORK",
  "BPL (1-1-1970 00:00:00)": "",
  "CPKDIARYWL (1-1-1970 00:00:00)": "",
  "GETBMSCRYPTOPRICEXMR (05-22-2020 17:18:13)": "Server?action=XMR_PRICE_QUOTE",
  "PRAYERSMUSTBESIGNED (1-1-1970 00:00:00)": "",
  "SLEEP_DURING_EMPTY_BLOCKS (1-1-1970 00:00:00)": "",
  "SPORK43 (05-16-2020 15:19:55)": "SPORK43VAL",
  "SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT (1-1-1970 00:00:00)": "",
  "TEST3 (05-14-2020 16:25:22)": "VALUE3",
  "TESTSPORK3 (05-16-2020 15:19:55)": "TESTSPORKVAL3"
}

I see a couple of SPORK proposals, which I voted for.
I also created the GETBMSCRYPTOPRICEXMR|sx_api_xmr_price, I hope I did it correctly
Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: MIP on May 23, 2020, 05:52:41 AM
Linux 64 bit testnet links are valid again (latest testnet version)

Linux PC 64bits Daemon:     https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz
Linux 64 bits QT:       https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz

 
Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 23, 2020, 03:23:59 PM
PS : It looks like the Testnet download link for windows downloads the older 1.5.0.5 version

Thanks, 10-4 on the cemetary! 
Ok, let me test the windows link.

EDIT:  Yeah, it looks like since we increased the minor version, it is picking up the wrong file during deploy (fixing now...) hang on.

(And I think you are the first to test on windows).


Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 23, 2020, 03:25:13 PM
I finally have the sanc online.

Code: [Select]
datalist spork
{
  "DataList": "SPORK",
  "BPL (1-1-1970 00:00:00)": "",
  "CPKDIARYWL (1-1-1970 00:00:00)": "",
  "GETBMSCRYPTOPRICEXMR (05-22-2020 17:18:13)": "Server?action=XMR_PRICE_QUOTE",
  "PRAYERSMUSTBESIGNED (1-1-1970 00:00:00)": "",
  "SLEEP_DURING_EMPTY_BLOCKS (1-1-1970 00:00:00)": "",
  "SPORK43 (05-16-2020 15:19:55)": "SPORK43VAL",
  "SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT (1-1-1970 00:00:00)": "",
  "TEST3 (05-14-2020 16:25:22)": "VALUE3",
  "TESTSPORK3 (05-16-2020 15:19:55)": "TESTSPORKVAL3"
}

I see a couple of SPORK proposals, which I voted for.
I also created the GETBMSCRYPTOPRICEXMR|sx_api_xmr_price, I hope I did it correctly

Yes, I also voted on these Spork proposals, so far they look good (they have 4 votes).
I also voted on your BMS crypto price; theoretically if it passes, the XMR price will go to zero in testnet (then we can manually fix it again) etc.

Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 23, 2020, 04:11:56 PM
Thanks, 10-4 on the cemetary! 
Ok, let me test the windows link.

EDIT:  Yeah, it looks like since we increased the minor version, it is picking up the wrong file during deploy (fixing now...) hang on.

(And I think you are the first to test on windows).


Ok, the windows download is fixed now.  Please open it from a new incognito window in order to avoid the cache.

Should be 1.5.1.2 now.

Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: earlzmoade on May 24, 2020, 07:44:10 AM
Sweet!

Quote
Removing "BiblePay-Evolution" from the windows wallet and fixing the default program directory name (it is still Evolution).  This should go back to BiblePay.  Check to see if the windows installer wizard is correct.


Biblepay installs correct folder for w10, no more evolution.

Quote
- 'exec price' : XMR price has been added

I tested now in console and looks just fine.

Code: [Select]
14:35:50

exec price


14:35:55

{
  "Command": "price",
  "BBP/BTC": "0.000000019000",
  "DASH/BTC": "0.008088008000",
  "XMR/BTC": 0.0069188835,
  "BTC/USD": 9315.602001499999,
  "DASH/USD": 75.34466351294802,
  "XMR/USD": 64.45356498074533,
  "BBP/USD": 0.0001769964380285
}
Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 24, 2020, 08:44:45 AM
Sweet!


Biblepay installs correct folder for w10, no more evolution.

I tested now in console and looks just fine.

Code: [Select]
14:35:50

exec price


14:35:55

{
  "Command": "price",
  "BBP/BTC": "0.000000019000",
  "DASH/BTC": "0.008088008000",
  "XMR/BTC": 0.0069188835,
  "BTC/USD": 9315.602001499999,
  "DASH/USD": 75.34466351294802,
  "XMR/USD": 64.45356498074533,
  "BBP/USD": 0.0001769964380285
}

Thanks! 
And I see two of the 3 sporks were voted in also - we are just waiting on MIPs (which is normal, because his was entered 1 day after mine).

Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 24, 2020, 08:51:32 AM
I tested these successfully:

- Test a VendorList change (Charity monero addresses in a semicolon delimited list) and a PoolList change (allowable RX pools).
->  Verified a voted in spork change updates the value - therefore the voted in vendorlist change will work in prod:  SUCCESS

- Remove POOM from the wallet (remove poom listchildren, poom pay).  Move POOM payment budget from GSC to Heat mined blocks.  Ensure these heat payments go to the heat side and not to the sanctuary.  I believe POOM causes the GSC budget to drop by 240K per day, and the mined block subsidy to rise by 1200~, and the sanc payment should stay the same.
->  I verified the POOM budget has freed up enough to increase the heat mined block to 4283 in testnet (about 3700 or so in prod, due to difference in deflation start date).  This looks correct.  The sanctuary reward in testnet is now 5678 - I believe this is pretty close (it was 5900 during our prior phase) so its within range.  The poom commands have been removed (listchildren , poom payments, cancel child, etc) and this should be fine - for retiring poom: SUCCESS

- Any Dash changes that occurred between Jan 1,2020 and March 30th? 
-> On hold til September while MIP refactors the wallet.


- The ability for a RandomX hash to be mined in a more RX compatible way (check to see if foundation.biblepay can receive a blakehash as Solution #1) (This is just a reminder note that may result in a code change in the core wallet if this streamlines the xmrig code to be 100% compatible with the xmrig branch), Checking this.  (This basically frees us from maintaining a special version of xmrig).
->  I added code to the foundation pool to operate in a new Mode.  Tested successfully.  This release will require coordinated effort to changes in the pools, the miner and the wallets: SUCCESS


Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 24, 2020, 09:39:16 AM
On the Ukrainian and Russian translations, I tested those after merging (you can see these in QT by navigating to the bible reader by clicking BIBLE on the top horiz. menu) and they were successful, great work Anton!

Does anyone else want to look at them that might be able to read Russian?

Also, if you are up for it please test the command line verse in Russian?

EDIT:
To read a verse from the console type:
exec readverse CO2 10 CN        <- To read in Chinese
exec readverse CO2 10 RU    <- To read in Russian
exec readverse CO2 10 UA    <- To read in Ukrainian

Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 25, 2020, 08:04:39 PM
I tested these successfully:

- Test a VendorList change (Charity monero addresses in a semicolon delimited list) and a PoolList change (allowable RX pools).
->  Verified a voted in spork change updates the value - therefore the voted in vendorlist change will work in prod:  SUCCESS

- Remove POOM from the wallet (remove poom listchildren, poom pay).  Move POOM payment budget from GSC to Heat mined blocks.  Ensure these heat payments go to the heat side and not to the sanctuary.  I believe POOM causes the GSC budget to drop by 240K per day, and the mined block subsidy to rise by 1200~, and the sanc payment should stay the same.
->  I verified the POOM budget has freed up enough to increase the heat mined block to 4283 in testnet (about 3700 or so in prod, due to difference in deflation start date).  This looks correct.  The sanctuary reward in testnet is now 5678 - I believe this is pretty close (it was 5900 during our prior phase) so its within range.  The poom commands have been removed (listchildren , poom payments, cancel child, etc) and this should be fine - for retiring poom: SUCCESS

- Any Dash changes that occurred between Jan 1,2020 and March 30th? 
-> On hold til September while MIP refactors the wallet.


- The ability for a RandomX hash to be mined in a more RX compatible way (check to see if foundation.biblepay can receive a blakehash as Solution #1) (This is just a reminder note that may result in a code change in the core wallet if this streamlines the xmrig code to be 100% compatible with the xmrig branch), Checking this.  (This basically frees us from maintaining a special version of xmrig).
->  I added code to the foundation pool to operate in a new Mode.  Tested successfully.  This release will require coordinated effort to changes in the pools, the miner and the wallets: SUCCESS


The sporks were all updated successfully.

I need to change the exec price (xmr) spork back now, because it makes the client wait for a long time (pointing to an invalid page).  But yes new adds are working, and edits are working.

Title: Re: June 2020 BiblePay Mandatory Upgrade - TestNet
Post by: Rob Andrews on May 31, 2020, 09:12:17 AM
Thank you all for this round of testnet testing!