Evidence · Building

Code changes, week of 2026-10-12 – 2026-10-18 · 2 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-12 – Sun 2026-10-18 (UTC), dated by the source to the week
HEY first saw it: 2026-10-15 (4d 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: 2 commits that week, not counting automation or merges.
add treasury version argument 2026-10-14
near: fix token transfers to new addresses 2026-10-14
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-10-15 ↗
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 cordialsys to see the next change HEY records, with its evidence.

Cite this

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

cordialsys: Code changes, week of 2026-10-12 – 2026-10-18 · 2 commits
Happened: in the week 2026-10-12 to 2026-10-18 (UTC)
Source: GitHub, https://github.com/cordialsys/crosschain/commits?since=2026-10-12T00%3A00%3A00.000Z&until=2026-10-19T00%3A00%3A00.000Z
Recorded by HEY Research: 2026-10-15 (UTC); accessed 2026-10-19 (UTC)
Evidence ship:3c26068e-e703-4625-be8b-5e41f2794b04: https://heyresearch.xyz/evidence/ship:3c26068e-e703-4625-be8b-5e41f2794b04
  Receipt: https://heyresearch.xyz/api/evidence/ship%3A3c26068e-e703-4625-be8b-5e41f2794b04

Evidence id ship:3c26068e-e703-4625-be8b-5e41f2794b04As data How HEY works