Skip to content

QTimelineHook

Perps

Is this your project? Claim it →

What HEY knows

Development

Shipped this weekShipping: 2 counted ships in 30 days; latest ship today. Evidence Source

Build Momentum 33How it is measured

Latest: Code changes this week (since Mon 16 Nov) · 42 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts QTimelineHook 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 QTimelineHook

No account? Email me QTimelineHook’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.

More detail
Product usage
Fact4 of 5 watched contracts active · 35 calls over the 3 of 7 days HEY holds; the rest unknown, not zero.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

Contracts
Fact5 contracts on record for code changes, 4 behind a proxy; no implementation or interface change recorded.
Not yet known
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 2 counted ships in the last 30 days, the newest 2026-11-18.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 16 Nov) · 42 commitsCode changes, week of 2026-11-09 – 2026-11-15 · 49 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 counted building from the project's own sources.
Source8 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 16 Nov) · 42 commitsCode changes, week of 2026-11-09 – 2026-11-15 · 49 commitssource:a754e338-aec9-4785-8eac-df0aaae047cc+4 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 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 3d ago.

Building

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

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 49m ago.

Code and packages

  • Repository detailsMeasuredRead 49m ago.
  • Published packagesMeasuredRead 49m ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, 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

Latest ship

Checked

Code changes this week (since Mon 16 Nov) · 42 commits

Code activitySource-backed

3 active days in quantum-timeline/qtimelinehook.

This week HEY looked inside 5 of 42 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

Record ship:ca2b51fa… · 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
3 of 5 commits 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-11-18; HEY first knew on 2026-11-18.
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.

Shared change · Published

QTimelineHook was published on HEY with its sources recorded.

Builder status: Shipping.

Observed by HEY on 2026-11-18Source: HEY’s research record

Builder activity

2 meaningful, source-backed ships in the 2 weeks since HEY began reading this project’s sources; earlier weeks are not yet read, not zero.

2-week shipping streak

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-11-09 – 2026-11-15 · 49 commits

    Code activitySource-backed

    1 active day in quantum-timeline/qtimelinehook.

    How HEY read this week

    This week HEY looked inside 4 of 49 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.

Other changes on HEY’s record

3 changes on HEY’s record for QTimelineHook: 1 new project on HEY · 2 weeks of code pushed.

All 3 changes for QTimelineHook →

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

Sources

8 places HEY reads for QTimelineHook

1 Uniswap v4 hook instance made by its factory · Builders shipping Uniswap v4 hooks