June 2022 - TestNet Release - Exodus

June 2022 Release - Exodus



Welcome to TestNet - Exodus!



Testing commences: April 1st, 2022
Testing Ends: June 2022



In this thread we will be testing:

- Dash 0.17.2.2+ changes:

- POVS (proof-of-video-streaming)

- Verify emissions for core subsidy, daily governance, and monthly governance

- Time Locked Trusts

- View sanctuary streamed video(s) from user perspective and sanc operator perspective

- BBP Drive



Explain Changes to Entire BiblePay Network:   

- Explain transition from POOS to POVS

- Explain usage instructions from customer and user perspective



Wiki Articles:

Time Locked Trusts:
https://wiki.biblepay.org/Time_Locked_Trust

Create a Sanc:
https://wiki.biblepay.org/Create_Sanctuary

BBP Drive:
https://wiki.biblepay.org/BBP_Drive

Installing BMS:
https://wiki.biblepay.org/Install_BMS




Starting Version:    0.17.2.2:

(Please ensure your version is greater than this, in order to sync.  See post #2 for current hash.


Testnet Download Links:


Ready:
     Windows 64-bit:      https://biblepay.org/biblepaydevelop-1.exe
     Linux 64 bits II (QT/biblepayd/biblepay-cli) zip:  https://biblepay.org/bbp-lin-develop-64.zip
     (not ready - inquire first) MacOS QT: https://biblepay.org/biblepay-harvest-develop.dmg


To self compile:
git pull origin develop

https://github.com/biblepay/biblepay/blob/develop/BuildBiblePayDevelop.txt


TODO during release:
Move Mobile Endpoint for mobile wallet unchained:
From foundation.biblepay.org to         https://unchained.biblepay.org/BMS/MobileAPI






CONFIGURING FOR TESTNET:

Create a biblepaytest.conf file with the following contents:
testnet=1
(optional:  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: If you only have one machine, you can run in testnet side by side a prod node.

To create a TestNet Sanctuary:

https://wiki.biblepay.org/Create_Sanctuary

__________________________________________________________________________________________________________________________________________________________________________________________



                                                                   OUR BIBLEPAY CORE TESTERS



#1 - Earlz 

#2 - Pat Buckley

#3 - Rob Andrews

#4 -

Welcome back everyone (our original thread was destroyed).

Good block hash:
18:59:12
getblockhash 142700
18:59:12
539f1b8c495a568e4dcb69ae817679e4b5f53e4ef2ccba78f030543fe5ae6316


So far we had Earlz test TLT, and he tested a maturity date ending in the past successfully.  I tested one past (and was able to spend) and one future (and was not to spend).
Then we added an error message preventing a user from spending early (so they dont get stuck with needing to do zapwallettxes=1).


One thing you guys can jump on testing:  You can test BBP drive.  That's documented in the wiki in the OP post.

Mornin!

One thing you guys can jump on testing:  You can test BBP drive.  That's documented in the wiki in the OP post.

Hey Rob could you update the BBP drive wiki when time , its still not restored.

Thanks.

Mornin!

Hey Rob could you update the BBP drive wiki when time , its still not restored.

Thanks.

Sure, I apparently saved it with an underscore this time.  I just updated the OP post.  Thanks.

Test case for MainNet subsidies:

Boot up into mainnet using exodus, verify chain is synced: PASS
Verify the daily block reward (nextdailylimit) using getgovernanceinfo has increased to ~325K (for UTXO staking rewards): PASS
Verify the block subsidy for RX miners and Sancs has increased to approx 4400: PASS
Verify the monthly governance budget has increased to 10% of block emission for orphan charity (it was approx 4MM and the total was about 6.75MM including non charity expenses) : PASS

Test Case for TLT (Time locked Trust):

Download time locked trust and install it.
Verify the user can create a mainnet or testnet TLT keypair by generating a trust: PASS
Save the trust to a file and read the trust in notepad - does it look correct? : PASS
Generate one TLT trust in the past (March 2022), and one in the future (May 2022) for testnet : PASS
Boot biblepaycore and import the keys (importprivkey privkey) for each of the TLTs: PASS
Edit the names of the keys (I named one March-2022-TLT and another May-2022-TLT)
Now fund each wallet with 5K
Now try to spend from the March 2022 wallet : PASS (I was able to spend it)
Now try to spend from the May 2022 wallet: PASS (I was NOT able to spend it)
In unit test, verify the new error appears preventing the spend : PASS

Test case for BBP Drive:

Navigate to BBP Drive github from op post.
Install Dokan driver on windows box: PASS
Install BBP drive using the MSI: PASS
Launch "BBP Drive" from Start | Applications | BBPDrive
When BBP Drive boots it asks for API key.
Enter the API key you obtain from the wiki instructions:  PASS
Once BBP drive is running, verify we have an N: drive in windows : PASS
Drop 10 files on the N: drive in root folder and some in the subfolder : PASS
Launch some of the files in windows, verify they load normally (tested images by double clicking them, tested one video, tested some notepad files) : PASS
Edit a file and re-save it , verify the contents have changed : PASS
Rename a file, verify it renames : PASS
Delete a file, verify it deletes : PASS
Try loading one of your files from the external URL:
According to my bbpdrive when it launched my storage area is :
https://globalcdn.biblepay.org:8443/video/96/
The file I stored is in subfolder mypath.  The file name is "bbphoriz.png". 
So navigate to URL:
https://globalcdn.biblepay.org:8443/video/96/mypath/bbphoriz.png
Verify the image is visible on the internet:  PASS

Image hosted on bbpdrive (pasting bbp drive URL into our forum image tag):

Evenin.

I have also done some testing on this  BBP drive.

https://wiki.biblepay.org/BBP_Drive

Test case for BBP Drive:

Navigate to BBP Drive github from op post.
Install Dokan driver on windows box: PASS
Install BBP drive using the MSI: PASS
Launch "BBP Drive" from Start | Applications | BBPDrive
When BBP Drive boots it asks for API key.
Enter the API key you obtain from the wiki instructions:  PASS
Once BBP drive is running, verify we have an N: drive in windows : PASS
Drop 10 files on the N: drive in root folder and some in the subfolder : PASS
Launch some of the files in windows, verify they load normally (tested images by double clicking them, tested one video, tested some notepad files) : PASS
Edit a file and re-save it , verify the contents have changed : PASS
Rename a file, verify it renames : PASS
Delete a file, verify it deletes : PASS
Try loading one of your files from the external URL:

The installation process went smooth overall. There was that thing about the .conf file but Rob fixed that.   

Navigate to BBP Drive github from op post.
Install Dokan driver on windows box: pass
Install BBP drive using the MSI:  pass
Launch "BBP Drive" from Start | Applications | BBPDrive
When BBP Drive boots it asks for API key.
Enter the API key you obtain from the wiki instructions:  pass
Once BBP drive is running, verify we have an N: drive in windows : pass
Rename a file, verify it renames : pass
renamed a picture, np there.
Edit a file and re-save it , verify the contents have changed : pass
changed a text document,  it checked out.
Delete a file, verify it deletes : Does not seemed that it deleted yet.

I deleted the picture from the N drive but still i can see it in the web browser.

Try loading one of your files from the external URL:
It works, for example some of my pictures:  https://bbpipfs.s3.filebase.com/video/45/timber12.gif , https://bbpipfs.s3.filebase.com/video/45/APPstyleLcabin.png

Overall i think nice feature.

When minimizing the BBPdrive.exe i would have liked if it could go to the hidden icons section on windows 10  where  your speakers , windows security , network etc are.  Also like a harddrive bbp icon would be sweet.

Evenin.

I have also done some testing on this  BBP drive.

https://wiki.biblepay.org/BBP_Drive

The installation process went smooth overall. There was that thing about the .conf file but Rob fixed that.   

Navigate to BBP Drive github from op post.
Install Dokan driver on windows box: pass
Install BBP drive using the MSI:  pass
Launch "BBP Drive" from Start | Applications | BBPDrive
When BBP Drive boots it asks for API key.
Enter the API key you obtain from the wiki instructions:  pass
Once BBP drive is running, verify we have an N: drive in windows : pass
Rename a file, verify it renames : pass
renamed a picture, np there.
Edit a file and re-save it , verify the contents have changed : pass
changed a text document,  it checked out.
Delete a file, verify it deletes : Does not seemed that it deleted yet.

I deleted the picture from the N drive but still i can see it in the web browser.

Try loading one of your files from the external URL:
It works, for example some of my pictures:  https://bbpipfs.s3.filebase.com/video/45/timber12.gif , https://bbpipfs.s3.filebase.com/video/45/APPstyleLcabin.png

Overall i think nice feature.

When minimizing the BBPdrive.exe i would have liked if it could go to the hidden icons section on windows 10  where  your speakers , windows security , network etc are.  Also like a harddrive bbp icon would be sweet.

Great testing man.  I really like the APPstyleLcabin, that things is beautiful.

So on the deleted file, this actually might be OK if it still on the internet.  This is because our CDN gives you a 'globalcdn.biblepay' link at first and that is the direct URL to the sanctuary.  (But we back up files into our IPFS provider just in case) and I will show you how to check if its really deleted once you get BMS up and running and we do a Video test, I can show you how to go that dir and see if its deleted.

Anyway you can also check like this:  If you restart BBP drive and leave it on for at least 60 seconds, if that file stays deleted, then its really deleted and this web instance is just an IPFS backup.

I like your two suggestions and frankly I would like to do those but if we get more interest in using the program cause of course theres a long list of things to do with our youtube feature (like adding AI to it for example), but yes those are definitely needed.    I added a github issue for you for this:
https://github.com/biblepay/BBPDrive/issues/1

Note that anyone can add these feature request to each github if they want.

Hello Brother Rob.

Finally i have got the testnet Sanctuary and BMS up and running on the 20.04 node.
It was easy enough following the guides https://wiki.biblepay.org/Create_Sanctuary and https://wiki.biblepay.org/Install_BMS
I also threw an eye at the  https://docs.dash.org/en/stable/masternodes/setup.html

As for compiling the core wallet https://github.com/biblepay/biblepay/blob/develop/BuildBiblePayDevelop.txt it was just copy paste on this VPS no issues there.

I ran the

Code: [Select]

masternode status and

Code: [Select]

mnsync status  and i got

Code: [Select]

"state": "READY",
  "status": "Ready"
and
"IsBlockchainSynced": true,
  "IsSynced": true
 

Good block hash:
18:59:12
getblockhash 142700
18:59:12
539f1b8c495a568e4dcb69ae817679e4b5f53e4ef2ccba78f030543fe5ae6316

so i ran the getblockhash comand

Code: [Select]

getblockhash 142700
539f1b8c495a568e4dcb69ae817679e4b5f53e4ef2ccba78f030543fe5ae6316

That looks fine.

After that i installed the BMS , went fine and after posting bms adress in the browser i got :

Code: [Select]

1029|0|v1.2|Status: OK
|https://185.182.186.162:8443|Synced_Count: 101, File_Count: 131838, Synced: 0.0007660916605158102
<EOF>

The only thing that i had abit trouble with was the biblepay-cli but that seems fixed aswell.   

Hello Brother Rob.

Finally i have got the testnet Sanctuary and BMS up and running on the 20.04 node.
It was easy enough following the guides https://wiki.biblepay.org/Create_Sanctuary and https://wiki.biblepay.org/Install_BMS
I also threw an eye at the  https://docs.dash.org/en/stable/masternodes/setup.html

As for compiling the core wallet https://github.com/biblepay/biblepay/blob/develop/BuildBiblePayDevelop.txt it was just copy paste on this VPS no issues there.

I ran the

Code: [Select]

masternode status and

Code: [Select]

mnsync status  and i got

Code: [Select]

"state": "READY",
  "status": "Ready"
and
"IsBlockchainSynced": true,
  "IsSynced": true
 so i ran the getblockhash comand

Code: [Select]

getblockhash 142700
539f1b8c495a568e4dcb69ae817679e4b5f53e4ef2ccba78f030543fe5ae6316

That looks fine.

After that i installed the BMS , went fine and after posting bms adress in the browser i got :

Code: [Select]

1029|0|v1.2|Status: OK
|https://185.182.186.162:8443|Synced_Count: 101, File_Count: 131838, Synced: 0.0007660916605158102
<EOF>

The only thing that i had abit trouble with was the biblepay-cli but that seems fixed aswell.

Hi Bro. Earlz, I hope you are blessed.
This looks really good, now we can make some real progress.

On the dash guide @ https://docs.dash.org/en/stable/masternodes/setup.htm, is there anything that we need to add to Create Sanctuary wiki page because its muddy?  Cause on one hand, getting the doc destroyed forced me to create a more succinct doc (which is good I think) but otoh its more for power users.  Ill be glad to add something if there was uncertainty somewhere.

Im very excited that you have both the sanc running and BMS is syncing now.  It should be synced within an hour or so.

In the mean time, I want to make you aware that we have a wilcard CDN SSL cert that we bought and deployed with BMS (its integrated with the program) and what this does is allows us to issue any hostname while the CDN is running and respond to the user without ssl errors.  So for example, your sanc is internally known as this DNS address to the other sancs:

https://sanc185182186162.cdn.biblepay.org:8443/BMS/Status

See if you open that in a browser, you won't get any SSL error because of the wildcard.  Anyway, the reason I mention this is I'm going to give you some pages you can hit from your browser that let you see Sanc videos directly from your sanc (proving that its working).  Its also possible to upload an s3 file directly into your sanc and get it onto the biblepay network by using the biblepay API.  https://wiki.biblepay.org/API

So let me get some of this info together for you once this sanc is almost synced, lll be back asap.

Evenin.

On the dash guide @ https://docs.dash.org/en/stable/masternodes/setup.htm, is there anything that we need to add to Create Sanctuary wiki page because its muddy?

Not at all. My problem was the biblepay-cli, i received some error "cannot connect to 127.0.0.1 make sure biblepayd is running" something like that so i added the RPC arguments in the config file.

Code: [Select]

#----
rpcuser=XXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
rpcallowip=127.0.0.1
#----
listen=1
server=1
daemon=1
#----
#masternodeblsprivkey=
externalip=XXX.XXX.XXX.XXX
#----

I dont know if the masternodeblsprivkey=xxxxx + testnet=1 should be enough but for some reason i dont get the cli to respond without the rpc commands.

For sure looking forward for some test cases 

Evenin.

Not at all. My problem was the biblepay-cli, i received some error "cannot connect to 127.0.0.1 make sure biblepayd is running" something like that so i added the RPC arguments in the config file.

Code: [Select]

#----
rpcuser=XXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
rpcallowip=127.0.0.1
#----
listen=1
server=1
daemon=1
#----
#masternodeblsprivkey=
externalip=XXX.XXX.XXX.XXX
#----

I dont know if the masternodeblsprivkey=xxxxx + testnet=1 should be enough but for some reason i dont get the cli to respond without the rpc commands.

For sure looking forward for some test cases 

Whew good, Im glad our wiki is OK for now praise God.  I think I know the problem with biblepay-cli.  When you run it simply as ./biblepay-cli command,  It tries to look to your "biblepay.conf" file for credentials to connect to biblepayd.
All you have to do is specify where your config is.  If for example your testnet conf is called "biblepaytest.conf" then do like this:

./biblepay-cli -conf=biblepaytest.conf getmininginfo
(This assumes of course that biblepaytest is in the ~/.biblepay directory, thats where I usually have it on non prod sancs. )

Yeah, let me look at these test cases next.

I'm going to start sharing some commands to query videos too.

PS
Your conf file is fine, but note that a lot of that is no longer necessary (I think each of those things had value in the past).
You can try putting a pound sign in front of everything except:
masternodeblsprivkey=
and
testnet=1


Using externalip is usually overkill.  I used to put that in because 'masternode status' showed some crazy result, but I found out later it always resolved itself after 20 hours lol.

Here is a little tiny test case that shows which nodes Your sanc knows about (this is so it knows how to reach out and refer video streamers to another sanc, if your sanc if missing a piece for example).  It also comes into play with our VIDEO-POSE (where sanc operators dont get paid if they run inferior nodes, ie low proc count and low hard drive size):

https://sanc185182186162.cdn.biblepay.org:8443/BMS/Nodes

If you run that command from a browser you should see everyone that your node connected to.
Note that the 64 processor machine is my home desktop but its not always on, so it would be a prime example of one getting POSE banned.
And I see your new node has 6 procs, way to go man.

We will also have other VIDEO-POSE rules (like hashes per sec) so that people cant cheat this etc.  I think when the sidechain is released we can also test that a node is fully synced too.  (For now however we do ensure the node can do 1MM HPS, that the hard drive is 399gb or greater and 6 proc count) so that this is very fair...

Test case to ensure an individual sanctuary can play a video directly from the sanc:

This is a nice feature even though it would be a long shot to actually use it, this allows you to play a Sanc video directly from the sanc into the browser (no CDN required).  So if your videos are synced, and you have a connection to the sanc, and the rest of the world is down, the video will still play.

URL:

https://sanc185182186162.cdn.biblepay.org:8443/BMS/PlayVideos

Note that this video list will grow as your sanc syncs to 100%.  We only have about 300 videos right now being stored (these videos are the ones uploaded into social.biblepay.org into the video room, that is what we are hosting). 

So to perform the test just click on one of the videos, and notice the sanc will generate a local url (a url playable directly from the sanc), then skip around in the video and ensure it plays.


And so how does this actually work for users?
The way it works for users is when the user hits our global CDN (thats our load balancer), this load balancer pushes the traffic out to one of our 'fully qualified bms nodes' (they get fully qualified when their reverse dns record is established and they are synced), and when that video request starts, it is only for seconds 1-5 of the video.  Each 5 seconds are re-evalutaed and the video is streamed from whichever node has the piece.  So a 20 min video might have 200 pieces, and each 5 sec piece is streamed independently from a different sanc (it is not designed for one sanc to stream an entire video but rather each piece is evaluated as the video is played, and pulled from the sanc that has it).