Coin Alerts

FLUX news archive

269 stories

Last checked

Refresh

Estimated news impact scores by coin. Scores are not price-change percentages.

Newest first

Check failed. Showing saved news from .

  15. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    FluxOS Gravity v8.17.0 is live. This release brings 24 commits focused on making Flux nodes smarter, more resilient, and more secure. The new app tampering model introduces weighted incident scoring, stronger identity handling, and automatic cleanup of legacy incident data.

  16. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    1 day to go. 🔥🔥🔥 Tomorrow, we unveil the Flux H2 2026–2027 Roadmap. Join us live for a look at what's next across the Flux ecosystem, including product updates, upcoming releases, and the vision driving the next phase of growth. Have all your questions ready!

  17. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    To better protect users and the integrity of the Flux network, ArcaneOS will soon be enforced on all residential nodes. This decision follows multiple incidents involving malicious node operators. Enforcement will begin rolling out over the next few weeks. Thank you.

  18. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Introducing Orbit— Git Deployment for Flux A new way to deploy on Flux. Connect a Git repository. Deploy globally. Manage everything from a single dashboard. No Docker. No server configuration. No infrastructure headaches. Just your code and the Flux Network.

  20. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    The application layer of the internet is more decentralized than it's ever been. The infrastructure layer is more centralized than it's ever been. One of these trends will give. But when everything is breaking and the chips are literally down. You can always count on Flux.

  21. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    ArcaneOS Security Audit InFlux Technologies is committed to security and transparency. We want Fluxers who use our systems daily to know that our infrastructure is stable and will protect their applications. We unveiled ArcaneOS in 2025 as a security upgrade to FluxOS that cryptographically encrypts and allocates secure disk space on provider machines, ensuring that only developers have access to their deployment data. To demonstrate our commitment to security and transparency, ArcaneOS recently underwent a rigorous security audit by the blockchain security firm Halborn. Flux granted Halborn access to the ArcaneOS Git repository to conduct thorough security testing, including automated and manual analyses, to detect potential vulnerabilities. This article will review the audit and highlight key details of Halborn’s security report. Let's get into it! Report Findings Overall, Halborn's security audit came back clean; the audit revealed 14 findings, including 2 high risk, 3 medium risk, and 9 low risk issues, all of which have been addressed and patched since the report was released. Additionally, Halborn's audit found zero critical vulnerabilities in ArcaneOS. The two high-risk findings the audit revealed occurred in the low-level system layer. Kernel modules serve as the foundation for applications, allowing codebases to be updated with new features without rebooting the entire system. Kernel-level vulnerabilities can cause issues elsewhere. The first high-risk vulnerability that Halborn's audit found was a use-after-free (UAF) bug in an ArcaneOS kernel module, leading to memory referencing issues between computing threads. UAF vulnerabilities occur when datasets in a codebase are removed but are still referenced by threads later, potentially corrupting the application's behavior. Halborn suggested synchronizing properly with spawned threads during app shutdowns to prevent data removal or cleanup from occurring while workloads are running. The report notes that the UAF finding has been resolved. The second high-risk finding the Halborn audit revealed was a race condition that could also corrupt application memory. Race conditions occur when app operations depend on the timing of uncontrollable events and variable workload sequencing rather than on fixed, predictable timelines. When two parts of an operating system access shared data simultaneously, and no one coordinates traffic, data flows become congested because memory references don't know which dataset to access first. Most of the time, race-condition vulnerabilities are harmless, and the Flux team has addressed this finding. ArcaneOS Boot Integrity Halborn noted that ArcaneOS features solid boot integrity—a mechanism within an operating system that enables apps to launch in unmodified, trusted states when devices boot consistently. Secure boot measurements can confirm certain early boot states. Halborn's audit found that despite its boot setup, the integrity of Arcane's initial RAM disk, a temporary root file for memory, was not automatically guaranteed and could lead to unauthorized tampering. If the integrity of early-boot components isn't guaranteed and can be tampered with, malicious parties could reduce protections before apps even launch. Halborn recommended that ArcaneOS strengthen access key protection by tying them more directly to additional boot measurements. Application Layer Vulnerabilities The low-level layer and Kernel modules handle backend interactions, while the application layer is the frontend that manages user interactions. Halborn's audit found several medium-risk vulnerabilities at the application layer of ArcaneOS. One medium-risk finding of the audit was the use of hardcoded tokens between systems, implemented as static strings with light obfuscation. Meaning that tokens, which are used as sensitive access credentials, are directly embedded into application source code rather than separately and securely stored on their own. Halborn's audit stated that hardcoded access can appear to be a security boundary without actually functioning as one, especially if a malicious actor already has deep access to the system. This issue was resolved because the Flux team holds that tokens don't serve as a point of access in ArcaneOS and that obfuscation is used to resist automated app scans, rather than as a headline security control. Another medium-level application‑layer issue was a CORS misconfiguration. CORS controls which websites are allowed to read responses from an API inside a user’s browser. If CORS is too permissive, a malicious site can potentially trick a logged‑in user’s browser into making requests and reading the API responses. Halborn recommended allowing only approved API requests when the origin can be determined. The Flux team has resolved this issue. Conclusion Halborn's audit found no critical security vulnerabilities in ArcaneOS. However, it identified a small number of high‑impact, low‑level problems and tracked the team's responses. Some issues were fixed directly. A few were accepted as risks based on how ArcaneOS is intended to be used Halborn also recommends a follow‑up assessment within six months or after major system updates, which is just standard maintenance. Flux will continue to improve the security of its systems for users, and we will always report audit findings directly to our community.

  22. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    How FluxAI Keeps User Data Safe Closed-source AI models are ineffective at securing user data. Closed-source AI models retain user data, but not FluxAI—we secure your data through RAM processing, no natural data persistence, and isolated model interactions! LLMs like OpenAI’s ChatGPT, Anthropic’s Claude, or Google’s Gemini retain user data by logging conversations and storing prompt histories for model retraining. These practices raise concerns about data retention and ownership. Privacy should always come first. So, rather than treating user data as fuel for model improvement, the solutions in the FluxAI product suite prioritize user-centric data sovereignty, keeping you in control of your data. Using Meta’s open-source Llama architecture, FluxAI secures user data through isolated model interactions, no natural data persistence, in-memory input processing, and no retention of user data for model training. Let’s take a closer look! Isolated Interactions Every interaction with a FluxAI solution is siloed; each session is an isolated event, and models cannot recall prompts from previous sessions. This is because FluxAI leverages a Stateless Architecture in which each conversation request is self-contained. For FluxAI to remember something from an earlier interaction, users must explicitly provide that context in a new request. Aside from the privacy it provides, a benefit of Stateless Architecture is that its design isolates computations, enabling more focused task execution. Stateless Architecture also simplifies horizontal scaling—in which computational workloads are distributed across multiple servers—by routing user requests to other servers without requiring session state synchronization. Zero Natural Data Persistence Data persistence occurs when data is retained after the program that curated it has ended. In this case, it occurs when closed-source LLMs track and store conversations to reference for context in new user engagements—previous interaction data “persists” even after an exchange ends. FluxAI does not retain conversational data from one chat to another unless opted into through a premium subscription. While data persistence enables continuous learning for models, there is no silent archiving of interaction data. Fluxers can use models knowing their inputs won’t be stored for model retraining. In-Memory Processing FluxGRADER, a FluxAI document evaluation tool, utilizes in-memory processing to secure user data. This tool processes documents entirely in RAM, meaning uploaded files will never be written to permanent disk space and will be discarded once processed (and a grade is assigned). The grades that documents receive are also discarded after they are assigned. Why It Matters Feeding user data into models to improve them is a double-edged sword. While retaining data can enhance model contextual outputs and indirectly reduce computational energy usage, it infringes on users' ownership of their data. By embedding privacy at the architectural level, FluxAI provides users with reliable trust, valuing data ownership not just as a feature but as a fundamental right. For more info on FluxAI, be sure to follow us on X and check out our blog!

  23. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    FluxOS Frontend v3.3.0 is live! This release introduces Stripe auto-renewal subscriptions across all deployment flows, including the Marketplace, WordPress and game installs, and Git paid plans. This latest version is now available on https://cloud.runonflux.com/

  26. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Deploy once, run everywhere. FluxCloud makes it simple to launch scalable apps on the world's most resilient decentralized infrastructure. Centralized cloud costs more than it should. Flux costs less than it should. Same uptime. Same speed. 90% savings. Switch today: http://runonflux.com/

  27. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Deploy once, run everywhere. FluxCloud makes it simple to launch scalable apps on the world's most resilient decentralized infrastructure. Centralized cloud costs more than it should. Flux costs less than it should. Same uptime. Same speed. 90% savings. Switch today: http://runonflux.com/

  28. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    FluxCloud v3.0.0 is rolling out across the Flux network! This a fundamental upgrade focused on global accessibility, faster deployments, and a smoother production experience on decentralized infrastructure. Here is all about it and why it matters. (A thread)

  30. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Flux Community Opportunity – Special Marketing Team Flux is opening a new Special Marketing Team, and we are looking for motivated, skilled community members who want to play a direct role in accelerating the ecosystem's growth and adoption. This team will work closely with InFlux and the broader Flux leadership to help drive: -Global brand awareness -Strategic partnerships -Content creation and campaigns -Community expansion and engagement -Product launches and announcements This is not just volunteer moderation; this is a focused, results-driven group tasked with pushing Flux into the next phase of adoption across Web3, DePIN, AI, and enterprise infrastructure. Who we’re looking for: -Marketers, designers, writers, editors -Social media and growth specialists -Influencers and community leaders Anyone with real-world marketing experience or proven on-chain contributions Why join: -Work directly with the core Flux team -Build your reputation inside a top-tier decentralized project -Be part of major launches and strategic initiatives -Potential for long-term roles and compensation based on performance If you believe in Flux and want to help shape its future, this is your chance to get involved at a deeper level. Apply here: info@runonflux.com Or message: Betty on Discord Let’s build the next phase of Flux — together.

  32. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    $FACT Nodes are live on the FluxCloud Marketplace! 🔥 The Factor team collaborated with us to lower the barrier for their community to run decentralized nodes and strengthen the Factor network. Start at $7.30/month for 3 Factor node servers 👇 https://cloud.runonflux.com/marketplace/factornode https://t.co/zUOYjR5NyO

  33. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Cloud buyers are becoming sharper. They’re no longer impressed by glossy dashboards if the underlying infrastructure still depends on one region, one data center, or one company. Flux offers a decentralized cloud that keeps your applications running even when traditional providers blink.

  35. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    We are partnering with @uquidcard to push Web3 commerce into a new level! Uquid is bringing millions of products into a crypto-native shopping experience, and Flux is delivering the decentralized, resilient infrastructure that makes it fast and reliable. #Web3ShoppingDay https://t.co/cyDU0tkp6H

  37. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Feels like one of those weeks where something big is about to drop. We’ve been tightening a few things behind the scenes on Flux, and it’s finally coming together. Can’t say much yet… but this week should be interesting.🤭🤭 Hold on to your hats! https://t.co/97npxdl3HM

  38. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    A Kadena resurrection courtesy of the community, @dak_flux and Flux? Here's all you need to know about this latest move: https://pintu.co.id/en/news/226986-kadena-rising-from-the-ashes-daniel-kellers-new-strategy-ready-to-change-the-crypto-world https://t.co/69rJhWS2J4

  40. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    FluxNode rewards are becoming the hottest thing on the block right now!!! Every cycle, more operators are joining in, securing the network, powering the ecosystem, and earning for contributing real infrastructure value. If you’ve been watching from the sidelines, this is your cue!

  41. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    FluxOS Gravity v7.1.0 is LIVE! We're excited to announce a significant update to FluxOS, featuring 97 commits and substantial architectural improvements! What's New: -Multiple Independent Mounts & File Support -Mount multiple volumes per component with granular control -Direct file-to-file mounting (not just directories!) Enhanced validation and automatic mount point recreation -The new FluxCloud website will be released with full support of the new multiple mount points in the next couple of days -Third-Party Docker Registry Authentication (BETA State) -Full support for private registries (AWS ECR, Azure ACR, Google GAR) -Smart token caching with auto-refresh Custom registry authentication -Component-Level Redeployment -Update individual components without redeploying entire apps -New /apps/redeploycomponent API endpoint Reduced downtime, improved efficiency -Enhanced Syncthing Integration -Auto-detection and recovery of stalled syncs Fixed race conditions in primary node selection Improved synchronization state management By The Numbers: 136 files changed 21,483+ additions 97 commits of improvements Full Release Notes: https://t.co/Je3Wp8bGRx Upgrade now to experience the enhanced FluxOS Gravity! Thank you, Influx Team @runonflux_edge @RunOnFlux

  43. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Today marks a defining milestone for the Flux ecosystem: the full rollout of Proof of Useful Work v2. The network now runs entirely on node-based validation, rewarding infrastructure providers for real-world utility. This transformation represents the culmination of years of innovation and collaboration across the Flux community

  44. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Announcement from the Flux Team The Flux team would like to reaffirm our continued support for the @kadena_io ecosystem and its community. Including but not limited to, wallets (Ecko and Zelcore) and technical guidance. As the Kadena Foundation begins to take shape, we are committed to assisting in this important transition toward a fully community-driven project. Flux was the first token added to KDA, and we created a parallel asset for it. We take great pride in what we have built with the community. Flux has always believed in the principles of decentralization, transparency, and collaboration, and we recognize the strength that comes when communities take the lead in shaping their own future. Our team will continue to offer technical guidance, infrastructure support, and strategic collaboration to help ensure the Kadena Foundation’s success. We’re excited to see the Kadena community step into this next phase of growth and governance — empowering users, builders, and supporters to carry the project forward together. Flux stands ready to support the Foundation and community every step of the way. Onward and upward, The Flux Team

  45. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Flux’s new emission model introduces predictable, annual 10% reductions in block rewards. This replaces the traditional cycles used by many blockchains, which can disrupt stability. By smoothing out the economic curve, Flux ensures steady growth for both infrastructure and participants. It’s a balanced approach that favors long-term health over short-term speculation.

  46. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Let’s talk numbers: Since integrating $KAS Public Nodes last week, we’ve seen 30 unique deployments, totaling 137 Public Node servers! 🔥 Already deployed on FluxCloud, or planning to spin one up soon? Let us know below, guide in the comments. https://t.co/BQ0cFw4zCc

  48. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    Another AWS outage is impacting the world wide web! DePIN solutions like FluxCloud help mitigate these issues. 💪 Past outages have led to great collaborations with companies exploring our solution. Interested in a free trial? Contact us at info@runonflux.com. https://t.co/5vBC3J4ZB9

  49. Published Social post

    Flux I Decentralized Cloud (@RunOnFlux)

    The Flux fork replaces halvings with a predictable 10% annual reduction in rewards. It’s a smoother model designed for long-term stability instead of sudden shifts in network economics. Gradual reward reductions let the ecosystem grow naturally, without shocks to supply or sudden inflation.

Showing 50 of 269 stories · Page 1 of 6. Filters apply to the full news archive.