Been a super busy day with the analytics network. Here are some changes from Today:
Split out logger/connection from rendering root object. This will be needed for new login screen as there is a lack of proper connection state managment
Started work on reservation by "Datamine Pro Key"
Added "Users In Memory" on stats page that will help monitor resource usage
Fixed memory leak on context destruction
Added new global widget disconnect event and now disconnecting will drain dispatch queue. This allows us to do async destructors on per-context
Fixed realtime events for shared widgets (This will be an example of our realtime events across multiplie users)
Improved how realtime stats are streamed no longer relying on api/rest context
Split out shared widgets registration into a separate file and fixed order of event subscriptions
Rewrote the reservation server today. Now each unique link is limited to 1 connection to the server. Additionally when you disconnect you are properly removed from reservation server.
Currently the second connection made to the same dashboard link will display an error saying you are already connected. In the future this will disconnect the other session. Think of this like the Tradingview limits on concurrent connections.
Tomorrow I will work on the login server where you will be able to paste in your invite link. For this initial wave of invites it is likely they will be special one-time codes until the burn queue is ready before Beta.
Currently targeting Monday for the release, The goal of this first set of invites is to make sure the network supports multiple users, you will get 3 login codes each and this will not be tied to the burn queue yet as we're testing network stability first. 🔥
Apparently SSL configuration was not completed yesterday. Today I noticed that our Event streams are dropped after ~100 seconds of idle time.
As our analytics are done in realtime these 100 second timeouts were not going to fly. I did a lot of digging round with nchan and nginx configurations trying out various timeouts and configurations.
Turns out the problem was with cloudflare DNS routing for SSL. We were using Cloudflare DNS proxy which made requests HTTP 2.0 and since they are routed through Cloudflare they terminated the streams after this idle time.
Had to get a new certificate and turn off Cloudflare DNS routing but now the connection to the server is persistent. Another advantage of this is that traffic is not routed through cloudflare anymore on pro analytics for another layer of security. 👌
I'll take this extra long weekend time to do some polish before Alpha invites. We're looking really good now, hope to see you guys on alpha soon! 🔥
This means your connection to the Datamine Network will be performed in a secure manner.
We've had to add ensure the SSL certificates work for our central reservation server. This server is responsible for issuing connections to the network. It also creates unique data points for each user that connects.
Another SSL secured server is our "nchan server". This server is responsible for all realtime communication between the network and your browser.
This means every user that connects to the website can essentially communicate with any other user on the network in realtime. We have not created any "P2P" widgets yet but it's something that's on to-do list.
Next order of business is to finalize the on-chain sign on link generation. This requires some new data points (as we have to consider delegate burn FLUX amount).
Alpha invitations are coming before Tuesday, we're just finalizing the initial version of FLUX burn queue mechanism 🔥
Datamine DeFi Network Pro Alpha IS NOW LIVE ON PRODUCTION SERVER
Before we can send out invites we need to finalize the following outstanding tasks:
Finalize off-chain sign on link generation
Enable SSL
Run through a security checklist
For Alpha and Beta everything runs off a single server. The idea behind this is that even though the network is made up of multiple Docker containers we want to see what kind of punishment a single VPS can handle.
So far the Alpha is blazing fast and our custom network communication is fast and efficient. Can't wait for you guys to check it out after these last set of remaining tasks.
I know you guys all want to check it out but we need to get these last of work items done. Our network is unlike any other website in the world and the speed of the UX will amaze you. 🔥
This is going to be my 1 priority tomorrow to find a work-around as we are few days from Alpha launch. Most likely solution will be as follows: Your delegated minter can sign and is counted as the same signature as locked-in DAM address.
Will have to investigate tomorrow but I've been able to get signing to work with Metamask with other addresses just fine. In the future we'll expand the alpha functionality to also consider "burn received amount" as qualification (not just burned amount). So if you are either burning OR someone burned to your address, you will be able to generate alpha links
IF INVITED: The number of links you get is dependent on your burn amount. Alpha dashboard links will function as follows (this will change in the future), the invitation links work as follows:
Burn or have received burn of ANY FLUX amount: 1 alpha link
Burn or have received burn of 10 FLUX(~$20) : 2 alpha links (You technically have 2 available spots in the burn queue at beta)
Burn or have received burn of 20 FLUX (~$40) : 3 alpha links (You technically have 3 available spots in the burn queue at beta)
Burn or have received burn of 100 FLUX (~$200) : 5 alpha links (You technically have 5 available spots in the burn queue at beta)
Burn or have received burn of 1000 FLUX (~$2000) : 10 alpha links (You technically have 10 available spots in the burn queue at beta)
ETH Automatic syncing is disabled. We'll be running syncs manually to catch up to latest block
Alpha is INVITE ONLY, Only MVBs and Community Assistants are invited at the start. These are still very early stages of the network and this is our first network test. We'll send out more invites as the need arises. 🔥
Added new "old version" splash if you are somehow caching old index.html version. The button on this screen will reload the current page with current timestamp to avoid cache.
Wanted to give you a quick update on how you will connect to our Datemine DeFi Pro Analytics.
There will be a new built-in button on all decentralized dashboard builds. By clicking this button you will be prompted to sign a custom message with your address. This does not cost anything but allows the analytics server to verify that you have access to the address that is signing the message.
Once you sign the message you will get unique access links to the dashboard. These links are unique and every time you use them you will kick anyone else out using the same link. (In a future update you will be able to re-generate these links by signing another message).
By using this approach with the burn queue we're able to eliminate registration but also connect core use base together. Don't forget YOU MUST burn FLUX to access the new analytics. The more FLUX that is burned for your address the higher your access priority is to the server.
We'll have more updates as the Alpha is coming in just 5 days. 🔥
· hodlforjesus · #dev-updates
