Skip to content

LATCHES

$LATCHES

DEX · Utility

Not named by the project: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Token market

Contract 0x90e87b1c68a17f10403b7704e0b9fdaad3036738

HEY holds 6 other Robinhood Chain tokens with the ticker $LATCHES. This page is only the contract above. See them

Is this your project? Claim it →

Deploy your own Launchpad or Dex.

What HEY knows

Development

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

Build Momentum 0How it is measured

Latest: Code changes, week of 2026-09-28 – 2026-10-04 · 2 commits

Token market · context

Low liquidity

Token check

Not named by the project
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

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

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

Attention
Discovery Gap not measured — 24h volume under $1,000. What the Discovery Gap is
More detail
Product usage
Fact1 of 1 watched contract active · 4 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.

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

Latch Protocol: TVL <$1 · fees 24h $0 · revenue 24h $0 (DefiLlama, 2026-11-16). Registry context, not a measure of building.

Contracts
Fact1 contract on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown4 gaps: Published packages (not enough yet), Official docs (not tied to the project yet), API description (not tied to the project yet), Official site changes (not tied to the project yet). 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
Quiet.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-10-01.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 2 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 2 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 11 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.
Source8 registered sources, 3 of them context only.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 2 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 2 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 11 commits+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.
Not named by the project.
Not named by the project: HEY has not confirmed that the project stands behind this contract — HEY knows it from a launchpad record, and the site that record named does not name it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedNot named by the project: HEY knows it from a launchpad record, and the site that record named does not name it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Low liquidity.
Low liquidity: the pool holds less than $5,000 of liquidity.
Source8 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Low liquidity”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Discovery Gap: Not measured — 24h volume under $1,000.
Not measured — market too thin: the tracked token's market reads “Low liquidity” but traded $0 in the 24 hours of its reading, under the $1,000 a measured market needs. A Discovery Gap is measured only on an active market that is more than a launch curve and trades at least $1,000 a day: a thin market's attention percentile sits near the floor, so its gap would measure the thinness, not the building.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — market too thin.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 16 of the 20 research questions that apply.
16 of 20 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

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

Official site

  • Official docsNot tied to the project yetOnly docs others link to; none the project publishes itself.
  • API descriptionNot tied to the project yetIts website is not yet confirmed as the project’s own.
  • Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.

Code and packages

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

Contracts

  • Contract creationMeasuredRead 2d ago.
  • Contract activityMeasuredRead 2d ago.
  • Published source codeMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 3h ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 8d ago.
  • LocksMeasuredRead 2m ago.
  • Market checksMeasured

Protocol economics

  • Protocol economicsMeasuredRead today.

Not applicable here: Package advisories.

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, week of 2026-09-28 – 2026-10-04 · 2 commits latch-protocol-team/latch-sdk

Code activitySource-backed

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

1 active day in latch-protocol-team/latch-sdk.

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

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

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit 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-10-01; HEY first knew on 2026-10-01. 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.

Shared change · Verified Builder

LATCHES is now a Verified Builder: HEY checked its builder sources.

Builder status: Quiet.

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

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: a week 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-28 – 2026-10-04 · 2 commits latch-protocol-team/dex-tokenl-list

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in latch-protocol-team/dex-tokenl-list.

    How HEY read this week

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits latch-protocol-team/latch-sdk

    Code activitySource-backed

    2 active days in latch-protocol-team/latch-sdk.

    How HEY read this week

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

  3. Code changes, week of 2026-09-07 – 2026-09-13 · at least 11 commits latch-protocol-team/latch-sdk

    Code activitySource-backed

    2 active days in latch-protocol-team/latch-sdk.

    How HEY read this week

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

Other changes on HEY’s record

12 changes on HEY’s record for LATCHES: 1 new Verified Builder or owner proof · 1 new project on HEY · 6 market moves · 4 weeks of code pushed.

All 12 changes for LATCHES →

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

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0x90E87B1C68A17F10403B7704E0b9FDaaD3036738 on Robinhood Chain

0x90e8…67380x90e87b1c68a17f10403b7704e0b9fdaad3036738

Not named by the project.

Market context

Low liquidity · FDV (fully diluted) $2K · current liquidity $3.5K · reading 3 h old (GeckoTerminal).

Token

Launch stage
Trading in a DEX pool
Pair age
46d ago

Market

24h volume
$0
Trades 24h
0 buys · 0 sells
Price 24h
unchanged over 24 hours· 6hunchanged over 6 hours· 1hunchanged over 1 hour

The tracked token has a small pool. Trades move the price a lot.

Market history, trading and checks →

Market integrity

Liquidity is 82% below the level it held two days running ($19.5K, 2026-10-05).

Market
Low liquidity
Last day with trading
2026-11-14

Liquidity is under 25% of the level it held, on two consecutive daily readings to 2026-11-16.

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-11-16 12:50 UTC · How HEY checks this

Sources

8 places HEY reads for LATCHES