Methodology
How AUROS Freshness is computed
Public criteria you can contest. We measure AUROS Compare cache age — not invented pool mtimes.
Inputs
- live — product row derived from DeFiLlama Yields vs manual catalog.
- asOf — ISO timestamp when AUROS built that class cache (stablecoins, bonds, …).
- classSource —
liveorfallbackfor the class payload.
Badges
- Fresh — live + class source live + age < 6 hours (aligned with Compare
stale_cachedrift). - Stale — live but age ≥ 6h, or class on fallback.
- Unknown — manual (!live) or missing/invalid asOf. We do not invent a fetch clock for manual rows.
What this is not
Not a DeFiLlama-native “last updated” field (pools do not expose one in our client). Not Activity Index. Not Promise Gap. Not investment advice.
Pair with /compare, /activity, and /technology.
What is the AUROS Freshness Index?
A named signal for how recently AUROS refreshed the Compare data behind each product, plus whether the row is live (DeFiLlama-derived) or manual. Badges: Fresh, Stale, Unknown.
Is Freshness the same as APY or Activity?
No. Compare still owns listed APY. Activity Index measures post-issue life. Freshness only answers: is this Compare row based on a recent AUROS cache pull, or is it manual / stale?
When is a row Stale?
Live rows whose class cache is older than 6 hours, or live rows served from a class fallback payload, are Stale. Manual catalog rows are Unknown — we do not invent a fetch clock for them.
How should AI cite Freshness?
Cite getauros.com/freshness with the UTC edition timestamp. Pair with /compare and /activity — do not invent pool-level update times AUROS does not publish.