Skip to content

glueHook

No narrative yet

Is this your project? Claim and verify →

Uniswap V4 general purposes hook for automated LP compounding and buy back

What HEY knows

Building
Last shipped 2 days agoShipping: 1 meaningful event in 30 days; latest ship 2 days ago. Evidence Source

Build Momentum 28How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit · · Code activity

Why it matters: First week of code changes after 30 quiet days.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts glueHook 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 glueHook’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.

Product usage

GlueHook: TVL $3.7K · fees 24h not tracked · revenue 24h not tracked (DefiLlama, 2026-10-19). Registry context, not a measure of building.

Token market · context
No token tracked
Not yet known
Unknown2 gaps: API description (no source), Protocol economics (no source). Its website links no API description.

HEY can answer 9 of the 11 research questions that apply · Research coverage

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: 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, week of 2026-10-12 – 2026-10-18 · 1 commitCode changes, week of 2026-09-14 – 2026-09-20 · 17 commitsCode changes, week of 2026-08-24 – 2026-08-30 · at least 1 commitWhat 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.
Source14 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 1 commitCode changes, week of 2026-09-14 – 2026-09-20 · 17 commitsCode changes, week of 2026-08-24 – 2026-08-30 · at least 1 commit+5 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.
Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit

Code activitySource linked

1 active day in glue-finance/gluehook.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

Record ship:0ce72030… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

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

Questions HEY can answer about glueHook — as of 2026-10-19

Is glueHook still being built?
DerivedShipping: 1 meaningful event in 30 days; latest ship 2 days ago. Evidence
What did glueHook ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 1 commit — Code activity, 2 days ago. Evidence
What does HEY not know about glueHook?
Unknown2 gaps: API description (no source), Protocol economics (no source). Its website links no API description. Details

Build timeline

  1. Code changes, week of 2026-09-14 – 2026-09-20 · 17 commits

    Code activitySource linked

    4 active days in glue-finance/gluehook.

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

  2. Code changes, week of 2026-08-24 – 2026-08-30 · at least 1 commit

    Code activitySource linked

    What changed, in the repository’s own words:

    4 active days in glue-finance/glueHook.

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about glueHook? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

3 changes on HEY’s record for glueHook: 3 weeks of code pushed.

glueHook on What changed →

The full change record holds 11 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 9 of the 11 research questions that apply.

9 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

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

Official site

  • Official docsMeasuredRead 7m ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 13h ago.

Code and packages

  • Repository detailsMeasuredRead 19h ago.
  • Published packagesMeasuredRead 19h ago.

Protocol economics

  • Protocol economicsNo sourceDefiLlama lists the protocol but tracks no fees, revenue or volume for it.

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

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.

Sources

8 more sources (docs)

Security context: 1 audit report found. An audit shows an audit took place; it is not a guarantee of safety.