Skip to content
HEY Research Lab
Menu

afterhours

StockFi

Is this your project? Claim it →

AfterHours: onchain weekend-gap protection for Robinhood Chain Stock Tokens. Stylus-priced puts, ERC-4626 writer vaults. Arbitrum Open House Singapore 2026.

What HEY knows

Development

Last shipped 29 days agoActive: 1 counted ship in 30 days; latest ship 29 days ago. Evidence Source

Build Momentum 23How it is measured

Latest: Code changes, week of 2026-09-28 – 2026-10-04 · 16 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts afterhours on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow afterhours

No account? Email me afterhours’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

View latest ship
Share
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 1 counted ship in the last 30 days, the newest 2026-09-30.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 16 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 3 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 15 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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, week of 2026-09-28 – 2026-10-04 · 16 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 3 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 15 commits+1 moreWhat 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.
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 19m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 2d ago.
  • Published packagesMeasuredRead 2d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-28 – 2026-10-04 · 16 commits

Code activitySource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

What changed, in the repository’s own words:

2 active days in bchuazw/afterhours.

This week HEY looked inside 1 of 16 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:5927f87d… · 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-09-30; HEY first knew on 2026-09-29.
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.

View evidence ↗ (opens in a new tab)

Shared change · Verified Builder

afterhours is now a verified builder: HEY verified its builder sources.

1 meaningful development event was recorded in the last 30 days. Builder status: Active.

Observed by HEY on 2026-09-15Source: HEY Signal

View evidence ↗Evidence receipt

Builder activity

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: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-09-21 – 2026-09-27 · 3 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in bchuazw/afterhours.

    How HEY read this week

    This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 3 commits (opens in a new tab)

  2. Code changes, week of 2026-09-14 – 2026-09-20 · at least 15 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in bchuazw/afterhours.

    How HEY read this week

    This week HEY looked inside 2 of 15 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.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 15 commits (opens in a new tab)

Other changes on HEY’s record

4 changes on HEY’s record for afterhours: 1 verification change · 3 weeks of code pushed.

All 4 changes for afterhours →

The full change record holds 2 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Questions HEY can answer about afterhours — as of 29 Oct

Show the answers
Is afterhours still being built?
DerivedActive: 1 counted ship in 30 days; latest ship 29 days ago. Evidence
What did afterhours ship last?
FactCode changes, week of 2026-09-28 – 2026-10-04 · 16 commits — Code activity, 29 days ago. Evidence
What does HEY not know about afterhours?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

Sources

1 place HEY reads for afterhours