We've now got another exciting way to prove the Datamine use case with a new view of how much FLUX was minted based on locked-in DAM.
The new analytics update will feature a number of new data points to get an even better understanding into what is happening behind the scenes. For example in the new view you can see how much FLUX was minted based on the locked-in DAM amount.
In this example we can see that someone that locked-in 7x less DAM minted MORE FLUX due to burning FLUX. Our ecosystem incentivizes smaller investors to perform a BUY->BURN->SELL cycle through a FLUX pool to receive up to 10x increased FLUX mints (something whales can never do).
We'll have more exciting new data points in the coming days so stay tuned! 🔥
This new build features the long awaited update to the calculator section. Now you can use our realtime FLUX forecasting tool Without Locking-in Datamine (DAM) tokens.
This comes with fair prefilled values of 3x time bonus, 1000 DAM-lock in (~$200 USD) and 3x time bonus for locking-in ~28 days.
This together with the updates from yesterday now provide a cleaner UX especially for new users that are onboarding.
This weekend we'll have some new analytics data views so be sure to stay tuned for updates. 🔥
Another analytics update is live! You now get "instant search" navigation so you can finally paste in any address you want to go to.
Tomorrow the plan is to make a couple of updates to our decentralized dashboard. Specifically I want to add automatic retry mechanism for the "Ethereum latency" error that pops up, fix a couple of display bugs and update the roadmap.
So be sure to check that update out in coming days for improved UX. 🔥
Today I've been able to add block syncing to our analytics platform. This means we can now assign dates to all actions instead of block numbers. This makes our running ledger even more powerful as well as being able to get a better idea of lock-in durations.
This adds a bit of overhead to syncing speed but I am hoping there will be better sources of Ethereum log data in the future.
Additionally cache is automatically purged when there is new data to sync. This means we can utilize cache until a new block comes in so data is always fresh. There will be additional improvements to cache in the future.
Current estimate for Alpha is 2 months which will take us into public BETA. By this time we should have all the data points we want, realtime syncing and FLUX burn queue.
Updated roadmap is coming later this week to reflect this upcoming Beta release. 🔥
Yesterday we've put up our build of the new Alpha analytics and sent out over 25 invite keys. There is a new build out today with the following features:
Reworked connection management. Now if you use the same Datamine Pro Key, the other window that was connected gets kicked out. This was the main major issue that happened to two users yesterday so I wanted to make sure that it was addresses as this was an oustanding item. This new connection management works a lot like Tradingview.
Alpha key is remembered now after login. This will make it easier to test out new features without re-entering the key each time.
New Docker optimizations to ensure higher uptime and better update rollouts in the future requiring a simple docker restart.
We'll be adding a ton of new features this week and hopefully testing Realtime Ethereum block updates later this week as it's a core feature! Lots to come this week so be sure to stay tuned 🔥
Was going to work on the rate limiting but decided to finish up the reservation updates I mentioned before.
Now the reservation server will properly recycle unused connections which means I can sleep better at night knowing the server won't go down due to a bottleneck.
Another security feature I added is privateKey generates a unique user id instead of it being same as privateKey. This means that even if you have the Datamine Pro Key you can't guess what nchan id that user is connected to.
Additionally the alpha keys have been generated and proper alpha key checks are in place now.
Now there is just two items remaining on my list before launch:
This extra week of Alpha polish is really epic. I've finished up the frontend state management updates and will jump to rate limiting tomorrow.
These new frontend updates and Datamine Pro key entry allow me to spin up multiple network connections and are great for testing purposes.
I think the extra time that we spent with the shared widgets is totally worth it. They're really a staple of how powerful the network is. For example in this screenshot we have two unique network connections.
Notice how the active widgets is still 1 even though there are two of the same shared widget. On top of this each shared widget can choose who to send messages to.
Things are coming along nicely, can't wait to show you guys! 🔥
Another busy day with Datamine Pro Analytics. I finished the last two remaining tasks but there are some last minute changes that I would like to squeeze in this week.
We need to add basic rate limiting before Alpha. Originally this was scheduled for Beta but after a frontend rewrite today we have a pretty good way to add this. This will ensure Alpha users don't abuse the server.
There are also some reservation server improvements I would like to add. Particularly recycling unused connections.
We also need to update how page routing works. Right now we're using HTML5 url fragments but this needs to be converted to hashes (as the centralized dashboard is also host on github).
Once these core additions are complete I will do another round of checks to see what else is remaining for launch.👌
· hodlforjesus · #dev-updates
