RunOnFlux/flux v3.31.0

on GitHub

• Flux App Specification v6
  • expire: v6 brings new parameter of 'expire' determining how many blocks application can live on the network. From 5000 blocks till 264000 blocks (~1 week - ~1 year). This parameter can be adjusted on a 1000 block interval (~1+ day).
  • Default supported options by Home UI are: 1 week, 2 weeks, 1 month, 3 months, 6 months, 1 year.

General:

• Flux Foundation Application address changes from single signature to a 3of5 multisignature address consisting of following core team key holders: Daniel, Parker, Tadeas, Jeremy, Valter. This adds additional trust and security to FluxOS

• Ability of soft forks:

  • Foundation multisig address can initiate soft-forks of FluxOS by sending proper transactions to itself with soft-fork specifications included in the message field.
  • Current soft fork supported is application price adjustments with more potential flags to come.
  • Soft forks activate immediately on the following block on which transaction was mined.
  • This introduces new database 'chainparams'

• Application prices can now be adjusted on the fly with soft-forks

• Blacklist was extended to also support blacklist of ZelID and application hash

• Continuous better check of blacklisted app images, ZelIDs, and application hashes. This adds faster response of Flux team to fight malicious applications on the network

• Test Launch: Applications can now be test launched. Upon broadcasting a message on the register application section, user can opt in for 'test launch'. This will launch the submitted application specifications on the locally connected stratus node and so app deployer can quickly see how app will perform and catch potential mistakes in set up. Test Launched app live on the node only for a few hours. Only one test launch is allowed per registration.

• Node owner can now launch any application on the global network as well as any prior existing application specification on his node. This launch is temporary and lasts about 36 hours.

• Applications can now have up to 10 components instead of 5

• Every application on flux now has its own flux docker network living on 172.50+X.0.0/16 subnet with 172.50+X.0.1 gateway. This adds more security and separates different apps from being able to talk to each other. X represents the total number of unique apps installed on a specific node. It is possible that 1st application instances will have a network of 172.55.0.1, and 2nd will have 172.51.0.1 in case there are already some apps installed on those nodes. The docker networks created have a format of fluxDockerNetwork_APPNAME

• Experimental: Multiple volumes:

  • Application component can now specify multiple paths to mount to the same volume or a volume of a previous component. containerData volumes are separated with | character.
  • Eg. Second component containerData s:/my/data/path|0:/my/another/data|0:/my/anotherB/data|1:/my/path Second component has its main data volume created and mounted to its location of 'my/data/path' and also specifies flag of s for syncing this data volume. Additionally mounts 3 more volumes - /my/another/data and /my/anotherB/data will be mounted to 1st component data volume, /my/path will be mounted to this second component data volume.

• Autmoatic addition of incoming connections. Flux will now ask other nodes to try initiate connection to our node.

• Additional UI and Backend improvements, fixes.

• v6 specifications activate at blockheight 1,300,000. ALL nodes must update to the release prior this blockheight.