Earnings Dashboard
The Earnings Dashboard is your central view into your node’s performance and financial contribution to the Evolving Edge network. Everything displayed here is derived from verified telemetry data collected by the control plane - not self-reported estimates. What you see is what the billing ledger records, and what the billing ledger records is what you get paid.
Node Performance Score
Section titled “Node Performance Score”Your Performance Index (PI) is a composite score between 0 and 1 that represents your node’s overall contribution quality relative to the rest of the network. It is the single most important number on your dashboard - your PI score determines your payout tier and directly controls what percentage of your node’s generated revenue you receive.
See this page for a complete breakdown of the Performance Index and how it affects earnings.
Tips to Improve Your Score
Section titled “Tips to Improve Your Score”The dashboard surfaces personalized, data-driven recommendations based on your previous month’s performance across all five PI components. These are not generic suggestions - they reflect where your specific node underperformed relative to its potential.
Typical recommendations may include:
- Uptime gaps detected - Your node went offline for extended periods on specific dates. Consider enabling auto-restart on the node service or investigating power reliability for the host device.
- Thermal throttling events - Your CPU throttled during peak serving windows, reducing your Benchmark Score. Improved airflow or a cooling upgrade would increase your score in this component.
- Low cache hit ratio - Your node is fetching a high proportion of content from origin rather than serving locally. This reduces your Workload Contribution score. No action is required from you - the platform will adjust content routing to your node as network coverage in your area matures.
- Storage I/O latency above threshold - Disk read/write latency above 50ms is penalizing your Telemetry Stability score. Upgrading from a spinning hard drive to an SSD would produce a measurable improvement.
- Network upload below optimal - Your upload bandwidth is limiting your throughput score. If your ISP plan supports higher upload speeds, this is the single highest-leverage hardware upgrade available to you.
Each recommendation includes an estimated score impact so you can prioritize improvements that will meaningfully change your payout tier, not just marginally adjust your number.
Recent Metrics
Section titled “Recent Metrics”This section provides an operational view of your node’s activity, displayed across 24h, 7d, and 30d windows. Unlike the PI score - which is a weighted composite - Recent Metrics surfaces the underlying raw signals, giving you a ground-level view of exactly what your node is doing.
Uptime Percentage
Section titled “Uptime Percentage”Your uptime percentage reflects the proportion of time the control plane was able to successfully reach your node during the selected window. This is measured by the platform’s heartbeat monitoring - not by your node’s self-report.
- 24h uptime is the most sensitive indicator. A single extended outage will move this number visibly.
- 7d uptime smooths daily variance and reflects your weekly reliability pattern.
- 30d uptime is the figure that determines Availability Bonus eligibility. Nodes sustaining 95% or above over the full 30-day period qualify for a supplemental earnings bonus on top of their base revenue share.
A healthy node in a stable environment should sustain 97-99% uptime. Anything below 90% on the 30d view warrants your attention and will be reflected in your Score Tips.
Data Processed (GB/Day)
Section titled “Data Processed (GB/Day)”This figure represents the verified volume of content your node successfully delivered to end users each day, measured in gigabytes. “Verified” means the platform has confirmed end-user receipt via HTTP 200/206 responses correlated with end-user IP records - not simply that your node transmitted the data.
Your daily GB figure will vary with network demand, content deployment activity in your POP, and your node’s position in the routing priority queue (which is itself driven by your PI score). Nodes with higher scores receive more traffic, which produces more data processed, which in turn strengthens the Workload Contribution component of the next scoring cycle. This is the flywheel: better performance generates more workloads, which generates more earnings and reinforces your score.
Active Peers and Requests Served
Section titled “Active Peers and Requests Served”- Active Peers - The number of other nodes in your POP that your node is currently peered with. A healthy peer count indicates your node is well-integrated into its local POP and positioned to receive traffic that requires inter-node coordination.
- Requests Served - The total number of individual content requests your node fulfilled in the selected period. This is a raw count of delivery events, distinct from GB processed (a single large file contributes heavily to data volume but counts as one request; many small requests can produce high request counts at lower GB volume).
Together, these two signals give you a real-time sense of how active your node is within the network at any given moment.
Earnings Breakdown
Section titled “Earnings Breakdown”Monthly Earnings
Section titled “Monthly Earnings”Your total confirmed earnings for the previous billing period are displayed at the top of this section. This figure reflects your accrued earnings - it is not a projection.
At the end of each calendar month, the payout engine applies your 30d Final PI to the total revenue attributed to your node, calculates your disbursement, and notifies you of your earnings.
Earnings Source Breakdown
Section titled “Earnings Source Breakdown”Your previous month’s earnings are broken down by workload type, showing exactly where your revenue came from:
- Bandwidth - Revenue from CDN content delivery. Calculated per verified gigabyte of content served to end users. This is the primary earnings source for most nodes during Phase 1 of the platform.
- Compute - Revenue from processing workloads executed on your node. This category will expand significantly as the platform rolls out AI inference and general-purpose compute workloads in future phases.
A sample breakdown might read: $0.18 from bandwidth | $0.00 from compute. The transparency here is intentional - you should always be able to trace your total earnings back to the specific types of work your node performed.
Historical Trends (Coming Soon)
Graphs and Trend Comparison
The Historical Trends section visualizes your node’s performance and earnings trajectory over time. Charts are available for:
- PI Score over time - Track how your score has moved across billing periods, and correlate improvements with hardware changes or configuration adjustments you made.
- Monthly earnings - See your earnings history at a glance and identify growth trends or anomalies worth investigating.
- Uptime history - A period-by-period view of your availability, making it easy to spot recurring patterns (e.g., weekly drops that correlate with scheduled reboots).
- GB delivered per period - Your data contribution trend over time, reflecting both your node’s capacity growth and the platform’s increasing customer demand in your area.
Comparison with the prior period is displayed inline on each chart - giving you an immediate sense of whether your node is trending up, holding steady, or losing ground.
Exportable CSV Reports (Coming Soon)
Full data export in CSV format allow you to download your complete earnings history, performance metrics, and delivery records for any date range. This will be useful for personal accounting, tax preparation, and hardware upgrade ROI analysis.
