v2.2.2

• Update Economics to Use api.runonflux.io to get node count

v2.2.1

• Updates Kadena Chainweb Data specifications - more CPU and RAM resources
• Updates several dependencies
• Dashboard Economics - Added a refresh timer (every 10 minutes) and retry-on-error for api calls

v2.2.0

• FluxOS Fork height: 983000

• Apps Specifications v3:

  • Inclusion of number of instances
  • instances is an integer value between 3-100 specifying minimum instances to be spawned per application
  • Minimum of 3 instances is required and new base standard
  • Price is calculated based on every 3 instances. Eg. For 3 instances (base) user is supposed to pay 4 Flux. If user decides to that a minimum of 8 instances is required, then price

let price = 4;
const additionalPrice = (price * 5) / 3;
price = (Math.ceil(additionalPrice * 100) + Math.ceil(price * 100)) / 100;
price = (Math.ceil(6.66666 * 100) + Math.ceil(4* 100)) / 100;
= 10.67 FLUX

• Price changes
  • price is now possible to be adjusted via Flux forks
  • In incoming Flux fork, price for applications will be lowered 10 times and as well minPrice for application registration or update.

height: 984000, // height from which price spec is valid. Counts from when app was registerd on blockchain!
cpu: 0.3, // per 0.1 cpu core,
ram: 0.1, // per 100mb,
hdd: 0.05, // per 1gb,
minPrice: 0.1, // minimum price that has to be paid for registration or update. Flux listens only to message above or equal this price

• Minimum instances changes to 3 (previously 5). Maximum additional instances per application stays same (+5). Eg. For application with minimum instances of 12, application will now run on 12-17 nodes.
• UDP support
• Applications can still use v2 or even v1 specifications. However UI will be enforced to v3 specifications at time blockheight fork
• Additional minor fixes and improvements

All nodes must update prior 983000 (3rd November).

v2.1.6

• Enforce minimum supported version to v2.1.5

v2.1.5

• Update FluxBench min version allowed 2.3.1
• New Anti-Cheating Measures
• Show on bottom right FluxOS instead of Flux version
• Update Kadena Chainweb Node application

v2.1.4

• Fix for open xDAO proposals not showing details
• Fix calculation of price for previous specs

v2.1.3

• Updates Kadena application (Kadena Chainweb Node)

v2.1.2

Fix setting DOS state for Flux IP detection failed for arm64 devices that take time for fluxBench to start.

v2.1.1

• Fix FluxOS mark node as DOS state before the FluxBench starts.

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