Progressive Node Rewards (PNR)

Progressive Node Rewards (PNR)

Progressive Node Rewards (PNR) is the Flux network's reward multiplier system designed to incentivize consistent, high-quality node operation. Rather than all nodes earning the same flat reward, PNR gives higher rewards to operators who maintain superior uptime, pass benchmarks reliably, and run ArcaneOS. This system rewards long-term commitment and discourages operators from running nodes with marginal hardware or inconsistent availability.

How PNR Works

PNR operates as a multiplier on the base block reward allocated to node operators. Nodes that demonstrate consistent quality over time earn progressively higher multipliers, meaning they receive a larger share of the reward pool compared to nodes with lower PNR scores. The system evaluates nodes based on multiple factors and assigns a PNR score that directly translates to a reward multiplier.

The core principle is simple: the longer you maintain excellent performance, the more you earn. New nodes start with a baseline multiplier and can increase their PNR score over time by maintaining continuous, high-quality operation.

PNR Eligibility Requirements

Not all nodes are eligible for PNR. To qualify, nodes must meet the following mandatory requirements:

• •ArcaneOS is mandatory: The node must be running ArcaneOS, the Flux custom operating system. Nodes running standard Linux distributions (Ubuntu, Debian, etc.) are NOT eligible for PNR, regardless of their uptime or performance.
• •Consistent benchmark passes: The node must pass all benchmark tests reliably. Frequent benchmark failures disqualify a node from PNR benefits.
• •97%+ uptime: The node must maintain at least 97% uptime over the evaluation period. This translates to no more than approximately 22 hours of total downtime per month.
• •Valid collateral: The required FLUX collateral must remain locked and unspent for the duration of node operation.

PNR Scoring and Tiers

The PNR score is calculated based on a combination of factors that measure node quality and consistency over time. Key factors include:

1. 1

   Uptime Duration

   Continuous uptime without interruption builds your PNR score over time. Longer uninterrupted operation results in higher multipliers. The system rewards nodes that have been running consistently for weeks and months.

2. 2

   Benchmark Consistency

   Not just passing benchmarks, but passing them with comfortable margins above the minimum thresholds. Nodes that consistently score well above minimums are scored higher than nodes that barely pass.

3. 3

   Hardware Attestation (ArcaneOS)

   ArcaneOS provides cryptographic hardware attestation that verifies the node is running on real, dedicated hardware. This prevents operators from gaming the system with fake or manipulated benchmark results.

4. 4

   Network Contribution

   Nodes that actively host applications and contribute to network operations are viewed favorably by the PNR system.

How PNR Multipliers Affect Rewards

The PNR multiplier directly scales the reward amount a node receives. For example, if the base reward for a Cumulus node is X FLUX, a node with a 1.5x PNR multiplier would receive 1.5X FLUX for the same reward event. The exact multiplier ranges are adjusted by the Flux team, but the impact is substantial — top PNR nodes can earn significantly more than baseline nodes of the same tier.

Node Rank and PNR Relationship

Node rank determines your position in the deterministic reward queue. A lower rank number means you are closer to receiving the next reward. PNR does not change your queue position or how quickly you reach the front of the queue — rather, it changes how much you receive when you do get rewarded. Two nodes at the same queue position in the same tier will receive different reward amounts if they have different PNR multipliers.

Why ArcaneOS Is Required

ArcaneOS is mandatory for PNR because it provides hardware attestation — cryptographic proof that the node is running on genuine hardware that matches claimed specifications. Without hardware attestation, operators could theoretically fake benchmark results, run nodes on substandard hardware, or use virtualization tricks to appear as multiple nodes. ArcaneOS closes these attack vectors by:

• •Verifying the physical hardware identity through secure boot and TPM (Trusted Platform Module) integration where available.
• •Ensuring benchmarks run against actual hardware, not spoofed or manipulated environments.
• •Providing a standardized, auditable operating environment that the Flux team can verify and update.
• •Enabling future hardware-verified features and enhanced security for application hosting.

Checking Your PNR Status

You can check your node PNR status through several channels:

• •FluxOS UI Dashboard: Navigate to http://YOUR_IP:16126 and check the node status section for PNR information.
• •Zelcore NodeTracker: The Zelcore wallet NodeTracker shows PNR status for all your registered nodes.
• •FluxNodes.net: Search for your node on FluxNodes.net to view PNR status, score history, and multiplier information.
• •FluxOS API: Query the FluxOS API endpoint for programmatic PNR status checks.

Strategies for Maximizing PNR Score

1. 1

   Install ArcaneOS from day one

   Do not start with standard Linux planning to migrate later. Every day on standard Linux is a day without PNR accumulation. Start with ArcaneOS to begin building your score immediately.

2. 2

   Over-provision hardware

   Hardware that barely meets minimums will eventually fail a benchmark. Provision 15-20% above minimum specs to ensure consistent benchmark passes with comfortable margins.

3. 3

   Use reliable hosting providers

   Choose providers with strong uptime SLAs and quality hardware. The small premium for a top-tier provider is quickly recovered through higher PNR multipliers.

4. 4

   Set up comprehensive monitoring

   Use external monitoring tools to detect problems immediately. Every minute of downtime erodes your PNR score. Fast response to issues protects your investment.

5. 5

   Plan maintenance carefully

   When maintenance is needed, keep downtime as brief as possible. Prepare everything in advance so the actual downtime window is minimal.

6. 6

   Keep ArcaneOS updated

   Apply ArcaneOS updates promptly when released. Updates may include PNR-related improvements and security patches that affect eligibility.

Impact of Downtime on PNR

Downtime has a significant negative impact on PNR scores. The severity depends on the duration and frequency of outages:

• •Brief downtime (minutes): A short reboot or momentary network interruption has minimal PNR impact. The system is designed to tolerate brief, infrequent interruptions.
• •Extended downtime (hours): Several hours of downtime will noticeably reduce your PNR score. If the downtime spans one or more benchmark cycles, the impact is compounded by missed benchmarks.
• •Prolonged downtime (days+): Extended outages can cause a significant PNR reset, potentially dropping your multiplier back to near-baseline levels. Rebuilding a high PNR score after a major outage takes weeks to months of continuous operation.
• •Frequent short outages: Repeated brief outages are more damaging than a single equivalent-duration outage. The system penalizes instability patterns, not just total downtime.