Release archive
3.2.255

CRYPTO-BASE-OFFICIAL-PROVENANCE (Reports)

Release v3.2.255 focuses on CRYPTO-BASE-OFFICIAL-PROVENANCE (Reports).

AddedFixedInternal
CRYPTO-BASE-OFFICIAL-PROVENANCE (Reports)

Release digest

Added

  • CRYPTO-BASE-OFFICIAL-PROVENANCE (Reports) — The canonical Base payload now attaches official Base documentation provenance for Security Council governance, vulnerability reporting, documented Base contract addresses, source references, and admin-control roles.
  • The crypto PDF regression pack now treats Base as a tokenless project with attached official security, contract/source, and admin-control provenance, so its remaining report-derived gaps focus on historical snapshots and source freshness instead of missing security/admin evidence.

Fixed

  • Admin-control normalization now preserves canonical admin_controls.multisig values in addition to existing Safe and multisig address aliases.

Internal

  • Added focused coverage for canonical Base provenance, canonical multisig admin-control preservation, updated regression-pack analyzer counts, and the refreshed Base regression PDF profile.
  • Updated docs/architecture/CRYPTO_REPORTS.md and knowledge-base/docs/crypto/dashboard-ui.md. Public docs decision: document the report-profile implication of attached official provenance because this affects user-visible report packaging, while explicitly avoiding audit, safety, billing, legal, or investment claims.

Technical notes