Legacy vs ArcaneOS

Feature comparison, migration path, and decision guide for choosing between Legacy and ArcaneOS.

8 min read

arcaneoslegacycomparisonmigration

Legacy vs ArcaneOS — Which Should You Run?

Flux supports two node types: Legacy (traditional Ubuntu installation with manual management) and ArcaneOS (purpose-built OS with automation and enhanced security). ArcaneOS is now the recommended standard, and legacy nodes will not be supported in the near future. Existing legacy operators should plan their migration as soon as possible.

Feature Comparison

Feature	Legacy	ArcaneOS
Base OS	Ubuntu 18/20/22	Ubuntu 24 (hardened)
Installation	Manual (Multitoolbox)	Guided ISO installer
PNR eligible	No	Yes
Auto-updates	Requires Watchdog	Built-in
Self-healing	No	Yes (SAS protocol)
Security hardening	Manual (SSH keys, firewall)	Automatic (SAS, TPM 2.0)
Notifications	Manual setup	Built-in (Discord, Telegram)
SSH access	Password or key	Key-only (enforced)
Maintenance	High (manual updates, monitoring)	Low (autonomous)
Supported hardware	AMD64, ARM, Raspberry Pi	AMD64 only
Multi-node (UPnP)	Manual Multitoolbox Option 14	Supported

Why Migrate to ArcaneOS?

1
PNR rewards
Progressive Node Rewards distribute 80% of app hosting revenue to ArcaneOS node operators. Legacy nodes receive zero PNR income.
2
Zero-maintenance operation
ArcaneOS handles FluxOS updates, daemon updates, benchmark updates, and even Docker version management automatically.
3
Self-healing
The SAS protocol detects and recovers from common failures (stuck daemon, failed benchmark, Docker issues) without operator intervention.
4
Security
TPM 2.0 support, enforced SSH key auth, and hardened OS configuration reduce attack surface significantly.

When Legacy May Still Be Used (Not Recommended)

Legacy nodes will not be supported in the near future. The cases below are temporary exceptions — migrate to ArcaneOS-compatible hardware as soon as feasible.

•ARM devices: Raspberry Pi and NVIDIA Jetson nodes must run legacy — ArcaneOS is AMD64 only. Consider migrating to AMD64 hardware.
•Highly customized setups: If you run specialized networking or storage configurations that require full OS control
•Testing environments: Legacy is acceptable for development or testnet nodes where PNR doesn't matter

Migration Path

Migrating from legacy to ArcaneOS requires a fresh installation. There is no in-place upgrade. The process involves:

1
Back up your node identity
Save your Flux private key, collateral TX hash, and output index. These are reused on the new ArcaneOS installation.
2
Ensure collateral is locked
Your collateral stays on the blockchain — it is not affected by the migration. Do NOT move your collateral during migration.
3
Install ArcaneOS
Follow the ArcaneOS Installation Guide to set up the new OS on the same or different hardware.
4
Reconfigure FluxNode
Enter your existing collateral details during ArcaneOS setup. The node will rejoin the network with its existing identity.
5
Wait for confirmations
After restart, the node needs to be confirmed on-chain again. PNR eligibility begins after 21,600 confirmed blocks (~30 days).

During migration, your node will be offline temporarily. Plan the migration during your maintenance window to minimize impact. The maintenance window is 480 blocks (~4 hours) after your last confirmed height.

Legacy vs ArcaneOS