Stability and Scale
This page presents operational signals from the live BDS mainnet market. Figures are derived from on-chain events on Powerloom L2 (chain 7869) unless noted otherwise.
Reproducibility: Committed analysis artifacts and reproduction commands are in the dsv-validator-activity reports tree (days-1-30/, days-31-60/, combined-days-1-60/summary.json). Raw log exports are not committed; rerun the scripts with an archive RPC to verify.
Network at a Glance (60 protocol days)
BDS mainnet has operated through 60 protocol days of DSV validator activity (two consecutive 30-day windows). Combined on-chain epoch coverage:
| Metric | Days 1–30 | Days 31–60 | Combined 1–60 |
|---|---|---|---|
| Epochs assigned | 217,295 | 215,226 | 432,521 |
| Epochs with submissions | 212,297 | 210,430 | 422,727 |
| Completion rate | 97.70% | 97.77% | 97.74% |
| Missed epochs | 4,998 (2.30%) | 4,796 (2.23%) | 9,794 (2.26%) |
| Median latency | 89s | 97s | — |
| P95 latency | 138s | 155s | — |
The second window matched the first on coverage (slightly fewer missed epochs) with higher end-to-end latency (median +8s, P95 +17s). Both windows show the same pattern: once a validator submits, batch completion stays above 99%.
Figure 1: Daily batch submission completion rate, protocol days 1–30 (217,295 epochs assigned).
Figure 2: Daily batch submission completion rate, protocol days 31–60 (215,226 epochs assigned). 28 of 30 days at full 7,200-epoch cadence; days 49–50 were shorter L2 windows.
First 30 days (baseline window)
Detailed figures for protocol days 1–30 (historical baseline for comparisons and charts):
| Metric | Value |
|---|---|
| Total epochs assigned | 217,295 |
| Epochs with submissions | 212,297 |
| Completion rate | 97.70% |
| Median end-to-end latency | 89 seconds |
| P95 latency | 138 seconds |
| Full steady-state days (7,200 priorities/day) | 26 of 30 |
The 2.3% coverage gap clustered around brief restart windows rather than uniform random loss.
Validator performance (days 1–30)
Six validator nodes maintained 22+ consecutive active days:
| Node | Active Days | Completion Rate | Total Submitted |
|---|---|---|---|
| Node 1 | 30/30 | 99.87% | 29,670 |
| Node 5 | 30/30 | 99.90% | 49,717 |
| Node 4 | 29/30 | 99.20% | 27,252 |
| Node 3 | 28/30 | 97.42% | 33,827 |
| Node 10 | 26/30 | 98.01% | 27,690 |
| Node 11 | 22/30 | 98.79% | 25,319 |
Three additional transient nodes participated during operator testing and rotation.
Figure 3: Validator constellation (days 1–30 window).
Days 31–60
The second production month is shown in Figure 2 above. Daily completion held in the same band as days 1–30; batch-level completion (submit → on-chain complete) averaged 99.10% across the window.
| Metric | Value |
|---|---|
| Epochs assigned | 215,226 |
| Epochs with submissions | 210,430 |
| Completion rate | 97.77% |
| Median latency | 97 seconds |
| P95 latency | 155 seconds |
| Days at 7,200 priorities/day | 28 of 30 |
| Batch submit → complete (log totals) | 208,550 / 210,437 (99.10%) |
Cadence exceptions: days 49 (6,490) and 50 (7,136) priorities — shorter L2 day windows, same class of anomaly as day 1 / day 14 in the first window.
Validator performance (days 31–60)
Fleet consolidated to five nodes at full-month uptime plus one transient:
| Node | Active Days | Completion Rate | Total Submitted |
|---|---|---|---|
| Node 5 | 30/30 | 99.99% | 70,070 |
| Node 4 | 30/30 | 99.49% | 45,434 |
| Node 1 | 30/30 | 99.92% | 39,829 |
| Node 3 | 30/30 | 97.57% | 30,472 |
| Node 11 | 28/30 | 96.27% | 23,411 |
| Node 9 | 2/30 | 99.92% | 1,221 |
Node 5 carried the largest submission share in this window (+41% vs its days 1–30 total). Nodes 2, 7, and 10 did not appear in the 31–60 summary (rotation / decommission).
Submission Latency
Latency is measured from priority assignment (PrioritiesAssigned) to on-chain batch submission (SnapshotBatchSubmitted).
Figure 4: Latency distribution (days 1–30 chart). Median 89s → 97s in days 31–60; P95 138s → 155s.
Patterns remain consistent across hours of day in the first window; the second window shows a modest shift toward higher absolute latency without a coverage regression.
Epoch Coverage Pattern
Figure 5: Coverage matrix (days 1–30). Gaps cluster at operational transitions, not random scatter.
Snapshotter Participation
Separate measurement of 1,811 epochs (April 17–24) — snapshotter / slot layer (not validator export):
| Metric | Value |
|---|---|
| Unique eligible nodes per day | 2,970 – 3,047 |
| Median eligible nodes per epoch | 305 |
| Active validators per epoch | 3–5 (median 4) |
Figure 6: Slot activity sample (3,078 slots).
What These Figures Show
Continuous cadence under pressure
BDS mainnet processes block-aligned epochs on Ethereum mainnet. 432k+ assigned epochs over 60 protocol days with 97.7% submission coverage shows sustained operation under continuous pressure.
Measurable validator participation
- Five stable validators at full-month uptime in days 31–60
- ~3,000 eligible snapshotter nodes per day (separate tally sample)
- 99%+ batch completion once a validator commits to submit
Observable mesh health
Local-collector health states (healthy / degraded / pruned) and peer counts remain part of the operational story; see deployment docs for collector configuration.
Related Pages
Methodology and Reproducibility
- On-chain export —
export_validator_activity.pywith archivePOWERLOOM_RPC_URL(Powerloom L2) - Epoch participation —
analyze_epoch_participation.py→participation_summary.json - Per-node reliability —
analyze_validator_reliability.py→reliability_summary.json - Window comparison —
compare_windows.pybetween output directories - Charts —
generate_visualizations.py→reports/charts/(e.g.dsv_network_health_timeline_days_31_60.png)
Committed artifacts: github.com/powerloom/dsv-validator-activity/reports — includes days-31-60/network_health_daily.csv and chart PNGs under reports/charts/.
Contracts (BDS mainnet):
- ProtocolState:
0x1d0e010Ff11b781CA1dE34BD25a0037203e25E2a - DataMarket:
0x26c44e5CcEB7Fe69Cffc933838CF40286b2dc01a
Last updated: 2026-05-19