How DePINly presents DATS. Last verified 2026-05-22.
TL;DR
DATS lets you lend idle PC compute to a decentralized cybersecurity network. After the 2026-05-21 audit, the per-hour USD calculator was retired (it was structurally wrong): DATS rewards are revenue-share (60% of network revenue buys back DATS for contributors), not a fixed per-hour emission, and the token is pre-TGE with no price. The page now shows a revenue-share + eligibility-points (DP) explainer.
How earning actually works
- Contribute idle CPU + bandwidth → accrue DP eligibility points today (pre-TGE).
- Rewards come from revenue-share buybacks (60% of revenue), not per-hour pay.
- Context (verified): network protects $1B+ in assets, ~1,184 active computers, 30+ Web2/Web3 clients, ~$600K revenue in 2024.
Why no USD figure
Pre-TGE (no token price) + revenue-share (not a fixed rate) → any USD/hour would be invented. We show the model and the verified context instead.
Assumptions & confidence
| Item | Basis | Confidence |
|---|---|---|
| Revenue-share (60% buyback), pre-TGE | DATS docs, audit 2026-05-21 | 🟢 |
| Network context ($1B+, 1184 nodes, $600K rev) | DATS reported | 🟡 |
| Per-hour USD | not modeled (would be fabricated) | n/a |
Confidence rating
🟡 — Model and context are sourced; deliberately no USD calculator (pre-TGE + revenue-share). The legacy per-hour lib is kept only as a deprecated audit record.
Sources (verified 2026-05-22)
DATS docs / reports · audit 2026-05-21.
Code
src/lib/peaq-subdepins/dats-calc.ts (@deprecated audit record) · src/components/calculators/peaq/DatsCalculator.tsx (explainer) · src/app/calculate/peaq/run/dats/page.tsx
These figures are point estimates inside a wide band and depend on local demand, hardware, uptime and token price. They may be wrong in either direction. Nothing here is financial advice — always do your own research.
Methodology updated 2026-05-22 · View source on GitHub →