Empowering innovation through secure, decentralized cloud solutions, fostering a future of limitless connectivity and data freedom: https://t.co/oY3uehWW2d
FluxOS version 8.24 has officially rolled out. With this release, incoming applications on Flux gain a dedicated gateway, ensuring that all app registrations as well as modifications proceed through authenticated connections between ArcaneOS nodes. Before any application is registered, a quorum must give its approval. In addition, each node now compiles its chain index using an accelerated process. This milestone arrives just one week after version 8.23 introduced on-chain recording for node migrations.
Powered by a global network of nearly 7,000 servers managed by independent operators, Flux offers a versatile environment for your hosting needs today. You can quickly launch a game server in roughly 30 seconds with pricing beginning at $1.99 per month. If you are looking to publish a static website without creating an account, you can do so completely free at http://drop.app.runonflux.io. Additionally, the network easily handles MySQL or PostgreSQL clusters, alongside any Docker application deployed redundantly across multiple machines at the same time to ensure constant uptime. Discover the possibilities at http://runonflux.com
FluxOS v8.23.0 officially launched on November 6, introducing several practical updates that node operators will want to note.
To start, tracking node relocations now relies directly on the blockchain's own ledger, with block height serving as the benchmark for evaluating any holds related to IP modifications. Resource management has also been strengthened, as component CPU restrictions are now strictly mandated instead of just requested. Alongside this, application storage volumes leverage direct I/O, ensuring that a single app cannot overwhelm the entire disk with traffic. Transparency sees an upgrade as well, with kernel taint flags being actively recorded so that an affected kernel cannot be mistaken for an untainted one. Finally, the software handles Bitcoin message signing without relying on bitcoinjs-message, removing an unnecessary dependency from the architecture.
You can explore the remaining details and technical documentation directly on the official release tag.
Even on a standard Tuesday, over 6,900 active game servers operate smoothly across 56 countries, ensuring thousands of virtual worlds stay live while their owners attend to their daily work.
This milestone comes just twelve days after the previous update, marking continued growth for the games hub. The catalog now stands at 37 titles, featuring comprehensive sections dedicated to Killing Floor 2 and Icarus.
Every single server is powered by independent nodes and provides convenient in-browser management, including direct file access, backups, system restarts, and an integrated terminal.
Following a security review completed in October, the newest release is now live for both mobile devices and web browsers.
At its core, authentic approval means being able to clearly read what is presented on your display, since accepting a mere hash leaves you signing blindly. SSP 2.2 resolves this by presenting the entire request prior to any signature. Through Wallet 2.2 and Key 2.2 from @SSPWallet_io, typed data appears comprehensively on the screens of both your wallet and your key. This setup allows you to inspect each transaction directly against your personal keys, while establishing pairing authentication using six words.
Additionally, outgoing Zcash transactions now adhere to the v5 format, satisfying the requirement introduced by NU7 on Nov 5.
The release of FluxOS 8.23.1 brings important updates to node maintenance and data privacy. Because unencrypted plain text remains vulnerable to exposure at any transit point, enterprise application specifications in this version completely eliminate plain text transmission. In addition, routine cleanup is streamlined across legacy nodes. If a node currently hosts an enterprise app that is not registered, the system will autonomously clear it out. Operators do not need to take any manual intervention beyond applying the update, as the purge process executes on its own.