I tried to work on this earlier but just couldn’t find the time and was probably over complicating things. So here is a simple dashboard that gets the data from omniexplorer, ethereum network (emaid smart contract) and gnosis-safe (mint queue).
You can find the website here for now, which can get a proper web domain later on:
http://emaid.online/ (https not working yet)
Very nice!
Where are the missing 30 eMAID though? 
Good question, but it’s not a problem since more MAID is burned than ERC20 minted in total history (+ in the queue). It can be from testing when Altcoinomy deployed the smart contract.
Or another explanation could be someone who did burn MAID but did not complete Altcoinomy on-boarding process. Basically unable to get his ERC20 until that is complete.
MAID Burned >= eMAID Minted 
MAID < eMAID Minted 
Im only seeing a blank page?
I’ll wait until it gets a proper domain and https.
Well done @DeusNexus 
Most encouraging to see this latest burst of creativity from everyone.
I restarted the instance it was hosted on. Trying out my free trial on Azure for a whole year 
Bought a cheap domain name, emaid.online for $2.
Still need to work on setting up HTTPS on Apache2 server.
I found this very helpful
for some applications https://zerossl.com/ is better, like they give you a cert for a year vs 90-days etc (when I was hosting matrix zerossl was the goto as letsenrypt had issues)
I used CloudFlare and there was an option for Always HTTPS. Now the HTTP site get’s served as HTTPS connection using their SSL certificate. Couldn’t have been easier 
The dashboard is now updated to be fully responsive and also adjust to phone screens and other window sizes. I’m really proud that I finally managed to do the CSS, working with divs really breaks my head sometimes…
The downside is that I’ve found it impossible to get my Flask API to connect to the ReactJS Front-end.
It’s serving API data on emaid.online:5000/api but I get errors regarding Cors or mixed content (http request while site is https).
Yeah still working on the API it’s giving me headaches. First I had the client-side make requests from browser but that seemed to throw issues, only server-side calls were allowed. Now I make API that fetches the data from the different sources and servers it as one JSON dict, but still having issue with getting it to work with the current front-end.
Ahh got ya, fully reading your post may have helped!
If anyone can help out. The issue is the following:
/var/www/emaid.online/public_html as how it is created from npm run build.<VirtualHost *:80>
ServerName emaid.online
ServerAlias www.emaid.online
Redirect permanent / https://emaid.online/
</VirtualHost>
and the HTTPS configuration (which uses letsencrypt ssl certificats):
<VirtualHost _default_:443>
ServerAdmin webmaster@emaid.online
ServerName emaid.online
ServerAlias www.emaid.online
DocumentRoot /var/www/emaid.online/public_html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
SSLEngine on
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<Directory /usr/lib/cgi-bin>
SSLOptions +StdEnvVars
</Directory>
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/emaid.online/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/emaid.online/privkey.pem
</VirtualHost>
Would it be possible to have Apache2 point a url, e.g. /api that is sources from localhost:5000/api?
I’m trying to find a way to have Apache2 serve the Flask API directly so it’s not using a different port when React tries to fetch it.
You could have a Reverse Proxy (traefik) in Front of everything so all services don’t need to worry about any certificate stuff (traefik takes care of that and even creates/extends lets encrypt certificates)
With the one reverse proxy in front you can get rid of all cross Site Trouble and the proxy internally routes all Traffic according to your needs
(it probably would be easiest to do this stuff when using docker containers to wrap your services (really not a lot of hassle) and then using traefik and the docker provider for stitching it all together)
OMG IT WORKED. I used the reverse proxy on apache2 and it does the job beautifully. First the API was also running on HTTPS but now I can run it as HTTP and the Proxy serves the forwarded local API as HTTPS!
Took three whole days but it’s working and I got smarter 
Main site:
