Skip to content
HEY Research Lab
Menu

aesop

Is this your project? Claim it →

Collects and reinvests Fables liquidity fees on Robinhood Chain, executed by KeeperHub

What HEY knows

Development

Quiet for 46 daysQuiet: 0 counted ships in 30 days; latest ship on 2026-09-17. Evidence Source

Build Momentum 0How it is measured

Latest: Code changes, week of 2026-09-14 – 2026-09-20 · 8 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me aesop’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
More detail
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
Quiet.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-09-17.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 8 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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.
Source2 registered sources, 1 of them context only.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 8 commitssource:95bfdc06-b740-4f3d-8671-89b29824a47cWhat 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 21h 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 5d ago.
  • Published packagesMeasuredRead 5d 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
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-14 – 2026-09-20 · 8 commits

Code activitySource-backed

Why it matters: The first week of code changes HEY has recorded for this project.

What changed, in the repository’s own words:

1 active day in imprint-hash/aesop.

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

Record ship:45bd18df… · 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 2 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-09-17; HEY first knew on 2026-09-18. HEY indexed it later, as history.
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)

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

What changed

2 changes on HEY’s record for aesop: 1 new Verified Builder or owner proof · 1 week of code pushed.

All 2 changes for aesop →

The full change record holds 1 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 aesop — as of 2 Nov

Show the answers
Is aesop still being built?
DerivedQuiet: 0 counted ships in 30 days; latest ship on 2026-09-17. Evidence
What did aesop ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · 8 commits — Code activity, on 2026-09-17. Evidence
What does HEY not know about aesop?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

Sources

2 places HEY reads for aesop
  • Repository
    https://github.com/imprint-hash/aesopOfficial
  • Repository
    https://github.com/imprint-hash/talosContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).