Release archive
3.2.179

CRYPTO-SOURCE-FRESHNESS-ALIAS-NORMALIZATION (Report Logic)

Release v3.2.179 focuses on CRYPTO-SOURCE-FRESHNESS-ALIAS-NORMALIZATION (Report Logic).

FixedInternal
CRYPTO-SOURCE-FRESHNESS-ALIAS-NORMALIZATION (Report Logic)

Release digest

Fixed

  • CRYPTO-SOURCE-FRESHNESS-ALIAS-NORMALIZATION (Report Logic) — Crypto project normalization now derives section/source freshness from common parseable date aliases such as market.last_updated, github.last_updated, defillama.updated_at, funding.updated_at, tokenomics.updated_at, security.updated_at, and source_freshness.<family>.updated_at. Reports can now reduce false source-freshness gaps without inventing dates from source labels, report generation time, URLs, or contract addresses.

Internal

  • Added backend normalizer and PDF view-model coverage for nested source freshness aliases, including invalid URL/address rejection and removal of false Source freshness model backlog rows when every current citation row has attached freshness metadata.
  • Updated docs/architecture/CRYPTO_REPORTS.md and knowledge-base/docs/crypto/dashboard-ui.md because this changes source freshness behavior. Public-docs decision: user-facing crypto docs now explain freshness alias normalization as attached timestamp provenance only, not source verification, audit coverage, legal assurance, or investment advice.

Technical notes