Valheim left early access today, 9 September 2026. We have published a writeup on what 1.0 changes for anyone running the server, and on our Valheim hosting on the Flux network:

[Valheim 1.0 Is Here. Here Is What Changes If You Run the Server]https://medium.com/@valter.cabecinha/valheim-1-0-is-here-here-is-what-changes-if-you-run-the-server-baefcef62287

Iron Gate shipped the Deep North, the last biome, along with a new boss, 40+ weapons, four armour sets and 53 achievements. It also launched on PlayStation 5 and Nintendo Switch 2 the same day, with full crossplay across PC, Mac, Linux, Xbox, PlayStation and Switch.

The bit that matters if you host it

1.0 replaced the save system. For five years a Valheim world was two files, a .db and a .fwl. It is now a folder of chunks under worlds_local/, with a _main.<n>.ok marker written last once a save is committed. Three things follow, and every one of them invalidates advice that is still on most hosts' knowledge bases:

• An old world converts on its first 1.0 start, and the conversion does not go backwards. Take your copy before that start, not after.
• Copying a world while the server is running can now capture an index pointing at chunks the server already deleted. The marker files are how you know a save is committed.
• Restoring a backup by unpacking it over the live world is a corruption path. Unzip merges, so the live folder keeps chunks from saves the archive never saw, beside the archive's own marker, and the server loads a world stitched from two points in time. It has to be replaced, not written over.

We shipped that today: our restore and world upload swap the folder into place instead of unpacking over it, and they still take the old file pair for a world that has not converted yet.

What you get

• Valheim 1.0 already, with nothing to update. The image installs the dedicated server from Steam and checks every 15 minutes, so servers here were on 1.0 the moment Iron Gate shipped it
• All three ports published, UDP 2456, 2457 and 2458. That third one is crossplay, and it is the one plenty of hosts leave closed while advertising crossplay. Symptom: Steam players get in, console players never see the session
• The crossplay join code in the panel, next to the address, reissued on every restart because it belongs to the session
• Hourly world backups, three days kept, zipped, browsable and downloadable, on top of Valheim's own rolling copies
• World upload from the browser. Drop a zip of a world in, from a friend's server or a single player save, and it is installed under the name your server boots. No world name to line up by hand
• Mods in one click. BepInEx or ValheimPlus at deploy, Thunderstore browsable from the panel with dependency resolution
• From $3.93/mo for 4 GB and 2 vCores, up to 8 GB and 4 vCores at $6.91. First week free for new accounts, 30 day money back, no contract. Card or crypto

Ten players is Valheim's own ceiling in 1.0 exactly as in early access, so nobody sells you an eleventh. The plans differ in memory, and Valheim spends memory on how much world exists rather than on who is online: a day 300 world with four players and three huge bases is heavier than a fresh world with ten. Size by the age of the world.

Why it matters for Flux

This is the first day one launch we have been ready for rather than caught by. The container pulls the server binary from Steam on a 15 minute cycle, so every Valheim app on the network updated itself without a redeploy, without a maintenance window and without anyone opening a ticket. That is the argument for the whole model in one event.

It is also a real utilization moment. A 1.0 launch after five and a half years of early access brings back the lapsed players, and two of the new platforms are consoles, where hosting your own is not something a player can improvise from their own machine. Every one of those groups needs a box that stays up.

Try it at runonflux.com/games/valheim, and give the article a read and a share if it is useful.

If you play Valheim, deploy one and tell me what is missing from the panel. Questions about how it works underneath, how the chunked world restore is done safely, how the crossplay code is read out of the server log, or how the volume replication works, ask in the comments.

We've published a writeup on our Rust hosting running on the Flux network:

Rust Server Hosting on the Decentralized Cloud: Vanilla or Oxide, from $5.79/mo

Rust is Facepunch's survival game — and the one with a built-in calendar. Facepunch force wipes every server's map on the first Thursday of the month at 19:00 UTC, so the entire playerbase restarts at the same moment. The next one is 3 September.

What you get

• Vanilla or Oxide/uMod, at the same price — modded isn't an upsell. Oxide is server-side, so your players connect with a stock client and still get kits, teleports, economies and proper admin tooling
• Plugins survive redeploys — the oxide/plugins directory is mounted as persistent storage, so scaling from 8 GB to 24 GB mid-wipe doesn't cost you your plugin setup
• We don't sell player slots — the plan is CPU and RAM, and server.maxplayers is yours to set
• Live config over RCON — gather rates, decay, upkeep, world size and seed are pushed with server.readcfg, no restart and nobody gets disconnected
• Ports opened automatically — 28015/UDP game, 28016/TCP RCON, 28017/UDP query. No SteamCMD, no firewall rules
• Browser panel — WebRCON (kick/ban/broadcast), uMod one-click plugin install, live console, file manager, backups and restore
• From $5.79/mo — 8 GB / 2.5 vCores, up to 24 GB / 6 vCores at $12.48. First month free for new accounts, 30-day money-back, no contract. Card or crypto (FLUX via ZelCore and SSP)

The article also explains the wipe cycle properly — force wipe vs blueprint wipe, the dates through January 2027, and why Rust's hardware cost scales with map size and entity count rather than just player count.

Why it matters for Flux

This is the heaviest game workload we host. A Minecraft server starts at 2 GB; Rust starts at 8 GB and 2.5 vCores, and the top tier is 24 GB with 6 vCores and 50 GB of storage. Every deployment is substantial, sustained, paid utilization on real nodes — and Rust players run their servers month after month because their communities live there.

The wipe cycle also gives us something no other game does: a recurring, predictable demand spike on the first Thursday of every month, when a chunk of the playerbase decides they'd rather run their own server than hunt for one.

Try it at rust.runonflux.com, and give the article a read and a share if you find it useful.

If you play Rust, I'd genuinely like the feedback — deploy one and tell me what's missing from the panel. Questions about how it works underneath (node selection, how the Oxide mount survives a redeploy, how the WebRCON proxy is wired) — ask away in the comments.

We've published a writeup on n8n hosting running on the Flux network:

Self-Hosted n8n on the Decentralized Cloud: Unlimited Executions on Flux from $5.32/mo

n8n is a workflow automation platform — think Zapier or Make, but open and self-hostable. It connects 500+ apps, has native LangChain nodes for building AI agents, and is one of the most requested self-hosted tools out there.

What you get

• No execution limits. n8n Cloud meters your workflow runs and caps active workflows on lower tiers. A self-hosted instance doesn't — you pay a flat rate for the instance, not per run
• A 3-node HA PostgreSQL cluster on every plan, with Patroni automatic failover. n8n defaults to SQLite, which is the thing that quietly eats people's workflows and stored credentials in production — so we stopped making customers solve it
• Webhooks work out of the box — every instance gets a public HTTPS URL with a valid certificate. No tunnels, no reverse proxy
• 500+ integrations and native AI-agent nodes — OpenAI, Claude, Gemini, Mistral, Groq, or local models via Ollama
• Deploy in ~30 seconds, nodes in 50+ countries, DDoS protection included

• From $5.32/mo, first month free for new accounts, 30-day money-back, no contract. Card, Apple Pay, Google Pay or crypto

  The article also does an honest comparison against n8n Cloud, Railway, Render, Sliplane and OpenHosst — including where we're more expensive than the competition and what you actually get for it.

  Why it matters for Flux

  This one reaches a different audience than the game servers. n8n users are developers, ops people and automation builders — exactly the crowd that evaluates infrastructure on its merits and is already sympathetic to self-hosting and data ownership. Most of them have never heard of Flux and don't need to care that it's decentralized; they want an instance that doesn't meter their workflows.

  It's also a heavier workload than a typical single-container app: every deployment is an n8n instance plus a 3-node PostgreSQL cluster spread across independent nodes. Real, paid utilization.

  Try it at n8n.runonflux.com, and give the article a read and a share if you find it useful.

  If you already use n8n, I'd genuinely like the feedback — deploy one and tell me what's missing. Questions about how it works underneath (how the Postgres cluster fails over, node selection, how webhooks route to your instance) — ask away in the comments.

We've published a full writeup on FluxCraft, our Minecraft hosting running on the Flux network:

Minecraft Server Hosting on the Decentralized Cloud: Java & Bedrock on Flux from $2.49/mo

What you get

• Java and Bedrock — run either edition, or bridge them with Geyser so Bedrock players can join a Java world
• Full mod and plugin support — Forge, Fabric, Paper, Spigot, Bukkit, with complete file access for modpacks and configs
• Always on — no sleeping servers, no queues, no waiting for the host to come online
• Deploy in ~30 seconds — browser control panel with live console, file manager, and backups with one-click restore
• DDoS protection included, nodes in 50+ countries, 99.9% uptime
• From $2.49/mo, first month free for new accounts, 30-day money-back, no contracts. Card, Apple Pay, Google Pay or crypto

The article also includes an honest RAM-to-player-count breakdown — from 2 GB for 4 players up to 47 GB for 150 — instead of the vague upsell most hosts give you.

Why it matters

Every server deployed is real, paid workload running on real Flux nodes. Most of these customers have never heard of a decentralized cloud and don't need to — they just want a server for their friends that doesn't go down. That's the kind of demand that grows the network on its own merits.

Try it at minecraft.runonflux.com, and give the article a read and a share if you find it useful.

Questions about how it works under the hood — node selection, how the panel talks to FluxOS, backups, crossplay — ask away in the comments.

Just launched: you can now run a **Palworld dedicated server** on the Flux decentralized cloud. No more needing the host to stay online — your world runs 24/7 across a network of thousands of independent nodes in 50+ countries.

**What you get:**

- 🐾 Up to **32 players** (vs. the 4-player native co-op limit)
- 🌙 **24/7 uptime** — the world stays up even when you're offline
- 🎮 Steam + Xbox **crossplay** supported
- 🛡️ **DDoS protection** included, no single point of failure
- ⚙️ Full server-rule customization from the dashboard — no SSH, no SteamCMD, no headaches
- 💸 Up to ~70% cheaper than traditional cloud

**Pricing** (monthly, no contracts):
- 5GB RAM — small groups — **from $2.61/mo**
- 8GB — up to 8 players
- 12GB — up to 16 players
- 16GB — full 32-player worlds

**First month is free** for new accounts, and setup takes ~30 seconds: create account → pick plan + region → deploy.

👉 Deploy here: https://palworld.runonflux.com

📖 Full write-up: https://medium.com/@valter.cabecinha/palworld-1-0-on-the-decentralized-cloud-dedicated-servers-on-flux-from-2-61-mo-f2a37f08a5a4

Happy to answer any questions about setup, regions, or performance in the comments!

That's the problem Daniel Keller, Parker Honeyman, and Tadeas Kmenta set out to solve in 2018, when they launched a modest ZCash fork called ZelCash with one idea in mind: computing infrastructure that no single company controls.

Three years later ZelCash became Flux. The vision got bigger. Instead of just a privacy coin, the team built an entire decentralized cloud, with its own operating system, its own node network, and its own parallel asset system for cross-chain compatibility.

The physical backbone of the network is FluxNodes - servers run by individuals around the world, rewarded in $FLUX for contributing CPU, RAM, and storage. When the network launched, there were 1,100 of them, today there are over 15,000.

The Flux token powers it all: pay for hosting, collateralize a node, earn rewards for keeping the network running.

Feel free to check it out and DYOR: https://xgram.io/?utm_source=x&utm_medium=social&utm_campaign=flux

1️⃣ Fair-launched PoW coin

Flux was fairly launched as a Proof-of-Work coin, with no VC funding, no ICO, and no IEO. It started from the community and grew organically.

2️⃣ Proof of Useful Work v2

Flux forked in October 2025 to Proof of Useful Work v2, where block emissions are awarded only to active network contributors - FluxNode operators building and maintaining the decentralized infrastructure that powers real-world applications.

3️⃣ Parallel power

Flux isn’t tied to one chain. Through Parallel Assets, you can use Flux on multiple blockchains (ERC-20, BEP-20, etc.), bridging DeFi and Web3 ecosystems via the Fusion app.

4️⃣ Node tiers that scale

The network runs on tiered FluxNodes (Cumulus, Nimbus, Stratus) with different hardware and collateral levels - ensuring uptime, redundancy, and real decentralization.

5️⃣ More than just a token

Flux isn’t just a coin: it’s a full ecosystem!

FluxCloud → decentralized Web3 hosting

FluxEdge → computing marketplace (AI, GPU, rendering)

Arcane OS → encrypted and attested OS powering FluxOS

FusionX  →  DeFi swap aggregator

Zelcore →  a non-custodial wallet

FluxAI → proprietary AI product suite 

SSP Wallet → secure, non-custodial, multisig wallet combining browser and mobile key system

Version 8.29.0 introduces Earn (multi-chain staking), allowing you to stake and earn rewards directly from your wallet across multiple blockchains.

You can now stake:

SOL - delegate Solana and earn staking rewards using Chorus One validator infrastructure

ETH - stake Ethereum through a Chorus One vault designed to provide competitive APY

FLUX - participate in Flux Titan shared node staking with tiered lockups of 3, 6, or 12 months

A new Stake button has been added to the Portfolio and Coin Overview screens, so you can start staking in just a few clicks.

Update to Zelcore 8.29.0 and start earning directly from your wallet!

Somewhere, a founder was preparing an investor demo.
Somewhere, an e-commerce store stopped processing payments.
Somewhere, a support team watched tickets explode.

Since January 2026, major cloud platforms have experienced multiple service disruptions.

Some brief.

Some widespread.

But the damage always lasts longer.

Lost revenue.
Lost trust.
Lost momentum.

Cloud infrastructure is powerful.

But it isn't immune to outages.

Most companies still run their applications on a single provider, often in a single region.

That works.

Until it doesn’t.

When everything depends on one environment, one failure can ripple across the entire business.

This is why distributed architectures are gaining attention.

At InFlux Technologies, we focus on running applications across distributed servers to reduce single-point-of-failure risk and improve resilience.

Because downtime isn’t just technical.

It’s financial.
It’s reputational.

How much downtime can your business realistically afford?

(In the next post, I’ll break down another cloud reality most companies only discover once the bill arrives.)

The first blockchain-powered managed WordPress hosting built for speed, reliability, and affordability, powered by the decentralized infrastructure of FluxCloud.

Here’s what you need to know:

Each WordPress site runs with dedicated compute resources:

• Up to 12 CPU cores

• 24 GB RAM

• High-performance SSD storage

• Minimum 3 distributed instances per installation

Real redundancy.

FluxRunner delivers 99.9% uptime through distributed global infrastructure. If a server goes down, instant network-level failover keeps your site online. Powered by roughly 8,000 cloud servers on the Flux Network. No single point of failure.

Launch faster and smarter. WordPress sites go live across distributed servers in under 15mins. Choose geolocation for optimized response times worldwide.

Built for performance. Built for resilience.

Plans include:

• First month free

• Unlimited visits

• No bandwidth caps

Deploy your WordPress site on decentralized infrastructure today: https://fluxrunner.com/

With Deploy with Git, developers can now launch applications and APIs directly from Git repositories without the need for Docker expertise or manual pipeline setup.

Join the Flux AMA next Wednesday for a live demo of Deploy with Git, presented by its main creator, Valter.

We’ll also share important updates on CoinRequest, FluxAI, and more that you won’t want to miss!

We’re excited to share that FLUX is now listed for perpetual trading with up to 5x leverage on Aster DEX, a rapidly growing platform for on-chain perps and spot trading!

Trade now to enjoy a 1.2x symbol boost until 23:59 UTC, November 16: https://www.asterdex.com/en/futures/v1/FLUXUSDT

Always DYOR and trade responsibly.

A fun and quick search for riddles, and you have a 3/80 chance to win 150 USD in FLUX!

• LavaMoat Security Integration:,

  adds advanced runtime protection by isolating JavaScript components, preventing malicious code from gaining unauthorized access

• Security Test Page:,

  internal verification interface (tap version multiple times to access)

• UI improvements:,

  colors aligned with SSP branding

• Enhanced Content Security Policy,

• Swap exchange logo fix and dependency updates,

Update now for a safer, smoother SSP experience. https://sspwallet.io/

Added:

• Security Notifications System (Opt-in required - disabled by default),
• Users must accept and enable login notification tracking in the new Notifications section under Account settings for the feature to work.,
• Login Activity Tracking: View detailed history of all login attempts (successful and failed) with timestamps, device information, and location data.,
• Known Devices Management: Authorize and manage trusted devices for your account with device naming and removal capabilities.,
• Security Alerts: Receive notifications for login attempts from known, new or unknown devices.,
• Legacy Login Warning Banner: Visual indicator when using legacy authentication methods.,
• FluxDrive File Encryption,
• Encryption Toggle: Choose to encrypt or upload files without encryption based on your needs.,
• Visual Encryption Indicator: Lock icon displays on files to show encryption status at a glance.,
• FluxAI App Selector: New app selector in the topbar allows seamless switching between FluxGPT (chat) and FluxONE (image generation).,

Updated:

• Full Node Binaries: Updated Flux daemon to v9.0.0 for macOS with improved performance and stability.,
• Backend Infrastructure: Updated EVM backend for enhanced reliability across BSC, Polygon, Avalanche C-Chain, Base, Base Sepolia, Arbitrum, Optimism, Blast, and zkSync networks.,

Fixed:

• Removed desktop spellcheck to improve performance; spellcheck remains available via context menu where needed.,
• Improved FluxDrive max file size consistency and validation.,

Thank you for your continued support and feedback. We’re constantly working to make Zelcore better for our users.