Skip to content
HEY Research Lab
Menu

Teller Protocol v2

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

What HEY knows

Development

Last shipped 35 days agoActive: 0 counted ships in 30 days; latest ship 35 days ago. Evidence Source

Build Momentum 18How it is measured

Latest: Code changes, week of 2026-09-21 – 2026-09-27 · 43 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Teller Protocol v2 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 Teller Protocol v2

No account? Email me Teller Protocol v2’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: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own.
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's longer window: 2 counted ships in the last 45 days (the rule needs at least 2); the newest, 2026-09-27, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 43 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 52 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".
Research coverage: HEY can answer 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 47d ago.

Building

  • Building activityMeasuredRead 22h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 7d ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 7d ago.

Code and packages

  • Repository detailsMeasuredRead 4d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

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)X (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-21 – 2026-09-27 · 43 commits

Code activitySource-backed

What changed, in the repository’s own words:

5 active days in teller-protocol/teller-protocol-v2.

This week HEY looked inside 5 of 43 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:8379cf6e… · HEY counts it as building; it does not judge the release’s quality.

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-09-14 – 2026-09-20 · at least 52 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 3 active days in teller-protocol/teller-protocol-v2 since 2026-09-17; the count stops at the newest 100 commits listed.

    How HEY read this week

    This week HEY looked inside 1 of 22 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-14 – 2026-09-20 · at least 52 commits (opens in a new tab)

Other changes on HEY’s record

6 changes on HEY’s record for Teller Protocol v2: 1 new Verified Builder or owner proof · 3 official source changes · 2 weeks of code pushed.

All 6 changes for Teller Protocol v2 →

The full change record holds 63 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 Teller Protocol v2 — as of 1 Nov

Show the answers
Is Teller Protocol v2 still being built?
DerivedActive: 0 counted ships in 30 days; latest ship 35 days ago. Evidence
What did Teller Protocol v2 ship last?
FactCode changes, week of 2026-09-21 – 2026-09-27 · 43 commits — Code activity, 35 days ago. Evidence
What does HEY not know about Teller Protocol v2?
Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own.

Sources

64 places HEY reads for Teller Protocol v2
59 more sources (docs)