Shilin v2 · 7 days + 72h & three-chain Registry
GitHub releaseSource-backed
Why it matters: First release after 43 quiet days.
Complete frozen evidence for Shilin v2, provided as one inputs.tar.gz archive. No evidence-part assembly is required. The shilin_v2 branch contains all 21 logical CSV tables: the original six-table 7day+72h cohort and all 15 P3 v6 tables, with curated source, tests, protocols… Show allShow less
- Complete frozen evidence for Shilin v2, provided as one inputs.tar.gz archive. No evidence-part assembly is required. The shilin_v2 branch contains all 21 logical CSV tables: the original six-table 7day+72h cohort and all 15 P3 v6 tables, with curated source, tests, protocols, dictionaries and the five-panel gallery. The evidence archive preserves raw public API responses, normalized native chain records, upstream tables, coverage/QA evidence and locked ABI dependencies. It is optional for table analysis and required for the full independent reconstruction.
- Creation window…
Record ship:14d71f08… · HEY counts it as building; it does not judge the release’s quality.
Release, read from the team’s GitHub · no deployment linked
- What it names
- The team’s release names it: “Shilin v2 · 7 days + 72h & three-chain Registry” (shilin-v2-20261029).
- Stage
- A release is code the team published; HEY has not observed it deployed unless a link below says so.
- 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 established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to 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 2026-10-29 06:38 UTC; HEY first knew on 2026-10-29.
- Not known
- HEY does not hold the commit the release was cut from.
- HEY has not observed a deployment of this change.
- Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
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.