v3.36.2

• Fixes IP check

v3.36.0

• Allow installation of multiple applications using the same image on the same instance (exclude presearch)
• Check for applications availability is adjusted
  • previous scheme was testing availability of installed applications. That had some limitations as ports may have been in use by the application and so respond in a different than expected way. Furthermore the test was only done on nodes on which some application was running
  • FluxOS will now choose a random unused port within application range and test availability of that port by running a simple listening server. This test is way more deterministic, predictable and properly tests even nodes without any app running.
• FluxOS Home Dashbord adjusted for halving with taking data about rewards directly from daemon.
• Introducing Flux Storage on Home UI
  • Storage for big variables and other parameters: https://github.com/RunOnFlux/fluxstorage
  • Upload Envionment parameters, Commands or Contacts to central Flux Storage managed by Flux team.
  • This allows for long list of Environment parameters or commands going beyond FluxOS character limitation.
  • Furthermore Environment parameters and Commands provide slight obfuscation as they are not directly stored on FluxOS but only as a link to Flux Storage that only FluxOS itself can access. This should definitely not be treated as private storage but just as a slight obfuscation mechanism
  • Contacts on the other hand if used in Flux Storage are fully private. Only Flux team managing Flux Storage can access it. This provides a set of anonymity where you email won't be exposed publicly. Contacts field is used primarily for notifications about applications - expiration, launches and more.
  • Flux Storage can be directly used on Home UI in app registration or update.
  • The Flux backend scheme for Flux Storage is F_S_[CMD, ENV, CONTACTS]=URL
• Introducing Apps Monitor https://github.com/RunOnFlux/appsmonitor
  • Very basic tool on which we will expand to add functionality of application monitoring, notification system via email and other provided contacts
• As Flux grows we are forced to protect development team, node operators and users of Flux by applying Terms of Service. This forces more strict rules on what can Run on Flux. https://cdn.runonflux.io/Flux_Terms_of_Service.pdf
• Don't allow incoming connections from non-routable ips

v3.35.0

• Titan UI improvements
• Improvements on application availability check
• Blacklist and application removal optimization

v3.34.1

• Various bug fixes

v3.34.0

• Enforce application port checks
• Corrections in app port checks, allowance and deletions
• Minor UI and other fixes
• Version will be enforced on the 19th of February

v3.33.1

• Fixes missing opening of port before asking if receiver applications port is available
• Fixes 'Flux does not have sufficient peers' error happening on nodes that are not yet confirmed on the network. FluxOS can't have peers if it is not confirmed on Flux network first.
• Better logging
• Fixes marketplace search

v3.33.0

• Adjustment of Firewall and UPNP is now done every 10 minutes instead of relying on Flux block times.
• Fixes bug in pricing on application updates - will come to effect on blockheight 1315000
• Fixes typo bugs on flux node flux apps availability that was causing some checks to be skipped
• Improvements int reindexing of global applications specifications

This is a forking release. Nodes MUST update before blockheight 1315000

v3.32.1

• TTL on UPNP mapping is set back to 0
  On development mode we will set the TTL to 1 hour and test with more community routers.

v3.32.0

• Visit button now accounts for more components and ports, should handle more apps for proper opening
• Minimum FluxBench allowed version is 3.7.0
• Restoration of Ports and UPNP will be happening every 6 blocks (~12 muntes) instead of every 25 blocks. This should lead to more reliable upnp mapping and ports management
• UPNP mapping is now assigning time for 2 hours, instead of indefinite. This should lead to more reliable mapping as routers reflect ttl of 0 differently
• Syncthing is now properly running on assigned port of fluxos on upnp nodes. NAT management of syncthing got disabled and is controlled by fluxos.
• Applications Docker Network is now deterministic based on the LAST character of application name:
  Docker network is created in following scheme

172.XXX.0.0
where XXX is character code of last character of the application name.

• Home UI and Syncthing properly running and be accessible is now being checked by other fluxos on the network. This should cause nodes that do not have properly set firewall rules to go offline
• Syncthing running properly is now enforced. This will cause nodes that have issue running syncthing properly to go offline
• Corrections of start and end options on some daemon rpc calls
• Reduced number of application running messages and broadcast of those messages. From every 20 minutes to 60 minutes. This should decrease node load while still maintain high accuracy.
• Applications are now being spawned on a node after 90 minutes of running fine (previously 20 minutes)
• Better removal logging of applications
• Corrects Home UI to give apps deployment multisig address
• Apps Service Test Suite
• /flux/checkappavailability post api calls is used internally by the nodes to test if app ports are properly responding verifying that application is running smoothly.
• Periodical checks of availability of applications installed on the node. This asks other flux nodes to check if application installed is truly available from outside. This check is in testing phase and will be enforced in the next version. Most likely many nodes will fall off the network if they have misconfigured firewall
• Automation of hash whitelist - this ensure hash list is always up to date, support for 'development' nodes and potential human factor mistakes on hash whitelist
• /flux/entermaster and /flux/enterdevelopment api calls are allowing to switch between master and development branches of fluxos. // for development purposes
• development flag added to userconfig file // for development purposes
• development nodes are running edge source code and receive updates first. Further periodically pull latest code to run. Development nodes are participating in main net testing latest features of Flux before entering mass production. The testing phase is so adding a crucial step to ensure mass production is unaffected from potential critical bugs.
• decryptionkey flag added to userconfig. Flux is preparing for introducing 'Trusted Nodes' to solve secrets and privacy of applications. // experimental
• Other minor improvements and bug fixes

v3.31.2

• Fix enforcement height of v6 on UI which was preventing application registration on Home UI
• Better responses and logging on app redeployments