Integration record: a multichain project that lists Robinhood Chain. Its code is filed under other ecosystems and HEY holds no Robinhood Chain evidence of its own, so its ships are recorded here but it is not a Verified Builder.
Follow puts Dev Portal on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
This week HEY looked inside 1 of 14 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 4 automated commits (bot accounts or a repeating scripted message) not counted.
Record ship:87a42af4… · 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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about Dev Portal — as of 2026-10-19
Is Dev Portal still being built?
DerivedShipping: 4 meaningful events in 30 days; latest ship 2 days ago.Evidence →
What did Dev Portal ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 14 commits — Code activity, 2 days ago.Evidence →
What does HEY not know about Dev Portal?
Unknown1 gap: API description (not enough yet). HEY has not read its website’s published files yet.Details →
Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.
This week HEY looked inside 7 of 31 commits to see what changed: 3 changed code, 4 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 5 automated commits (bot accounts or a repeating scripted message) not counted.
Mostly maintenance or automation — not counted as building. A burst of 33 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 10 of 33 commits to see what changed: 1 changed code, 9 documentation or maintenance only. 4 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 7 of 24 commits to see what changed: 1 changed code, 6 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 1 automated commit (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 1 of 11 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 2 automated commits (bot accounts or a repeating scripted message) not counted.
Code changes, week of 2026-09-07 – 2026-09-13 · at least 4 commits
Code activity · Source linked
24 active days in chainstack/dev-portal.
This week HEY looked inside 2 of 4 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 2 automated commits (bot accounts or a repeating scripted message) not counted.
Code changes, week of 2026-08-31 – 2026-09-06 · at least 11 commits
Code activity · Source linked
25 active days in chainstack/dev-portal.
This week HEY looked inside 3 of 11 commits to see what changed: 1 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 2 automated commits (bot accounts or a repeating scripted message) not counted.
https://docs.chainstack.com/sitemap.xmlContext onlyContext only: shown for background and not counted as this project’s evidence.HEY lost access 17d ago; nothing has been read since.
HEY keeps these on record as context. None counts toward the activity status or Build Momentum; each says why.
AnnouncementChainstack updates: September 30, 20262026-10-09Recorded, not counted: the same entry, published again under a new id, is already on the timeline.
AnnouncementChainstack updates: October 7, 20262026-10-08Recorded, not counted: the same entry, published again under a new id, is already on the timeline.
