Code changes, week of 2026-09-14 – 2026-09-20 · at least 10 commits

What it is

Code activity

Where HEY read it

GitHub · Commits that week ↗ · Repository ↗

When it happened

In the week of Mon 2026-09-14 – Sun 2026-09-20 (UTC), dated by the source to the week

HEY first saw it

2026-09-17 (39d ago)These are two different clocks: when the work happened, as the source dates it, and when HEY first read it. A week of code activity is one record, which HEY writes when it first sees the week and keeps up to date while the week runs, so HEY can first see it before the week ends.

What changed that week

at least 10 commits that week, not counting automation or merges.

• fix: refuse a launch feed that cannot be trusted, and stop a threshold wrapping in silence 2026-09-20
• Make the roadmap and the security notes agree with the auditor network notes and the Slither record (#7) 2026-09-18
• Make the audit deadline hard, gate team vesting on the launch settling, and give the registry a read with both clocks (#6) 2026-09-18

How it is backed

Source linked

Counts toward building

Yes. It is one of the records HEY’s activity status is built from.

Records behind it

• Github repo, read 2026-09-17 ↗

What it does not say

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.