Code changes this week (since Mon 26 Oct) · 62 commits

What it is: Code activity
Where HEY read it: GitHub · Commits that week ↗ · Repository ↗
When it happened: In the week of Mon 2026-10-26 – Sun 2026-11-01 (UTC), dated by the source to the week
HEY first saw it: 2026-11-01 (5h 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: 62 commits that week, not counting automation or merges.
fix(contracts): pay each side of a VOID on its own and revert relayed no-ops 2026-10-30
test(app): keeper, price watcher and indexer on a private anvil (end to end, shadow parity, refund fallback, reorg) and env docs 2026-10-30
feat(escrow): launch cap on new entries, handler-based invariants 2026-10-30
How it is backed: Source-backed
Counts toward building: Yes. It is one of the records HEY’s activity status is built from.
Records behind it: Github repo, read 2026-11-01 ↗
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.

Follow ifso to see the next change HEY records, with its evidence.

Cite this

Absolute dates in UTC and a link that does not move.

ifso: Code changes, week starting 2026-10-26 (to 2026-11-01) · 62 commits
Happened: in the week 2026-10-26 to 2026-11-01 (UTC)
Source: GitHub, https://github.com/ifsodev/ifso/commits?since=2026-10-26T00%3A00%3A00.000Z&until=2026-11-02T00%3A00%3A00.000Z
Recorded by HEY Research Lab: 2026-11-01 (UTC); accessed 2026-11-01 (UTC)
Evidence ship:f5a94d60-8fa1-48b5-8f73-720c2d5fddc7: https://heyresearch.xyz/evidence/ship:f5a94d60-8fa1-48b5-8f73-720c2d5fddc7
  Receipt: https://heyresearch.xyz/api/evidence/ship%3Af5a94d60-8fa1-48b5-8f73-720c2d5fddc7

Evidence id ship:f5a94d60-8fa1-48b5-8f73-720c2d5fddc7As data How HEY works