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