Code changes this week (since Mon 26 Oct) · 9 commits
Code activitySource-backed
Why it matters: The first week of code changes HEY has recorded for this project.
What changed, in the repository’s own words:
- snapshot.sh: resume from the file's real size (curl --retry restarted a part from 0); HTTP/1.1, stall timeout; drop a leftover app name…
- v2 token card: refuse (503) when the holder count isn't exact, instead of holders_count null
- M6 prep: nitro service (profile node), tuned for a 16 GB box; official chain config files
1 active day in robert-schmidt/rhnode.
This week HEY looked inside 1 of 9 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
Record ship:e44c8f3b… · HEY counts it as building; it does not judge the release’s quality.
Code changes, read from the team’s GitHub · not a deployment
- What it names
- 1 of 1 commit HEY read changed code. A week of code names no capability.
- Stage
- Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
- Reported by
- Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
- Release and deployment
- Not a release or a deployment: code is not a deployment.
- Activity
- No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
- When
- The source dates it to the week of 2026-10-29; HEY first knew on 2026-10-30.
- Not known
- No source HEY holds names what this change does.
- HEY has not observed a deployment of this change.
Evidence: ship record
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.