Releases: RunOnFlux/flux
v2.1.4
v2.1.3
v2.1.2
v2.1.1
v2.1.0
- Update economics dashboard
- Fixes several conditions on applications
- Fixes message processing
- Resolves missing application messages, specifications caused by wrong message processing
- Better checks on Flux responsiveness
- Removal of old UI code
Previous message processing was purely chronological and did not count cases of application messages coming in random order. Previous processing was always looking just for its local knowledge of application that is in global specifications - application that is up to date right now running on the network based on local node knowledge. The update was based on local knowledge of existing specifications not on exactly previous message of specifications. This was wrong. In case node joins the network, there was no way for the node to update the apps specifications based on previous messages. Application that already expired based on local node knowledge would never registered as application available on the network as a whole.
This version will be enforced within 72 hours
v2.0.5
v2.0.3
v2.0.2
v2.0.1
v2.0.0
- Welcome to your new FluxOS Dashbord UI
- Our focus with new UI was to bring user experience to another level. New UI had to met industry standards, be easy to navigate, orient and understandable for end user
- We have focused on experience across all devices, use your mobile phone for node management, app browsing, table, your TV, the choice is yours
- Focused on speed. Performance is a key to factor, we will be constantly trying to improve on it and deliver Flux to you as fast as possible.
- Our experience and history with VueJS across both Flux and Zelcore was always a pleasant one and thus we choose this framework to build onto as well. Since FluxOS v1, Vue has changed as well. Our team embedded latest Vue features and structured v2 around composition API. We are looking forward to transition to pure Vue 3 and leverage all of its latest functionality this year.
- Flux now comes with prebuilt UI which comes with benefits across the table, faster, predictable, lower hw usage...
- To get the most out of Flux v2, It is recommended for Flux to be fully stopped and started using
npm run hardupdateflux
- To get the most out of Flux v2, It is recommended for Flux to be fully stopped and started using
- Improvements on hardware measuring
- Update scripts improvements