Follow puts Lincoln Protocol Core on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
No account? Email me Lincoln Protocol Core’s changes
“Shipping” by the activity rule: 1 meaningful event in the last 30 days, the newest 2026-10-17.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 12 Oct) · 25 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source1 registered source, 0 of them context only.ReadRecordsCode changes this week (since Mon 12 Oct) · 25 commitssource:cac441ce-14d8-4a35-9cff-065a1b5e8769What HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
1 active day in lincolnprotocol-com/lincoln-protocol-core.
This week HEY looked inside 4 of 25 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.
Record ship:8a34e6d5… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 11 weeks before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about Lincoln Protocol Core — as of 2026-10-18