Skip to main content

Reputation System

Your reputation score (0-100) determines your ranking in the network. It rewards consistency and uptime while being forgiving of occasional downtime.

How Scoring Works​

  • 100 points total across 4 categories
  • 7-day rolling window for all calculations
  • 30-minute minimum uptime required to start earning points
  • New nodes get a 7-day warm-up period with adjusted expectations
  • Updates every 30 seconds

Score Breakdown​

🌐 Availability (45 points max)​

Earn points based on distinct hours online over 7 days.

  • Full credit: 154+ hours online (~22 hours/day)
  • Measurement: Counts unique hours with heartbeats
  • Minimum: Must have at least 30 minutes continuous uptime
  • Fair counting: Running 24/7 vs. 22h/day scores similarly

Your node earns availability points as soon as it has been online for 30 minutes in a single session. The score scales with the number of distinct hours you're online each day over the past week.

⚡ Network Quality (30 points max)​

Based on throughput and latency from your heartbeats.

Throughput (20 points):

  • Full credit at 400+ Mbps
  • Scales linearly from 0 to 400 Mbps
  • Missing data defaults to 0

Latency (10 points):

  • Full credit at 0ms latency
  • Zero credit at 200ms or higher
  • Scales linearly between 0-200ms
  • Missing data defaults to 200ms

🧠 Resource Headroom (10 points max)​

Keep enough CPU, memory, and disk free for QuikDB tasks.

  • CPU headroom (6 points): Lower usage = more points
  • Memory headroom (3 points): Lower usage = more points
  • Disk headroom (1 point): Lower usage = more points
  • Missing resource data defaults to 50% usage (neutral)

Formula: Points = (1 - usage%) × weight

🔄 Consistency (15 points max)​

Regular activity and recent heartbeats.

Coverage (12 points):

  • Target: 80% of 168 hours (134 hours/week)
  • Scales linearly to target
  • Rewards consistent daily presence

Recency (3 points):

  • Full credit: Last seen within 0 hours
  • Zero credit: Last seen 72+ hours ago
  • Linear decay between 0-72 hours

Rank Badges​

ScoreBadgeStatus
75-100🏆 ExcellentRock solid and fast
55-74😊 GoodReliable with strong performance
40-54👍 FairRoom for improvement
0-39 (new)🙂 Getting StartedBuilding reputation (less than 7 days)
0-39 (established)⚠️ Needs ImprovementInconsistent activity

New nodes (registered less than 7 days ago) are labeled "Getting Started" to differentiate them from established nodes with low scores.

Key Rules​

Minimum Requirements​

  • 30 minutes continuous uptime to start earning any points
  • Must send regular heartbeats every 2 minutes
  • No points for sessions shorter than 30 minutes

Time Windows​

  • All metrics use a 7-day rolling window
  • Recent data weighted same as older data in 7-day window
  • Reputation updates every 30 seconds
  • New nodes flagged for first 7 days

What Hurts Your Score​

  1. Long offline periods - Reduces availability dramatically
  2. Slow network - Low throughput or high latency
  3. Resource saturation - Consistently high CPU/RAM/disk usage
  4. Irregular heartbeats - Going offline for 72+ hours
  5. Short sessions - Under 30 minutes don't count

What Helps Your Score​

  1. Stay online consistently - Aim for 22+ hours per day
  2. Maintain good network - 400+ Mbps throughput, less than 50ms latency
  3. Free up resources - Keep CPU/RAM/disk usage reasonable
  4. Send regular heartbeats - Don't let gaps exceed 72 hours
  5. Run longer sessions - Multi-hour uptimes better than short bursts

How to Improve​

Quick Wins​

  1. Run 22-24 hours daily - Even missing 2 hours/day gives near-full availability credit
  2. Use wired connection - Ethernet beats WiFi for speed and stability
  3. Close background apps - Free up CPU and memory during operation
  4. Keep it running - Avoid unnecessary restarts or shutdowns
  5. Enable auto-start - Recover automatically after reboots

Pro Tips​

  1. Monitor your dashboard - Watch for patterns in your metrics
  2. Test your network - Use speedtest to verify your connection quality
  3. Set resource reservations - Allocate specific CPU/RAM to QuikDB
  4. Check system load - Identify apps consuming resources during peak times
  5. Maintain consistency - Regular 22h/day beats occasional 48h marathons

Recovery After Downtime​

  • Points rebuild as you accumulate online hours
  • No instant recovery - requires consistent uptime over days
  • Expect 3-5 days to stabilize after extended outage
  • New 7-day window gradually replaces old data

Technical Details​

  • Scoring updates: Every 30 seconds via background service
  • Heartbeat window: Last 7 days of heartbeat data
  • Distinct hour counting: Each unique hour-bucket counts once
  • Resource defaults: Missing metrics default to neutral (50%)
  • Warm-up detection: Based on device registration date
  • Minimum session: 30-minute continuous uptime required

Common Questions​

Why did my score drop overnight?​

Your score is based on a 7-day rolling window. As older high-activity days drop out of the window and new lower-activity days roll in, your score adjusts.

I'm online 24/7 but not at 100 score?​

Reputation isn't just uptime. Network quality, resource headroom, and consistency also matter. Check your network speeds and resource usage.

Does restarting hurt my score?​

Brief restarts have minimal impact if your overall 7-day pattern shows consistent uptime. Avoid frequent or long restarts.

How long to reach "Excellent"?​

With 22+ hours daily uptime, good network (400+ Mbps, less than 50ms latency), and reasonable resource usage, expect 75+ score within 7 days.

Can I recover from "Needs Improvement"?​

Yes. Consistent 22+ hour daily sessions with good network performance will rebuild your score over 5-7 days.

Summary: Run 22+ hours daily with good network speeds, keep resources free, and maintain consistency. Your score reflects your last 7 days of behavior.