Evidence · Building
Code changes, week of 2026-10-05 – 2026-10-11 · 6 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-05 – Sun 2026-10-11 (UTC), dated by the source to the week
- HEY first saw it
- (2h 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
- 6 commits that week, not counting automation or merges.
- ci: the stock checks run without the SDK; the Vault per chain is vaults.json 2026-10-11
- README: a Features section; lists unchanged (56 v1.1.0, 4663 v2.1.0, 8453 v2.1.0, 999 v1.1.0) 2026-10-11
- lists: 56 v1.1.0 (75 tokens), 4663 v2.1.0 (10 tokens), 8453 v2.1.0 (25 tokens), 999 v1.1.0 (16 tokens) 2026-10-10
- 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-12 ↗
- 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.
Cite this
Absolute dates in UTC and a link that does not move.
deep-core-protocol: Code changes, week of 2026-10-05 – 2026-10-11 · 6 commits
Happened: in the week 2026-10-05 to 2026-10-11 (UTC)
Source: GitHub, https://github.com/deep-core-protocol/token-list/commits?since=2026-10-05T00%3A00%3A00.000Z&until=2026-10-12T00%3A00%3A00.000Z
Recorded by HEY Research: 2026-10-12 (UTC); accessed 2026-10-12 (UTC)
Evidence ship:4cbac2a6-0fd2-435e-b47a-fd61f64e7086: https://heyresearch.xyz/evidence/ship:4cbac2a6-0fd2-435e-b47a-fd61f64e7086
Receipt: https://heyresearch.xyz/api/evidence/ship%3A4cbac2a6-0fd2-435e-b47a-fd61f64e7086Follow deep-core-protocol to see the next change HEY records, with its evidence.
Evidence id ship:4cbac2a6-0fd2-435e-b47a-fd61f64e7086As dataHow HEY works