Skip to content
HEY Research Lab
Menu

Tegridy Farms

DEX

Is this your project? Claim it →

What HEY knows

Development

Shipping consistentlyShipping: 5 counted ships in 30 days; latest ship today. Evidence Source

Build Momentum 53How it is measured

Latest: Code changes this week (since Mon 26 Oct) · 75 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Tegridy Farms 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 Tegridy Farms

No account? Email me Tegridy Farms’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
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: 5 counted ships in the last 30 days, the newest 2026-11-01.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 75 commitsCode changes, week of 2026-10-19 – 2026-10-25 · at least 258 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 202 commits+2 moreWhat 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.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 26 Oct) · 75 commitsCode changes, week of 2026-10-19 – 2026-10-25 · at least 258 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 202 commits+3 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 45d 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 2d ago.

Code and packages

  • Repository detailsMeasuredRead 2d ago.
  • Published packagesMeasuredRead 2d 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
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 26 Oct) · 75 commits

Code activitySource-backed

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

What changed, in the repository’s own words:

7 active days in fomotsar-commits/tegridy-farms.

This week HEY looked inside 3 of 75 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

Record ship:adc00919… · 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 3 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-01; HEY first knew on 2026-10-28.
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: 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-10-19 – 2026-10-25 · at least 258 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 6 active days in fomotsar-commits/tegridy-farms since 2026-10-20; the count stops at the newest 100 commits listed.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · at least 258 commits (opens in a new tab)

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 202 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in fomotsar-commits/tegridy-farms.

    How HEY read this week

    This week HEY looked inside 3 of 202 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 202 commits (opens in a new tab)

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 142 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    4 active days in fomotsar-commits/tegridy-farms.

    How HEY read this week

    This week HEY looked inside 3 of 142 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 142 commits (opens in a new tab)

  4. Code changes, week of 2026-09-28 – 2026-10-04 · at least 331 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 5 active days in fomotsar-commits/tegridy-farms since 2026-09-30; the count stops at the newest 100 commits listed.

    How HEY read this week

    This week HEY looked inside 5 of 331 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.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · at least 331 commits (opens in a new tab)

  5. Code changes, week of 2026-09-21 – 2026-09-27 · at least 96 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in fomotsar-commits/tegridy-farms.

    How HEY read this week

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

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

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

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 5 active days in fomotsar-commits/tegridy-farms since 2026-09-16; the count stops at the newest 100 commits listed.

    How HEY read this week

    This week HEY looked inside 3 of 122 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 9 automated commits (bot accounts or a repeating scripted message) not counted.

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

Questions HEY can answer about Tegridy Farms — as of 1 Nov

Show the answers
Is Tegridy Farms still being built?
DerivedShipping: 5 counted ships in 30 days; latest ship today. Evidence
What did Tegridy Farms ship last?
FactCode changes this week (since Mon 26 Oct) · 75 commits — Code activity, today. Evidence
What does HEY not know about Tegridy Farms?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

Sources

2 places HEY reads for Tegridy Farms