Bible Pay

Read 2245 times

  • earlzmoade
  • Developer

    • 311


    • 48
    • August 02, 2018, 03:22:01 AM
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #15 on: April 22, 2022, 03:46:45 PM »
Hey.

Quote
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. )

Indeed. when i pointed the cli to the test config file it worked just fine..  Haah can be that easy sometimes right :)     I also tested to pound out all the rpc commands , external ip and such on another node and it still worked so seems they are not needed indeed.

Quote
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.


I tested to play some videos from the sanc, its cool man...  I like the BBP logo on the video player. The buffering wasnt to bad either when scrolling thru the videos.
Looking sweet rob. 
I noticed when clicking from the sanc onto the video it says the  "certificate is not valid" 

Quote
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...

Pretty cool to see this stuff coming into fruition. I mean one thing talking about it, another ball game to test it out.  On the sancs what do the "FullyQualified":false}]   mean? 
I noticed some of the nodes had  true or false.

Well i saw that you wrote more in the post :
Quote
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).
« Last Edit: April 22, 2022, 04:11:44 PM by earlzmoade »
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #16 on: April 22, 2022, 04:43:06 PM »
Hey.

Indeed. when i pointed the cli to the test config file it worked just fine..  Haah can be that easy sometimes right :)     I also tested to pound out all the rpc commands , external ip and such on another node and it still worked so seems they are not needed indeed.

I tested to play some videos from the sanc, its cool man...  I like the BBP logo on the video player. The buffering wasnt to bad either when scrolling thru the videos.
Looking sweet rob. 
I noticed when clicking from the sanc onto the video it says the  "certificate is not valid" 

Pretty cool to see this stuff coming into fruition. I mean one thing talking about it, another ball game to test it out.  On the sancs what do the "FullyQualified":false}]   mean? 
I noticed some of the nodes had  true or false.

Well i saw that you wrote more in the post :

So on the certificate invalid, thats OK, thats because we dont pass the cert URL in when you play the video (thats because that would require a special CORS rule which we dont have yet) so for simple debugging (since these pages are meant for sanc ops only) yeah thats still showing the IP itself has no ssl cert.  We might be able to add a cors rule for that though soon.

Now on the fully qualified, the FQ boolean always shows false for your own sanc *if* being viewed from the sanc itself (this is to keep it from calling itself for missing pieces of videos). And its FQ=false when someone runs a node < min requirements.
But you can check on your own node from the viewpoint of someone elses node like this:

https://globalcdn.biblepay.org:8443/BMS/Nodes
Note that your node is FQ=true now meaning its actually ready to serve some videos and it would get paid. Notice my 64 proc machine = false, thats because its not responding.
(Although I think we need a little refining on not setting them to FQ=true until the video chain is synced.. will look at that too).

Alright looks good.  I'm working on exposing the sidechain features next.

Also one other exciting feature is the auto upgrade feature.  We need to test that next... Ill put together a test case today.



« Last Edit: April 23, 2022, 06:20:48 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #17 on: April 23, 2022, 07:39:53 AM »
Automatic Upgrade test case:

So the BMS nodes have a nice feature in that they can automatically upgrade themselves when we have a new version. 
So to test this, we were on version 1029 last night.  I just added a tiny feature to demonstrate this upgrade ability.
In this page:

https://globalcdn.biblepay.org:8443/BMS/Status

I made it JSON instead of homegrown. 
This page itself also reveals the version (which should now be 1030).

From your sanc IPs, please hit this page and see if your version increased?



  • earlzmoade
  • Developer

    • 311


    • 48
    • August 02, 2018, 03:22:01 AM
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #18 on: April 23, 2022, 11:03:19 AM »
Quote
Automatic Upgrade test case:

So the BMS nodes have a nice feature in that they can automatically upgrade themselves when we have a new version.
So to test this, we were on version 1029 last night.  I just added a tiny feature to demonstrate this upgrade ability.
In this page:

https://globalcdn.biblepay.org:8443/BMS/Status

I made it JSON instead of homegrown.
This page itself also reveals the version (which should now be 1030).

From your sanc IPs, please hit this page and see if your version increased?

I just checked the vps and i see that the bms has changed from 10.2v to 10.31 version.

« Last Edit: April 23, 2022, 11:09:11 AM by earlzmoade »
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #19 on: April 25, 2022, 07:10:51 AM »
I just checked the vps and i see that the bms has changed from 10.2v to 10.31 version.

Ok great.

I will work to release the sidechain feature next then we can test that.

We are going to need a mandatory upgrade on the biblepayd for the sancs soon, but no rush (not released to github yet).



  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #20 on: April 28, 2022, 06:44:10 PM »
*** 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.



  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #21 on: May 02, 2022, 09:13:38 AM »
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.



  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #22 on: May 02, 2022, 09:20:41 AM »
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.



  • earlzmoade
  • Developer

    • 311


    • 48
    • August 02, 2018, 03:22:01 AM
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #23 on: May 03, 2022, 12:52:27 PM »
*** 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.
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #24 on: May 05, 2022, 05:38:24 PM »
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.




  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #25 on: May 06, 2022, 02:47:26 PM »
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?



  • earlzmoade
  • Developer

    • 311


    • 48
    • August 02, 2018, 03:22:01 AM
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #26 on: May 07, 2022, 06:01:51 AM »
Mornin.

Quote
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.


Quote
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
    },

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Quote
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.

Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #27 on: May 07, 2022, 09:20:47 AM »
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.




  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #28 on: May 08, 2022, 01:36:40 PM »
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).




« Last Edit: May 08, 2022, 01:40:32 PM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 3899


    • 94
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: June 2022 - TestNet Release - Exodus
« Reply #29 on: May 11, 2022, 09:14:15 AM »
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).