June 2022 - TestNet Release - Exodus

*** Additional Instructions Added to BMS Install Wiki ***


Testers, the BMS installation procedure has been enhanced to allow our sidechain to work with MySQL.
This will give us the unique ability to be the first known coin that can leverage DSQL in mainnet (allowing our social media product to run on the sidechain, and, giving us many other Layer 2 features).

The wiki guide here has been extended:

https://wiki.biblepay.org/Install_BMS

For those of you who already have BMS running please do the following:

Stop BMS by going to the node, to the terminal, and simply press ctrl-c.  (It may already be stopped due to the failed upgrade, simply continue from here with the BMS program stopped).

Find the place in the document where it says "Installing MYSQL".  Start running those commands as root until "End of MySQL".

Once finished, start BMS again (by running the command to start the node:  dotnet BiblePay.BMSD.dll).

At this point the menu should appear and the node should not crash.

Post if you have trouble.

Next I'm going to post some test cases related to BMS that should work After MySQL is installed on your local BMS node (before that point these commands dont work).  Also note that each of our sancs have one decentralized mysql database each.  This is so we can decentralize the DSQL queries.  That will allow our front end systems, such as social media system or Gospel Front End System, to reach the decentralized database for SQL queries.

Test 1, ensure your sidechain syncs:

Restart BMS.  Verify you are at block 152 or higher:
https://globalcdn.biblepay.org:8443/BMS/Status

To get the block hash try this:
https://globalcdn.biblepay.org:8443/BMS/GetBlock?id=152

This will also show you the transactions in that block and the hash and the diff etc.

Note that social.biblepay.org is already using our sidechain for Photos and Videos.
So this next test, lets add a photo to a group in social.biblepay.org.  To do this go to any group (or you could go to your home profile timeline) and then Add a picture.  Save the post.
Now quickly go to this page
https://globalcdn.biblepay.org:8443/BMS/Status


At this point the memory pool should have 1 transaction waiting.  Once it is mined, you can then go to the new block number (IE if its one higher, you have to change the block height here):  Change NNN to the correct height:
https://globalcdn.biblepay.org:8443/BMS/GetBlock?id=NNN

Then look for the transaction that contains your image.
This shows how we not only have a decentralized file storage system, but now a decetranlized DSQL system also.

(On a side note, optionally, you can install mysql workbench on Windows PC if you want to learn how to query your own sanctuary for the image metadata). But that is mostly unecessary because we can do this with RPC commands. 

Let me know when you all are up to this point and I will move on to explain a video.

So our videos are stored in HLS format so they can be decentralized (meaning they are split up into many pieces) which gives us the ability to stream them from multiple sancs and view them with fast start.
To test this, its easiest to upload a small mp4 (smaller than 5 meg) simply because otherwise you will be waiting for the file to be converted from mp4 to HLS before you see the block transactions start.

I uploaded  a  5 meg file to a group in this block:
https://globalcdn.biblepay.org:8443/BMS/GetBlock?id=146

To try this, upload your file.  Then quickly go to the:
https://globalcdn.biblepay.org:8443/BMS/Status
Page, and look at the memory pool.  Once the file is converted to HLS, you will see the memory pool increase in size for each Piece of the file.

Then view the block:
https://globalcdn.biblepay.org:8443/BMS/GetBlock?id=146

Find the *.ts files.  Each .ts file is a piece of your video and this metadata is stored across our DSQL servers so everyone has exactly the same view.
Additionally, our SQL server creates a representation or "view table" (one table per data type) automatically, so that our front end system can access this metadata with extremely fast speed.

*** Additional Instructions Added to BMS Install Wiki ***


Testers, the BMS installation procedure has been enhanced to allow our sidechain to work with MySQL.
This will give us the unique ability to be the first known coin that can leverage DSQL in mainnet (allowing our social media product to run on the sidechain, and, giving us many other Layer 2 features).

The wiki guide here has been extended:

https://wiki.biblepay.org/Install_BMS

For those of you who already have BMS running please do the following:

Stop BMS by going to the node, to the terminal, and simply press ctrl-c.  (It may already be stopped due to the failed upgrade, simply continue from here with the BMS program stopped).

Find the place in the document where it says "Installing MYSQL".  Start running those commands as root until "End of MySQL".

Once finished, start BMS again (by running the command to start the node:  dotnet BiblePay.BMSD.dll).

At this point the menu should appear and the node should not crash.

Post if you have trouble.

Evenin Brother Rob.

I got the BMS up and running again.

The  part : Installing Local MySQL database  , went just fine for me no hickups there. Copy pasting the terminal commands no problems.

 I did check now in the browser and got:

Code: [Select]

{
  "URL": "https://185.182.186.162:8443",
  "BMS_VERSION": 1039,
  "COMMON_VERSION": 1002,
  "Status": "OK",
  "Synced_Count": 1070.0,
  "File_Count": 144628.0,
  "Synced_Percent": 0.007398290275860118,
  "EOF": "<EOF>",
  "Memory_Pool_Count": 0,
  "Best_Block_Hash": "00005450cb29ae91e2a2decd27c2d8d101b6c1cb49cbd7f5e92cd459f9818807",
  "Block_Count": 159,
  "Hashes": 519
}
I will do the test cases you posted tomorrow.
Talk to you laters.

All,

I'm working on adding some powerful features to BMS including the ability to serve a GUI from our sanctuaries.  This means we will be able to add gospel features to BMS later, and in the near term, we can convert our RandomX pools over to Sanc Pools (meaning that every BMS node would not only be a CDN and a video streamer, but also a randomX mining pool.)

Since this upgrade is major the nodes cannot upgrade themselves in this case, so I expanded the wiki guide to include Manually upgrading the node.

Please see this guide:
https://wiki.biblepay.org/Install_BMS

See the bottom section, manually upgrading.  Please follow that and your node should upgrade.

Then you can move on to testing the Sidechain test cases.  In the mean time I will work on porting a RandomX pool to the BMS sidechain.

Hi All,

I had a couple people ask me in chat about testnet syncing and I finally had a chance to verify the sync.
Im on Exodus 0.17.2.2, and we seem to be on block 143823.
Here is a good hash:
14:45:32
getblockhash 143823

14:45:32
8768e6e083ba46ad58bfc3d1eeced588cf5066969f40116b094856bdb0d742f0

I believe we are in sync (my sanc has stayed in sync with my home node).
It could be that no one was mining (from what I can see no one was mining for 5 days).
I turned on my miner and we moved up a block...

Please verify the hash above?

Mornin.

Here is a good hash:
14:45:32
getblockhash 143823

14:45:32
8768e6e083ba46ad58bfc3d1eeced588cf5066969f40116b094856bdb0d742f0

My testnet wallet syncs just fine now.

Code: [Select]

10:52:03
getblockhash 143823


10:52:03
8768e6e083ba46ad58bfc3d1eeced588cf5066969f40116b094856bdb0d742f0

Looks same as yours Rob, looks accurate.

On the installation of the  https://wiki.biblepay.org/Install_BMS

The manual upgrade of the BMS on the sanc went without any troubles , just copy paste commands for me.

Test 1, ensure your sidechain syncs:

Restart BMS.  Verify you are at block 152 or higher:
https://globalcdn.biblepay.org:8443/BMS/Status

To get the block hash try this:
https://globalcdn.biblepay.org:8443/BMS/GetBlock?id=152

This will also show you the transactions in that block and the hash and the diff etc.

Looking at the bms i can see that its at block 172.

Code: [Select]

{
  "URL": "https://185.182.186.162:8443",
  "BMS_VERSION": 1047,
  "COMMON_VERSION": 1003,
  "Status": "OK",
  "Synced_Count": 145194.0,
  "File_Count": 145194.0,
  "Synced_Percent": 0.9999999311266352,
  "EOF": "<EOF>",
  "Memory_Pool_Count": 0,
  "Best_Block_Hash": "000047aeb2a015ba903b3279ae2dfcc183e035eeb11ead618ca3a9fadc59bdee",
  "Block_Count": 172,
  "Hashes": 81364
}
I also tested the blockhash

Code: [Select]

{
  "Version": 1,
  "PreviousBlockHash": "0000b39315a9de15a80a41f7f31cbd1a93fcd73ecf2b0eb51b1bfbf4794cd4e8",
  "MerkleRoot": "37feb5947ec3c60f5d05af7bbbf023997862b90bb66dccfb4622bebc7d78fa59",
  "Time": 1651493630,
  "Target": 1766847064778384329583297500742918515827483896875618958121606201292619775,
  "Nonce": 393054,
  "BlockNumber": 152,
  "Transactions": [
    {
      "Data": "{\"field1\":\"https://7e825619-9da1-4b87-bcba-577aeef9bd28\",\"field2\":\"https://99bde5a8-da37-49da-99ff-929794a3756d\",\"me_id\":4000,\"table\":\"Junk2\",\"nMeID\":1.0}",
      "Time": 1651493625,
      "BlockHash": "00001107a8f9f1803b15ebddf30fd0bf0277d852d722372cac9c1c44977a19c8",
      "Height": 152
    },
    {
      "Data": "{\"field1\":\"https://3b168786-1e58-46bb-8377-e4f777a195ab\",\"field2\":\"https://62cd6ce1-12a2-4ccf-9ca7-770d97a88f97\",\"me_id\":7000,\"table\":\"Junk2\",\"nMeID\":1.0}",
      "Time": 1651493625,
      "BlockHash": "00001107a8f9f1803b15ebddf30fd0bf0277d852d722372cac9c1c44977a19c8",
      "Height": 152
    },
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Note that social.biblepay.org is already using our sidechain for Photos and Videos.
So this next test, lets add a photo to a group in social.biblepay.org.  To do this go to any group (or you could go to your home profile timeline) and then Add a picture.  Save the post.
Now quickly go to this page
https://globalcdn.biblepay.org:8443/BMS/Status


At this point the memory pool should have 1 transaction waiting.  Once it is mined, you can then go to the new block number (IE if its one higher, you have to change the block height here):  Change NNN to the correct height:
https://globalcdn.biblepay.org:8443/BMS/GetBlock?id=NNN

Then look for the transaction that contains your image.
This shows how we not only have a decentralized file storage system, but now a decetranlized DSQL system also.

Next i uploaded a image to social and followed the instructions:

Code: [Select]

"Transactions": [
    {
      "Data": "{\"URL\":\"upload/photos/2022/05/ZwJcrXZVlWIrxRYxGNGy_07_c846a84e7dee71ba98459c475ec2da98_image.jpg\",\"Added\":\"5/7/2022 5:37:18 AM\",\"userid\":\"3\",\"size\":11535,\"syncedlocal\":\"0\",\"syncedremote\":\"0\",\"table\":\"pin\"}",
      "Time": 1651919838,
      "BlockHash": "000003f84d42083417689806396c3cfe6689df21d5611764c1806449ef6bc32b",
      "Height": 173
    },
    {
      "Data": "{\"URL\":\"upload/photos/2022/05/ZwJcrXZVlWIrxRYxGNGy_07_c846a84e7dee71ba98459c475ec2da98_image_small.jpg\",\"Added\":\"5/7/2022 5:37:17 AM\",\"userid\":\"3\",\"size\":14519,\"syncedlocal\":\"0\",\"syncedremote\":\"0\",\"table\":\"pin\"}",
      "Time": 1651919837,
      "BlockHash": "000003f84d42083417689806396c3cfe6689df21d5611764c1806449ef6bc32b",
      "Height": 173
    }
and upon inspecting my picture at social hitting the "open original"  button :

Code: [Select]

https://sanc1.cdn.biblepay.org:8443/upload/photos/2022/05/ZwJcrXZVlWIrxRYxGNGy_07_c846a84e7dee71ba98459c475ec2da98_image.jpg
i can see them matching.

Hi Bro Earlz,

Great on the testnet sync!  Great on the great testing.
So just so you understand, any data that gets inserted in the sidechain between blocks (into DSQL tables) also gets replicated into your local node into the mysql tables.  If they do not contain the correct schema, the schema is automatically expanded.  If records need inserted they get inserted (as that block syncs).
So for example, last night I inserted 100 records into Gospel Illustration/Article/Wiki on the sidechain (so we can make a decentralized gospel menu).
You can see some of these transactions in this block:
https://sanc185182186162.cdn.biblepay.org:8443/BMS/getblock?id=172

So this means as an admin of your node you could theoretically go into Mysql and type 'select * from Illustrations' and see these particular records now they are available to the front end gospel app.

I will move on to creating v1.0 of our GUI so we can demo that soon.

So I guess I can let the cat out of the bag:  The Gui 1.0 has been released.

So if you go to the root of your sanc address like this:
https://sanc185182186162.cdn.biblepay.org:8443/

We now respond with a gui.  Note that in the future, we will be able to get rid of the port once we have a BBP wallet (or metamask) login schema working.
But anyway lets talk about what we have now.

First of all, the theme settings are now working, you can click your avatar circle and change to dark, light theme etc.  Note that our new themer also supports 16 sub themes, so you can also pick a color above the master theme, and it will tint the menus and tables for you and the theme is stored on your machine.

So I ported Accountability over to the sidechain:  All the expenses, revenue, orphans and orphan expenses now live in 4 sidechain tables (these went in the last 5 blocks or so).
So if you click on Accountability, then run a report, we actually run this report from the sidechain on your node and gen the pdf, its pretty interesting...
(Of course permissions are not complete yet, so we still need to devise a way to let an authorized signing key Add more expense records.  Im currently the one to add the monthly expense record but we can decentralize that by having an ACL list feature added to BMS). 

Next check out In Development | Demo Dash | Demo Table.  This just proves that our next upcoming datatable will support sorting, searching, and Pagination.  If you use the Search option on the new datatable, this searchbar limits the results down to rows that contain the search anywhere in the system (for example, say historical payouts for randomx , you could type in a few character etc).  And check out the accordian, its a bootstrap feature that lets the user minimize a section of a page .

Now check out Gospel menu.  Each of the 5 sub menu items, those actually required me to port Illustration, Wiki, and Article tables from our centralized sql server over to the decentralized sidechain, so all those records are decentralized now too!  So click on some Theological studies for example, and its pulling the record from your local sidechain then displaying its corresponding article.

Look good?

Im still working on a new scheme to decentralize the bbp wallet send-money page from unchained - so that the private key is either tied to metamask, or possibly to a bbp browser plugin.  Im thinking about using Metamask to handle our logins and then we can port the User Profile over to the decentralized chain.  So for example what Im thinking you come in as a new user, if you dont have metamask we tell you to install it and then you can log on, otherwise you cannot log on without metamask.

If you do have metamask, we ask you to sign a code (once every week roughly) or when you log out--and this login page then gives you access to your decentralized profile like any other web site (until logged off), and your profile is then stored on the sidechain.  (For nickname, name, anything else we might normally need, bbp public key, utxo pub key etc). 

Then our users would always be using their pub cryptokeys to access our site (similar to openseas method).... I think this might invite a lot more of the hardcore web3 community over here.  With the goal being to eliminate the username and password login in the future phasing out traditional logins.  Then we need to move the bbp wallet (for web purchases) to either a plugin on the page, or, to a derived key based on something you sign in metamask (Im still thinking about this idea, because I want it to be easy for the user, and maybe having metamask is asking enough for the user, if they already have to use metamask to log in, they may not want a second plugin).  But anyway I could envision someone signing a "bbp" message from metamask, then our javascript can derive their keypair from that signature - hence being the method for spending from the bbp webwallet, and in this case user would not lose the bbp priv key as long as they can access current metamask - and of course all we store in the sidechain is the public erc20 address to link the user to the profile.  (Im leaning toward this method for our next iteration).

Reminder for MIP and me:
When we retire our windows pool server, we will need to move the endpoint for the "MobileAPI" to a new endpoint.
I will update the OP post with this.  I think this will need to be in production by June 30th (and cannot be tested earlier than June 1st).

Good afternoon.

First of all, the theme settings are now working, you can click your avatar circle and change to dark, light theme etc.  Note that our new themer also supports 16 sub themes, so you can also pick a color above the master theme, and it will tint the menus and tables for you and the theme is stored on your machine.

Easy to change the themes, the default indigo blue looks awesome. dark mode not to bad either. Well alot of choices, thumbs up Rob.

Now check out Gospel menu.  Each of the 5 sub menu items, those actually required me to port Illustration, Wiki, and Article tables from our centralized sql server over to the decentralized sidechain, so all those records are decentralized now too!  So click on some Theological studies for example, and its pulling the record from your local sidechain then displaying its corresponding article.

The gospel feature looks real nice aswell.  Illustrations with all the pictures are a  sweet addition. The wiki and the theological  studies looks fine to me.  Easy to read, the font size looks all good on my 1080p monitor.

One thing i was thinking of was when you click on "Bible viewer"  you get forwarded to biblegateway in the same tab, personally i think would be better if it opens up in new tab so that the sanc  ip tab is still there.


Overall i think it looks fine Rob, snappy and no lags when navigating around.  Will be intresting to see what comes next.

laters.

Good afternoon.

Easy to change the themes, the default indigo blue looks awesome. dark mode not to bad either. Well alot of choices, thumbs up Rob.



The gospel feature looks real nice aswell.  Illustrations with all the pictures are a  sweet addition. The wiki and the theological  studies looks fine to me.  Easy to read, the font size looks all good on my 1080p monitor.

One thing i was thinking of was when you click on "Bible viewer"  you get forwarded to biblegateway in the same tab, personally i think would be better if it opens up in new tab so that the sanc  ip tab is still there.


Overall i think it looks fine Rob, snappy and no lags when navigating around.  Will be intresting to see what comes next.

laters.

Thanks for Testing Earlz!
Yeah that sounds like a good idea, we can open a new tab for the bible viewer.

On a side note, the data that you view when you view accountability for example is stored in the sidechain now, so that is a nice addition.
(Illustrations, wiki, expenses, revenue) all that is in the sidechain.

Since my last post, I ported our RandomX mining system in to aspnetcore.  Isnt it interesting that our users will be mining against sanctuaries?

I also built out a separate randomx pool for testnet, and one for mainnet.  So now we can mine properly (and test properly) in testnet for our releases.  (That will come in handy when we make a large code change and we have to test true randomx mining).  The sanctuary will pay the user for their mining activity from the hot wallet balance in the sanctuary. 

I will put together a test case now so you guys can test some randomx mining in testnet next.
Theoretically what we will do is expose a few of our sancs to port 80 and start a load balanced BMS presence for production.  When we go live at the end of June, we can take down foundation.biblepay.org and point that domain over to unchained.biblepay.org, and take down unchained also, and point that domain to our Sanc pool.
This means this software you are testing now will end being our Mining pool, our Staking (portfolio builder) interface, our BBP University, our memorize scriptures, our gospel web pages, and it will also allow you to log in via metamask (like a web 3 login).  I didnt see any comments or questions on that-- do you all understand, and like that feature?  We will be doing away with username and password in the next release.

Not sure if you clicked the accountability PDFs; please be sure those work too.

Very large BMS release this week - just released.  Miraculously, the auto upgrade process seemed to work for our testnet participants (looking at Earlz node it appears to be upgraded, should be on v1054 now. ) I'm surprised because this new version adds a dependency for Nethereum, which normally requires a manual upgrade but we'll cover that when we get to portfolio builder.

This upgrade includes:  RandomX mining against sancs, mining in testnet And mainnet against sancs, Switching Chains, Web3 Login:Authenticating with metamask (in contrast to usernames and passwords), a user profile page, profile avatar, BBP web wallet (based on metamask for your BBP priv key), Logging Out (clearing the metamask sig), The chain indicator in the header, The logged in indicator, The RandomX pool pages (metrics , leaderboard etc), half of BBP Univ, 75% of portfolio builder, Charts for PB & mining.

So first we need to tackle logging in and logging out (web 3 authentication) before we can discuss anything else (otherwise you cant see your profile or switch chains etc).

The user record is now decentralized and stored on the sidechain, so before we go to prod we need to obfuscate the email address (as that is our only sensitive field at this point) thats not done yet.

The way we access your user record is :  Now your metamask public ERC-20 key is your user record primary key, and that pulls up your profile which pulls your avatar, email address, nickname, PB pub signature etc.

So lets go through a few test cases to get logged in and out using web3:

Navigate to my sanc1 for these tests (you can do a lot of this on your own node if you want, but will get errors when doing the RX tests because you need a lot of pool settings to run a pool) so I will recommend just use this endpoint for these tests:

https://sanc20914556214.cdn.biblepay.org:8443/

If you go to that sanc1, you will see the new UI and the new menu. 
Test case to Register as new User:
- Go to Authentication - Profile
- Our system recognizes you are new, and launches metamask (if you dont have metamask, I think it just throws an error telling you its not installed.  We need to make it redirect you to wiki page to explain this web3 mechanism before we go live).  Anyway if you have metamask installed, it will prompt you with a signature request.
- The sig request is the brand new non harmless type (IE cant access coins) and its a signing request for logging in.  Now sign the message.
- We store this signature for up to 30 days as a cookie on your machine.  If you are on a non-secure machine you can Log Out, otherwise for convenience you can keep coming back authenticated.
- Once logged in the header should say Logged In.

Test to populate your profile:
- Navigate to Authentication | Profile
- Populate nickname and save it .  Change avatar.  It should auto save the avatar.
- Verify that you have a BBP wallet (this wallet is now derived from your Metamask key! An improvement).  Another words if you move machines, and reload your metamask key, your bbp webwallet coins will move with you.
(Lets test spending some coins from the web wallet.  )
- First, Switch chains by clicking Change Chain- then the header should show chain : TESTNET.
- In testnet mode, verify your bbp wallet has an address for TESTNET now (its no longer starting with a B).
- Try spending some testnet coins by sending them to your biblepaycore wallet.  Verify they come through on the core wallet side.

Test to Log Out:
Click the top right avatar circle | Log Out.
Verify the header shows logged out.
If you navigate to Profile, it will try to log you in again (simply because we have that process there to log a user in who has been logged out).

Just for sanity sake since Im mining against sanc1 in testnet, can you please verify the hash Earlz:


09:22:35
getblockhash 145394


09:22:35
adf539f4df232ffc9bedcee77ba9a0402932b10a28d711ec5b2db9d995bbc417


Are we all in sync?

Next I will write a test case so we can test some randomx mining in testnet! 

** RandomX TestNet Mining Case **

So I made this page relatively accurate for a new user to get started (its similar to the one we have) but it dynamically populates the port too depending on which chain you are on and the DNS address of the sanc you are mining against:

Be sure to change your chain to TESTNET mode before hitting this page (your header should say TESTNET):
https://sanc20914556214.cdn.biblepay.org:8443/bbp/poolgettingstarted
(That ensures the port on the page is correct).

So looking at that page, you can make a new batch file on windows to mine against sanc1.  In my case Im mining against port 3002 against sanc1.

And then you can wait a little while and check our Leaderboard, and it should be very similar to what you are used to in Foundation (its a direct port of our old software).
Next you can go to Pool Metrics and see that your hashpower has increased the pool hashpower.

Finally, lets mine for a while then wait 24 hours, and you should receive testnet coins from the sanctuary over to your personal wallet.
Be sure that you have your Testnet BBP address in your mining batch file so the pool can pay on the right chain.

Then give us an update that you actually got paid (I recommend using an address book address that is labeled for TestNet mining so you know that you got it).

Btw, if anyone wants to mine against prod, that code is running against MainNet live (against our current mainnet branch version) so it should theoretically mine and pay (thats why you should see the correct Height in the Pool Metrics page for mainnet and the correct height for TestNet).