How to Improve Your TrustFingerprint Score
Your TrustFingerprint score is a direct reflection of your reliability within the Noderr network. A higher score leads to greater rewards and increased voting power in governance. This guide explains exactly how the score is calculated and what you can do to maximize it.
How the Score Is Calculated
The TrustFingerprint score is built from three objective, on-chain verifiable components. All three are measured automatically — there is nothing subjective or manual about the process.
| Component | Weight | What It Measures |
|---|---|---|
| Uptime | 50% | Is your node reliably online and reachable? |
| Success Rate | 40% | When the network assigns your node a task, does it complete successfully? |
| Stake | 10% | Do you have economic skin in the game? |
The score ranges from 0 to 100%. It is updated on-chain periodically by the protocol's scoring service.
1. Maximize Uptime (50% of Your Score)
Uptime is the single most important component of your TrustFingerprint. It is measured by how many days your node has been active and how recently it was last seen online.
Uptime tiers:
| Days Active | Base Uptime Score |
|---|---|
| 90+ days | 50% (maximum) |
| 30–89 days | ~33% |
| 7–29 days | ~17% |
| 1–6 days | ~8% |
| < 1 day | 0% |
Forgiveness mechanism: If your node goes offline temporarily, your score is not immediately zeroed. The protocol applies a graduated penalty:
| Time Since Last Seen | Penalty Applied |
|---|---|
| < 24 hours | No penalty |
| 24–72 hours | −25% of uptime score |
| 3–7 days | −50% of uptime score |
| > 7 days | −75% of uptime score |
How to maximize uptime:
- Run your node on dedicated hardware or a reliable VPS with a stable internet connection.
- Set up monitoring and alerts so you are notified immediately if your node goes offline.
- Avoid running your node on a laptop or home machine that may sleep or lose connectivity.
2. Maximize Your Success Rate (40% of Your Score)
Your success rate is the percentage of tasks assigned to your node that completed successfully. This is a direct measure of your node software's performance.
How to maximize your success rate:
- Keep your node software up to date. New releases fix bugs and improve compatibility.
- Ensure your machine meets the hardware requirements for your node tier.
- Do not modify the one-click node software. It is pre-configured to perform optimally.
- Monitor your node's logs for errors and address them promptly.
Grace period: New nodes receive a minimum score of 50% for the first 30 days to allow time to establish a track record. After the grace period, the minimum floor is 30%.
3. Maintain Your Stake (10% of Your Score)
Your stake component is proportional to your staked NODR relative to your tier's minimum requirement. Operators who meet or exceed their tier's minimum stake receive the full 10%.
Tier minimum stake requirements:
| Tier | Minimum Stake |
|---|---|
| Oracle | 150,000 NODR |
| Guardian | 50,000 NODR |
| Validator | 25,000 NODR |
| Micro | None (10% awarded by default) |
How to maximize your stake component:
- Ensure your staked NODR meets or exceeds the minimum for your tier.
- Do not unstake below the tier minimum while your node is active — this will reduce your score and may trigger a slashing review.
Frequently Asked Questions
Can I game the score? No. All three components are derived from on-chain data and heartbeat signals. There is no manual review, no peer voting, and no subjective element. The score reflects exactly what your node does.
Why was governance participation removed from the score? Governance participation belongs in the DAO voting system, not in the network performance score. Mixing the two created a conflict of interest where operators could boost their performance score through political activity rather than technical reliability. Governance participation still affects your voting power through the DAO multiplier — it just does not affect your TrustFingerprint.
Why was volume (task count) removed from the score? Task volume reflects how much work the network sends to your node, which is a function of network demand — not your performance. Rewarding volume would have created an unfair advantage for early operators who happened to receive more tasks during high-demand periods.
What happens if I go offline for maintenance? The forgiveness mechanism gives you a 24-hour window with no penalty. If you need longer maintenance, plan for a score reduction during that period. Your score will recover automatically once your node is back online and active.