Context you
can check.

A feed, with boundaries.

We collect titles or release identifiers, publisher links and dates. We do not republish article bodies, release notes or third-party artwork. The original publisher remains the source of each announcement.

The desk covers selected project announcements, crypto policy, blockchain security research, service notices and software releases. It is not a complete breaking-news service. A release may concern shared infrastructure and does not establish an exploit or a mainnet upgrade.

Freshness is visible.

News, policy, research and service feeds have a two-minute collection target. Software releases retain an hourly target. The open source feed checks for changes every 30 seconds while visible; new headlines appear when you choose Show updates. Cached means a validated source snapshot is available; it does not mean the publisher has been checked this second. A news source is overdue after ten minutes without a successful collection; a release source is overdue after three hours. Publisher delays and source failures can make updates take longer than the target. A saved snapshot is a retained collection used when it is newer than the cache or a source cannot be reached. Its collection date stays visible.

A source failure does not erase a previous successful batch. The publication date belongs to the source item; the collection date records when Forensia fetched it. Neither date is an independent verification of its claims.

From reading to investigating.

Context links are editorial suggestions, not claims that an announcement caused an incident. Incident pages reuse Forensia’s existing case files and their stated evidence limits. Unsupported networks remain visibly unsupported.