Follow puts PingApp on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
Building and market attention rank about level among comparable projects: 97 of 100 for building, 84.6 of 100 for market attention (a gap of 12.4). What the Discovery Gap is
It compares building with market attention; it is not a prediction and not a reason to trade.
Product usage
UnknownThe project has a contract, but HEY does not count its calls yet: a token joins the watch once it takes calls in a thirty-day window, and any contract the project’s own sources name is watched. Unknown, not zero.
Contracts
Fact1 contract on record for code changes, 1 with verified source; no implementation or interface change recorded.
Token market · context
Active market$99K fully diluted valuationToken verified
Not yet known
Unknown4 gaps: Official docs (no source), API description (no source), Market history (not enough yet), Supply distribution (not enough yet). HEY read its website and found no link to docs.
“Shipping” by the activity rule: 2 meaningful events in the last 30 days, the newest 2026-10-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 19 Oct) · 48 commits0.1.0What 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.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 19 Oct) · 48 commits0.1.0source:022d32e0-58ae-49be-a73f-3d7b6f467e3e+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.
Token verified.
Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source4 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology
This week HEY looked inside 3 of 48 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:e094c71e… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
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: 10 weeks before HEY began reading this project’s sources — not yet read, not zero.
Questions HEY can answer about PingApp — as of 2026-10-19
Is 0xFFB390e5B6136704905E2635afC3E5150E768a26 PingApp’s own contract?
FactToken verified: The project’s own site names this contract.Details →
What does HEY not know about PingApp?
Unknown4 gaps: Official docs (no source), API description (no source), Market history (not enough yet), +1 more. HEY read its website and found no link to docs.Details →